January 2010 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Does someone know why Nile is in Dev images?

by Mariano Martinez Peck

Sorry Stef but I disagree. PLEASE don't misunderstand me. I know a lot of very good people have worked and is still working in Nile project. So, I am sure it is an excellent product. However, I don't think it should be in Dev image. Dev image is for "Developers". So, we put tools like NewInspector, RoelTyper, E and OCompletion, Refactoring, etc. But why Nile ? I am not agree this is neither a way to push Nile to be used. It is no difference if you already have the code in the image or not, it is just one click of difference (as you have the Nile-All). Even if it where the case, I think it should be in Core image. The way to push a project to be used is to write documentation, tutorials, show the benefits over other implementations....and so on. If Moose use it, ok, put it as a dependency. Now you have a Metacello configuration for Moose :) I mean, in SqueakDBX we use FFI and we don't put in the image. Seaside uses Slime and it is not in the image. Just my opinion. I hope no one feels offended. What others think about this ? Cheers Mariano On Sun, Jan 3, 2010 at 11:02 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > Nile is in dev because it should be progressively use to replace existing > streams. > For example in Moose some important collection extensions depend on it. > > > > Does another package of the dev image depends on Nile? If not, I don't > understand why it is part of the dev image. I see it as any other external > package but not a "dev tool" that should be included. > > > > Thanks > > > > Mariano > > _______________________________________________ > > 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 >

Jan. 3, 2010

[Pharo-project] Fwd: ChangeSorter vs. ChangeOrganizer as entry point

by StÃ©phane Ducasse

> > > > Hi guys > > may be one of you can confirm but I have the impression that the code > should use ChangesOrganizer instead of ChangeSorter for example in fileIntoNewChangeSet. > I do not see why we should rely on tools and instead of model? > > Stef > >

Jan. 3, 2010

Re: [Pharo-project] Code Critics pragmas for classes - do they need to be on instance *and* class side?

by Lukas Renggli

> Yes, that's how it is implemented ;-) I mean, if it is added to the class-side it affects the class-side, and if it is added to the instance-side it affects the instance-side. We can change it that it affects both sides, if this is what everybody wants? Lukas -- Lukas Renggli http://www.lukas-renggli.ch

Jan. 3, 2010

Re: [Pharo-project] Error when passing file (without full path) at startup

by StÃ©phane Ducasse

John here is what I get with VM500 /Applications/Squeak/Squeak500b96432.app/Contents/MacOS/Squeak PharoCore-1.0-10503rc1.1.image test.st 2010-01-03 11:40:32.135 Squeak[46852:903] Can't open input server /Library/InputManagers/Inquisitor 2010-01-03 11:40:32.139 Squeak[46852:903] openFile state 1 with file PharoCore-1.0-10503rc1.1.image 2010-01-03 11:40:32.139 Squeak[46852:903] openFile state 0 with file test.st Stef On Jan 2, 2010, at 11:56 PM, John M McIntosh wrote: > Hey so what does a V5 VM do? > > why don't you try with a './' > >> /Applications/Squeak/Squeak\ 4.2.2beta1U.app/Contents/MacOS/Squeak\ VM\ Opt PharoCore-1.0-10503rc1.1.image ./test.st > > At 3.8.19b1 I did > sqMacMain.c drop cwd to VM directory at startup time to help script writers use ../ or ./ > > which commented out this > > /* LETS NOT DO THIS, SEE what happens for people wanting to do ./Squeak.app foobar.image zingger.st > > { > // Change working directory, this works under os-x, previous logic worked pre os-x 10.4 > > char target[4097],temp[4097]; > getVMPathWithEncoding(target,gCurrentVMEncoding); > sqFilenameFromStringOpen(temp,(sqInt) target, strlen(target)); > chdir(temp); > } > */ > > > > > On 2010-01-02, at 2:22 PM, StÃ©phane Ducasse wrote: > >> Hi >> >> Can somebody confirm that he gets the same error than me with the following code expression >> >> /Applications/Squeak/Squeak\ 4.2.2beta1U.app/Contents/MacOS/Squeak\ VM\ Opt PharoCore-1.0-10503rc1.1.image test.st >> >> where test.st is deadline >> >> Beeper beep >> >> >> <test.st> >> >> I get Error: No content to install >> >> I also get the same error with PharoCore1.1ALPHA Latest update: #11131 >> >> Now if I use >> >> /Applications/Squeak/Squeak\ 4.2.2beta1U.app/Contents/MacOS/Squeak\ VM\ Opt PharoCore-1.0-10503rc1.1.image /Users/ducasse/Workspace/FirstCircle/ActiveResearch/Pharo/Pharo/Coral/test.st >> >> it is working I thought that the passed argument was resolved using the current directory. >> John I remember that you change that is it true? >> >> >> Stef_______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > -- > =========================================================================== > John M. McIntosh <johnmci(a)smalltalkconsulting.com> Twitter: squeaker68882 > Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com > =========================================================================== > > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Jan. 3, 2010

[Pharo-project] Worth squeak changes

by StÃ©phane Ducasse

Here is a list of features that we should avoid to reinvent/reimplement. If you want to help there is space. Stef > From: Andreas Raab <andreas.raab(a)gmx.de> > Date: January 2, 2010 2:32:10 PM GMT+01:00 > To: The general-purpose Squeak developers list <squeak-dev(a)lists.squeakfoundation.org> > Subject: [squeak-dev] Updated trunk image (Squeak3.11-8720-alpha.zip) > Reply-To: The general-purpose Squeak developers list <squeak-dev(a)lists.squeakfoundation.org> > > Folks - > > After a whole batch of changes, I'v put an updated trunk image up at > > http://ftp.squeak.org/trunk/Squeak3.11-8720-alpha.zip > > Loads of great new stuff in there as you can see from the summary of changes below. Since the summary is getting a bit too long for my taste, I'm starting to only include the three most recent updates in email - if you want the full list please download the image and refer to the full summary in the "What's new" window. And if people disagree with this policy I'd be happy to change it again - I'm just trying to cut down on the spam factor a little. So let me know what you think. > > Cheers, > - Andreas > > (for the full history refer to the "What's new" section in the image) > > [------------------------- updated 01/02/10 ---------------------------] > > NanoTraits > ---------- > A new traits implementation has been added. The implementation is significantly smaller and simpler than the old version and can be unloaded and reloaded without loss of information (i.e., traits flattened during unload are restored during traits reloading). To unload traits simply execute: > Trait unloadTraits. > To restore traits load the traits package from the repository at source.squeak.org. > **** already in the bugtracker => TextDiffBuilder > --------------- > A new algorithm for producing text diffs has been added. The algorithm is smaller, faster, and provides better results compared to the previous implementation. > **** we should have a look => Source / Changes Files > > ---------------------- > Sources and changes files are no longer limited to 32MB max size. ExpandedSourceFileArray provides an implementation for source files of arbitrary length, based on the CompiledMethodTrailer changes. > **** already in Pharo => CompiledMethodTrailer > > --------------------- > Handling compiled method trailers for storing source code has been generalized. The new representation deals more explicitly with various forms of encodings (source pointer, temps-only, etc) and has room for future extensions (i.e., retrieval from other sources). > > Future Messages > --------------- > Support for the future/future: keywords has been added. Future messages enable sending messaging at a later point in time. Timed futures allow sending messages a specific number of miliseconds into the future, futures without arguments are executed at the earliest convenience. For example a message like: > > MyMorph>>mouseDown: event > self color: Color red. > (self future: 1000) color: Color white. > > will turn the given morph red and one second later back to white. > > [------------------------- updated 12/12/09 ---------------------------] > > Image Version > ------------- > The new version scheme is now active. The image version number is the sum of all package versions. A stub package "Squeak-Version" has been added to define the "base" number for the version. This image is designated as "Squeak3.11.alpha". > In general we should have a look at ToolBuilder improvements > Morphic > ------- > New window resizers better in tone with the general UI look. A new UserDialogBoxMorph for simple modal inform/confirm dialogs. > **** we should have a look => Files > > ----- > StandardFilestream now performs read-buffering, dramatically speading up some operations like "Object compileAll" (2x improvement) as well as various other operations (scanning change lists etc). > **** we should have a look => Numbers > > ------- > Implementations for Float #predecessor, #successor etc. Update to the compact class indexes of LargePositiveInteger and LargeNegativeInteger for Cog. Additional tests for all of the new features. > > **** already in Pharo => Exceptions > ---------- > OutOfMemory has been added as a standard exception being signaled when an allocation fails, replacing the previous signaling of the low space semaphore. **** we should have a look => > Improved #ensure: performance avoiding remote context manipulation (via #tempAt:put:) in the default case. > > SUnit > ----- > Faster execution by speeding up some low level operations (like allTestSelectors). Fixes for thumbnail creation which would leave open morphs around after some tests. > **** Martin is working on that I imagine => Kernel > > ------ > The default hash for all objects is now a scaled identity has to avoid extreme degradations in speed when using large numbers of objects without explicit hash implementation in Dictionary and Set. > > [------------------------- updated 11/28/09 ---------------------------] > > Menu Bar > -------- > Squeak now has a standard menu bar to make it easier to discover its contents for new users, replacing the World menu as the prime source for launching tools and other activities. > **** from pharo => Compiler > -------- > Support for literal ByteArray syntax has been added. Byte arrays can now be written as #[1 2 3 "..."] instead of #(1 2 3) asByteArray avoiding the need for conversion and a more compact default representation. > > *** in pharo => Numbers > ------- > Some prime related changed: Integer>>isPrime is now a deterministic test, Integer>>isProbablyPrime a probabilistic variant. Intger>>highBit and Integer>>lowBit have been sped up significantly. > *** in pharo => CRLF Handling > > ------------- > CR and LF are now treated interchangeably in rendering. Both cause a line break and both are not displayed. Various line related methods have been updated to deal with both CR and LF. > > Collections > ----------- > Dictionary is no longer a subclass of Set. HashedCollection is the new superclass for both Set and Dictionary. ***Normally in pharo but not sure > Conversion of OrderedCollection and SortedCollection to Arrays has been sped up significantly. > >

Jan. 3, 2010

Re: [Pharo-project] Code Critics pragmas for classes - do they need to be on instance *and* class side?

by Lukas Renggli

> It seems only to work when the pragma is on both instance and class side. Is > this the intention? Yes, that's how it is implemented ;-) Lukas -- Lukas Renggli http://www.lukas-renggli.ch

Jan. 3, 2010

Re: [Pharo-project] Does someone know why Nile is in Dev images?

by StÃ©phane Ducasse

Nile is in dev because it should be progressively use to replace existing streams. For example in Moose some important collection extensions depend on it. > Does another package of the dev image depends on Nile? If not, I don't understand why it is part of the dev image. I see it as any other external package but not a "dev tool" that should be included. > > Thanks > > Mariano > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Jan. 3, 2010

Re: [Pharo-project] Error when passing file (without full path) at startup

by StÃ©phane Ducasse

On Jan 2, 2010, at 11:56 PM, John M McIntosh wrote: > Hey so what does a V5 VM do? I will try it. I was not sure that it worked with default images. Now there are three variables location of the vm location of the image location of the script ideally the two first ones do not have to be in the same place than the script. > ./Squeak.app foobar.image zingger.st does not show that zingger.st can be in another place than the vm or image. > why don't you try with a './' OK it is working but this is not really natural to run a script stating ./fileName instead of fileName > >> /Applications/Squeak/Squeak\ 4.2.2beta1U.app/Contents/MacOS/Squeak\ VM\ Opt PharoCore-1.0-10503rc1.1.image ./test.st > > At 3.8.19b1 I did > sqMacMain.c drop cwd to VM directory at startup time to help script writers use ../ or ./ > > which commented out this > > /* LETS NOT DO THIS, SEE what happens for people wanting to do ./Squeak.app foobar.image zingger.st > > { > // Change working directory, this works under os-x, previous logic worked pre os-x 10.4 > > char target[4097],temp[4097]; > getVMPathWithEncoding(target,gCurrentVMEncoding); > sqFilenameFromStringOpen(temp,(sqInt) target, strlen(target)); > chdir(temp); > } > */ > > > > > On 2010-01-02, at 2:22 PM, StÃ©phane Ducasse wrote: > >> Hi >> >> Can somebody confirm that he gets the same error than me with the following code expression >> >> /Applications/Squeak/Squeak\ 4.2.2beta1U.app/Contents/MacOS/Squeak\ VM\ Opt PharoCore-1.0-10503rc1.1.image test.st >> >> where test.st is deadline >> >> Beeper beep >> >> >> <test.st> >> >> I get Error: No content to install >> >> I also get the same error with PharoCore1.1ALPHA Latest update: #11131 >> >> Now if I use >> >> /Applications/Squeak/Squeak\ 4.2.2beta1U.app/Contents/MacOS/Squeak\ VM\ Opt PharoCore-1.0-10503rc1.1.image /Users/ducasse/Workspace/FirstCircle/ActiveResearch/Pharo/Pharo/Coral/test.st >> >> it is working I thought that the passed argument was resolved using the current directory. >> John I remember that you change that is it true? >> >> >> Stef_______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > -- > =========================================================================== > John M. McIntosh <johnmci(a)smalltalkconsulting.com> Twitter: squeaker68882 > Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com > =========================================================================== > > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Jan. 3, 2010

Re: [Pharo-project] [Seaside] Mac VM 5.2b1 ships

by Lukas Renggli

Hi John > As a reminder I do need more people to use it as their development platform so we can work out any bugs. It would make testing much easier if you provided a direct download link. It usually takes me a couple of minutes to find the right file, which is not ideal if you would like to get as much feedback as possible. Also the slash in the package name makes things more difficult than necessary. For my comments below I am referring to "experimental/64bit/32bitImage*64bitVM/Squeak 64\/32 5.2b1.app", which seems to have a timestamp from today. - Running the Seaside 3.0 tests reproducibly results in the attached crash of the VM (seaside-crash.txt). - Running the Seaside 2.8, Pier, Magritte, Refactoring and OB tests work fine. I also worked a bit with the VM and couldn't observe other problems. The clipboard works well. Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch

Jan. 3, 2010

[Pharo-project] Mac VM 5.2b1 ships

by John M McIntosh

I've push the latest cocoa based 32/64bit macintel/powerpc VM to the folder experimental/64bits in the regular places found via http://smalltalkconsulting.com/squeak.html Look for the Squeak 64/32 5.2b1.app This *beta* VM runs in 32 or 64 bit mode on macIntel, and 32bit mode on powerpc to support Squeak 32bit images. I've updated the app so that the extended clipboard support is built in so that you can do cut/copy/paste in the latest Pharo image. At the moment the only supported plugin is the FreeType2 (32/64bit mode) and is also included, I hope to rebuild the mac menu logic in a few weeks/days. It is possible the VM will support other plugins, but only if you run it in 32bit mode via get info. As a reminder I do need more people to use it as their development platform so we can work out any bugs. I'll look at building a 64bit vm/ 64bit images if there is interest... =========================================================================== John M. McIntosh <johnmci(a)smalltalkconsulting.com> Twitter: squeaker68882 Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com ===========================================================================

Jan. 3, 2010