- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Showing the setUp method in Nautilus

by Mariano Martinez Peck

On Mon, Mar 5, 2012 at 6:20 PM, Benjamin < benjamin.vanryseghem.pharo(a)gmail.com> wrote: > You are using a really old version of Nautilus. > > You load the configuration from the old repo. Now everything is on > Gemstone. > Ben, can you update not only the "Wiki" in ss but also the "Overview" (first tab) ? :) > > I still can't understand why you do not use a plugin for that. > Or an external class. > > Since menu items and shortcuts are pragma based, you can define them > anywhere in the system. And you can also retrieve data from the NautilusUI > instance. > > Ben > > On Mar 5, 2012, at 6:09 PM, Alexandre Bergel wrote: > > > Voila, I produced version 4.1 > > Please check. > > I did not use a plugin since the commands are directly implemented on > NautilusUI, I therefore guess that a plugin is not the way to define > commands. > > > > Also, something that I would find very useful, is to open a new Nautilus > directly on the Group tab. I often see myself switching to the Group tab. > Am I the only one? > > > > Cheers, > > Alexandre > > > > > > On 5 Mar 2012, at 13:40, Benjamin wrote: > > > >> > >> On Mar 5, 2012, at 12:52 PM, Alexandre Bergel wrote: > >> > >>> Hi! > >>> > >>> I worked on a new method item action to easily show the setUp method > of a testCase. This helps reduce the amount of clicks and context switching > when one wants to know what the setUp method is about while writing a test > method. > >> > >> Cool > >> > >>> I think it is a good candidate for being included in Nautilus. > >>> Ben, if you agree with this, I can to commit in the Nautilus rep and > produce a new version of the configuration. How does that sound? > >> > >> Commit, and I will have a look ;) > >> I though you started also a NautilusPlugin related to that, am I wrong ? > >> > >>> > >>> Question: how to associate a shortcut to an action? > >> > >> Anywhere on class side something like: > >> > >> buildRefactoringMethodShortcutsOn: aBuilder > >> <keymap> > >> > >> (aBuilder shortcut: #rename) > >> category: #NautilusMethodShortcuts > >> default: $r command > >> do: [:target || scroll | > >> scroll := target methodWidget vScrollValue. > >> target refactor renameMethodFor: target > selectedMethod. > >> target methodWidget vScrollValue: scroll] > >> > >> The categories are: > >> #NautilusMethodShortcuts > >> #NautilusProtocolShortcuts > >> #NautilusClassShortcuts > >> #NautilusPackageShortcuts > >> > >> and here target is the NautilusUi instance which get the keyStroke. > >> > >>> > >>> Side comment: it would be a good move to adopt a class hierarchy a la > OB to define commands. Defining all the commands in NautilusUI does not > scale and simply does not work for non trivial command. > >> > >> For me, it generates to much classes. And now that Guillermo did a > great work for KeyMappings, I prefer to use it :) > >> > >> > >> Ben > >> > >>> > >>> Cheers, > >>> Alexandre > >>> -- > >>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > >>> Alexandre Bergel http://www.bergel.eu > >>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > >>> > >>> > >>> > >>> <ShowSetupInNautilus.1.cs> > >> > > > > -- > > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > > Alexandre Bergel http://www.bergel.eu > > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > > > > > > > > > -- Mariano http://marianopeck.wordpress.com

March 5, 2012

Re: [Pharo-project] Showing the setUp method in Nautilus

by Mariano Martinez Peck

On Mon, Mar 5, 2012 at 6:09 PM, Alexandre Bergel <alexandre.bergel(a)me.com>wrote: > Voila, I produced version 4.1 > Please check. > I did not use a plugin since the commands are directly implemented on > NautilusUI, I therefore guess that a plugin is not the way to define > commands. > > Also, something that I would find very useful, is to open a new Nautilus > directly on the Group tab. I often see myself switching to the Group tab. > Am I the only one? > > There is a setting for that. > Cheers, > Alexandre > > > On 5 Mar 2012, at 13:40, Benjamin wrote: > > > > > On Mar 5, 2012, at 12:52 PM, Alexandre Bergel wrote: > > > >> Hi! > >> > >> I worked on a new method item action to easily show the setUp method of > a testCase. This helps reduce the amount of clicks and context switching > when one wants to know what the setUp method is about while writing a test > method. > > > > Cool > > > >> I think it is a good candidate for being included in Nautilus. > >> Ben, if you agree with this, I can to commit in the Nautilus rep and > produce a new version of the configuration. How does that sound? > > > > Commit, and I will have a look ;) > > I though you started also a NautilusPlugin related to that, am I wrong ? > > > >> > >> Question: how to associate a shortcut to an action? > > > > Anywhere on class side something like: > > > > buildRefactoringMethodShortcutsOn: aBuilder > > <keymap> > > > > (aBuilder shortcut: #rename) > > category: #NautilusMethodShortcuts > > default: $r command > > do: [:target || scroll | > > scroll := target methodWidget vScrollValue. > > target refactor renameMethodFor: target > selectedMethod. > > target methodWidget vScrollValue: scroll] > > > > The categories are: > > #NautilusMethodShortcuts > > #NautilusProtocolShortcuts > > #NautilusClassShortcuts > > #NautilusPackageShortcuts > > > > and here target is the NautilusUi instance which get the keyStroke. > > > >> > >> Side comment: it would be a good move to adopt a class hierarchy a la > OB to define commands. Defining all the commands in NautilusUI does not > scale and simply does not work for non trivial command. > > > > For me, it generates to much classes. And now that Guillermo did a great > work for KeyMappings, I prefer to use it :) > > > > > > Ben > > > >> > >> Cheers, > >> Alexandre > >> -- > >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > >> Alexandre Bergel http://www.bergel.eu > >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > >> > >> > >> > >> <ShowSetupInNautilus.1.cs> > > > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > -- Mariano http://marianopeck.wordpress.com

March 5, 2012

Re: [Pharo-project] Showing the setUp method in Nautilus

by Benjamin

You are using a really old version of Nautilus. You load the configuration from the old repo. Now everything is on Gemstone. I still can't understand why you do not use a plugin for that. Or an external class. Since menu items and shortcuts are pragma based, you can define them anywhere in the system. And you can also retrieve data from the NautilusUI instance. Ben On Mar 5, 2012, at 6:09 PM, Alexandre Bergel wrote: > Voila, I produced version 4.1 > Please check. > I did not use a plugin since the commands are directly implemented on NautilusUI, I therefore guess that a plugin is not the way to define commands. > > Also, something that I would find very useful, is to open a new Nautilus directly on the Group tab. I often see myself switching to the Group tab. Am I the only one? > > Cheers, > Alexandre > > > On 5 Mar 2012, at 13:40, Benjamin wrote: > >> >> On Mar 5, 2012, at 12:52 PM, Alexandre Bergel wrote: >> >>> Hi! >>> >>> I worked on a new method item action to easily show the setUp method of a testCase. This helps reduce the amount of clicks and context switching when one wants to know what the setUp method is about while writing a test method. >> >> Cool >> >>> I think it is a good candidate for being included in Nautilus. >>> Ben, if you agree with this, I can to commit in the Nautilus rep and produce a new version of the configuration. How does that sound? >> >> Commit, and I will have a look ;) >> I though you started also a NautilusPlugin related to that, am I wrong ? >> >>> >>> Question: how to associate a shortcut to an action? >> >> Anywhere on class side something like: >> >> buildRefactoringMethodShortcutsOn: aBuilder >> <keymap> >> >> (aBuilder shortcut: #rename) >> category: #NautilusMethodShortcuts >> default: $r command >> do: [:target || scroll | >> scroll := target methodWidget vScrollValue. >> target refactor renameMethodFor: target selectedMethod. >> target methodWidget vScrollValue: scroll] >> >> The categories are: >> #NautilusMethodShortcuts >> #NautilusProtocolShortcuts >> #NautilusClassShortcuts >> #NautilusPackageShortcuts >> >> and here target is the NautilusUi instance which get the keyStroke. >> >>> >>> Side comment: it would be a good move to adopt a class hierarchy a la OB to define commands. Defining all the commands in NautilusUI does not scale and simply does not work for non trivial command. >> >> For me, it generates to much classes. And now that Guillermo did a great work for KeyMappings, I prefer to use it :) >> >> >> Ben >> >>> >>> Cheers, >>> Alexandre >>> -- >>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>> Alexandre Bergel http://www.bergel.eu >>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>> >>> >>> >>> <ShowSetupInNautilus.1.cs> >> > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > >

March 5, 2012

Re: [Pharo-project] Showing the setUp method in Nautilus

by Benjamin

On Mar 5, 2012, at 6:09 PM, Alexandre Bergel wrote: > Voila, I produced version 4.1 Version 4.1 already existed :S > Please check. > I did not use a plugin since the commands are directly implemented on NautilusUI, I therefore guess that a plugin is not the way to define commands. Why did you add stuff in Nautilus for that ? Why not using an external class ? > > Also, something that I would find very useful, is to open a new Nautilus directly on the Group tab. I often see myself switching to the Group tab. Am I the only one? There is a setting for that Ben > > Cheers, > Alexandre > > > On 5 Mar 2012, at 13:40, Benjamin wrote: > >> >> On Mar 5, 2012, at 12:52 PM, Alexandre Bergel wrote: >> >>> Hi! >>> >>> I worked on a new method item action to easily show the setUp method of a testCase. This helps reduce the amount of clicks and context switching when one wants to know what the setUp method is about while writing a test method. >> >> Cool >> >>> I think it is a good candidate for being included in Nautilus. >>> Ben, if you agree with this, I can to commit in the Nautilus rep and produce a new version of the configuration. How does that sound? >> >> Commit, and I will have a look ;) >> I though you started also a NautilusPlugin related to that, am I wrong ? >> >>> >>> Question: how to associate a shortcut to an action? >> >> Anywhere on class side something like: >> >> buildRefactoringMethodShortcutsOn: aBuilder >> <keymap> >> >> (aBuilder shortcut: #rename) >> category: #NautilusMethodShortcuts >> default: $r command >> do: [:target || scroll | >> scroll := target methodWidget vScrollValue. >> target refactor renameMethodFor: target selectedMethod. >> target methodWidget vScrollValue: scroll] >> >> The categories are: >> #NautilusMethodShortcuts >> #NautilusProtocolShortcuts >> #NautilusClassShortcuts >> #NautilusPackageShortcuts >> >> and here target is the NautilusUi instance which get the keyStroke. >> >>> >>> Side comment: it would be a good move to adopt a class hierarchy a la OB to define commands. Defining all the commands in NautilusUI does not scale and simply does not work for non trivial command. >> >> For me, it generates to much classes. And now that Guillermo did a great work for KeyMappings, I prefer to use it :) >> >> >> Ben >> >>> >>> Cheers, >>> Alexandre >>> -- >>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>> Alexandre Bergel http://www.bergel.eu >>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>> >>> >>> >>> <ShowSetupInNautilus.1.cs> >> > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > >

March 5, 2012

Re: [Pharo-project] Showing the setUp method in Nautilus

by Alexandre Bergel

Voila, I produced version 4.1 Please check. I did not use a plugin since the commands are directly implemented on NautilusUI, I therefore guess that a plugin is not the way to define commands. Also, something that I would find very useful, is to open a new Nautilus directly on the Group tab. I often see myself switching to the Group tab. Am I the only one? Cheers, Alexandre On 5 Mar 2012, at 13:40, Benjamin wrote: > > On Mar 5, 2012, at 12:52 PM, Alexandre Bergel wrote: > >> Hi! >> >> I worked on a new method item action to easily show the setUp method of a testCase. This helps reduce the amount of clicks and context switching when one wants to know what the setUp method is about while writing a test method. > > Cool > >> I think it is a good candidate for being included in Nautilus. >> Ben, if you agree with this, I can to commit in the Nautilus rep and produce a new version of the configuration. How does that sound? > > Commit, and I will have a look ;) > I though you started also a NautilusPlugin related to that, am I wrong ? > >> >> Question: how to associate a shortcut to an action? > > Anywhere on class side something like: > > buildRefactoringMethodShortcutsOn: aBuilder > <keymap> > > (aBuilder shortcut: #rename) > category: #NautilusMethodShortcuts > default: $r command > do: [:target || scroll | > scroll := target methodWidget vScrollValue. > target refactor renameMethodFor: target selectedMethod. > target methodWidget vScrollValue: scroll] > > The categories are: > #NautilusMethodShortcuts > #NautilusProtocolShortcuts > #NautilusClassShortcuts > #NautilusPackageShortcuts > > and here target is the NautilusUi instance which get the keyStroke. > >> >> Side comment: it would be a good move to adopt a class hierarchy a la OB to define commands. Defining all the commands in NautilusUI does not scale and simply does not work for non trivial command. > > For me, it generates to much classes. And now that Guillermo did a great work for KeyMappings, I prefer to use it :) > > > Ben > >> >> Cheers, >> Alexandre >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> <ShowSetupInNautilus.1.cs> > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

March 5, 2012

Re: [Pharo-project] Nautilus would be a nice GSoC project (was MVP)

by Janko MivÅ¡ek

Dne 05. 03. 2012 18:00, piÅ¡e Benjamin: > Why not :) > > The thing is I do not know which steps have to be done to apply so :) For start just describe here answering these questions: Project name Level (Beginner, Intermediate, Advanced) Description Technical Details Benefits to the Student Benefits to the Community Those are just ideas for now, but we need to be as detailed already. Later we can choose the mentor, second mentor etc. Best regards Janko > > > Ben > > On Mar 5, 2012, at 5:54 PM, Janko MivÅ¡ek wrote: > >> Hi Benjamin, >> >> Are you thinking about applying with Nautilus on this Google Summer of >> Code? I think your work is to be supported more, and applying to the >> GSoC stipendium is a nice opportunity, not to be missed :) >> >> Best regards >> Janko >> >> Dne 05. 03. 2012 17:46, piÅ¡e Benjamin: >>> The problem is that we improved a lot he morphic layout in 1.4, and Spec is based on that. So most probably it doesn't work in 1.3 (and I didn't put effort in this direction, and will probably not) >>> >>> >>> Try Nautilus instead of OB ^^ >>> Again, we improved the system, but we are not maintaining OB, so it could be not up to date. >>> >>> >>> Have fun with Spec, >>> >>> Ben >>> >>> On Mar 5, 2012, at 1:41 PM, StÃ©phane Ducasse wrote: >>> >>>> spec is not made to work on 1.3 >>>> >>>> Stef >>>> >>>> On Mar 5, 2012, at 10:03 AM, Schwab,Wilhelm K wrote: >>>> >>>>> Stef, >>>>> >>>>> Thanks for the code! #stable does some things on 1.4, but I still got nowhere with 1.3. The big thing keeping me off of 1.4 is shout in the browsers - I *really* like syntax highlighting. In fairness, I have not looked at 1.4 in a week or so, so maybe that's been fixed. However, I can certainly run it to play around with spec. >>>>> >>>>> Even on 1.4, I got a DNU over groups; this time I had to add the noop to OB, which is apparently the default in 1.4?? >>>>> >>>>> More fiddling to come. >>>>> >>>>> Bill >>>>> >>>>> >>>>> ________________________________________ >>>>> From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] on behalf of StÃ©phane Ducasse [stephane.ducasse(a)inria.fr] >>>>> Sent: Monday, March 05, 2012 3:26 AM >>>>> To: Pharo-project(a)lists.gforge.inria.fr >>>>> Subject: Re: [Pharo-project] MVP >>>>> >>>>> bill >>>>> >>>>> thanks for the catch. I updated the document. >>>>> >>>>> >>>>> Gofer new >>>>> url: 'http://ss3.gemstone.com/ss/Spec'; >>>>> package: 'ConfigurationOfSpec'; >>>>> load >>>>> >>>>> ConfigurationOfSpec project load: #stable >>>>> >>>>> >>>>> Stef >>>>> >>>>> >>>>> On Mar 5, 2012, at 1:24 AM, Schwab,Wilhelm K wrote: >>>>> >>>>>> Ben, >>>>>> >>>>>> Great, but I'm still getting nipped by a DNU of #addGroupForPackage:. I found that no-oped in 1.4 so added it to 1.3 and was able to loadFull. It looks like great work, but I can't get anything to run in 1.3 or 1.4. Any ideas? >>>>>> >>>>>> Bill >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] on behalf of Benjamin [benjamin.vanryseghem.pharo(a)gmail.com] >>>>>> Sent: Sunday, March 04, 2012 6:53 PM >>>>>> To: Pharo-project(a)lists.gforge.inria.fr >>>>>> Subject: Re: [Pharo-project] MVP >>>>>> >>>>>> Everything has been moved in ss3.gemstone.com/ss/Spec :) >>>>>> >>>>>> >>>>>> Ben >>>>>> >>>>>> On Mar 5, 2012, at 12:47 AM, Schwab,Wilhelm K wrote: >>>>>> >>>>>>> Ben, >>>>>>> >>>>>>> Ok, but I don't see it in either dirty experiments or the mc repository. Am I missing a ConfigurationOfSpec? >>>>>>> >>>>>>> Bill >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] on behalf of Benjamin [benjamin.vanryseghem.pharo(a)gmail.com] >>>>>>> Sent: Sunday, March 04, 2012 6:38 PM >>>>>>> To: Pharo-project(a)lists.gforge.inria.fr >>>>>>> Subject: Re: [Pharo-project] MVP >>>>>>> >>>>>>> I am kind of a middle of something right now, so my advice is really to use the configuration (moreover I have added a lot of packages) >>>>>>> >>>>>>> >>>>>>> Keep me in touch, >>>>>>> >>>>>>> Ben >>>>>>> >>>>>>> On Mar 5, 2012, at 12:34 AM, Schwab,Wilhelm K wrote: >>>>>>> >>>>>>>> Stef, >>>>>>>> >>>>>>>> I skimmed the documentation and attempted to load Spec-BenjaminVanRyseghem.34.mcz into 1.3, but got an error and backed off. >>>>>>>> >>>>>>>> Any ideas? >>>>>>>> >>>>>>>> Bill >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] on behalf of StÃ©phane Ducasse [stephane.ducasse(a)inria.fr] >>>>>>>> Sent: Sunday, February 05, 2012 2:56 AM >>>>>>>> To: Pharo-project(a)lists.gforge.inria.fr >>>>>>>> Subject: Re: [Pharo-project] MVP >>>>>>>> >>>>>>>> if you want to have a look at what we are doing with benjamin you can have a look at >>>>>>>> Spec >>>>>>>> >>>>>>>> Yesterday benjamin added inputField support and rewrote the changeSorter. >>>>>>>> >>>>>>>> Stef >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> On Feb 5, 2012, at 3:28 AM, Schwab,Wilhelm K wrote: >>>>>>>> >>>>>>>>> More: >>>>>>>>> >>>>>>>>> proportional layouts need to let each view have a proportion (zero makes it fixed size) and splitters should be just another view that is added to a composite, following the horizontal/vertical nature of the layout manager. >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] on behalf of Schwab,Wilhelm K [bschwab(a)anest.ufl.edu] >>>>>>>>> Sent: Saturday, February 04, 2012 9:25 PM >>>>>>>>> To: Pharo-project(a)lists.gforge.inria.fr >>>>>>>>> Subject: Re: [Pharo-project] MVP >>>>>>>>> >>>>>>>>> I'm still a little overwhelmed, but I see attention to layout; this has been a BIG stumbling block for me in my efforts to bring MVP to Pharo. I recommend using nested composite view/presenter pairs for most layout. First, it lends itself well to an eventual view editor, and second, can be surprisingly easy to code directly. >>>>>>>>> >>>>>>>>> Each composite view has a layout manager. Layouts include constrained table-like elements, but the real workhorses are proportional layouts, which can be set either horizontal or vertical. By nesting them, very complicate behavior can be achieved. >>>>>>>>> >>>>>>>>> There, said "nesting," and that has been where I have fallen into trouble. Pharo/morphic layout works great for children of the top level, but after that, I can't get reliable results. >>>>>>>>> >>>>>>>>> Sleep calls... >>>>>>>>> >>>>>>>>> Bill >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] on behalf of Schwab,Wilhelm K [bschwab(a)anest.ufl.edu] >>>>>>>>> Sent: Saturday, February 04, 2012 6:36 PM >>>>>>>>> To: pharo-project(a)lists.gforge.inria.fr >>>>>>>>> Subject: [Pharo-project] MVP >>>>>>>>> >>>>>>>>> Hello all, >>>>>>>>> >>>>>>>>> I have been to busy to read today, but I like seeing any discussion of MVP. I am **slowly** working on a framework for it, but would be glad to be beaten to it. >>>>>>>>> >>>>>>>>> Default models are key; they must be replaceable, but (sub)triads should work "out of the box." Models can include value holders, value adapters, converters, and contexts, depending on how they are wired. >>>>>>>>> >>>>>>>>> I have something of a start on the adapters and converters, which I can try to package and make available. If nothing else, they will have value in seeding discussion if not be directly usable. More to come. >>>>>>>>> >>>>>>>>> Bill >>>>> >>>>> >>>>> >>>> >>>> >>> >>> >>> >> >> -- >> Janko MivÅ¡ek >> Aida/Web >> Smalltalk Web Application Server >> http://www.aidaweb.si >> > > > -- Janko MivÅ¡ek Aida/Web Smalltalk Web Application Server http://www.aidaweb.si

March 5, 2012

[Pharo-project] [update 1.4] #14378

by Marcus Denker

14378 ----- Issue 5436: Move DialogItemsChooser to Finder (its only user) http://code.google.com/p/pharo/issues/detail?id=5436 Issue 5435: clean up unusedBlocks tests http://code.google.com/p/pharo/issues/detail?id=5435 -- Marcus Denker -- http://marcusdenker.de

March 5, 2012

Re: [Pharo-project] Nautilus would be a nice GSoC project (was MVP)

by Benjamin

Why not :) The thing is I do not know which steps have to be done to apply so :) Ben On Mar 5, 2012, at 5:54 PM, Janko MivÅ¡ek wrote: > Hi Benjamin, > > Are you thinking about applying with Nautilus on this Google Summer of > Code? I think your work is to be supported more, and applying to the > GSoC stipendium is a nice opportunity, not to be missed :) > > Best regards > Janko > > Dne 05. 03. 2012 17:46, piÅ¡e Benjamin: >> The problem is that we improved a lot he morphic layout in 1.4, and Spec is based on that. So most probably it doesn't work in 1.3 (and I didn't put effort in this direction, and will probably not) >> >> >> Try Nautilus instead of OB ^^ >> Again, we improved the system, but we are not maintaining OB, so it could be not up to date. >> >> >> Have fun with Spec, >> >> Ben >> >> On Mar 5, 2012, at 1:41 PM, StÃ©phane Ducasse wrote: >> >>> spec is not made to work on 1.3 >>> >>> Stef >>> >>> On Mar 5, 2012, at 10:03 AM, Schwab,Wilhelm K wrote: >>> >>>> Stef, >>>> >>>> Thanks for the code! #stable does some things on 1.4, but I still got nowhere with 1.3. The big thing keeping me off of 1.4 is shout in the browsers - I *really* like syntax highlighting. In fairness, I have not looked at 1.4 in a week or so, so maybe that's been fixed. However, I can certainly run it to play around with spec. >>>> >>>> Even on 1.4, I got a DNU over groups; this time I had to add the noop to OB, which is apparently the default in 1.4?? >>>> >>>> More fiddling to come. >>>> >>>> Bill >>>> >>>> >>>> ________________________________________ >>>> From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] on behalf of StÃ©phane Ducasse [stephane.ducasse(a)inria.fr] >>>> Sent: Monday, March 05, 2012 3:26 AM >>>> To: Pharo-project(a)lists.gforge.inria.fr >>>> Subject: Re: [Pharo-project] MVP >>>> >>>> bill >>>> >>>> thanks for the catch. I updated the document. >>>> >>>> >>>> Gofer new >>>> url: 'http://ss3.gemstone.com/ss/Spec'; >>>> package: 'ConfigurationOfSpec'; >>>> load >>>> >>>> ConfigurationOfSpec project load: #stable >>>> >>>> >>>> Stef >>>> >>>> >>>> On Mar 5, 2012, at 1:24 AM, Schwab,Wilhelm K wrote: >>>> >>>>> Ben, >>>>> >>>>> Great, but I'm still getting nipped by a DNU of #addGroupForPackage:. I found that no-oped in 1.4 so added it to 1.3 and was able to loadFull. It looks like great work, but I can't get anything to run in 1.3 or 1.4. Any ideas? >>>>> >>>>> Bill >>>>> >>>>> >>>>> >>>>> >>>>> From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] on behalf of Benjamin [benjamin.vanryseghem.pharo(a)gmail.com] >>>>> Sent: Sunday, March 04, 2012 6:53 PM >>>>> To: Pharo-project(a)lists.gforge.inria.fr >>>>> Subject: Re: [Pharo-project] MVP >>>>> >>>>> Everything has been moved in ss3.gemstone.com/ss/Spec :) >>>>> >>>>> >>>>> Ben >>>>> >>>>> On Mar 5, 2012, at 12:47 AM, Schwab,Wilhelm K wrote: >>>>> >>>>>> Ben, >>>>>> >>>>>> Ok, but I don't see it in either dirty experiments or the mc repository. Am I missing a ConfigurationOfSpec? >>>>>> >>>>>> Bill >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] on behalf of Benjamin [benjamin.vanryseghem.pharo(a)gmail.com] >>>>>> Sent: Sunday, March 04, 2012 6:38 PM >>>>>> To: Pharo-project(a)lists.gforge.inria.fr >>>>>> Subject: Re: [Pharo-project] MVP >>>>>> >>>>>> I am kind of a middle of something right now, so my advice is really to use the configuration (moreover I have added a lot of packages) >>>>>> >>>>>> >>>>>> Keep me in touch, >>>>>> >>>>>> Ben >>>>>> >>>>>> On Mar 5, 2012, at 12:34 AM, Schwab,Wilhelm K wrote: >>>>>> >>>>>>> Stef, >>>>>>> >>>>>>> I skimmed the documentation and attempted to load Spec-BenjaminVanRyseghem.34.mcz into 1.3, but got an error and backed off. >>>>>>> >>>>>>> Any ideas? >>>>>>> >>>>>>> Bill >>>>>>> >>>>>>> >>>>>>> >>>>>>> From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] on behalf of StÃ©phane Ducasse [stephane.ducasse(a)inria.fr] >>>>>>> Sent: Sunday, February 05, 2012 2:56 AM >>>>>>> To: Pharo-project(a)lists.gforge.inria.fr >>>>>>> Subject: Re: [Pharo-project] MVP >>>>>>> >>>>>>> if you want to have a look at what we are doing with benjamin you can have a look at >>>>>>> Spec >>>>>>> >>>>>>> Yesterday benjamin added inputField support and rewrote the changeSorter. >>>>>>> >>>>>>> Stef >>>>>>> >>>>>>> >>>>>>> >>>>>>> On Feb 5, 2012, at 3:28 AM, Schwab,Wilhelm K wrote: >>>>>>> >>>>>>>> More: >>>>>>>> >>>>>>>> proportional layouts need to let each view have a proportion (zero makes it fixed size) and splitters should be just another view that is added to a composite, following the horizontal/vertical nature of the layout manager. >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] on behalf of Schwab,Wilhelm K [bschwab(a)anest.ufl.edu] >>>>>>>> Sent: Saturday, February 04, 2012 9:25 PM >>>>>>>> To: Pharo-project(a)lists.gforge.inria.fr >>>>>>>> Subject: Re: [Pharo-project] MVP >>>>>>>> >>>>>>>> I'm still a little overwhelmed, but I see attention to layout; this has been a BIG stumbling block for me in my efforts to bring MVP to Pharo. I recommend using nested composite view/presenter pairs for most layout. First, it lends itself well to an eventual view editor, and second, can be surprisingly easy to code directly. >>>>>>>> >>>>>>>> Each composite view has a layout manager. Layouts include constrained table-like elements, but the real workhorses are proportional layouts, which can be set either horizontal or vertical. By nesting them, very complicate behavior can be achieved. >>>>>>>> >>>>>>>> There, said "nesting," and that has been where I have fallen into trouble. Pharo/morphic layout works great for children of the top level, but after that, I can't get reliable results. >>>>>>>> >>>>>>>> Sleep calls... >>>>>>>> >>>>>>>> Bill >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] on behalf of Schwab,Wilhelm K [bschwab(a)anest.ufl.edu] >>>>>>>> Sent: Saturday, February 04, 2012 6:36 PM >>>>>>>> To: pharo-project(a)lists.gforge.inria.fr >>>>>>>> Subject: [Pharo-project] MVP >>>>>>>> >>>>>>>> Hello all, >>>>>>>> >>>>>>>> I have been to busy to read today, but I like seeing any discussion of MVP. I am **slowly** working on a framework for it, but would be glad to be beaten to it. >>>>>>>> >>>>>>>> Default models are key; they must be replaceable, but (sub)triads should work "out of the box." Models can include value holders, value adapters, converters, and contexts, depending on how they are wired. >>>>>>>> >>>>>>>> I have something of a start on the adapters and converters, which I can try to package and make available. If nothing else, they will have value in seeding discussion if not be directly usable. More to come. >>>>>>>> >>>>>>>> Bill >>>> >>>> >>>> >>> >>> >> >> >> > > -- > Janko MivÅ¡ek > Aida/Web > Smalltalk Web Application Server > http://www.aidaweb.si >

March 5, 2012

[Pharo-project] Nautilus would be a nice GSoC project (was MVP)

by Janko MivÅ¡ek

Hi Benjamin, Are you thinking about applying with Nautilus on this Google Summer of Code? I think your work is to be supported more, and applying to the GSoC stipendium is a nice opportunity, not to be missed :) Best regards Janko Dne 05. 03. 2012 17:46, piÅ¡e Benjamin: > The problem is that we improved a lot he morphic layout in 1.4, and Spec is based on that. So most probably it doesn't work in 1.3 (and I didn't put effort in this direction, and will probably not) > > > Try Nautilus instead of OB ^^ > Again, we improved the system, but we are not maintaining OB, so it could be not up to date. > > > Have fun with Spec, > > Ben > > On Mar 5, 2012, at 1:41 PM, StÃ©phane Ducasse wrote: > >> spec is not made to work on 1.3 >> >> Stef >> >> On Mar 5, 2012, at 10:03 AM, Schwab,Wilhelm K wrote: >> >>> Stef, >>> >>> Thanks for the code! #stable does some things on 1.4, but I still got nowhere with 1.3. The big thing keeping me off of 1.4 is shout in the browsers - I *really* like syntax highlighting. In fairness, I have not looked at 1.4 in a week or so, so maybe that's been fixed. However, I can certainly run it to play around with spec. >>> >>> Even on 1.4, I got a DNU over groups; this time I had to add the noop to OB, which is apparently the default in 1.4?? >>> >>> More fiddling to come. >>> >>> Bill >>> >>> >>> ________________________________________ >>> From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] on behalf of StÃ©phane Ducasse [stephane.ducasse(a)inria.fr] >>> Sent: Monday, March 05, 2012 3:26 AM >>> To: Pharo-project(a)lists.gforge.inria.fr >>> Subject: Re: [Pharo-project] MVP >>> >>> bill >>> >>> thanks for the catch. I updated the document. >>> >>> >>> Gofer new >>> url: 'http://ss3.gemstone.com/ss/Spec'; >>> package: 'ConfigurationOfSpec'; >>> load >>> >>> ConfigurationOfSpec project load: #stable >>> >>> >>> Stef >>> >>> >>> On Mar 5, 2012, at 1:24 AM, Schwab,Wilhelm K wrote: >>> >>>> Ben, >>>> >>>> Great, but I'm still getting nipped by a DNU of #addGroupForPackage:. I found that no-oped in 1.4 so added it to 1.3 and was able to loadFull. It looks like great work, but I can't get anything to run in 1.3 or 1.4. Any ideas? >>>> >>>> Bill >>>> >>>> >>>> >>>> >>>> From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] on behalf of Benjamin [benjamin.vanryseghem.pharo(a)gmail.com] >>>> Sent: Sunday, March 04, 2012 6:53 PM >>>> To: Pharo-project(a)lists.gforge.inria.fr >>>> Subject: Re: [Pharo-project] MVP >>>> >>>> Everything has been moved in ss3.gemstone.com/ss/Spec :) >>>> >>>> >>>> Ben >>>> >>>> On Mar 5, 2012, at 12:47 AM, Schwab,Wilhelm K wrote: >>>> >>>>> Ben, >>>>> >>>>> Ok, but I don't see it in either dirty experiments or the mc repository. Am I missing a ConfigurationOfSpec? >>>>> >>>>> Bill >>>>> >>>>> >>>>> >>>>> >>>>> From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] on behalf of Benjamin [benjamin.vanryseghem.pharo(a)gmail.com] >>>>> Sent: Sunday, March 04, 2012 6:38 PM >>>>> To: Pharo-project(a)lists.gforge.inria.fr >>>>> Subject: Re: [Pharo-project] MVP >>>>> >>>>> I am kind of a middle of something right now, so my advice is really to use the configuration (moreover I have added a lot of packages) >>>>> >>>>> >>>>> Keep me in touch, >>>>> >>>>> Ben >>>>> >>>>> On Mar 5, 2012, at 12:34 AM, Schwab,Wilhelm K wrote: >>>>> >>>>>> Stef, >>>>>> >>>>>> I skimmed the documentation and attempted to load Spec-BenjaminVanRyseghem.34.mcz into 1.3, but got an error and backed off. >>>>>> >>>>>> Any ideas? >>>>>> >>>>>> Bill >>>>>> >>>>>> >>>>>> >>>>>> From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] on behalf of StÃ©phane Ducasse [stephane.ducasse(a)inria.fr] >>>>>> Sent: Sunday, February 05, 2012 2:56 AM >>>>>> To: Pharo-project(a)lists.gforge.inria.fr >>>>>> Subject: Re: [Pharo-project] MVP >>>>>> >>>>>> if you want to have a look at what we are doing with benjamin you can have a look at >>>>>> Spec >>>>>> >>>>>> Yesterday benjamin added inputField support and rewrote the changeSorter. >>>>>> >>>>>> Stef >>>>>> >>>>>> >>>>>> >>>>>> On Feb 5, 2012, at 3:28 AM, Schwab,Wilhelm K wrote: >>>>>> >>>>>>> More: >>>>>>> >>>>>>> proportional layouts need to let each view have a proportion (zero makes it fixed size) and splitters should be just another view that is added to a composite, following the horizontal/vertical nature of the layout manager. >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] on behalf of Schwab,Wilhelm K [bschwab(a)anest.ufl.edu] >>>>>>> Sent: Saturday, February 04, 2012 9:25 PM >>>>>>> To: Pharo-project(a)lists.gforge.inria.fr >>>>>>> Subject: Re: [Pharo-project] MVP >>>>>>> >>>>>>> I'm still a little overwhelmed, but I see attention to layout; this has been a BIG stumbling block for me in my efforts to bring MVP to Pharo. I recommend using nested composite view/presenter pairs for most layout. First, it lends itself well to an eventual view editor, and second, can be surprisingly easy to code directly. >>>>>>> >>>>>>> Each composite view has a layout manager. Layouts include constrained table-like elements, but the real workhorses are proportional layouts, which can be set either horizontal or vertical. By nesting them, very complicate behavior can be achieved. >>>>>>> >>>>>>> There, said "nesting," and that has been where I have fallen into trouble. Pharo/morphic layout works great for children of the top level, but after that, I can't get reliable results. >>>>>>> >>>>>>> Sleep calls... >>>>>>> >>>>>>> Bill >>>>>>> >>>>>>> >>>>>>> >>>>>>> From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] on behalf of Schwab,Wilhelm K [bschwab(a)anest.ufl.edu] >>>>>>> Sent: Saturday, February 04, 2012 6:36 PM >>>>>>> To: pharo-project(a)lists.gforge.inria.fr >>>>>>> Subject: [Pharo-project] MVP >>>>>>> >>>>>>> Hello all, >>>>>>> >>>>>>> I have been to busy to read today, but I like seeing any discussion of MVP. I am **slowly** working on a framework for it, but would be glad to be beaten to it. >>>>>>> >>>>>>> Default models are key; they must be replaceable, but (sub)triads should work "out of the box." Models can include value holders, value adapters, converters, and contexts, depending on how they are wired. >>>>>>> >>>>>>> I have something of a start on the adapters and converters, which I can try to package and make available. If nothing else, they will have value in seeding discussion if not be directly usable. More to come. >>>>>>> >>>>>>> Bill >>> >>> >>> >> >> > > > -- Janko MivÅ¡ek Aida/Web Smalltalk Web Application Server http://www.aidaweb.si

March 5, 2012

Re: [Pharo-project] small thoughts... system browser to show super methods & wide debugger

by Marcus Denker

On Mar 5, 2012, at 11:33 AM, Ben Coman wrote: > > Just sharing some small thoughts as they cross my mind on the chance the are of any interest. Not necessarily looking for any response or action. > > 1. In the System Browser when viewing a method, this might include an expandable list of overridden methods. Beneath the code of the current method being viewed each 'super' method would be listed with an expandable '+' symbol. I have attached a mock up [1] showing all expanded but the default might be the collapsed state. > > 2. The debugger lists instance and temporary variables to be inspected, but not every object that 'passes through' the method being executed is held in a variable. More often messages are chained together such that to inspect the object returned from the middle of this chain you need to select that bit of the code and choose to inspect it again. However there may be side-effects of executing that a second time so you are not guaranteed to end up looking at the object actually encountered by the execution of the method. > What would be interesting would be if in certain circumstances every object returned by every message in a method was held to be inspected. This might take the form of hovering or right-clicking on any message an choosing something like 'inspect context'. The circumstances this might be turned on for could be: > a. globally > b. ongoing execution from within debugger > c. certain methods / classes / categories. > > 3. With screens getting much bigger, perhaps the debugger could have an option to show code from previous calls back to a certain level. I have attached a mock up [2]. Even though this image shows using a lot of vertical space, this would be scrolled. Ultimately it would be horizontal space required as the code steps in, but todays wide screens match this even better than those a few years ago. Note the yellow highlighted line in the top pane which can position how far back you look. > I like the debugger idea! Especially combined with mouse-over infos (show the value if var in a pop-up when the mouse it over it), this should allow for a very quick way to understand code... Marcus -- Marcus Denker -- http://marcusdenker.de

March 5, 2012