- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Website screenshots

by Damien Cassou

2009/9/16 Gary Chambers <gazzaguru2(a)btinternet.com>: > I guess the IDE screenshot could do with updating... old-stlye buttons! > Just mention because linked from Planet Squeak (re: Facelifiting Smalltalk). > > Might be nice with #showTextEditingState preference enabled now too... Done. What do you think? -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry

Sept. 17, 2009

[Pharo-project] Fwd: Status of Alien FFI

by StÃ©phane Ducasse

ken eliot is not in the pharo mailing-list so I repost it. Begin forwarded message: > From: Eliot Miranda <eliot.miranda(a)gmail.com> > Date: September 17, 2009 12:17:13 AM CEDT > To: StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > Subject: Re: [Pharo-project] Status of Alien FFI > > > what should I do? > > On Wed, Sep 16, 2009 at 3:09 PM, <pharo-project-owner(a)lists.gforge.inria.fr > > wrote: > You are not allowed to post to this mailing list, and your message has > been automatically rejected. If you think that your messages are > being rejected in error, contact the mailing list owner at > pharo-project-owner(a)lists.gforge.inria.fr. > > > > ---------- Forwarded message ---------- > From: Eliot Miranda <eliot.miranda(a)gmail.com> > To: Ken Treis <ken(a)miriamtech.com> > Date: Wed, 16 Sep 2009 15:09:43 -0700 > Subject: Re: [Pharo-project] Status of Alien FFI > Hi Ken, > > On Wed, Sep 16, 2009 at 12:17 PM, Ken Treis <ken(a)miriamtech.com> > wrote: > > On Sep 16, 2009, at 12:02 PM, Douglas Brebner wrote: > > One minor point is that whether integers and longs are different > depends > on the platforms data model. Under MS Win64, integers and long > integers > are both 32bit, while on most unixes integers are 32bit while long > ints > are 64bit. (LLP64 and LP64 models respectively) > > Really? so sizeof(int) == sizeof(long) and sizeof(long) ~= > sizeof(__int64)?? Strange choice (see below) ;) > Every other 64bit platform I've seen has used > sizeof(int) == 4, sizeof(long) == sizeof(long long) > > But one should insulate oneself using appropriate defines/typedefs, > and include asserts to confirm basic types are of the size one > assumes. > > I don't know if this is important though. > > Good point. All of my platforms are LP64 (Mac OS X and Linux > x86-64), and my main objective at present is to get this working for > an application I'm committed to build, so I was ignoring those sorts > of cross-platform details. > > Perhaps there would need to be new primitives for the basic size of > each relevant C type? I'm anxious to hear what Eliot might have to > say about this since he's got about 2000x more experience with this > than I do. > > are you using the 64-bit VM? If you're using a 32-bit VM on a 64- > bit platform then yu're using 32-bits and you'll be linking against > 32-bit libraries and hence nothing will have changed. > > Alien has support for 64-bit values. Of course it uses the Windows > choice, short = 2, int unused as a name, long = 4, longLong = 8. e.g. > anAlien unsignedByteAt: oneRelativeIndex > anAlien unsignedShortAt: oneRelativeIndex > anAlien unsignedLongAt: oneRelativeIndex > anAlien unsignedLongLongAt: oneRelativeIndex > are the basic primitives for fetching unsigned integers. > > But this needs to be wrapped with something that selects the right > sizes based on the current platform and that's yet to be addressed. > > > > > -- > Ken Treis > Miriam Technologies, Inc. > > > >

Sept. 17, 2009

Re: [Pharo-project] NBS-ISCC Color Names

by StÃ©phane Ducasse

ken it would really important that we get only MIT code in the image. Now I do not really now how to handle these? For now an external package would be nice. stef On Sep 17, 2009, at 2:16 AM, Ken Dickey wrote: > Greetings, > > I don't know if anyone is interested, but PharoInbox now contains a > change > set, Graphics-KenDickey.131, which adds Color names based on NBS- > ISCC Color > Centroids as described in: > > http://people.csail.mit.edu/jaffer/Color/Dictionaries > > After the change set has been filed in, one should invoke "Color > initializeNames" in a workspace. "Color explore" and look at the pool > dictionary for swatches and details. > > This set of Color names has the properties: > > * explicit and non-restrictive copyright and license (below) > * no name conflicts between colors > * color names are specific to surface colors or lighting > * colors are distributed to equalize perceptual distances between them > and > * colors are derived from matching physical samples > > > In particular, the licence is > > " > Copyright \251 2003 Voluntocracy. Permission is granted to copy and > distribute modified or unmodified versions of this color dictionary > provided the copyright notice and this permission notice are preserved > on all copies and the entire such work is distributed under the terms > of a permission notice identical to this one. > " > > Cheers, > -KenD > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Sept. 17, 2009

[Pharo-project] Macintosh os-x 10.4.x and Alien & ObjectiveC plugins get updated.

by John M McIntosh

In the sometimes hectic rush in building both the Alien and ObjectiveC plugins for OS-X when Apple pushed out it seems 53 beta version of XCode for snow leopard and iPhone OS 3.x I managed to build both plugins for OS-X 10.5 only. Finally someone noticed, oddly this took awhile... Therefore today I did recompile the IA32ABI.bundle (Alien plugin) for usage on 10.4.x as IA32ABI.1.1.1.bundle.zip and uploaded to my ftp site (experimental folder). The ObjectiveCPlugin was more problematic, since it makes optional use of Protocols which aren't fully supported in 10.4. But I did build a special version ObjectiveCPlugin.1.1.1.OSX10.4.xOnly. bundle.zip which you again will find on the ftp site in the experimental folder. That 10.4.x only plugin doesn't support the optional protocol interface. But likely if you need it, then you don't support 10.4 anyway. -- = = = ======================================================================== John M. McIntosh <johnmci(a)smalltalkconsulting.com> Twitter: squeaker68882 Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com = = = ========================================================================

Sept. 17, 2009

Re: [Pharo-project] NBS-ISCC Color Names

by Michael van der Gulik

On Thu, Sep 17, 2009 at 12:16 PM, Ken Dickey <Ken.Dickey(a)whidbey.com> wrote: > Greetings, > > I don't know if anyone is interested, but PharoInbox now contains a change > set, Graphics-KenDickey.131, which adds Color names based on NBS-ISCC > Color > Centroids as described in: > > http://people.csail.mit.edu/jaffer/Color/Dictionaries > > After the change set has been filed in, one should invoke "Color > initializeNames" in a workspace. "Color explore" and look at the pool > dictionary for swatches and details. > > This set of Color names has the properties: > > * explicit and non-restrictive copyright and license (below) > * no name conflicts between colors > * color names are specific to surface colors or lighting > * colors are distributed to equalize perceptual distances between them > and > * colors are derived from matching physical samples > > Can we handle "white" being F2 F3 F4 rather than FF FF FF? This is like this because of some reason to do with printer gamuts. Otherwise - good find! I'll be keeping the reference. Gulik. -- http://gulik.pbwiki.com/

Sept. 17, 2009

[Pharo-project] NBS-ISCC Color Names

by Ken Dickey

Greetings, I don't know if anyone is interested, but PharoInbox now contains a change set, Graphics-KenDickey.131, which adds Color names based on NBS-ISCC Color Centroids as described in: http://people.csail.mit.edu/jaffer/Color/Dictionaries After the change set has been filed in, one should invoke "Color initializeNames" in a workspace. "Color explore" and look at the pool dictionary for swatches and details. This set of Color names has the properties: * explicit and non-restrictive copyright and license (below) * no name conflicts between colors * color names are specific to surface colors or lighting * colors are distributed to equalize perceptual distances between them and * colors are derived from matching physical samples In particular, the licence is " Copyright \251 2003 Voluntocracy. Permission is granted to copy and distribute modified or unmodified versions of this color dictionary provided the copyright notice and this permission notice are preserved on all copies and the entire such work is distributed under the terms of a permission notice identical to this one. " Cheers, -KenD

Sept. 17, 2009

Re: [Pharo-project] Website screenshots

by Michael Roberts

If someone would like to post a screenshot or mail me off list, i can edit the web site. thanks, Mike On Wed, Sep 16, 2009 at 7:22 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Mike I do not know if you can edit the site because adrian is on > holiday and I do not remember :) > > On Sep 16, 2009, at 7:09 PM, Gary Chambers wrote: > >> I guess the IDE screenshot could do with updating... old-stlye >> buttons! >> Just mention because linked from Planet Squeak (re: Facelifiting >> Smalltalk). >> >> Might be nice with #showTextEditingState preference enabled now too... >> >> Regards, Gary >> _______________________________________________ >> 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. 16, 2009

Re: [Pharo-project] Status of Alien FFI

by Douglas Brebner

Ken Treis wrote: > On Sep 16, 2009, at 12:02 PM, Douglas Brebner wrote: > > >> One minor point is that whether integers and longs are different >> depends >> on the platforms data model. Under MS Win64, integers and long >> integers >> are both 32bit, while on most unixes integers are 32bit while long >> ints >> are 64bit. (LLP64 and LP64 models respectively) >> >> I don't know if this is important though. >> > > Good point. All of my platforms are LP64 (Mac OS X and Linux x86-64), > and my main objective at present is to get this working for an > application I'm committed to build, so I was ignoring those sorts of > cross-platform details. > > Perhaps there would need to be new primitives for the basic size of > each relevant C type? I'm anxious to hear what Eliot might have to say > about this since he's got about 2000x more experience with this than I > do. > > There's actually four 64bit data models, though I believe that pretty much every mainstream 64 bit platform is LP64 except MS Windows. Though no doubt someone is waiting to prove me wrong :) BTW, I just read about an embedded processor with 32 bit pointers, 32 bit integers but 40 bit(!) longs. Now that's nasty.

Sept. 16, 2009

Re: [Pharo-project] contents of file

by Tudor Girba

Lukas pointed me to CrLfFileStream which seems to do the job: (CrLfFileStream readOnlyFileNamed: fullPath) contentsOfEntireFile Also, it looks like readOnlyFileFullyNamed: is an extension and that I should use readOnlyFileNamed: Please tell me if I am missing something else. Cheers, Doru On 16 Sep 2009, at 22:33, Tudor Girba wrote: > Hi, > > I want to obtain the contents of a file. I am doing the followings: > (FileStream readOnlyFileFullyNamed: fullPath) contentsOfEntireFile > > However, what I get is a string with tabs instead of new lines. I am > on a Mac, and the file I am using is UTF8 using LF. Can anyone tell me > what I am doing wrong? > > Cheers, > Doru > > -- > www.tudorgirba.com > > "Not knowing how to do something is not an argument for how it cannot > be done." > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- www.tudorgirba.com "Reasonable is what we are accustomed with."

Sept. 16, 2009

Re: [Pharo-project] Fixes for image segments

by StÃ©phane Ducasse

Thanks nicolas I could not find enough energy to work on the closure fixes... so far. stef > I just fixed Symbol allInstances -> Symbol allSymbols in > http://source.squeak.org/trunk/System-nice.148.mcz > This was already in Pharo I think, however, Eliot did some other > changes that might be worth to check. > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Sept. 16, 2009