- Pharo-dev - lists.pharo.org

[Pharo-project] [ANN] SqueakSource 3 RC 1

by Tobias Pape

Dear All, I hereby release SqueakSource 3 RC 1 to the public. I wasn't able to come up with a nice name this time, so it is just 'the Release Candidate' :) Thanks to Dale, Norbert, and Philippe for their support, to many I met at ESUG'11 who gave good inspiration and anybody who listened and helped. == Improvements since the Beta: - Backgrounding does not fork but use a separate process on Squeak; Service VM on GS. - New feature: "well known name" for a Repo, like Squeaksource or gemsource... (So, that Gofer new gemsource: â¦ can be used in the Repo strings on the project sites) - Improvements in Sitemap building, XML-parser not required, plain Seaside - Pick up newer versions of several, esp. gemstone projects. Email support should be back now. - Fix display of "news" section - Fix for #9: Sorting of Projects can be confusing. - Fix: by default, non-world-read projects are not visible, now. - Fix for #7: "Tags" link responds with MessageNotUnderstood page - Fix for #22: SSProject>>versionAdded: forks a process - Fix for #23: Sitemap generation fails - Fix for #24: SSVersionAlreadyExists thrown by SSVersionView>>move:to: but not handled... - Fix for #27: MNU #ifNotEmpty: in SSEmailSubscription >> versionAdded:to: nukes gem - Fix for #29: add "breathing space" in tables'. - HTTP DELETE for versions (e.g., for future Monticello tool usage) - more tests. == The (up to now) sole instance is the HPIâs Software Architecture Groupâs Squeaksource, wich is not open to registration at the moment. However, I hope the GemStone ss3 instance will be migrated soon (http://ss3.gemstone.com) Install it yourself! Pharo: == Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfSqueakSource'; load. ((Smalltalk at: #ConfigurationOfSqueakSource) project version: '3.0-rc.1') load: #('All') == Squeak: == Installer ss project: 'MetacelloRepository'; load: 'ConfigurationOfSqueakSource'. ((Smalltalk at: #ConfigurationOfSqueakSource) project version: '3.0-rc.1') load: #('All') == GemStone (with ProjectGofer, else like pharo): == Gofer project load: 'SqueakSource' version: '3.0-rc.1' group: #('All'). == To come: === â¢ more tests â¢ moving and copying via backend (i.e., HTTP request) â¢ inboxes â¢ branch projects â¢ (converting squeaksource.com to a SqueakSource3 ;) ) === I hope you like it. Best -Tobias PS: Did you know that â¢ you can get a personal rss stream of your âfavouriteâ projects? (like following on github) â¢ you can set up parent projects for your projects and automatically move all your packages there? â¢ you can extend SqueakSource quite easily? (Example: Issues) â¢ you can install a stripped down version on SqueakSource? (e.g., without Issue tracking, Statistics or filesystem support)

Nov. 16, 2011

Re: [Pharo-project] SystemChangeNotifier and Traits

by Fernando Olivero

Please note that eventually the system is going to be using solely System announcements, instead of the old mechanism in place right now. Did you try hooking up to the SystemAnnouncements? For examples, check out Nautius. Fernando On Tue, Nov 15, 2011 at 9:02 PM, ezequiel lamonica <lamonicaezequiel(a)gmail.com> wrote: > Hello again, > > Now the problem is when I create a class that use Traits, > SystemChangeNotifier sends two messages to report this creation: 1st for > class added without traits, and 2nd for class modified to use this trait. > And this last message has Object as old class instead of ClassForTesting > without traits. > > For example: > > Object subclass: #ClassForTesting > Â Â Â Â uses: TSortable > Â Â Â Â instanceVariableNames: 'a' > Â Â Â Â classVariableNames: '' > Â Â Â Â poolDictionaries: '' > Â Â Â Â category: 'OOSCM-ClientImageTest' > > > Can I change those messages to use only one message that includes traits? Is > not this better? > > What do you suggest? > > > > ----- > eze > -- > View this message in context: http://forum.world.st/SystemChangeNotifier-and-Traits-tp4073962p4073962.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > >

Nov. 16, 2011

Re: [Pharo-project] SystemChangeNotifier and Traits

by Mariano Martinez Peck

On Tue, Nov 15, 2011 at 5:02 PM, ezequiel lamonica < lamonicaezequiel(a)gmail.com> wrote: > Hello again, > > Now the problem is when I create a class that use Traits, > SystemChangeNotifier sends two messages to report this creation: 1st for > class added without traits, and 2nd for class modified to use this trait. > Weird... > And this last message has Object as old class instead of ClassForTesting > without traits. > heheheheh > > For example: > > Object subclass: #ClassForTesting > uses: TSortable > instanceVariableNames: 'a' > classVariableNames: '' > poolDictionaries: '' > category: 'OOSCM-ClientImageTest' > > > Can I change those messages to use only one message that includes traits? > Is > not this better? > >From the outside it looks better, but you never know... > > What do you suggest? > > > > ----- > eze > -- > View this message in context: > http://forum.world.st/SystemChangeNotifier-and-Traits-tp4073962p4073962.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > -- Mariano http://marianopeck.wordpress.com

Nov. 16, 2011

Re: [Pharo-project] ChangeNotifier for recategorize a class

by Mariano Martinez Peck

Hi. I really don't know how the SystemChangeNotifier works, but wouldn't it send TWO notifications in your example? one for the class reshape change (the instance variables) and one for the category change ? is it doing this at least ? On Tue, Nov 15, 2011 at 4:30 PM, ezequiel lamonica < lamonicaezequiel(a)gmail.com> wrote: > Hello, > > I'm working on Pharo 1.3 in a software content management project and I > have > some problems with the SystemChangeNotifier. > I want to get changes between an old class and the new class when I change > its category. > The problem is when I change a category for a class, the > SystemChangeNotifier sends this message: > "class: aClass recategorizedFrom: oldCategory to: newCategory ", but I > can't > get the changes on the new class to get the differences between old class > and new class. > > For example, I want to get the change of instanceVariableNames in addition > of category change: > > I change: > > Object subclass: #ClassForTesting > instanceVariableNames: 'a' > classVariableNames: 'xx2' > poolDictionaries: '' > category: 'OOSCM-ClientImageTest' > > TO: > > Object subclass: #ClassForTesting > instanceVariableNames: 'a b c ' > classVariableNames: 'xx2' > poolDictionaries: '' > category: 'OOSCM-ClientImageTest2' > > Any help? > > > > ----- > eze > -- > View this message in context: > http://forum.world.st/ChangeNotifier-for-recategorize-a-class-tp4073854p407… > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > -- Mariano http://marianopeck.wordpress.com

Nov. 16, 2011

[Pharo-project] About Zinc API

by Esteban Lorenzano

Hi, I just updated my Zinc related projects to the latest version. This is a cool piece of software and I'm really enjoying using it! Thank you! but now... just an observation: I really don't like the ZnEasy facade :( why? because it feels "overdesigned" for me: I think those methods should be on ZnNeoClient directly... of course, that's because you want to prevent a change in the api if something changes in the future... but I think precisely there is where you are overdesigning the framework. Other thing: ZnNeoClient should be just ZnClient in next versions.... yeah... maybe I'm just talking too early and you are already thinking on do that... or maybe I'm just wrong... just wanted to say my impressions about something I think is, in general, really great and a really cool improvement over what we had before. Cheers, Esteban

Nov. 16, 2011

Re: [Pharo-project] The SmalltalkHub demo is online!

by Geert Claes

Nicolas Petton wrote: > > I hope before the end of the year. The next demo will very likely run on > GemStone, then the final app will be hosted by the INRIA. > Good stuff! How about a mirror/failover app that runs at GemStone/VMWare? -- View this message in context: http://forum.world.st/The-SmalltalkHub-demo-is-online-tp4073806p4075717.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Nov. 16, 2011

Re: [Pharo-project] Headless PetitParser

by Alberto Bacchelli

StÃ©phane Ducasse wrote: > > can you give an example so that people can learn too? > Sure. So I have a simple bash script that calls the vm, the image, and the script: ----------------bash script----------- #!/bin/bash export AN_ENVIRONMENT_VARIABLE=somevalue export SCRIPT_LOG_FILE=afilename "$pharovm_dir"/squeak -plugins "$pharovm_dir" -encoding Latin1 -headless "$pharo_image" "$smalltalk_script" && exit 0 echo Something bad happened! exit 1 ---------------------------------------- the $smalltalk_script is an .st file with the code to be executed (an example later). environment variables, such as AN_ENVIRONMENT_VARIABLE and SCRIPT_LOG_FILE, are useful to pass some info to the smalltalk script in an easy way, here we use SCRIPT_LOG_FILE to save some script's output to a file. Here I put a very simple example based on what I did: ----------------pharo script (aka $smalltalk_script)----------- [| fs environment pid | environment := OSProcess thisOSProcess environment. pid := OSProcess thisOSProcess pid. someValue := (environment at: 'AN_ENVIRONMENT_VARIABLE'). fs := FileStream forceNewFileNamed: (environment at: 'SCRIPT_LOG_FILE'). loggingBlock := [:message | fs nextPutAll: TimeStamp now asString, ' [', pid asString, '] ' . fs nextPutAll: message; nextPut: Character lf.]. loggingBlock value: 'Starting script with ', someValue. "do some interesting stuff here" "..." Smalltalk snapshot: false andQuit: true.] on: Error do: [:err | OSProcess thisOSProcess stdErr nextPutAll: err asString; nextPut: Character lf. Smalltalk snapshot: false andQuit: true.] ------------------------------------------ A few comments: - with "OSProcess thisOSProcess environment" you can access environment variables as a dictionary (that's why I use them instead of command line arguments) - "OSProcess thisOSProcess pid" gives you the pid of your process, in this way I can make a unix-like log file - "Smalltalk snapshot: false andQuit: true." closes the image correctly at the end of your script and does NOT save the state on the image. - "[...] on: Error do: [:err | OSProcess thisOSProcess stdErr nextPutAll: err asString; nextPut: Character lf. Smalltalk snapshot: false andQuit: true.]" is _VERY_ useful to debug your code. Any time there is an error in the main block, it catches it and prints the message to the console using the standard error. This is essential to be able not to spend ages in trying to understand what went wrong with your script. That's all. I hope it's useful to someone. Cheers, Alberto -- View this message in context: http://forum.world.st/Headless-PetitParser-tp3994446p4075649.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Nov. 16, 2011

[Pharo-project] Can we display and input chinese?

by Hilaire Fernandes

Hello A friend of me in Taiwan ask me about that because previous version of DrGeo used to work with Chinese display and input. Hilaire -- Education 0.2 -- http://blog.ofset.org/hilaire

Nov. 16, 2011

Re: [Pharo-project] [squeak-dev] The SmalltalkHub demo is online!

by Nicolas Petton

On Tue, 2011-11-15 at 17:56 -0300, Mariano Martinez Peck wrote: > > BTW.... one thing I would love but I think you already answered to me > that yes, is the ability to have a ConfigurationOfSmalltalkHub which > let me take a standard Pharo image and execute: > ConfigurationOfSmalltalkHab loadWithFuelPresistency. > and I can have my own/company/whatever repo running :) Exactly. that's the goal :) Nicolas

Nov. 15, 2011

Re: [Pharo-project] The SmalltalkHub demo is online!

by Nicolas Petton

On Tue, 2011-11-15 at 20:52 +0100, Sven Van Caekenberghe wrote: > On 15 Nov 2011, at 20:18, Nicolas Petton wrote: > > > I'm glad to tell you that the demo of SmalltalkHub is online. > > http://www.smalltalkhub.com > > > > Note that this is a demo only (all projects will be deleted at some point). > > Beautiful ! > > When can we start using this, knowing that the data is kept safe ? I hope before the end of the year. The next demo will very likely run on GemStone, then the final app will be hosted by the INRIA. Nicolas > > Sven >

Nov. 15, 2011