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

Re: [Pharo-project] Re: Re: Re: Re: [ANN] Demo with both Truetype+Polymorph

by StÃ©phane Ducasse

May be we should add this info in a class comment. This is why I should continue to work on this idea of a manisfesto per package. Stef On Sep 24, 2008, at 12:01 AM, Andrew Tween wrote: > > "Norbert Hartl" <norbert(a)hartl.name> wrote in message news:1222159745.9772.5.camel@localhost > ... >> On Tue, 2008-09-23 at 10:01 +0200, Marcus Denker wrote: >>> On 23.09.2008, at 09:09, Andrew Tween wrote: >>> >>> > Note that with a one-click app distribution, it isn't necessary to >>> > embed the fonts in the image. >>> > FreeType Plus looks for a folder named Fonts relative to >>> the .image >>> > file, and loads any fonts it finds from there. >>> > >>> > Putting the font file(s) into the Fonts folder has these >>> advantages... >>> > >>> > 1.The image isn't bloated. (embedding a 20Mb font file would grow >>> > the image by 20Mb) >>> > So, the default font could be a large Unicode one, for example >>> > >>> > 2.Easier to create a one-click app for distribution. >>> > >>> > 3.Easier to install the font files into the OS so that other >>> > applications can also use them. >>> > >>> > 4. Free fonts that don't allow embedding can be used (e.g. >>> > Bitstream). This widens the choice of available free fonts. >>> > >>> > The advantage to embedding the font file in the image is that it >>> > moves around with the .image file. >>> > Which for a one-click app isn't really an advantage at all :) >>> >>> Cool! >>> >>> We should actually think about moving more data into files... for >>> example, there are huge literal arrays >>> in UCSTable's class side initialize methods that are only there for >>> initializing the class a long time ago. >>> These would not even be needed to be read on startup. >>> >>> Of course, this is violently against the "everything in the image" >>> philosophy of Squeak... but I guess >>> that any device one would want to run it on would have a >>> filesystem of >>> some sort. >>> >> Or there could be a call that reads it in and keeps it in the image. >> Easy for people they want to have it in their image. > > FreeTypeFontProvider current embedFilesInDirectory: aDirectory > will do this > >> >> Norbert > > > > _______________________________________________ > 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] [OT] Sophie in Java

by StÃ©phane Ducasse

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 >

Sept. 24, 2008

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

by Damien Cassou

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. 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)

Sept. 24, 2008

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

by Damien Cassou

On Tue, Sep 23, 2008 at 5:04 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: > Maybe it would be better then to keep two options, but name them differently: > - simple text editor > - workspace I think that is the best solution. For the text editor, Stef also proposed TextPad. What do you prefer? -- 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

[Pharo-project] Re: Re: Re: Re: [ANN] Demo with both Truetype+Polymorph

by Andrew Tween

"Norbert Hartl" <norbert(a)hartl.name> wrote in message news:1222159745.9772.5.camel@localhost... > On Tue, 2008-09-23 at 10:01 +0200, Marcus Denker wrote: >> On 23.09.2008, at 09:09, Andrew Tween wrote: >> >> > Note that with a one-click app distribution, it isn't necessary to >> > embed the fonts in the image. >> > FreeType Plus looks for a folder named Fonts relative to the .image >> > file, and loads any fonts it finds from there. >> > >> > Putting the font file(s) into the Fonts folder has these advantages... >> > >> > 1.The image isn't bloated. (embedding a 20Mb font file would grow >> > the image by 20Mb) >> > So, the default font could be a large Unicode one, for example >> > >> > 2.Easier to create a one-click app for distribution. >> > >> > 3.Easier to install the font files into the OS so that other >> > applications can also use them. >> > >> > 4. Free fonts that don't allow embedding can be used (e.g. >> > Bitstream). This widens the choice of available free fonts. >> > >> > The advantage to embedding the font file in the image is that it >> > moves around with the .image file. >> > Which for a one-click app isn't really an advantage at all :) >> >> Cool! >> >> We should actually think about moving more data into files... for >> example, there are huge literal arrays >> in UCSTable's class side initialize methods that are only there for >> initializing the class a long time ago. >> These would not even be needed to be read on startup. >> >> Of course, this is violently against the "everything in the image" >> philosophy of Squeak... but I guess >> that any device one would want to run it on would have a filesystem of >> some sort. >> > Or there could be a call that reads it in and keeps it in the image. > Easy for people they want to have it in their image. FreeTypeFontProvider current embedFilesInDirectory: aDirectory will do this > > Norbert

Sept. 23, 2008

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

by Norbert Hartl

Very good solution. Now we just have to discuss which is the default setting: on or off? :))) Norbert On Tue, 2008-09-23 at 20:47 +0100, 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 > _______________________________________________ > 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] Re: First pharo-dev with limited package set + a Shout workspace where highlighting can be toggled

by Adrian Lienhard

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

Sept. 23, 2008

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

by Igor Stasenko

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.

Sept. 23, 2008

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

by Michael Rueger

Janko MivÅ¡ek wrote: > Terrible indeed! And please, put the names of that guys in public, so > that we will know in the future, who to avoid for all costs. Because > this company is made out of people... well, yes. But I must really defend the little guys here, all very smart kids from the University there. They were basically caught on the wrong side of politics and IMHO to naive to know. Michael

Sept. 23, 2008

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

by Janko MivÅ¡ek

Terrible indeed! And please, put the names of that guys in public, so that we will know in the future, who to avoid for all costs. Because this company is made out of people... Janko StÃ©phane Ducasse wrote: > Terrible! > I'm really sad. > And I went to give them lectures for free..... > No comment. > > > Stef > > >> Hi all, >> >> the Mellon foundation just approved the grant to Astea in Bulgaria to >> redevelop Sophie in Java! Astea (http://asteasolutions.com) are the >> nice guys that we trained and who then turned around, stating on their >> web site that they developed Sophie, took our Sophie documents and >> artwork for their proposal and managed to persuade Mellon to actually >> give them money... >> >> We moved the current Sophie project to http://opensophie.org, hoping >> to keep Sophie alive and making Sophie better than what they can come >> up with. >> >> And why I'm sending this to the Pharo list? >> Pharo already has so much promise as a base system, hopefully >> providing in the core already what we had to re-invent in Sophie >> because it didn't work in the main Squeak version. The Freetype stuff >> already turned out really well! Hopefully more to come. >> >> And once I finish these new etoys installers I can do some Pharo work >> too, hopefully ;-) >> >> >> Michael >> >> _______________________________________________ >> 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 > -- Janko MivÅ¡ek Svetovalec za informatiko Eranova d.o.o. Ljubljana, Slovenija www.eranova.si tel: 01 514 22 55 faks: 01 514 22 56 gsm: 031 674 565

Sept. 23, 2008