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

[Pharo-project] Re: Re: Re: First pharo-dev with limited package set+ aShout workspace where highlighting can be toggled

by Andrew Tween

"Damien Cassou" <damien.cassou(a)gmail.com> wrote in message news:6ac749c10809240351o32c3b4f3qff0a9ba9988d851a@mail.gmail.com... > On Wed, Sep 24, 2008 at 9:02 AM, Andrew Tween <amtween(a)hotmail.com> wrote: >> It's here - >> http://www.squeaksource.com/shout/ShoutWorkspace.1-tween.3.mcz > > > I think I found a bug : > > 1- Open a shout workspace > 2- Activate syntax highlighting > 3- Type any non smalltalk text ('etekjkldg' for example) > 4- It appears in red which is correct > 5- Deactivate syntax highlighting > 6- It is still red which is incorrect Thanks, I think I've fixed it - http://www.squeaksource.com/shout/ShoutWorkspace.1-tween.4.mcz Cheers, Andy > > -- > 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. 24, 2008

Re: [Pharo-project] Re: Re: First pharo-dev with limited package set + aShout workspace where highlighting can be toggled

by Damien Cassou

On Wed, Sep 24, 2008 at 9:02 AM, Andrew Tween <amtween(a)hotmail.com> wrote: > It's here - http://www.squeaksource.com/shout/ShoutWorkspace.1-tween.3.mcz I think I found a bug : 1- Open a shout workspace 2- Activate syntax highlighting 3- Type any non smalltalk text ('etekjkldg' for example) 4- It appears in red which is correct 5- Deactivate syntax highlighting 6- It is still red which is incorrect -- 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. 24, 2008

Re: [Pharo-project] On Icons

by David RÃ¶thlisberger

> What about using the left *and* also the right side of the method list > to show icons... > > If we could use the right side for "optionnal" icons, that would be > still readable and we could have more icons. yes, but it gets very confusing when you have icons on the left and on the right. And when you only have icons on the right, then they are not getting the same attention as when they are on the left. It also depends whether you place the icons always directly after the method label, or in one vertical column whose position is decided by the longest method label in the list. The latter looks nicer, but has the problem that you don't see the icons when you have just one single very long method name in your list that takes more space than the column is width (which happens many times when browsing all methods of a class in my image). You then have to make your browser window bigger which is cumbersome. So I don't know whether this is a good solution. Icons should be easy to grasp visually and normally, as we read from left to right, this is achieved when they are on the left side. David

Sept. 24, 2008

Re: [Pharo-project] On Icons

by CÃ©drick BÃ©ler

What about using the left *and* also the right side of the method list to show icons... If we could use the right side for "optionnal" icons, that would be still readable and we could have more icons. Just a thought. CÃ©drick

Sept. 24, 2008

Re: [Pharo-project] [OT] Sophie in Java

by Nikolay Suslov

Some moments 'clear'!? From thier site? "Sophie... Developed by Astea in collaboration with Impara GmbH..." . On Tue, Sep 23, 2008 at 10:13 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: > Hmm, maybe before blaming people, you should make some moments clear? > > For reading from their site http://asteasolutions.com/ > --- > Sophie has received key support from The Andrew W. Mellon Foundation > (http://www.mellon.org/) The Institute for the Future of the Book > designs and develops the tools and philosophy that will guide the form > and function of books as they evolve from the print-based format to a > digital format. Developed by Astea in collaboration with Impara GmbH > (http://www.impara.de/) of Magdeburg, Germany, and a team of the > world's leading Squeak experts, Sophie is the Institute's premiere > effort. > --- > > They have a references to origin, and maybe a point of > misunderstanding that they not clearly stating their goals? > I see nothing bad, if they like to adopt original idea using Java - it > is their own problem, after all. > > And before starting a war/conflict, try to resolve it peacefully - ask > them to rename the project, and ask to keep referencing to origin. > > > -- > Best regards, > Igor Stasenko AKA sig. > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Sept. 24, 2008

Re: [Pharo-project] Re: about http://bugs.squeak.org/view.php?id=6336

by Marcus Denker

On 24.09.2008, at 09:02, StÃ©phane Ducasse wrote: > Thanks. > Another problem with real atomic loading. > > Stef > >> Hi Stef, >> >> there is nothing special with the two change sets except their >> fileIn order, since instances of Character are used while both of >> them are loaded and compiled ... >> >> The 3.10 release team attempted to make .mcz out of them but failed >> miserably, so I suggest you just file them in. >> >> Let me know how it worked for you; perhaps also see if before/after >> the .image indeed gets smaller by ca. 300 KB. >> >> Ah, and before I forget: because of Association #hash #= (since 3.8 >> or so, Marcus knows the problem), compilation of Unicode methods >> take looong, since one of its class variables has a populated >> SparseLarge* thing which is #hash'ed and #='ed when compiling >> access to each class variable :( But this is a genaral problem, >> which just manifests, when compiling Unicode, with pain. I added Association = while working on AOStA... I searched for a long time for some bug until I found that = was inherited from LookUpKey only taking the key into account. I checked with VW, and there it checks both key and value for =. What I then did is to add a hash, too. That was no good idea, as it makes now the #hash very slow. In VW, theu just use the #hash of LookUpKey. So: we should do the same. Keep =, but remove #hash. Marcus -- Marcus Denker -- denker(a)iam.unibe.ch http://www.iam.unibe.ch/~denker

Sept. 24, 2008

Re: [Pharo-project] [OT] Sophie in Java

by CÃ©drick BÃ©ler

maybe Pharo would have change that ? I don't know if we can blame people from beeing scared by squeak ;) I really think this is important Sophie continue to evolve to show Java is not the way to go. After seaside, this could be the second main ST project developped with it... My 2 cents. CÃ©drick 2008/9/24 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > this is not the way politics works. > Apparently the founder was ready to found anything but squeak. > Strange no. > > Stef > > On Sep 23, 2008, at 10:13 PM, Igor Stasenko wrote: > >> Hmm, maybe before blaming people, you should make some moments clear? >> >> For reading from their site http://asteasolutions.com/ >> --- >> Sophie has received key support from The Andrew W. Mellon Foundation >> (http://www.mellon.org/) The Institute for the Future of the Book >> designs and develops the tools and philosophy that will guide the form >> and function of books as they evolve from the print-based format to a >> digital format. Developed by Astea in collaboration with Impara GmbH >> (http://www.impara.de/) of Magdeburg, Germany, and a team of the >> world's leading Squeak experts, Sophie is the Institute's premiere >> effort. >> --- >> >> They have a references to origin, and maybe a point of >> misunderstanding that they not clearly stating their goals? >> I see nothing bad, if they like to adopt original idea using Java - it >> is their own problem, after all. >> >> And before starting a war/conflict, try to resolve it peacefully - ask >> them to rename the project, and ask to keep referencing to origin. >> >> >> -- >> Best regards, >> Igor Stasenko AKA sig. >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > _______________________________________________ > 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. 24, 2008

[Pharo-project] Re: Re: First pharo-dev with limited package set + aShout workspace where highlighting can be toggled

by Andrew Tween

"Damien Cassou" <damien.cassou(a)gmail.com> wrote in message news:6ac749c10809232226h45195cecg94ba10fb82421a44@mail.gmail.com... > On Tue, Sep 23, 2008 at 9:47 PM, Andrew Tween <amtween(a)hotmail.com> wrote: >> Attached is a fileout of the Shout Workspace class, modified so that the >> Syntax Highlighting can be toggled from the title bar menu. >> see attached pic >> It remembers the last toggle value in a class inst var and uses that as >> the >> default for any new workspaces opened. >> This could easily be changed to be a real Preference setting. >> >> You can try it out in the pharo-dev image, just install it and open a new >> Workspace. >> >> What do people think? > > This is the best solution I think. Please post it to SqueakSource and > I will update the Universe. Thanks Damien, It's here - http://www.squeaksource.com/shout/ShoutWorkspace.1-tween.3.mcz Andy > > Thank you > > -- > 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. 24, 2008

[Pharo-project] Re: about http://bugs.squeak.org/view.php?id=6336

by StÃ©phane Ducasse

Thanks. Another problem with real atomic loading. Stef > Hi Stef, > > there is nothing special with the two change sets except their > fileIn order, since instances of Character are used while both of > them are loaded and compiled ... > > The 3.10 release team attempted to make .mcz out of them but failed > miserably, so I suggest you just file them in. > > Let me know how it worked for you; perhaps also see if before/after > the .image indeed gets smaller by ca. 300 KB. > > Ah, and before I forget: because of Association #hash #= (since 3.8 > or so, Marcus knows the problem), compilation of Unicode methods > take looong, since one of its class variables has a populated > SparseLarge* thing which is #hash'ed and #='ed when compiling access > to each class variable :( But this is a genaral problem, which just > manifests, when compiling Unicode, with pain. > > Cheers, > Klaus > > On Tue, 23 Sep 2008 21:52:35 +0200, StÃ©phane Ducasse wrote: > >> Hi klaus >> >> I would like to include the following in pharo >> about http://bugs.squeak.org/view.php?id=6336 >> >> can you tell me if I should pay attention to something in particular. >> >> Stef >> > >

Sept. 24, 2008

Re: [Pharo-project] Re: First pharo-dev with limited package set + a Shout workspace where highlighting can be toggled

by StÃ©phane Ducasse

Yes On Sep 23, 2008, at 10:29 PM, Adrian Lienhard wrote: > I like it. I think this is a good compromise. > Adrian > > On Sep 23, 2008, at 21:47 , Andrew Tween wrote: > >> Attached is a fileout of the Shout Workspace class, modified so >> that the Syntax Highlighting can be toggled from the title bar menu. >> see attached pic >> It remembers the last toggle value in a class inst var and uses >> that as the default for any new workspaces opened. >> This could easily be changed to be a real Preference setting. >> >> You can try it out in the pharo-dev image, just install it and open >> a new Workspace. >> >> What do people think? >> >> Cheers, >> Andy >> >> >> "Adrian Lienhard" <adi(a)netstyle.ch> wrote in message news:1E60C000-96B4-44FE-95F8-F19B951E0D41@netstyle.ch >> ... >> For sake of simplicity I would prefer to have just one menu item. I >> would put just the workspace without highlighting. Like Bill, I don't >> need my notes or code snippets in the workspace colorized. >> >> Which version of the workspace do people use most often? >> >> Adrian >> >> >> On Sep 23, 2008, at 13:58 , Damien Cassou wrote: >> >>> On Tue, Sep 23, 2008 at 11:42 AM, Adrian Lienhard >>> <adi(a)netstyle.ch> wrote: >>>> Question: Does this include Universes? It's not listed below but >>>> I see the >>>> menu item (which does not work because of a deprecation warning). >>>> I think we >>>> need Universes mainly because Seaside will be packaged with >>>> Universes soon, >>>> and being able to easily load Seaside is a key requirement for >>>> Pharo. >>> >>> >>> Universes and Installer are present. They are not listed because I >>> installed them by hand and not by using Universe. I will fix it for >>> the next version. >>> >>>> Another thing we need to look at (and I planned to do this) is >>>> the open >>>> menu. With all the additional packages in the dev version its >>>> even worse >>>> than before. For example there are 3(!) items for opening a >>>> workspace >>> >>> I think we need to keep two entries. Something like 'Smalltalk >>> workspace' and 'Text workspace'. What do you think? >>> >>> -- >>> 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 >> < >> SHWorkspace >> .st >> > >> < >> shworkspacetoggle.PNG>_______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Sept. 24, 2008