Why? Just curious..
On Thu, Aug 27, 2015 at 7:04 PM, commits@source.squeak.org wrote:
Eliot Miranda uploaded a new version of Morphic to project The Trunk: http://source.squeak.org/trunk/Morphic-eem.1002.mcz
==================== Summary ====================
Name: Morphic-eem.1002 Author: eem Time: 27 August 2015, 5:03:26.429 pm UUID: d94fff6d-5fef-4500-9144-4dc8bfa1510e Ancestors: Morphic-mt.1001
It's really convenient to be able to identify MenuItemMorphs easily.
=============== Diff against Morphic-mt.1001 ===============
Item was added:
- ----- Method: MenuItemMorph>>isMenuItemMorph (in category 'testing') -----
- isMenuItemMorph
^true!Item was added:
- ----- Method: Morph>>isMenuItemMorph (in category 'testing') -----
- isMenuItemMorph
^false!
Hi Chris,
I wanted to add a "delete all Monticello load change sets" menu pick to the change set sorter, but because menu pragmas are not right yet the only way to add a menu item next to another is to edit the menu using removeMorph: and addMorph:after: (instead of defining order in the menu pragma itself). And I can't stomach isKindOf: or isMemberOf:/class to distinguish MenuItemMorphs from MenuLineMorphs.
Sent from my iPhone
On Aug 28, 2015, at 8:23 AM, Chris Muller asqueaker@gmail.com wrote:
Why? Just curious..
On Thu, Aug 27, 2015 at 7:04 PM, commits@source.squeak.org wrote: Eliot Miranda uploaded a new version of Morphic to project The Trunk: http://source.squeak.org/trunk/Morphic-eem.1002.mcz
==================== Summary ====================
Name: Morphic-eem.1002 Author: eem Time: 27 August 2015, 5:03:26.429 pm UUID: d94fff6d-5fef-4500-9144-4dc8bfa1510e Ancestors: Morphic-mt.1001
It's really convenient to be able to identify MenuItemMorphs easily.
=============== Diff against Morphic-mt.1001 ===============
Item was added:
- ----- Method: MenuItemMorph>>isMenuItemMorph (in category 'testing') -----
- isMenuItemMorph
^true!Item was added:
- ----- Method: Morph>>isMenuItemMorph (in category 'testing') -----
- isMenuItemMorph
^false!
On 28.08.2015, at 18:15, Eliot Miranda eliot.miranda@gmail.com wrote:
Hi Chris,
I wanted to add a "delete all Monticello load change sets" menu pick to the change set sorter, but because menu pragmas are not right yet the only way to add a menu item next to another is to edit the menu using removeMorph: and addMorph:after: (instead of defining order in the menu pragma itself).
Huh? Then I've done something wrong. With <menuPriority: aNumber> you can define an order, and if the order is adjacent, menu items should show up adjacent :(.
I'll look into that
best -tobias
And I can't stomach isKindOf: or isMemberOf:/class to distinguish MenuItemMorphs from MenuLineMorphs.
Sent from my iPhone
On Aug 28, 2015, at 8:23 AM, Chris Muller asqueaker@gmail.com wrote:
Why? Just curious..
On Thu, Aug 27, 2015 at 7:04 PM, commits@source.squeak.org wrote: Eliot Miranda uploaded a new version of Morphic to project The Trunk: http://source.squeak.org/trunk/Morphic-eem.1002.mcz
==================== Summary ====================
Name: Morphic-eem.1002 Author: eem Time: 27 August 2015, 5:03:26.429 pm UUID: d94fff6d-5fef-4500-9144-4dc8bfa1510e Ancestors: Morphic-mt.1001
It's really convenient to be able to identify MenuItemMorphs easily.
=============== Diff against Morphic-mt.1001 ===============
Item was added:
- ----- Method: MenuItemMorph>>isMenuItemMorph (in category 'testing') -----
- isMenuItemMorph
^true!Item was added:
- ----- Method: Morph>>isMenuItemMorph (in category 'testing') -----
- isMenuItemMorph
^false!
Hi Tobias,
On Fri, Aug 28, 2015 at 9:56 AM, Tobias Pape Das.Linux@gmx.de wrote:
On 28.08.2015, at 18:15, Eliot Miranda eliot.miranda@gmail.com wrote:
Hi Chris,
I wanted to add a "delete all Monticello load change sets" menu pick
to the change set sorter, but because menu pragmas are not right yet the only way to add a menu item next to another is to edit the menu using removeMorph: and addMorph:after: (instead of defining order in the menu pragma itself).
Huh? Then I've done something wrong. With <menuPriority: aNumber> you can define an order, and if the order is adjacent, menu items should show up adjacent :(.
Then I've probably misunderstood how the scheme should work. Or perhaps the implementation in ChangeSorter is an early one. Anyway, take a look at my attempt to add a single item next to the 'destroy change set (x)' item in ChangeSorter that is in Monticello-eem.617. My intent is to add 'delete Monticello load change sets' after 'destroy change set (x)'.
I'll look into that
best -tobias
And I can't stomach isKindOf: or isMemberOf:/class to distinguish
MenuItemMorphs from MenuLineMorphs.
Sent from my iPhone
On Aug 28, 2015, at 8:23 AM, Chris Muller asqueaker@gmail.com wrote:
Why? Just curious..
On Thu, Aug 27, 2015 at 7:04 PM, commits@source.squeak.org wrote: Eliot Miranda uploaded a new version of Morphic to project The Trunk: http://source.squeak.org/trunk/Morphic-eem.1002.mcz
==================== Summary ====================
Name: Morphic-eem.1002 Author: eem Time: 27 August 2015, 5:03:26.429 pm UUID: d94fff6d-5fef-4500-9144-4dc8bfa1510e Ancestors: Morphic-mt.1001
It's really convenient to be able to identify MenuItemMorphs easily.
=============== Diff against Morphic-mt.1001 ===============
Item was added:
- ----- Method: MenuItemMorph>>isMenuItemMorph (in category 'testing')
- isMenuItemMorph
^true!Item was added:
- ----- Method: Morph>>isMenuItemMorph (in category 'testing') -----
- isMenuItemMorph
^false!
What is the difference between "delete" and "destroy"?
On Fri, Aug 28, 2015 at 3:13 PM, Eliot Miranda eliot.miranda@gmail.com wrote:
Hi Tobias,
On Fri, Aug 28, 2015 at 9:56 AM, Tobias Pape Das.Linux@gmx.de wrote:
On 28.08.2015, at 18:15, Eliot Miranda eliot.miranda@gmail.com wrote:
Hi Chris,
I wanted to add a "delete all Monticello load change sets" menu pick to the change set sorter, but because menu pragmas are not right yet the only way to add a menu item next to another is to edit the menu using removeMorph: and addMorph:after: (instead of defining order in the menu pragma itself).
Huh? Then I've done something wrong. With <menuPriority: aNumber> you can define an order, and if the order is adjacent, menu items should show up adjacent :(.
Then I've probably misunderstood how the scheme should work. Or perhaps the implementation in ChangeSorter is an early one. Anyway, take a look at my attempt to add a single item next to the 'destroy change set (x)' item in ChangeSorter that is in Monticello-eem.617. My intent is to add 'delete Monticello load change sets' after 'destroy change set (x)'.
I'll look into that
best -tobias
And I can't stomach isKindOf: or isMemberOf:/class to distinguish MenuItemMorphs from MenuLineMorphs.
Sent from my iPhone
On Aug 28, 2015, at 8:23 AM, Chris Muller asqueaker@gmail.com wrote:
Why? Just curious..
On Thu, Aug 27, 2015 at 7:04 PM, commits@source.squeak.org wrote: Eliot Miranda uploaded a new version of Morphic to project The Trunk: http://source.squeak.org/trunk/Morphic-eem.1002.mcz
==================== Summary ====================
Name: Morphic-eem.1002 Author: eem Time: 27 August 2015, 5:03:26.429 pm UUID: d94fff6d-5fef-4500-9144-4dc8bfa1510e Ancestors: Morphic-mt.1001
It's really convenient to be able to identify MenuItemMorphs easily.
=============== Diff against Morphic-mt.1001 ===============
Item was added:
- ----- Method: MenuItemMorph>>isMenuItemMorph (in category 'testing')
- isMenuItemMorph
^true!Item was added:
- ----- Method: Morph>>isMenuItemMorph (in category 'testing') -----
- isMenuItemMorph
^false!-- _,,,^..^,,,_ best, Eliot
Sent from my iPhone
On Aug 29, 2015, at 9:10 AM, Chris Muller asqueaker@gmail.com wrote:
What is the difference between "delete" and "destroy"?
one brain fart
On Fri, Aug 28, 2015 at 3:13 PM, Eliot Miranda eliot.miranda@gmail.com wrote: Hi Tobias,
On Fri, Aug 28, 2015 at 9:56 AM, Tobias Pape Das.Linux@gmx.de wrote:
On 28.08.2015, at 18:15, Eliot Miranda eliot.miranda@gmail.com wrote:
Hi Chris,
I wanted to add a "delete all Monticello load change sets" menu pick to the change set sorter, but because menu pragmas are not right yet the only way to add a menu item next to another is to edit the menu using removeMorph: and addMorph:after: (instead of defining order in the menu pragma itself).
Huh? Then I've done something wrong. With <menuPriority: aNumber> you can define an order, and if the order is adjacent, menu items should show up adjacent :(.
Then I've probably misunderstood how the scheme should work. Or perhaps the implementation in ChangeSorter is an early one. Anyway, take a look at my attempt to add a single item next to the 'destroy change set (x)' item in ChangeSorter that is in Monticello-eem.617. My intent is to add 'delete Monticello load change sets' after 'destroy change set (x)'.
I'll look into that
best -tobias
And I can't stomach isKindOf: or isMemberOf:/class to distinguish MenuItemMorphs from MenuLineMorphs.
Sent from my iPhone
On Aug 28, 2015, at 8:23 AM, Chris Muller asqueaker@gmail.com wrote:
Why? Just curious..
On Thu, Aug 27, 2015 at 7:04 PM, commits@source.squeak.org wrote: Eliot Miranda uploaded a new version of Morphic to project The Trunk: http://source.squeak.org/trunk/Morphic-eem.1002.mcz
==================== Summary ====================
Name: Morphic-eem.1002 Author: eem Time: 27 August 2015, 5:03:26.429 pm UUID: d94fff6d-5fef-4500-9144-4dc8bfa1510e Ancestors: Morphic-mt.1001
It's really convenient to be able to identify MenuItemMorphs easily.
=============== Diff against Morphic-mt.1001 ===============
Item was added:
- ----- Method: MenuItemMorph>>isMenuItemMorph (in category 'testing')
- isMenuItemMorph
^true!Item was added:
- ----- Method: Morph>>isMenuItemMorph (in category 'testing') -----
- isMenuItemMorph
^false!-- _,,,^..^,,,_ best, Eliot
squeak-dev@lists.squeakfoundation.org
-
Chris Muller -
Eliot Miranda -
Tobias Pape