[Pharo-project] pharo ide task force - morphic issues
Hi, Here is a list of Morphic-related issues that would make the work on the Pharo IDE easier. Btw, if you want to join this cool task force, all you have to do is announce yourself and I offer to provide tasks :). === Keymappings should work with Morph instances - Currently, Keymappings define the keys for all instances of a morph class. This is not useful when we want to create new user interfaces. - Nevertheless, it would be great if we could use the same infrastructure both as it is used now for defining image-wise shortcuts and for controlling instance-based mappings === PluggableTextMorph / TextMorph should provide a means to announce the current selection - Currently, to get notified of when the selection changed, we need to create three subclasses (see below). This solution does not work well with other GLMPluggableTextMorph>>textMorphClass ^ GLMTextMorphForEditView GLMTextMorphForEditView>>editorClass ^ GLMSmalltalkEditor GLMSmalltalkEditor>>storeSelectionInParagraph super storeSelectionInParagraph. self morph ifNotNil: [ self morph editView announceSelectionFrom: self startIndex to: self stopIndex - 1 ] === The label of a TabMorph should shrink to fit the space - Right now a tab with a large title will expand the bounds of the tab. - We would need the possibility to limit the size of the title to the size of the contents. Ideally, there should be some abbreviation (with ...) of the title. === MorphTreeMorph should expand the embedded morphs horizontally - Currently, a row in the MorphTreeMorph takes the preferred size of the embedded morph. Instead, it should expand the row horizontally to fill the space. Or at least we should have the option to have it like that - MorphTreeMorph inherits from ScrollPane. I think it would be great to get it inherit from GeneralScrollPane. Or maybe there is a better solution. === In place editing of items in a list morph - It would be great to have the possibility of editing an item in a list morph in place, rather than being forced to open a dialogue === The button icons in Scrollbar and Expander should work with forms defined in UITheme - Currently, the buttons from Scrollbar and Expander create the arrow icons by drawing them directly. This does not work well with the other icons in the theme. - Instead, the Theme should have a means to provide a form for drawing these === A flexible layout - The idea is to offer a mechanism that would enable us to collapse a pane, and have the rest of the panes expand to fill the space - There is a start of an implementation, but we need to integrate this deeper. - See the thread from: http://lists.gforge.inria.fr/pipermail/pharo-project/2011-January/040408.htm... === Integrate TWM windows grouping mechanism - I know that for it to work, it requires some changesets that need to be filed in. - It would be great if they were integrated :) - See thread: http://lists.gforge.inria.fr/pipermail/pharo-project/2011-June/050116.html Cheers, Doru -- www.tudorgirba.com "The coherence of a trip is given by the clearness of the goal."
Where do you keep this list? I would like to have inplace edit in list item :) On Jul 21, 2011, at 6:11 AM, Tudor Girba wrote:
Hi,
Here is a list of Morphic-related issues that would make the work on the Pharo IDE easier.
Btw, if you want to join this cool task force, all you have to do is announce yourself and I offer to provide tasks :).
=== Keymappings should work with Morph instances - Currently, Keymappings define the keys for all instances of a morph class. This is not useful when we want to create new user interfaces. - Nevertheless, it would be great if we could use the same infrastructure both as it is used now for defining image-wise shortcuts and for controlling instance-based mappings
=== PluggableTextMorph / TextMorph should provide a means to announce the current selection - Currently, to get notified of when the selection changed, we need to create three subclasses (see below). This solution does not work well with other
GLMPluggableTextMorph>>textMorphClass ^ GLMTextMorphForEditView
GLMTextMorphForEditView>>editorClass ^ GLMSmalltalkEditor
GLMSmalltalkEditor>>storeSelectionInParagraph super storeSelectionInParagraph. self morph ifNotNil: [ self morph editView announceSelectionFrom: self startIndex to: self stopIndex - 1 ]
=== The label of a TabMorph should shrink to fit the space - Right now a tab with a large title will expand the bounds of the tab. - We would need the possibility to limit the size of the title to the size of the contents. Ideally, there should be some abbreviation (with ...) of the title.
=== MorphTreeMorph should expand the embedded morphs horizontally - Currently, a row in the MorphTreeMorph takes the preferred size of the embedded morph. Instead, it should expand the row horizontally to fill the space. Or at least we should have the option to have it like that - MorphTreeMorph inherits from ScrollPane. I think it would be great to get it inherit from GeneralScrollPane. Or maybe there is a better solution.
=== In place editing of items in a list morph - It would be great to have the possibility of editing an item in a list morph in place, rather than being forced to open a dialogue
=== The button icons in Scrollbar and Expander should work with forms defined in UITheme - Currently, the buttons from Scrollbar and Expander create the arrow icons by drawing them directly. This does not work well with the other icons in the theme. - Instead, the Theme should have a means to provide a form for drawing these
=== A flexible layout - The idea is to offer a mechanism that would enable us to collapse a pane, and have the rest of the panes expand to fill the space - There is a start of an implementation, but we need to integrate this deeper. - See the thread from: http://lists.gforge.inria.fr/pipermail/pharo-project/2011-January/040408.htm...
=== Integrate TWM windows grouping mechanism - I know that for it to work, it requires some changesets that need to be filed in. - It would be great if they were integrated :) - See thread: http://lists.gforge.inria.fr/pipermail/pharo-project/2011-June/050116.html
Cheers, Doru
-- www.tudorgirba.com
"The coherence of a trip is given by the clearness of the goal."
i think it should be put on wiki to prevent get buried in mails. On 21 July 2011 16:04, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote:
Where do you keep this list? I would like to have inplace edit in list item :)
On Jul 21, 2011, at 6:11 AM, Tudor Girba wrote:
Hi,
Here is a list of Morphic-related issues that would make the work on the Pharo IDE easier.
Btw, if you want to join this cool task force, all you have to do is announce yourself and I offer to provide tasks :).
=== Keymappings should work with Morph instances - Currently, Keymappings define the keys for all instances of a morph class. This is not useful when we want to create new user interfaces. - Nevertheless, it would be great if we could use the same infrastructure both as it is used now for defining image-wise shortcuts and for controlling instance-based mappings
=== PluggableTextMorph / TextMorph should provide a means to announce the current selection - Currently, to get notified of when the selection changed, we need to create three subclasses (see below). This solution does not work well with other
GLMPluggableTextMorph>>textMorphClass    ^ GLMTextMorphForEditView
GLMTextMorphForEditView>>editorClass    ^ GLMSmalltalkEditor
GLMSmalltalkEditor>>storeSelectionInParagraph    super storeSelectionInParagraph.    self morph ifNotNil: [        self morph editView            announceSelectionFrom: self startIndex            to: self stopIndex - 1 ]
=== The label of a TabMorph should shrink to fit the space - Right now a tab with a large title will expand the bounds of the tab. - We would need the possibility to limit the size of the title to the size of the contents. Ideally, there should be some abbreviation (with ...) of the title.
=== MorphTreeMorph should expand the embedded morphs horizontally - Currently, a row in the MorphTreeMorph takes the preferred size of the embedded morph. Instead, it should expand the row horizontally to fill the space. Or at least we should have the option to have it like that - MorphTreeMorph inherits from ScrollPane. I think it would be great to get it inherit from GeneralScrollPane. Or maybe there is a better solution.
=== In place editing of items in a list morph - It would be great to have the possibility of editing an item in a list morph in place, rather than being forced to open a dialogue
=== The button icons in Scrollbar and Expander should work with forms defined in UITheme - Currently, the buttons from Scrollbar and Expander create the arrow icons by drawing them directly. This does not work well with the other icons in the theme. - Instead, the Theme should have a means to provide a form for drawing these
=== A flexible layout - The idea is to offer a mechanism that would enable us to collapse a pane, and have the rest of the panes expand to fill the space - There is a start of an implementation, but we need to integrate this deeper. - See the thread from: http://lists.gforge.inria.fr/pipermail/pharo-project/2011-January/040408.htm...
=== Integrate TWM windows grouping mechanism - I know that for it to work, it requires some changesets that need to be filed in. - It would be great if they were integrated :) - See thread: http://lists.gforge.inria.fr/pipermail/pharo-project/2011-June/050116.html
Cheers, Doru
-- www.tudorgirba.com
"The coherence of a trip is given by the clearness of the goal."
-- Best regards, Igor Stasenko AKA sig.
Hi Doru,
=== Integrate TWM windows grouping mechanism - I know that for it to work, it requires some changesets that need to be filed in. - It would be great if they were integrated :)
in 1.3 ? They have been integrated in 1.4. Laurent.
- See thread: http://lists.gforge.inria.fr/pipermail/pharo-project/2011-June/050116.html
Cheers, Doru
-- www.tudorgirba.com
"The coherence of a trip is given by the clearness of the goal."
Hi, On 25 Jul 2011, at 23:28, laurent laffont wrote:
Hi Doru,
=== Integrate TWM windows grouping mechanism - I know that for it to work, it requires some changesets that need to be filed in. - It would be great if they were integrated :)
in 1.3 ? They have been integrated in 1.4.
Great, I did not know. 1.4 should be just fine. Cheers, Doru
Laurent.
- See thread: http://lists.gforge.inria.fr/pipermail/pharo-project/2011-June/050116.html
Cheers, Doru
-- www.tudorgirba.com
"The coherence of a trip is given by the clearness of the goal."
-- www.tudorgirba.com "Every thing has its own flow."
participants (4)
-
Igor Stasenko -
laurent laffont -
Stéphane Ducasse -
Tudor Girba