April 2009 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] [update] #10263

by Damien Cassou

On Thu, Apr 2, 2009 at 6:03 PM, Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com> wrote: > Maybe to make it a bit less cryptic: > > "all VMs have closure support required for latest images" done -- Damien Cassou http://damiencassou.seasidehosting.st

April 2, 2009

Re: [Pharo-project] [update] #10263

by Nicolas Cellier

Thank, it is far better yet. Maybe to make it a bit less cryptic: "all VMs have closure support required for latest images" ... a hard work maintaining up to date site for a project moving so fast... 2009/4/2 Damien Cassou <damien.cassou(a)gmail.com>: > On Thu, Apr 2, 2009 at 10:49 AM, Nicolas Cellier > <nicolas.cellier.aka.nice(a)gmail.com> wrote: >> update http://www.pharo-project.org/download > > What do you think now? > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

April 2, 2009

Re: [Pharo-project] [update] #10263

by Damien Cassou

On Thu, Apr 2, 2009 at 10:49 AM, Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com> wrote: > update http://www.pharo-project.org/download What do you think now? -- Damien Cassou http://damiencassou.seasidehosting.st

April 2, 2009

Re: [Pharo-project] [Vm-dev] Re: Build, send and comment on Plugins page

by Michael Rueger

Andreas Raab wrote: > > Good idea. Any reason not to maintain the page at Squeak.org in (or > near) the downloads section? I think this would make it easier for > people to find it when they're looking for a download. It would be a good idea to have that on Squeak.org *too*. The table on the Pharo website is meant to be for the Pharo distribution. Right now we use the same VMs, but in the future we will most likely see differently packaged VMs (different sets of internal plugins). Also bundled for me refers to everything that comes with a download, which shouldn't really be a naked VM anyways. So usually you will have internal plugins and bundled external plugins and additional dlls. Michael

April 2, 2009

Re: [Pharo-project] About unicodeToMacRoman

by Michael Rueger

Nicolas Cellier wrote: > So, as announced, I conclude there is no use in forming a Character > when we only need a charCode in a specific encoding... Thanks for the analysis. What I basically did was a simple rename of the old squeakToMac etc selectors, without really analyzing the usage too much. So basically the freetype maintainer could change the caller sites and remove the then obsolete methods. Michael

April 2, 2009

Re: [Pharo-project] [update] #10263

by Damien Cassou

On Thu, Apr 2, 2009 at 12:00 PM, Adrian Lienhard <adi(a)netstyle.ch> wrote: > So if you like to help I'm happy to send you a login. But forking the > content on the wiki is no option. I agree, please give me a login and I will move the content. -- Damien Cassou http://damiencassou.seasidehosting.st

April 2, 2009

Re: [Pharo-project] About unicodeToMacRoman

by Nicolas Cellier

To follow up, I downloaded a more recent Pharo and analyzed senders of #unicodeToMacRoman Most are in FreeType but one in unused message TTFontReader>>#winToMac: FreeType mostly use this pattern: aCharacter unicodeToMacRoman asUnicode asInteger except: FreeTypeFont>>#linearKerningLeft:right: -> which further calls FT2Face>>#kerningLeft:right: -> -> which further apply (self primGetCharIndex: leftCharacter asInteger) So the two patterns I see for #unicodeToMacRoman usage are: aCharacter unicodeToMacRoman asUnicode asInteger and for Kerning: aCharacter unicodeToMacRoman asInteger Note that (asUnicode asInteger) seems to be a workaround for kind of old bug/mess like http://bugs.squeak.org/view.php?id=6395 The other message #macRomanToUnicode has a single sender TTFontreader>>#macToWin: which uses the pattern i announced macRomanCharCode asCharacter macRomanToUnicode charCode So, as announced, I conclude there is no use in forming a Character when we only need a charCode in a specific encoding... QED Nicolas 2009/4/1 Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com>: > Hello list, > > that's just a detail, but I do not much like Character>>unicodeToMacRoman. > > Why? > Because a Character does not explicitely carry encoding information. > On the contrary, Character are implicitely considered as unicode > encoded in 99% of code. > > So, pretending a Character can change encoding is just a hack for a > small portion of code... > ...and IMO a ugly one because a Debugger for example would be fooled > and its user too (ego quoque). > I bet most usages of this message will be (someCharacter > unicodeToMacRoman charCode), > so the pretended MacRoman encoded Character does not really need to exist... > (Shame on me, I have not downloaded a recent image, I'm just picking > changes here and there). > > If what I say is true, wouldn't a Character>>macRomanCharCode be more clean? > > Nicolas >

April 2, 2009

Re: [Pharo-project] [update] #10263

by Adrian Lienhard

We cannot open access to the web page for everybody. What we need is a small group of people that is responsible for the web site contents. So if you like to help I'm happy to send you a login. But forking the content on the wiki is no option. Cheers, Adrian On Apr 2, 2009, at 11:44 , Damien Cassou wrote: > On Thu, Apr 2, 2009 at 11:11 AM, Adrian Lienhard <adi(a)netstyle.ch> > wrote: >> Hence, the links to the VMs have to live on http://www.pharo-project.org/download >> and http://code.google.com/p/pharo/wiki/Downloads should only link >> to the former page and have no other content. >> >> I'll try to clean this up soon. > > The problem with this approach is that most people can't modify > pharo-project.org. I update the wiki on code.google.com twice a month > at least. > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

April 2, 2009

Re: [Pharo-project] [update] #10263

by Damien Cassou

On Thu, Apr 2, 2009 at 11:11 AM, Adrian Lienhard <adi(a)netstyle.ch> wrote: > Hence, the links to the VMs have to live on http://www.pharo-project.org/download > Â and http://code.google.com/p/pharo/wiki/Downloads should only link > to the former page and have no other content. > > I'll try to clean this up soon. The problem with this approach is that most people can't modify pharo-project.org. I update the wiki on code.google.com twice a month at least. -- Damien Cassou http://damiencassou.seasidehosting.st

April 2, 2009

Re: [Pharo-project] [update] #10263

by Adrian Lienhard

Nicola, you are right, its a mess! ;) We have three places: the web page, the wiki and the GForge. A piece of information or a file should be at one and only one location. - GForge is only for file downloads. All files should be linked directly from the wiki or web page (because its GUI is so terrible) - the wiki is for Pharo *developers* - the web page is for *end users* Hence, the links to the VMs have to live on http://www.pharo-project.org/download and http://code.google.com/p/pharo/wiki/Downloads should only link to the former page and have no other content. I'll try to clean this up soon. Adrian On Apr 2, 2009, at 10:49 , Nicolas Cellier wrote: > Thanks Damien, > that's certainly clear for U, not for me. > Is it the same that main Pharo page http://www.pharo-project.org/download > ? > How do I know if http://www.pharo-project.org/download provides > closure ready VM ? > Why is there a mac VM on https://gforge.inria.fr/frs/?group_id=1299 > and only a mac VM ? > Sorry, all this looks messy to me (i'm not in Pharo bath for about 4 > month). > > I see things like a newb: > 1) Marcus information tells I need a closure VM but direct me to a > page without unix VM. > 2) main pharo download page does not tell whether VM are closure > ready or not > 3) I'm stuck... (pretend I don't want to scan mailing list archive to > find your usefull link) > > That's why I ask information to be gathered in a single place. > 1) complete Marcus warning message > 2) update http://www.pharo-project.org/download > > Nicolas > > 2009/4/2 Damien Cassou <damien.cassou(a)gmail.com>: >> On Thu, Apr 2, 2009 at 10:30 AM, Nicolas Cellier >> <nicolas.cellier.aka.nice(a)gmail.com> wrote: >>> Please also inform with a link to non-mac closure VM (or put some on >>> inria forge). >> >> Everything is linked in the download page: >> >> http://code.google.com/p/pharo/wiki/Downloads?tm=2 >> >> -- >> Damien Cassou >> http://damiencassou.seasidehosting.st >> >> _______________________________________________ >> 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

April 2, 2009