March 2011 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Issue 3545 in pharo: FEATURE: Multiple Worlds

by pharo＠googlecode.com

Comment #13 on issue 3545 by stephane...(a)gmail.com: FEATURE: Multiple Worlds http://code.google.com/p/pharo/issues/detail?id=3545 Excellent idea. This is still on my todo to play with it.

March 31, 2011

Re: [Pharo-project] Issue 3917 in pharo: Make all uses of SystemWindow go thru UIManger.

by pharo＠googlecode.com

Updates: Status: FixProposed Labels: Milestone-1.3 Comment #1 on issue 3917 by marcus.d...(a)gmail.com: Make all uses of SystemWindow go thru UIManger. http://code.google.com/p/pharo/issues/detail?id=3917 (No comment was entered for this change.)

March 31, 2011

Re: [Pharo-project] Regarding SimpleMorphic

by StÃ©phane Ducasse

> OK! Thanks for the feedback. > > In CUIS 3.1, Juan simplified many things. For example there's only one > button class, which suffices for all the different needs of todays > buttons. :) > Then the layout part was simplified. I thought is was already in PharoSimpleMorphic > Anwsers: > > 1) Editors and EditorState: Ok, i will coordinate with Alain for this. excellent > 2) 4) Regarding TextModel and subclasses such as CodeProvider and > Browser in CUIS: so it means that hierarchy wouldn't be needed at all > in Pharo. At least Nautilus must have a model for the text ? In CUIS > the root class is called TextModel , in Pharo 1.3 is called > StringHolder. I propose moving this discussion on another thread. > Maybe Benjamin could clarify this? benjamin will let us know. > So then i believe that for the SimpleMorphic part, it would just a > matter of porting Nautilus to SimpleMorphic, to be have "System > browsers". yes. So it requires TreeMorphTreeMorph So what we would be good is to have a nice ListMorph (with icons, with multiple selection) TreeMorph ... So that we can rebuild everything on that. > As we spoke with Alain, we will first make SimpleMorphic run side by > side with Morphic on Pharo1.3. Good. > Then start to enhance SM, to the point of not needing Morphic anymore! For example: porting Polymorph > (Merging UITheme and SMxTheme, for example). Good. > Please look at Juan's email about simple morphic, i believe the > simplicity of this Morphic system deserves this effort. Don;t get me wrong. I'm convinced about that but I do not have the expertise to do it. > > Fernando > > > On Thu, Mar 31, 2011 at 9:21 AM, StÃ©phane Ducasse > <stephane.ducasse(a)inria.fr> wrote: >> Hi guys >> >> Since this is interesting for all of us I prefer to publicly discuss it. >> >> From: Fernando Olivero <fernando.olivero(a)usi.ch> >>> Date: March 31, 2011 8:40:26 AM GMT+02:00 >>> To: alain.plantec(a)free.fr, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> >>> Subject: Regarding SimpleMorphic >>> Reply-To: fernando.olivero(a)usi.ch >>> >>> Hi, i've been working on the necessary steps to ease the adoption of >>> SimpleMorphic. >> >> Excellent! >> >>> I found it really nice, and would like to code the new >>> version of Gaucho on top of it. I post here the conclusions roadmap, >>> maybe you are starting the same effort, so this is just to collect >>> feedback or let you know! >> >> We want to join forces. >> I would love to have key widgets: list, tree ported and totally revised so that we >> do not have 20 of them but just two or four. >> >>> I always start from the Morphic in CUIS 3.1, and then go one by one >>> trying to port the relevant classes, honoring the intent behind Pharo >>> UI by, for example, adding in the UIManager uses whenever posible, >>> >>> Saludos, >>> Fernando >> >> Question: should we look in Cuis3.1 or Pharo1.3 SMx >> >>> %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% >>> CUIS >>> System >>> 1) Review Editor and friends: Separate hierarchy or try to merge with >>> the existing one in Pharo? Alain's great work on EditorState is >>> missing in CUIS. >> >> Yes I love the selection and highlights of Alain. >> >>> 2) import TextModel and hierarchy or maintain a separate hierarchy? >>> The changes in text model and subclasses seem to be good to have! >> >> >>> 3) (CUIS )DifferenceFinder vs (Pharo)TextDiffBuilder ? ( Seems that >>> DifferenceFinder has extra funcionality) >> >> No idea there. >> >>> 4) Transcript and TranscriptMorph. DONE ISSUE 3736 >> >> soon in Pharo1.3 >>> >>> %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% >>> CUIS3.1 into Pharo1.3 SimpleMorphic >> >> So what is the difference with the one we have. >> >>> 1) Make current implementation of SMx load in Pharo1.3. >>> DONE ISSUE 3878: Implementing enableTextChange >>> DONE ISSUE 3584: Cleanup removing DisplayText =>to remove >>> UIManager>>composeForm: >>> DONE ISSUE 3915: DiffMorph requests thru UIManager: so we don't have >>> to change senders such as ChangeList and VersionBrowser. >> >> Good. >> >>> 2) World, ActiveHand, ActiveEvent and ActiveWorld cleanup in Morphic. >>> To merge Morphic and SimpleMorphic handling of the global state, >>> centralizing the accessors in UIManager, by removing Globals. ALMOSTE >>> DONE ISSUE 3903 >>> 3) general up to date from CUIS 3.1: ALMOST DONE >>> 4) tools?: Revise the SMxBrowser and family, replace maybe with the >>> new TextModel>>openAsMorph: , etcâ¦ >> >> For the Browser we plan >> - to simply **Throw** away all the stringHolder and codeHolder classes and subclasses. >> Benjamin can show you Nautilus beta. >> - We will remove also ToolBuilder (as soon as we have a new version of the test runner) >> - We need a model for the debugger (we should check glamour people for that). >> So we will temporary keep stringHolde but compact it only for the debugger. >> >> >>> 5) Remove SMxTheWorldMenu and replace with MenuPragmaBuilder as in Pharo. >> >> Yes >> >>> 6) ? >>> >>> ++++++++++++++++++++++ >>> LOAD ORDER (uncomplete) >>> 3878 >>> 3584 >>> 3915 >>> 3736 >>> (PENDING) 3903 >>> ... >> >> >> > <SqueakScreen.1.png>

March 31, 2011

Re: [Pharo-project] Regarding SimpleMorphic

by Fernando Olivero

OK! Thanks for the feedback. In CUIS 3.1, Juan simplified many things. For example there's only one button class, which suffices for all the different needs of todays buttons. Then the layout part was simplified. Also themes were introduced, and above all: AMAZING rounded corners appearance! (Look at the attached figure) Anwsers: 1) Editors and EditorState: Ok, i will coordinate with Alain for this. 2) 4) Regarding TextModel and subclasses such as CodeProvider and Browser in CUIS: so it means that hierarchy wouldn't be needed at all in Pharo. At least Nautilus must have a model for the text ? In CUIS the root class is called TextModel , in Pharo 1.3 is called StringHolder. I propose moving this discussion on another thread. Maybe Benjamin could clarify this? So then i believe that for the SimpleMorphic part, it would just a matter of porting Nautilus to SimpleMorphic, to be have "System browsers". As we spoke with Alain, we will first make SimpleMorphic run side by side with Morphic on Pharo1.3. Then start to enhance SM, to the point of not needing Morphic anymore! For example: porting Polymorph (Merging UITheme and SMxTheme, for example). Please look at Juan's email about simple morphic, i believe the simplicity of this Morphic system deserves this effort. Fernando On Thu, Mar 31, 2011 at 9:21 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Hi guys > > Since this is interesting for all of us I prefer to publicly discuss it. > > From: Fernando Olivero <fernando.olivero(a)usi.ch> >> Date: March 31, 2011 8:40:26 AM GMT+02:00 >> To: alain.plantec(a)free.fr, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> >> Subject: Regarding SimpleMorphic >> Reply-To: fernando.olivero(a)usi.ch >> >> Hi, i've been working on the necessary steps to ease the adoption of >> SimpleMorphic. > > Excellent! > >> I found it really nice, and would like to code the new >> version of Gaucho on top of it. I post here the conclusions roadmap, >> maybe you are starting the same effort, so this is just to collect >> feedback or let you know! > > We want to join forces. > I would love to have key widgets: list, tree ported and totally revised so that we > do not have 20 of them but just two or four. > >> I always start from the Morphic in CUIS 3.1, and then go one by one >> trying to port the relevant classes, honoring the intent behind Pharo >> UI by, for example, Â adding in the UIManager uses whenever posible, >> >> Saludos, >> Fernando > > Question: should we look in Cuis3.1 or Pharo1.3 SMx > >> %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% >> CUIS >> System >> 1) Review Editor and friends: Separate hierarchy or try to merge with >> the existing one in Pharo? Alain's great work on EditorState is >> missing in CUIS. > > Yes I love the selection and highlights of Alain. > >> 2) import TextModel and hierarchy or maintain a separate hierarchy? >> The changes in text model and subclasses seem to be good to have! > > >> 3) Â (CUIS )DifferenceFinder vs (Pharo)TextDiffBuilder ? ( Seems that >> DifferenceFinder has extra funcionality) > > No idea there. > >> 4) Transcript and TranscriptMorph. DONE ISSUE 3736 > > soon in Pharo1.3 >> >> %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% >> CUIS3.1 into Pharo1.3 SimpleMorphic > > So what is the difference with the one we have. > >> 1) Make current implementation of SMx load in Pharo1.3. >> Â Â Â DONE ISSUE 3878: Implementing enableTextChange >> Â Â Â DONE ISSUE 3584: Cleanup removing DisplayText =>to remove >> UIManager>>composeForm: >> Â Â Â DONE ISSUE 3915: DiffMorph requests thru UIManager: so we don't have >> to change senders such as ChangeList and Â VersionBrowser. > > Good. > >> 2) World, ActiveHand, ActiveEvent and ActiveWorld cleanup in Morphic. >> To merge Morphic and SimpleMorphic handling of the global state, >> centralizing the accessors in Â UIManager, by removing Globals. ALMOSTE >> DONE ISSUE 3903 >> 3) general up to date from CUIS 3.1: ALMOST DONE >> 4) tools?: Revise the SMxBrowser and family, replace maybe with the >> new TextModel>>openAsMorph: , etcâ¦ > > For the Browser we plan > Â Â Â Â - to simply **Throw** away all the stringHolder and codeHolder classes and subclasses. > Â Â Â Â Â Â Â Â Benjamin can show you Nautilus beta. > Â Â Â Â - We will remove also ToolBuilder (as soon as we have a new version of the test runner) > Â Â Â Â - We need a model for the debugger (we should check glamour people for that). > Â Â Â Â So we will temporary keep stringHolde but compact it only for the debugger. > > >> 5) Remove SMxTheWorldMenu and replace with Â MenuPragmaBuilder as in Pharo. > > Yes > >> 6) ? >> >> ++++++++++++++++++++++ >> LOAD ORDER (uncomplete) >> 3878 >> 3584 >> 3915 >> 3736 >> (PENDING) 3903 >> ... > > >

March 31, 2011

[Pharo-project] Issue 3917 in pharo: Make all uses of SystemWindow go thru UIManger.

by pharo＠googlecode.com

Status: New Owner: ---- New issue 3917 by fernando...(a)gmail.com: Make all uses of SystemWindow go thru UIManger. http://code.google.com/p/pharo/issues/detail?id=3917 It would strengthen the UIManager responsibilities as the centralizer of UI requests. 1) To remove globals such as TopWindow in SystemWindow, and move some of the global state from SystemWindow class to the more appropriate UIManager subclass. The same for methods like SystemWindow>>wakeUpTopWindowUponStartup, SystemWindow>>fullScreenMargin , etc.. 2)To merge the approaches in different UIManagers, such as Morphic and SimpleMorph UIManagers. 3) Removed SMxSystemWindow noteTopWindowIn: aWorld, replaced by PasteUpMorph>>noteTopWindow. Attachments: SystemWindowThruUIManager-Preamble.2.cs 2.8 KB SystemWindowThruUIManager.3.cs 73.1 KB

March 31, 2011

[Pharo-project] Regarding SimpleMorphic

by StÃ©phane Ducasse

Hi guys Since this is interesting for all of us I prefer to publicly discuss it. From: Fernando Olivero <fernando.olivero(a)usi.ch> > Date: March 31, 2011 8:40:26 AM GMT+02:00 > To: alain.plantec(a)free.fr, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > Subject: Regarding SimpleMorphic > Reply-To: fernando.olivero(a)usi.ch > > Hi, i've been working on the necessary steps to ease the adoption of > SimpleMorphic. Excellent! > I found it really nice, and would like to code the new > version of Gaucho on top of it. I post here the conclusions roadmap, > maybe you are starting the same effort, so this is just to collect > feedback or let you know! We want to join forces. I would love to have key widgets: list, tree ported and totally revised so that we do not have 20 of them but just two or four. > I always start from the Morphic in CUIS 3.1, and then go one by one > trying to port the relevant classes, honoring the intent behind Pharo > UI by, for example, adding in the UIManager uses whenever posible, > > Saludos, > Fernando Question: should we look in Cuis3.1 or Pharo1.3 SMx > %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% > CUIS > System > 1) Review Editor and friends: Separate hierarchy or try to merge with > the existing one in Pharo? Alain's great work on EditorState is > missing in CUIS. Yes I love the selection and highlights of Alain. > 2) import TextModel and hierarchy or maintain a separate hierarchy? > The changes in text model and subclasses seem to be good to have! > 3) (CUIS )DifferenceFinder vs (Pharo)TextDiffBuilder ? ( Seems that > DifferenceFinder has extra funcionality) No idea there. > 4) Transcript and TranscriptMorph. DONE ISSUE 3736 soon in Pharo1.3 > > %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% > CUIS3.1 into Pharo1.3 SimpleMorphic So what is the difference with the one we have. > 1) Make current implementation of SMx load in Pharo1.3. > DONE ISSUE 3878: Implementing enableTextChange > DONE ISSUE 3584: Cleanup removing DisplayText =>to remove > UIManager>>composeForm: > DONE ISSUE 3915: DiffMorph requests thru UIManager: so we don't have > to change senders such as ChangeList and VersionBrowser. Good. > 2) World, ActiveHand, ActiveEvent and ActiveWorld cleanup in Morphic. > To merge Morphic and SimpleMorphic handling of the global state, > centralizing the accessors in UIManager, by removing Globals. ALMOSTE > DONE ISSUE 3903 > 3) general up to date from CUIS 3.1: ALMOST DONE > 4) tools?: Revise the SMxBrowser and family, replace maybe with the > new TextModel>>openAsMorph: , etcâ¦ For the Browser we plan - to simply **Throw** away all the stringHolder and codeHolder classes and subclasses. Benjamin can show you Nautilus beta. - We will remove also ToolBuilder (as soon as we have a new version of the test runner) - We need a model for the debugger (we should check glamour people for that). So we will temporary keep stringHolde but compact it only for the debugger. > 5) Remove SMxTheWorldMenu and replace with MenuPragmaBuilder as in Pharo. Yes > 6) ? > > ++++++++++++++++++++++ > LOAD ORDER (uncomplete) > 3878 > 3584 > 3915 > 3736 > (PENDING) 3903 > ...

March 31, 2011

Re: [Pharo-project] Issue 2559 in pharo: Senders of #ifNotNil: do not show

by pharo＠googlecode.com

Comment #7 on issue 2559 by ryd...(a)gmail.com: Senders of #ifNotNil: do not show http://code.google.com/p/pharo/issues/detail?id=2559 FWIW, this looks like a good solution for the standard Compiler though :)

March 31, 2011

Re: [Pharo-project] Issue 3916 in pharo: Can't input some Russian characters at text editors

by pharo＠googlecode.com

Updates: Status: FixProposed Labels: Milestone-1.3 Comment #3 on issue 3916 by marcus.d...(a)gmail.com: Can't input some Russian characters at text editors http://code.google.com/p/pharo/issues/detail?id=3916 (No comment was entered for this change.)

March 31, 2011

Re: [Pharo-project] Issue 3905 in pharo: Delete empty packages

by pharo＠googlecode.com

Updates: Status: FixToInclude Comment #1 on issue 3905 by marcus.d...(a)gmail.com: Delete empty packages http://code.google.com/p/pharo/issues/detail?id=3905 in the next postscript: (MCPackage named: 'System-Digital Signatures') workingCopy unregister. (MCPackage named: 'MimeConverter') workingCopy unregister. (MCPackage named: 'System-GUISupport') workingCopy unregister.

March 31, 2011

Re: [Pharo-project] Issue 3545 in pharo: FEATURE: Multiple Worlds

by pharo＠googlecode.com

Comment #12 on issue 3545 by aplan...(a)gmail.com: FEATURE: Multiple Worlds http://code.google.com/p/pharo/issues/detail?id=3545 the code is simple and clean and it is cool to have multiple worlds. I would suggest to make a separate package with it and that we load it in the dev-version. I mean not in the core, even I like it very much.

March 31, 2011