-
Notifications
You must be signed in to change notification settings - Fork 72
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New-control-panel-in-spec2 #1155
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Very cool!
One thing only: for me the icon in the menu is missing.
This is weird because I have the icon and I don't see what might be the problem :( |
The icon isn't being properly registered. The method on |
Should be fixes |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Prefect, thanks!
This causes the Squeak builds to fail because we send |
repository/BaselineOfSeaside3.package/GRPlatform.extension/instance/pharoVersionsFrom..st
Outdated
Show resolved
Hide resolved
I'm trying to recover these changes and get them into master. I never investigated in detail but always thought the PR was blocked with requested changes... I have the impression they have been resolved...? |
|
||
spec | ||
for: (GRPlatform current pharoVersionsFrom: 8) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
shouldn't this be self pharoVersionsFrom: 8
?
(not sure if I like this way, but for sure it's where the travis builds fail on...)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jecisc if possible, could you just change it to pharo8
? I prefer to manually update for new versions rather than trying to figure out later on if some package should have a self pharoVersionsBetween: xx and: yy
method :)
I forgot I can very easily complete this myself by merging it into another branch first and make the necessary changes. Going ahead with that. |
Hi @jbrichau For info: When I do a PR I let the maintainers of the projects edit my PR. This means that you can checkout my branch, change it and push directly on the branch in my fork and it will update the current PR without the need of creating a new one. |
@jecisc I did not try to see if I could write to your branch, so the easiest for me was to quickly pull it into another branch. I don't know if you have seen that before and what the best way to prevent it is? (it's the same issue as raised by Max before) |
Introduce a new Control panel in Spec 2 for Pharo 8 +