November 2011 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] FSReference

by Sean P. DeNigris

Sean P. DeNigris wrote: > > Would it be valuable to have FSFileReference and FSDirectoryReference > subclasses? > Another weird ramification of FSReference's identity ambiguity is, on a reference to an existing file: * #allChildren -> anArray containing only the file itself * children -> an error -- View this message in context: http://forum.world.st/FSReference-tp3985640p3985818.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Nov. 3, 2011

Re: [Pharo-project] [Pharo-users] Brainstorming on the roadmap for first Pharo Consortium Engineer :)

by Norbert Hartl

Am 03.11.2011 um 13:13 schrieb Guido Stepken: > Should be very easy to introduce reference pointers towards a number of additional images.... > Well, sure. Drop us a note when you have it ready. Norbert > Am 03.11.2011 um 13:05 schrieb Norbert Hartl <norbert(a)hartl.name>: > >> >> Am 03.11.2011 um 12:57 schrieb Guido Stepken: >> >>> I always thought, the IMAGE *is* already an OO database!?? >>> >> Yes, it is an OO database with a restriction in the size of your volatile memory (unless you use GemStone or LOOM) >> >> Norbert >> >>> Guido Stepken >>> >>> Am 02.11.2011 um 15:27 schrieb Igor Stasenko <siguctua(a)gmail.com>: >>> >>>> How about new source code management? >>>> >>>> In terms of: >>>> - better abstraction of source code access in image >>>> - create a shared repository (database) , which can be used to browse >>>> the history of all source code of Pharo and its predecessor up to >>>> Squeak 1.0. >>>> >>>> We are discussed this idea couple times, and we already having some >>>> pieces of puzzle , like Ring. >>>> Also, there is already a project made by someone (forgot the name) , >>>> who already storing all source code in database and managing it there. >>>> >>>> -- >>>> Best regards, >>>> Igor Stasenko. >>>> >>> >> >> >

Nov. 3, 2011

[Pharo-project] SortDescriptors

by HwaJong Oh

I've ported NSSortDescriptor to Pharo. It works well with SortedCollection and has more features. Gofer new squeaksource: 'DaliotsPlayground'; package: 'ConfigurationOfDaliotsPlayground'; load. (Smalltalk at: #ConfigurationOfDaliotsPlayground) project lastVersion load: 'SortDescriptors'. Take a look the class comment and unittests. HwaJong Oh -- View this message in context: http://forum.world.st/SortDescriptors-tp3985696p3985696.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Nov. 3, 2011

[Pharo-project] FSReference

by Sean P. DeNigris

I'm /really/ enjoying FS (I couldn't wait so I loaded it into 1.3-rc; all working so far). I keep finding myself writing things like: FSReference>>doSomething "double dispatch extension method" self isDirectory ifTrue: [ ... ] ifFalse: [ ... ]. I feel dirty every time, but FS doesn't make this piece of a reference's identity explicit. Would it be valuable to have FSFileReference and FSDirectoryReference subclasses? It would certainly make my code cleaner as I could then double dispatch without conditionals. Thanks. Sean -- View this message in context: http://forum.world.st/FSReference-tp3985640p3985640.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Nov. 3, 2011

[Pharo-project] adding author to compiledMethod and authors to class.

by StÃ©phane Ducasse

http://code.google.com/p/pharo/issues/detail?id=4971

Nov. 3, 2011

Re: [Pharo-project] [Pharo-users] Brainstorming on the roadmap for first Pharo Consortium Engineer :)

by Guido Stepken

Should be very easy to introduce reference pointers towards a number of additional images.... Am 03.11.2011 um 13:05 schrieb Norbert Hartl <norbert(a)hartl.name>: > > Am 03.11.2011 um 12:57 schrieb Guido Stepken: > >> I always thought, the IMAGE *is* already an OO database!?? >> > Yes, it is an OO database with a restriction in the size of your volatile memory (unless you use GemStone or LOOM) > > Norbert > >> Guido Stepken >> >> Am 02.11.2011 um 15:27 schrieb Igor Stasenko <siguctua(a)gmail.com>: >> >>> How about new source code management? >>> >>> In terms of: >>> - better abstraction of source code access in image >>> - create a shared repository (database) , which can be used to browse >>> the history of all source code of Pharo and its predecessor up to >>> Squeak 1.0. >>> >>> We are discussed this idea couple times, and we already having some >>> pieces of puzzle , like Ring. >>> Also, there is already a project made by someone (forgot the name) , >>> who already storing all source code in database and managing it there. >>> >>> -- >>> Best regards, >>> Igor Stasenko. >>> >> > >

Nov. 3, 2011

Re: [Pharo-project] [Pharo-users] Brainstorming on the roadmap for first Pharo Consortium Engineer :)

by Norbert Hartl

Am 03.11.2011 um 12:57 schrieb Guido Stepken: > I always thought, the IMAGE *is* already an OO database!?? > Yes, it is an OO database with a restriction in the size of your volatile memory (unless you use GemStone or LOOM) Norbert > Guido Stepken > > Am 02.11.2011 um 15:27 schrieb Igor Stasenko <siguctua(a)gmail.com>: > >> How about new source code management? >> >> In terms of: >> - better abstraction of source code access in image >> - create a shared repository (database) , which can be used to browse >> the history of all source code of Pharo and its predecessor up to >> Squeak 1.0. >> >> We are discussed this idea couple times, and we already having some >> pieces of puzzle , like Ring. >> Also, there is already a project made by someone (forgot the name) , >> who already storing all source code in database and managing it there. >> >> -- >> Best regards, >> Igor Stasenko. >> >

Nov. 3, 2011

Re: [Pharo-project] [Pharo-users] Brainstorming on the roadmap for first Pharo Consortium Engineer :)

by Guido Stepken

I always thought, the IMAGE *is* already an OO database!?? Guido Stepken Am 02.11.2011 um 15:27 schrieb Igor Stasenko <siguctua(a)gmail.com>: > How about new source code management? > > In terms of: > - better abstraction of source code access in image > - create a shared repository (database) , which can be used to browse > the history of all source code of Pharo and its predecessor up to > Squeak 1.0. > > We are discussed this idea couple times, and we already having some > pieces of puzzle , like Ring. > Also, there is already a project made by someone (forgot the name) , > who already storing all source code in database and managing it there. > > -- > Best regards, > Igor Stasenko. >

Nov. 3, 2011

Re: [Pharo-project] [Pharo-users] Brainstorming on the roadmap for first Pharo Consortium Engineer :)

by StÃ©phane Ducasse

Yes but now I was more thinking about what is urgent to get done. Stef > How about new source code management? > > In terms of: > - better abstraction of source code access in image > - create a shared repository (database) , which can be used to browse > the history of all source code of Pharo and its predecessor up to > Squeak 1.0. > > We are discussed this idea couple times, and we already having some > pieces of puzzle , like Ring. > Also, there is already a project made by someone (forgot the name) , > who already storing all source code in database and managing it there. > > -- > Best regards, > Igor Stasenko. >

Nov. 3, 2011

Re: [Pharo-project] Moving a file

by StÃ©phane Ducasse

we should add it. Stef On Nov 3, 2011, at 2:09 AM, Sean P. DeNigris wrote: > Neither the Squeak file system support, nor FS seem to contain logic to move > a file, like Unix's mv command. This seems like a basic piece of > functionality. Why is it missing? > > Thanks. > Sean > > -- > View this message in context: http://forum.world.st/Moving-a-file-tp3983916p3983916.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >

Nov. 3, 2011