September 2008 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Tree View in OmniBrowser

by CÃ©drick BÃ©ler

Morever Janko, if you use OBEnhencement, and the OBPackageBrowser, you'll have the monticello command directly in the browser as you want ;)... Cheers, CÃ©drick 2008/9/23 Janko MivÅ¡ek <janko.mivsek(a)eranova.si>: > Hi David, > > Sound very interesting. Can you attach a small screenshoot for us who won't > be able to test it directly? > > Best regards > Janko > > David RÃ¶thlisberger wrote: >> >> Hello, >> >> It was very hard work, but finally and eventually I managed to integrate >> the tree >> view of Juraj in a reasonable way into OmniBrowser, so that we can use it >> for >> instance to browse packages. The package browser of OB-Enhancements is now >> using this >> tree in the first column to render packages on the first level and class >> categories >> on the second level. >> >> As this is a rather drastic change affecting also the underlying >> meta-model >> representing navigation in OB, I'd appreciate if some people give this a >> try and >> report any problems they might find to me. I extensively tested it, but >> you never know. >> I'm still working on some little things concerning this tree integration, >> mostly internal stuff, so nothing that should stand in way of using it >> already now. Just drop me a note if you encounter any problems, something >> that can still occur right now. >> >> >> Other recent enhancements include: >> >> - OB-TraitsIntegration is now part of OB-Enhancements as some people >> wanted to have it integrated in this package >> - mouse-over for icons in columns to get an explanation label >> - some icons are clickable, eg. to directly browse methods in superclasses >> - improvements in smart groups >> >> >> You need to load the following packages: >> >> OmniBrowser-dr.417 >> OB-Morphic-dr.54 >> OB-Standard-dr.351 >> OB-Enhancements-dr.207 >> >> >> ToDos: >> >> - refactor some of the code for the tree view >> - address several minor issues (eg. performance) >> - write more tests for tree view >> - integrate OmniBrowserFixes in OB-Enhancements >> >> >> Cheers, >> David > > -- > Janko MivÅ¡ek > AIDA/Web > Smalltalk Web Application Server > http://www.aidaweb.si > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- CÃ©drick

Sept. 23, 2008

Re: [Pharo-project] First pharo-dev with limited package set

by StÃ©phane Ducasse

Damien I would go for the workspace with color. and we should set the pref to have to type | | to declare varaibles. stef On Sep 23, 2008, at 4:30 PM, Damien Cassou wrote: > On Tue, Sep 23, 2008 at 2:17 PM, StÃ©phane Ducasse > <stephane.ducasse(a)inria.fr> wrote: >> uh? does not work for me no idea what is a Smalltalk workspace. > > a workspace to write Smalltalk code as opposed to a workspace to > write text. > > At the beginning, the ShoutWorkspace replaced the Workspace but some > people complained. That's why there are two workspaces now. I've never > used the non-colored workspace: when I want to write text, I enclose > it in quotes. > > -- > Damien Cassou > Peter von der AhÃ©: Â«I'm beginning to see why Gilad wished us good > luckÂ». (http://blogs.sun.com/ahe/entry/override_snafu) > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Sept. 23, 2008

Re: [Pharo-project] Tree View in OmniBrowser

by Janko MivÅ¡ek

Hi David, Sound very interesting. Can you attach a small screenshoot for us who won't be able to test it directly? Best regards Janko David RÃ¶thlisberger wrote: > Hello, > > It was very hard work, but finally and eventually I managed to integrate > the tree > view of Juraj in a reasonable way into OmniBrowser, so that we can use > it for > instance to browse packages. The package browser of OB-Enhancements is > now using this > tree in the first column to render packages on the first level and class > categories > on the second level. > > As this is a rather drastic change affecting also the underlying meta-model > representing navigation in OB, I'd appreciate if some people give this a > try and > report any problems they might find to me. I extensively tested it, but > you never know. > I'm still working on some little things concerning this tree > integration, mostly internal stuff, so nothing that should stand in way > of using it already now. Just drop me a note if you encounter any > problems, something that can still occur right now. > > > Other recent enhancements include: > > - OB-TraitsIntegration is now part of OB-Enhancements as some people > wanted to have it integrated in this package > - mouse-over for icons in columns to get an explanation label > - some icons are clickable, eg. to directly browse methods in superclasses > - improvements in smart groups > > > You need to load the following packages: > > OmniBrowser-dr.417 > OB-Morphic-dr.54 > OB-Standard-dr.351 > OB-Enhancements-dr.207 > > > ToDos: > > - refactor some of the code for the tree view > - address several minor issues (eg. performance) > - write more tests for tree view > - integrate OmniBrowserFixes in OB-Enhancements > > > Cheers, > David -- Janko MivÅ¡ek AIDA/Web Smalltalk Web Application Server http://www.aidaweb.si

Sept. 23, 2008

[Pharo-project] Tree View in OmniBrowser

by David RÃ¶thlisberger

Hello, It was very hard work, but finally and eventually I managed to integrate the tree view of Juraj in a reasonable way into OmniBrowser, so that we can use it for instance to browse packages. The package browser of OB-Enhancements is now using this tree in the first column to render packages on the first level and class categories on the second level. As this is a rather drastic change affecting also the underlying meta-model representing navigation in OB, I'd appreciate if some people give this a try and report any problems they might find to me. I extensively tested it, but you never know. I'm still working on some little things concerning this tree integration, mostly internal stuff, so nothing that should stand in way of using it already now. Just drop me a note if you encounter any problems, something that can still occur right now. Other recent enhancements include: - OB-TraitsIntegration is now part of OB-Enhancements as some people wanted to have it integrated in this package - mouse-over for icons in columns to get an explanation label - some icons are clickable, eg. to directly browse methods in superclasses - improvements in smart groups You need to load the following packages: OmniBrowser-dr.417 OB-Morphic-dr.54 OB-Standard-dr.351 OB-Enhancements-dr.207 ToDos: - refactor some of the code for the tree view - address several minor issues (eg. performance) - write more tests for tree view - integrate OmniBrowserFixes in OB-Enhancements Cheers, David

Sept. 23, 2008

Re: [Pharo-project] First pharo-dev with limited package set

by Igor Stasenko

2008/9/23 Damien Cassou <damien.cassou(a)gmail.com>: > On Tue, Sep 23, 2008 at 2:17 PM, StÃ©phane Ducasse > <stephane.ducasse(a)inria.fr> wrote: >> uh? does not work for me no idea what is a Smalltalk workspace. > > a workspace to write Smalltalk code as opposed to a workspace to write text. > > At the beginning, the ShoutWorkspace replaced the Workspace but some > people complained. That's why there are two workspaces now. I've never > used the non-colored workspace: when I want to write text, I enclose > it in quotes. > I never use any advanced workspace features, only for holding a useful text like todos & doits. So, i don't care if it auto-colored or not, but i'd like to not have a magic like holding temp vars. As for me, a simple text editor and Alt-d/Alt-p shortcuts is more than enough to work efficiently :) Maybe it would be better then to keep two options, but name them differently: - simple text editor - workspace > -- > Damien Cassou > Peter von der AhÃ©: Â«I'm beginning to see why Gilad wished us good > luckÂ». (http://blogs.sun.com/ahe/entry/override_snafu) > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > -- Best regards, Igor Stasenko AKA sig.

Sept. 23, 2008

Re: [Pharo-project] First pharo-dev with limited package set

by Damien Cassou

On Tue, Sep 23, 2008 at 2:17 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > uh? does not work for me no idea what is a Smalltalk workspace. a workspace to write Smalltalk code as opposed to a workspace to write text. At the beginning, the ShoutWorkspace replaced the Workspace but some people complained. That's why there are two workspaces now. I've never used the non-colored workspace: when I want to write text, I enclose it in quotes. -- Damien Cassou Peter von der AhÃ©: Â«I'm beginning to see why Gilad wished us good luckÂ». (http://blogs.sun.com/ahe/entry/override_snafu)

Sept. 23, 2008

[Pharo-project] SharedQueue Fixes from OLPC distro

by StÃ©phane Ducasse

http://tinlizzie.org/updates/etoys/updates 2009fixSharedQueue-b.. 2010fixSharedQueueAg..>

Sept. 23, 2008

Re: [Pharo-project] On Icons

by StÃ©phane Ducasse

excellent! On Sep 23, 2008, at 2:44 PM, David RÃ¶thlisberger wrote: > >>> Right now you get these methods in italic (Juraj did it like >>> that). If we change methods to be in italic when they are >>> extension methods, then we get a conflict here. >> Do you have the tree structure now? > > yes, I committed a working version just yesterday, but want to test > it a bit more today. I will probably announce it later today. > > > David > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Sept. 23, 2008

Re: [Pharo-project] On Icons

by StÃ©phane Ducasse

> >>>>>> - The same is for abstract method icon. When browsing the >>>>>> protocol/interface I don't need to know that. I am more >>>>>> interested if >>>>>> any of the subclasses override it. >>>>> >>>>> ok, I agree here. >>>> I disagree there. >>>> Browse stream and collection. >>> >>> I meant that the icon should show whether the abstract method is >>> overridden or not. What about keeping the cyan icon for abstract >>> methods, but as a triangle pointing south when the method is >>> overridden and as a square when it's not? >> or nothing when it is not? > > no, the case when it's not overridden is quite interesting as this > might be a hint for a problem (not needed abstract method or missing > override, etc.) I meant that a cyan triangle alone should reveal that. >> Try to come up with a nice model. >> Then after we should see how we can sell it also as a paper. > > ok, alright. > > > David > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Sept. 23, 2008

Re: [Pharo-project] On Icons

by David RÃ¶thlisberger

>> Right now you get these methods in italic (Juraj did it like that). If >> we change methods to be in italic when they are extension methods, >> then we get a conflict here. > Do you have the tree structure now? yes, I committed a working version just yesterday, but want to test it a bit more today. I will probably announce it later today. David

Sept. 23, 2008