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

Re: [Pharo-project] bootable Pharo image

by Pavel Krivanek

License? There is no new code in it except few shell oneliners :-) Let's say MIT License. btw. you can extend it with any tinyCore package. You can simply mount the package file to the loopback device under squashfs and copy it to the system root directory. mount -o loop -t squashfs pci-utils.tcz outputDirectory So you can easily build for example a small image with Chromium etc. Cheers, -- Pavel On Sun, Nov 6, 2011 at 2:31 PM, S Krish <krishnamachari.sudhakar(a)gmail.com> wrote: > Cool stuff, simple, zipping fast to boot and get to Pharo.. An exciting > playground to build up Pharo tools for everything to make Pharo the GUI for > the tinycore with: > * Run this with VirtualBox.. Â build out everything that is needed and push > it back as embedded to a device..!.. headless / or headful as reqd. > What will be the license on this..? Though components are open source.. > Obliged if Pavel can comment.. > > On Fri, Nov 4, 2011 at 1:33 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > wrote: >> >> thanks pavel. >> Jean-Baptiste may be this can be interesting for your project >> >> >> On Nov 3, 2011, at 11:39 PM, Pavel Krivanek wrote: >> >> > Hi, >> > >> > I tried to prepare a bootable Pharo ISO image based on Tiny Core >> > Linux. Namely on MicroCore (kernel 3.0.3) that was extended with WiFi >> > support. There is standard Pharo 1.3 image with OSProcess and >> > CommandShell installed on the Smalltalk side. The resultant image has >> > about 37 MB. >> > >> > Download: >> > http://www.windmap.cz/playground/pharo/pharo.iso >> > >> > If you want to add it directly to your Grub menu, you may do it >> > without need of extra partition. To the grub.conf add something like: >> > >> > title Pharo >> > Â Â Â root (hd0,1) >> > Â Â Â kernel /boot/pharo/vmlinuz vga=791 quiet >> > Â Â Â initrd /boot/pharo/tinycore.gz >> > >> > where vmlinuz and tinycore.gz are the only files needed from the ISO >> > image. >> > >> > Remastering: >> > >> > unpack: >> > zcat tinycore.gz | sudo cpio -i -H newc -d >> > >> > pack: >> > find | cpio -o -H newc | gzip -2 > ../tinycore.gz >> > >> > better compression: >> > advdef -z4 tinycore.gz >> > >> > create ISO (you need unpacked original ISO image): >> > /bin/cp -pfr tinycore.gz boot >> > mkdir -p newiso >> > /bin/cp -pfr Â boot newiso >> > mkisofs -l -J -R -V TC-custom -no-emul-boot -boot-load-size 4 \ >> > -boot-info-table -b boot/isolinux/isolinux.bin \ >> > -c boot/isolinux/boot.cat -o pharo.iso newiso >> > >> > Cheers, >> > -- Pavel >> > >> >> > >

Nov. 6, 2011

Re: [Pharo-project] Funny DrGeo sketch

by Schwab,Wilhelm K

Small typo: look at the status bar of the second image. It reads "Erase and object..." - should be "an." The second "and" is of course correct. Dumb question: what is it that makes the file so big? At first glance, it looks very simple. Seeing the "hidden constructions" reveals that there has to be more to it. Is it big because of the construction process, or are there other elements that are not rendered? This reminds me of 3D. Some casual browsing through Croquet gave me the impression that their handling of objects, meshes, etc. was/is excellent. IMHO, it was a huge mistake to force 3D immersion from the top. Options are good; mandates are often bad. I have worked around 3D simulations; the group in question is moving from Director to Unity. With the ability to embed 3D in otherwise 2D apps, I think Pharo would be highly competitive with those environments. Bill ________________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] on behalf of Hilaire Fernandes [hilaire.fernandes(a)edu.ge.ch] Sent: Sunday, November 06, 2011 4:18 AM To: pharo-project(a)lists.gforge.inria.fr Subject: [Pharo-project] Funny DrGeo sketch http://blog.ofset.org/hilaire/index.php?post/2011/10/28/Huge-sketch

Nov. 6, 2011

[Pharo-project] KeyboardEvent differences between platforms

by Guillermo Polito

In TextEditor>>initializeShiftCmdKeyShortcuts the shortcuts are set in a way that it creates three handlers for each shortcut to make it work xD. The main difference here is that in Linux, ubuntu 11.04 the Ctrl+a comes with the right keyCharacter, but in Windows and MacOS it does not :(. We've tested that on host OSs with friends :). I've captured the problem I'm experimenting so far and wrote down an ugly hack in this method. KeyboardEvent>>modifiedCharacter self flag: #hack. "Hack me. When Ctrl is pressed, the key ascii value is not right and we have to do this shit" ^(self controlKeyPressed and: [ (#(MacOSX Windows) includes: Smalltalk os current platformFamily) and: [ keyValue <= 26 ]]) ifTrue: [ (self keyValue + $a asciiValue - 1) asCharacter ] ifFalse: [ self keyCharacter ] But I'd like to replace that by: KeyboardEvent>>modifiedCharacter ^self keyCharacter :P Are there any technical reasons why the Sensor behaves like that? How difficult is it to make it work the same for all three vms? Thanks! Guille

Nov. 6, 2011

[Pharo-project] Pharo suffers internal Traffic Jams ...

by Guido Stepken

Hi guys! Please first first have a look at that simulation: http://www.youtube.com/watch?v=EmMY1nq_tgI Surprisingly the architecture of pharo looks very much this. Message sends, "information flow" through a dynamic ambience of "living objects" cause serious "hangs" Unpredictable traffic jams occurr, depending on load, e.g. Seaside, during GC, Image sync, subtile timeouts or countdows, waiting for resources to be freed, network timeouts, database lookups, e.t.c. Those can much easier be identified, when you downclock your machine to good old 50MHz of ancient times of squeak and develop/profile then. Design flows pretty soon become visible then, that are not visible when you proudly use always the newest Apple machine for development. >From advanced Software architects of a new old Smalltalk OS i expect to know about such dynamic phenomenons, having deep insight into analytically identifying such normally difficult to indentifying problems, that always should be part of TDD ... Tnx for reading and understanding. Have fun! Guido Stepken

Nov. 6, 2011

Re: [Pharo-project] bootable Pharo image

by S Krish

Cool stuff, simple, zipping fast to boot and get to Pharo.. An exciting playground to build up Pharo tools for everything to make Pharo the GUI for the tinycore with: * Run this with VirtualBox.. build out everything that is needed and push it back as embedded to a device..!.. headless / or headful as reqd. What will be the license on this..? Though components are open source.. Obliged if Pavel can comment.. On Fri, Nov 4, 2011 at 1:33 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>wrote: > thanks pavel. > Jean-Baptiste may be this can be interesting for your project > > > On Nov 3, 2011, at 11:39 PM, Pavel Krivanek wrote: > > > Hi, > > > > I tried to prepare a bootable Pharo ISO image based on Tiny Core > > Linux. Namely on MicroCore (kernel 3.0.3) that was extended with WiFi > > support. There is standard Pharo 1.3 image with OSProcess and > > CommandShell installed on the Smalltalk side. The resultant image has > > about 37 MB. > > > > Download: > > http://www.windmap.cz/playground/pharo/pharo.iso > > > > If you want to add it directly to your Grub menu, you may do it > > without need of extra partition. To the grub.conf add something like: > > > > title Pharo > > root (hd0,1) > > kernel /boot/pharo/vmlinuz vga=791 quiet > > initrd /boot/pharo/tinycore.gz > > > > where vmlinuz and tinycore.gz are the only files needed from the ISO > image. > > > > Remastering: > > > > unpack: > > zcat tinycore.gz | sudo cpio -i -H newc -d > > > > pack: > > find | cpio -o -H newc | gzip -2 > ../tinycore.gz > > > > better compression: > > advdef -z4 tinycore.gz > > > > create ISO (you need unpacked original ISO image): > > /bin/cp -pfr tinycore.gz boot > > mkdir -p newiso > > /bin/cp -pfr boot newiso > > mkisofs -l -J -R -V TC-custom -no-emul-boot -boot-load-size 4 \ > > -boot-info-table -b boot/isolinux/isolinux.bin \ > > -c boot/isolinux/boot.cat -o pharo.iso newiso > > > > Cheers, > > -- Pavel > > > > >

Nov. 6, 2011

Re: [Pharo-project] Keymapping Questions

by Guillermo Polito

Sean P. DeNigris wrote: > Guillermo Polito wrote: > > > > Hmm, strange. There are two implementations of this method in my image. > > One in KMShortcut and one in KMNoShortcut, one does nothing (on purpose > > with a comment :P) but the other has an implementation :/... > > > I may not be understanding correctly, but they seem backwards (i.e. > NoShortcut is doing something and Shortcut is not). Although (see below)... > Haha! You are right :). Since I introduced the concept of defaultShortcuts vs current shortcuts, that was meaningless! I only had to replace the defaultShortcut without doing any of that. Thanks! Guille, hungry of feedback :)

Nov. 6, 2011

Re: [Pharo-project] about name for logging message

by David T. Lewis

It is OSProcess class>>trace and OSProcess class>>trace: so there is no conflict at all. I mentioned it only as a data point. I chose the name "trace" because it is used for debugging, and the intent is to trace the flow of execution by putting e.g. "OSProcess trace: 'the VM is about to core dump now' " in various methods ;) Dave On Sat, Nov 05, 2011 at 10:35:36PM +0100, St?phane Ducasse wrote: > Thanks david > > I do not have OSProcess at hand, but where are these messages defined? On Object? > Would it be a problem for you if we define trace and trace: on Object? > > Stef > > >>> Hi guys > >>> > >>> I introduce > >>> log to replace Transcript show: ? > >>> logCr and crLog > >>> > >>> Now stupidly I did not notice that it will capture log on number :( and also on collection, > >>> > >>> So any suggestion of what would be a nice logging message? > >>> short and cool. > >>> > >> How about trace? > > > > In OSProcess, #trace and #trace: are used for a similar purpose. > > This is intended for debugging with "transcript" output coming > > from the VM and therefore less dependent on process scheduling > > in the image. > > > > Dave > > > > >

Nov. 6, 2011

[Pharo-project] [update 1.4] #14219

by StÃ©phane Ducasse

14219 ----- - Issue 4956: Optimized RunArray. Thanks Nicolas Cellier. http://code.google.com/p/pharo/issues/detail?id=4956

Nov. 6, 2011

[Pharo-project] [update 1.4] #14218

by StÃ©phane Ducasse

14218 ----- - Issue 4952: Browse senders from a flat message list leads to MessageNotUnderstood. Thanks Nicolas Cellier for whining endlessly :) Tools should always work :). Thanks for Benjamin van Ryseghem for the good fix and spirit. http://code.google.com/p/pharo/issues/detail?id=4952 - Fix openComparision... -> openComparison....

Nov. 6, 2011

Re: [Pharo-project] about name for logging message

by Stefan Marr

On 06 Nov 2011, at 12:28, StÃ©phane Ducasse wrote: > can you publish the code and I will fill a bug entry. > May be log: was added after. This is nothing but a quick hack... I have not checked how that interacts all the stuff I am not using in the Transcript TranscriptModel>>#initialize initialize super initialize. showOnDisplay := false. innerRectangle := 20@20 extent: 300@500. logToFile := false. entries := Array new: self maxEntries. unfinishedEntry := '' writeStream. accessSemaphore := Mutex new. informDepedents := true. self clear. TranscriptModel>>#log: log: aString accessSemaphore critical: [ self addEntry: aString. self display ]. Best regards Stefan -- Stefan Marr Software Languages Lab Vrije Universiteit Brussel Pleinlaan 2 / B-1050 Brussels / Belgium http://soft.vub.ac.be/~smarr Phone: +32 2 629 2974 Fax: +32 2 629 3525

Nov. 6, 2011