Skip to content
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

Merged
merged 5 commits into from
Jul 12, 2020
Merged

Conversation

jecisc
Copy link
Member

@jecisc jecisc commented Aug 26, 2019

Introduce a new Control panel in Spec 2 for Pharo 8 +

@jecisc jecisc changed the base branch from master to develop August 26, 2019 10:01
Copy link
Member

@theseion theseion left a 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.

@jecisc
Copy link
Member Author

jecisc commented Aug 28, 2019

This is weird because I have the icon and I don't see what might be the problem :(

@theseion
Copy link
Member

The icon isn't being properly registered. The method on ThemeIcons is never executed.

@jecisc
Copy link
Member Author

jecisc commented Aug 28, 2019

Should be fixes

theseion
theseion previously approved these changes Aug 28, 2019
Copy link
Member

@theseion theseion left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Prefect, thanks!

@marschall
Copy link
Contributor

This causes the Squeak builds to fail because we send SystemVersion>>major

@jbrichau jbrichau changed the base branch from develop to master July 11, 2020 09:19
@jbrichau jbrichau dismissed theseion’s stale review July 11, 2020 09:19

The base branch was changed.

@jbrichau
Copy link
Member

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)
Copy link
Member

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...)

Copy link
Member

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 :)

@jbrichau jbrichau changed the base branch from master to spec2 July 12, 2020 07:53
@jbrichau
Copy link
Member

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.

@jbrichau jbrichau merged commit fb9f5a8 into SeasideSt:spec2 Jul 12, 2020
@jecisc
Copy link
Member Author

jecisc commented Jul 15, 2020

Hi @jbrichau
Thank you for taking care of that! Was a little busy this week end and you were faster than me to update the baseline :)

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.

@jbrichau
Copy link
Member

@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.
There still is an issue though: #1214 (comment)

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)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants