- Pharo-dev - lists.pharo.org

[Pharo-project] Fwd: [Pharo-users] Smalltalk server pages
by StÃ©phane Ducasse Jan. 5, 2011

Jan. 5, 2011

Begin forwarded message: > From: Annick Fron <info(a)afceurope.com> > Date: January 5, 2011 12:43:53 PM GMT+01:00 > To: A friendly place where any question about pharo is welcome <pharo-users(a)lists.gforge.inria.fr> > Subject: [Pharo-users] Smalltalk server pages > Reply-To: A friendly place where any question about pharo is welcome <pharo-users(a)lists.gforge.inria.fr> > > Hi, > > and in order to get a minimum of dynamic pages, (I think Seaside will be too large for my memory) what is best to get simple Smalltalk server pages, swazoo or Komhttpserver ? > > Annick Fron

3 2

[Pharo-project] IRC meeting next Tuesday, January 4, at ...?
by Adrian Lienhard Jan. 5, 2011

Jan. 5, 2011

Hi all, During the last meeting [1] we decided to do the next one on January 4 but we didn't decide when to start. The previous meeting started at 20:00 CET/UTC/GMT+1, which may not be optimal for people in other time zones. If somebody likes to suggest another time, please let us know soon! Cheers, Adrian [1] http://pharo-project.org/news?article=irc-meeting-notes

5 6

Re: [Pharo-project] [Pharo-users] Minimal pharo
by Mariano Martinez Peck Jan. 5, 2011

Jan. 5, 2011

Hi Annick. I don't know which image they told you, but if you take a PharoCore 1.1.1 from here: http://www.pharo-project.org/pharo-download/stable-core And you evaluate: ScriptLoader new cleanUpForRelease. And then save and quite, the image is 6.8 MB. Another hack I sometimes do is o put all all classes with the default category. You can still can browse and recompile the whole image. Most production enviroments don't care about categories...they make sense when developing. (not everybody agree). But anyway, if you then evaluate: Smalltalk allClassesAndTraitsDo: [:each | each zapOrganization ]. Symbol compactSymbolTable. Smalltalk garbageCollect Then the resulted image is 6.1 mb ;) If you then evaluate: "Compact all MethodDictionary instances" | oldInstances newInstances | oldInstances := MethodDictionary allInstances. newInstances := oldInstances collect: [ :md | (MethodDictionary new: md size) compactCopyFrom: md; yourself]. oldInstances elementsForwardIdentityTo: newInstances. "Different cleanUps" TextStyle allSubInstancesDo: [:ts | ts newFontArray: (ts fontArray copyFrom: 1 to: (2 min: ts fontArray size))]. "Clean all Monticello related stuff. You won't be able to browse packages for example" MCWorkingCopyBrowser allInstancesDo: [:each | each flushAllCaches ]. MCWorkingCopy allInstancesDo:[:wc| SystemChangeNotifier uniqueInstance noMoreNotificationsFor: wc. wc unregister]. SystemChangeNotifier uniqueInstance noMoreNotificationsFor: MCPackageManager. SystemChangeNotifier uniqueInstance noMoreNotificationsFor: MCWorkingCopy. "Most application don't need sound" SoundService default: nil. SoundService unregister: DummySoundSystem. SystemChangeNotifier uniqueInstance noMoreNotificationsFor: (Smalltalk at: #RecentMessageSet). TranscriptStream newTranscript: ThreadSafeTranscript new. ImageSegment classPool at: #RecentlyRenamedClasses put: Dictionary new. ExternalSettings classPool at: #RegisteredClients put: Set new. Locale classPool at: #LocaleChangeListeners put: nil. "Clean all the changes" ChangeSet resetCurrentToNewUnnamedChange Set. ChangeSet current initialize. ChangeSet classPool at: #AllChangeSets put: (OrderedCollection with: ChangeSet current). Symbol rehash. 3 timesRepeat: [ Smalltalk garbageCollect. Symbol compactSymbolTable ]. You will have a 5.9 MB image :) is that enought? If not, you can start unloading packages. Esteban did a lot of work with this of IPhone images. You can ask him. ps: I wonder if any of those scripts should be added to ScriptLoader Cheers Mariano On Tue, Jan 4, 2011 at 6:48 PM, Annick Fron <info(a)afceurope.com> wrote: > Hi all, > > I have now tried the minimal images indicated by Torsten and Stephane, on > Windows it amounts to 9.1 Mega in memory ... > Would it be smaller on Linux ? > Yet, I still need a shoe horn, having only 8 M ram from which 1.5 is > already taken by the kernel... > Any idea to downsize even more ? > Best regards > > Annick Fron >

5 6

[Pharo-project] ConfigurationOfPharo: now with Mocketry, Autotest, XMLSupport and Helps
by laurent laffont Jan. 5, 2011

Jan. 5, 2011

Hi, I've updated ConfigurationOfPharo 1.2-beta2: Added: - Mocketry - XMLSupport - Autotest - Shortcuts-Help more tests and Help. I've put methods in categories. Can someone check ? For independent Help packages, shouldn't we create a ConfigurationOfPharoHelp ? Cheers, Laurent Laffont Pharo Smalltalk Screencasts: http://www.pharocasts.com/ Blog: http://magaloma.blogspot.com/

3 2

Re: [Pharo-project] Hudson Win setup build
by Marcus Denker Jan. 5, 2011

Jan. 5, 2011

On Jan 5, 2011, at 11:11 AM, Torsten Bergmann wrote: > Would be nice if Hudson could also build > the Pharo windows setup automatically > in the future. Should be easy to setup. > > I know thats not the highest prio but > I wanted to check if it is possible anyway > (dont know what kind of machine the ci server > is currently runnning on). > right now we just have a linux slave builder. This is what IT Services was able to provide. > Since I think VM's are built in the future > via Hudson too there must be access to a > win32 machine anyway. Yes, we will look into setting up a Mac and a Windows slave soon. One idea is to use an older intel mac and install windows there as a virtual machine and use this machine for both windows and mac. Alternatively, Hudson can have Amazon E2C slaves... for windows, that would be an alternative (but an expensive one). Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

2 1

[Pharo-project] Hudson Win setup build
by Torsten Bergmann Jan. 5, 2011

Jan. 5, 2011

Would be nice if Hudson could also build the Pharo windows setup automatically in the future. Should be easy to setup. I know thats not the highest prio but I wanted to check if it is possible anyway (dont know what kind of machine the ci server is currently runnning on). Since I think VM's are built in the future via Hudson too there must be access to a win32 machine anyway. Thx T. -- NEU: FreePhone - kostenlos mobil telefonieren und surfen! Jetzt informieren: http://www.gmx.net/de/go/freephone

1 0

[Pharo-project] Generators for Pharo Xmax wish)
by Ralph Boland Jan. 5, 2011

Jan. 5, 2011

I earlier posted a Xmas wish that Pharo add generators (steal the generators code from Squeak). No one appeared to be familiar with them. The generators code was added to Squeak by Andreas Raas. The class Generator can be found in Squeak as a subclass of Stream. It's about 140 lines of code and, as I said before, is really useful and needed in order for me to port some of the packages I am developing from Squeak to Pharo. Class Generator is tested in class GeneratorTest which also serves as examples of uses of Generators. So please, someone go steal the code! And stealing is easy. For example I stole the following comment on class Generator directly from the class comment: " A Generator transforms callback interfaces into stream interfaces. When a producer algorithm provide results as callbacks (blocks) and a consumer algorithm expects streamable input, a Generator transforms one into the other, for example: | generator | generator := Generator on: [:g| Integer primesUpTo: 100 do:[:prime| g yield: prime]]. [generator atEnd] whileFalse:[Transcript show: generator next]. " Regards, Ralph Boland

4 4

[Pharo-project] Best way for change a window style
by Torsten Bergmann Jan. 5, 2011

Jan. 5, 2011

> Finally I implemented the posibility of create a custom windows in > CLFramework. That really rocks! Looks cool. And I'm glad that you continue working on it since the result is really impressive. One of my goals this year is to find the time to have a look at UI framework and to start building one or the other small helper tool with it to give feedback. Is it working with 1.2 already? What is planned next! Thanks Torsten -- Neu: GMX De-Mail - Einfach wie E-Mail, sicher wie ein Brief! Jetzt De-Mail-Adresse reservieren: http://portal.gmx.net/de/go/demail

1 0

[Pharo-project] Help system for pharo [WAS ] Re: ConfigurationOfPharo: now with Mocketry, Autotest, XMLSupport and Helps
by Mariano Martinez Peck Jan. 4, 2011

Jan. 4, 2011

On Tue, Jan 4, 2011 at 10:46 PM, laurent laffont <laurent.laffont(a)gmail.com>wrote: > Hi, > > I've updated ConfigurationOfPharo 1.2-beta2: > Added: > - Mocketry > - XMLSupport > - Autotest > - Shortcuts-Help > > more tests and Help. > > Excellent!!!! :) > I've put methods in categories. > > Can someone check ? > > For independent Help packages, shouldn't we create a > ConfigurationOfPharoHelp ? > > Uhh this is a good question....let me write what it just came to my mind: - For external packages (external to PharoCore), they each have packages for tests, core, blah. Those that have Help pages, then it would be really cool to have a separate package for them. - For each external package, they need to only to put Help pages in a separate package, but also create a group for them in the Metacello Configuration. Then, people can choose what to load. - PharoDev should include the metacello groups that contains the Help. Now...regarding this example, about the shortcuts...that is related to PharoCore...So, we have to options: 1) Cotinue commiting them in 'http://www.squeaksource.com/HelpSystem' and create a ConfigurationOfPharoHelp that we load for the dev image 2) Commit them into PharoCore and then remove them in #cleanUpForProduction I am not sure which I like more, but I think 2). Since we have Help already integrated in the core, the idea is to use it, isn't it ? otherwise this should be in the dev image. And I like to have the Help as closer as possible to the real code. So, I choose for 2), but of course, I am all ears. Cheers Mariano > Cheers, > > Laurent Laffont > > Pharo Smalltalk Screencasts: http://www.pharocasts.com/ > Blog: http://magaloma.blogspot.com/ >

1 0

Re: [Pharo-project] Pharo and CommandShell on OSX ?
by Stef T Jan. 4, 2011

Jan. 4, 2011

On Jan 3, 2011, at 7:25 PM, David T. Lewis wrote: > On Mon, Jan 03, 2011 at 06:55:45PM -0800, Stef T wrote: >> 1) CommandShell complains about AioPlugin not being present and that it will use the 'old slow' way. That's fine, it's merely a warning > > AFAIK, noone has tried building the AioPlugin for Mac, so you will get this > warning when running on a Mac. But as you say, it's just a warning. Is there a pointer for the source code ? I am pretty handy with Xcode and don't mind giving it a whirl ;) > >> but >> 2) None of the commands get executed. If I try the stuff which will eval inside squeak/pharo, then that's fine (Eg; stdout nextPutAll: 'hello world'; cr.). However, if I try a command such as 'ls' or 'who', all hell breaks lose. stack trace follows :) >> >> If I am doing anything obviously wrong, please feel free to hit me over the head :) > > Nope, it's not you, it's the plugin included with your VM. Some > of the Mac VMs in circulation were accidentally built with a very > out of date version of the OSProcessPlugin. Apparently you have > one of them, and it will definitely not work. But I think there > is a newer version (4.2.5 IIRC) that has the up to date plugin > that works properly on Mac. > Hrm, I am using the OSProcess from squeaksource .59. The version history says Name: OSProcess-dtl.59 Author: dtl Time: 28 November 2010, 8:43:48.839 pm UUID: bd5d2b4e-efbd-4091-ac0a-d0bd7af64b2c surely this is 'new enough' ? Is there a known 'stable' version you would suggest ? regards S. > Dave > > >> >> Regards >> S. >> >> >> >> >> 3 January 2011 6:49:43 pm >> >> VM: Mac OS - intel - 1065 - Squeak3.8.1 of '28 Aug 2006' [latest update: #6747] Squeak VM 4.2.4b1 >> Image: Pharo-1.1-11406-rc3 [Latest update: #11406] >> >> SecurityManager state: >> Restricted: false >> FileAccess: true >> SocketAccess: true >> Working Dir /Users/stef/squeak/SeaSide-3.0 >> Trusted Dir /foobar/tooBar/forSqueak/bogus >> Untrusted Dir /Users/stef/Library/Preferences/Squeak/Internet/My Squeak >> >> UndefinedObject(Object)>>mustBeBooleanIn: >> Receiver: nil >> Arguments and temporary variables: >> context: BufferedAsyncFileReadStream>>moveAvailableDataFrom: >> proceedValue: nil >> Receiver's instance variables: >> nil >> >> UndefinedObject(Object)>>mustBeBoolean >> Receiver: nil >> Arguments and temporary variables: >> >> Receiver's instance variables: >> nil >> >> BufferedAsyncFileReadStream>>moveAvailableDataFrom: >> Receiver: BufferedAsyncFileReadStream: 'pipeReader' >> Arguments and temporary variables: >> sqFile: #[48 205 236 155 72 91 120 160 0 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0] >> bufferSize: 1000 >> buffer: '...etc... >> count: #(0) >> Receiver's instance variables: >> >> >> BufferedAsyncFileReadStream>>moveAvailableDataToBuffer >> Receiver: BufferedAsyncFileReadStream: 'pipeReader' >> Arguments and temporary variables: >> >> Receiver's instance variables: >> >> >> BufferedAsyncFileReadStream>>update: >> Receiver: BufferedAsyncFileReadStream: 'pipeReader' >> Arguments and temporary variables: >> aParameter: a PseudoAioEventHandler >> Receiver's instance variables: >> >> >> [] in PseudoAioEventHandler(Object)>>changed: >> Receiver: a PseudoAioEventHandler >> Arguments and temporary variables: >> aParameter: BufferedAsyncFileReadStream: 'pipeReader' >> aDependent: a PseudoAioEventHandler >> Receiver's instance variables: >> dependents: a DependentsArray(BufferedAsyncFileReadStream: 'pipeReader') >> eventGenerator: a Process in Debugger class>>openOn:context:label:contents:full...etc... >> >> DependentsArray>>do: >> Receiver: a DependentsArray(BufferedAsyncFileReadStream: 'pipeReader') >> Arguments and temporary variables: >> aBlock: [:aDependent | aDependent update: aParameter] >> dep: BufferedAsyncFileReadStream: 'pipeReader' >> i: 1 >> iLimiT: 1 >> Receiver's instance variables: >> a DependentsArray(BufferedAsyncFileReadStream: 'pipeReader') >> >> PseudoAioEventHandler(Object)>>changed: >> Receiver: a PseudoAioEventHandler >> Arguments and temporary variables: >> aParameter: a PseudoAioEventHandler >> Receiver's instance variables: >> dependents: a DependentsArray(BufferedAsyncFileReadStream: 'pipeReader') >> eventGenerator: a Process in Debugger class>>openOn:context:label:contents:full...etc... >> >> PseudoAioEventHandler(Object)>>changed >> Receiver: a PseudoAioEventHandler >> Arguments and temporary variables: >> >> Receiver's instance variables: >> dependents: a DependentsArray(BufferedAsyncFileReadStream: 'pipeReader') >> eventGenerator: a Process in Debugger class>>openOn:context:label:contents:full...etc... >> >> [] in [] in PseudoAioEventHandler>>eventGeneratorProcess >> Receiver: a PseudoAioEventHandler >> Arguments and temporary variables: >> d: a Delay(125 msecs) >> Receiver's instance variables: >> dependents: a DependentsArray(BufferedAsyncFileReadStream: 'pipeReader') >> eventGenerator: a Process in Debugger class>>openOn:context:label:contents:full...etc... >> >> BlockClosure>>repeat >> Receiver: [self changed. >> d wait] >> Arguments and temporary variables: >> >> Receiver's instance variables: >> outerContext: [] in PseudoAioEventHandler>>eventGeneratorProcess >> startpc: 59 >> numArgs: 0 >> >> [] in PseudoAioEventHandler>>eventGeneratorProcess >> Receiver: a PseudoAioEventHandler >> Arguments and temporary variables: >> d: a Delay(125 msecs) >> Receiver's instance variables: >> dependents: a DependentsArray(BufferedAsyncFileReadStream: 'pipeReader') >> eventGenerator: a Process in Debugger class>>openOn:context:label:contents:full...etc... >> >> [] in BlockClosure>>newProcess >> Receiver: [[self changed. >> d wait] repeat] >> Arguments and temporary variables: >> >> Receiver's instance variables: >> outerContext: PseudoAioEventHandler>>eventGeneratorProcess >> startpc: 54 >> numArgs: 0 >> >> >> --- The full stack --- >> UndefinedObject(Object)>>mustBeBooleanIn: >> UndefinedObject(Object)>>mustBeBoolean >> BufferedAsyncFileReadStream>>moveAvailableDataFrom: >> BufferedAsyncFileReadStream>>moveAvailableDataToBuffer >> BufferedAsyncFileReadStream>>update: >> [] in PseudoAioEventHandler(Object)>>changed: >> DependentsArray>>do: >> PseudoAioEventHandler(Object)>>changed: >> PseudoAioEventHandler(Object)>>changed >> [] in [] in PseudoAioEventHandler>>eventGeneratorProcess >> BlockClosure>>repeat >> [] in PseudoAioEventHandler>>eventGeneratorProcess >> [] in BlockClosure>>newProcess >> >

6 8