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

Re: [Pharo-project] [GS/SS Beta] serializing object graphs / ordering graph anchors

by Stephan Eggermont

Hello Norbert, That sounds like a silly algorithm. There is no reason you should get a large stack size as long as you don't try to do this more than one level deep only: add object to the table repeat find first unwritten object in the table write its contents: simple objects direct for a complex object: look it up in the table if it doesn't exist, add it to the table write its reference mark as written until no unwritten objects in the table Stephan On 2 jun 2011, at 12:38, Norbert Hartl wrote: > Before I start a utility myself I want to ask if there is such a tool already. > > I'm using sixx for object graph serialization. It works quite good but it has some severe limits. Well, the limits are not really sixx dependent but a problem of usual serializers. My problem is the size of the stack such a tool generates. Especially in gemstone this appears to be a problem because the stack is limited per gem. > > If I look at the serializers I know the mechanics are simple: > > 1. take an object and look it up in a table. > 2. if the object is in the table it has already been serialized. We take a reference from the table and write it down > 3. if it isn't in the table it means the object has not been serialized and the contents need to be written. After that the object with a reference representation is written to the table > 4. while writing the content of an object (inst vars) I encounter simple objects (direct string representation) or complex objects (composite). In the latter case we start over from 1. > > If the object graph is well interconnected than the odds are high that a stack will grow high until the first reference can be written. With a small pier kernel I already matched a stack size of 1000. > > One solution I can think of is to collect and order objects in the graph that cover smaller segments from the overall graph. This way I would construct a sorted collection that is sorted by stack depth (lowest first). The collection will then be serialized leading to a much smaller possible stack sizes. It might be there are cases it can't work but I think for most cases it will do its job. And it will be slow of course. > > Does anybody know if such a tool exists? > > Norbert >

June 3, 2011

[Pharo-project] Simple rest server

by Guillermo Polito

Maybe it's useful for someone. A very very very simple rest server which converts http://localhost:8090/look/at/this/in/1 into mainResource look at this in at: 1 I did it in half an hour so it's no comments nor documentation :P. The repo is free to write ;) Guille ---------- Forwarded message ---------- From: Guillermo Polito <guillermopolito(a)gmail.com> Date: Fri, Jun 3, 2011 at 1:26 PM Subject: mira mira To: Montonero <santiagobragagnolo(a)gmail.com> Gofer it squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfKomHttpServer'; load. (ConfigurationOfKomHttpServer project version: #stable) load Gofer it squeaksource: 'SimpleRestServer'; package: 'SimpleRestServer'; package: 'SimpleRestServerExample'; load. "To Start:" SRSHttpRestService new mainResource: (SRSExample new); startOn: 8090. "Then web browse: http://localhost:8090/look/ http://localhost:8090/look/something http://localhost:8090/look/at/ http://localhost:8090/look/at/this/ http://localhost:8090/look/at/this/example/ http://localhost:8090/look/at/this/in/1 http://localhost:8090/look/at/this/example/1 "

June 3, 2011

Re: [Pharo-project] [TODO] 1.3 (please help)

by Dale Henrichs

Marcus, I'll take on 4337. Do any of those other issues have Metacello-related problems, if so I'll take them as well ... Dale ----- Original Message ----- > Core > ==== > > http://code.google.com/p/pharo/issues/list?can=2&q=milestone=1.3 > > 4319 VM parameter handling problems > 4326 Connection timeout problem > 4328 Transcript: 5 ) Update problem when evaluating 1 to: 30 do: [: > ... > 4329 Transcript: 4) clear on cmd-s > 4338 testAllDictionariesAreHealthy sometimes fails > > > Full 4 Issues > =========== > > > 4245 Add file ArchiveViewer not working (fixed, needs to be added) > 4303 completion and tab key > 4318 Test for LedMorph (fixed, needs to be added) > 4337 Fix OB Metacello Config (This is actualy 1.2-dev) > > > http://code.google.com/p/pharo/issues/list?can=2&q=Milestone%3D1.3-DevImage > > Here it would be nice to have *someone* (not me) who is willing to > look at the Metacello configs > and include the work that is already finished. > > Marcus > > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > > >

June 3, 2011

Re: [Pharo-project] usability of Pharo and Squeak

by Dale Henrichs

Thanks Geert....I am all thumbs when it comes to javascript (or UI design for that matter:), so there are very likely better ways to do things...for them moment I am satisfied that I have _a way_ to do things ... I needed to move to a web-browser for GLASS and I just didn't think that the window-centric model we are all familiar with would translate well into the web-browser world and I stumbled onto the current model, that does seem to fit well ... I am building in the notion of multiple "sessions" where each "session" manages the history and navigation stacks so that multiple internet browser tabs can have independent lives ... I am also interested in exploring the possibility of working with two independent smalltalk processes/images from within the same session ... I think that it would be interesting and useful for the folks that develop in Pharo and deploy in GemStone to be able to run tODE in GemStone, but be able to easily view and edit the pharo source (an vice versa) from within the same development environment ... I've already been working with one internet tab for Pharo and one for GemStone, but being able to navigate directly without the standard "copy, switch window/tab, open search, paste" steps that are usually needed ... Dale ----- Original Message ----- > I really like the idea Dale! I do realize you are still in the early > stages > but from a UI design point of view its a shame the typical back, > forward, > home and bookmark Internet browser buttons had to duplicated in the > tODE. > Since it is browser based I assume the idea is to allow developers to > open > as many (Internet browser) tabs as they want? Anyhow good stuff Dale > :) > > -- > View this message in context: > http://forum.world.st/usability-of-Pharo-and-Squeak-tp3562378p3570224.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > >

June 3, 2011

[Pharo-project] Pharo by Example German translation: repository

by Marcus Denker

Hello, There is now a repository for a german translation of PBE: https://github.com/SquareBracketAssociates/PharoByExample-german right now this is just a copy of the english text as a starting point. Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

June 3, 2011

[Pharo-project] ACM Student Research Competition

by Alexandre Bergel

Hi! There is a news I would like to share with you. Vanessa, a student at the University of Chile, is just back from ICSE, a top conference on software engineering. She presented Hapao (http://hapao.dcc.uchile.cl) a Pharo application, at the ACM Student Research Competition[*]. It was a success: she arrived 2nd in the category undergraduate student. A nice medal for the Pharo community! Cheers, Alexandre [*] http://2011.icse-conferences.org/content/src-call -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

June 3, 2011

Re: [Pharo-project] OSProcess on 1.2

by David T. Lewis

Hi Sean, If you have a chance, could you please run the following and post your results from the transcript? Thanks a lot. Transcript clear. { 'CommandShell versionString ==> ', CommandShell versionString. 'OSProcess versionString ==> ', OSProcess versionString. OSProcess accessor osppModuleName asString. 'OSPP versionString ==> ', OSProcess accessor osppModuleVersionString asString. OSProcess accessor aioModuleName asString. 'AIO plugin versionString ==> ', OSProcess accessor aioVersionString asString. OSProcess accessor xdcpModuleName asString. 'XDCP versionString ==> ', OSProcess accessor xdcpVersionString asString } do: [:e | Transcript cr; show: e] For reference, on a Linux platform with interpreter VM you might get results like this: CommandShell versionString ==> 4.4.15 OSProcess versionString ==> 4.4.2 UnixOSProcessPlugin 24 May 2011 (e) OSPP versionString ==> 4.4.3 AioPlugin 24 May 2011 (e) AIO plugin versionString ==> 2.2.4 XDisplayControlPlugin 24 May 2011 (e) XDCP versionString ==> 2.1.6 Thank you, Dave On Fri, Jun 03, 2011 at 04:04:35AM -0700, Sean P. DeNigris wrote: > Okay, many of the problems were being caused by another squeak vm on my > machine highjacking the image. With a fresh 4.2.5, > > ***********************OSProcess test results are... > > UnixProcessTestCase - it seems like tests that fork (e.g. > UnixProcessTestCase>>testClassForkHeadlessSqueakAndDo) hang forever and then > things that were working don't work anymore (there is often a warning > "forkSqueak requires XDisplayControlPlugin" before something bad happens, > but it seems like it gets screwed up whether you hit proceed or abandon). > This seems to be the major issue. > > All pass in OSPipeTestCase, UnixProcessFileLockTestCase, > UnixProcessUnixFileLockingTestCase, UnixProcessWin32FileLockingTestCase > > UnixProcessAccessorTestCase > Failures: > testChDir > testIsExecutableForUserInGroup > testIsReadableForUserInGroup > testIsWritableForUserInGroup > > AioEventHandlerTestCase: > Errors: > '#(''AioEventHandlerTestCase>>#testPrimAioModuleName'' > > Failures: > ''AioEventHandlerTestCase>>#testFileReadableEvent'' > ''AioEventHandlerTestCase>>#testFileWritableEvent'' > ''AioEventHandlerTestCase>>#testSuspendAioForSocketReadableEvent'' > ''AioEventHandlerTestCase>>#testHandleForFile'' > ''AioEventHandlerTestCase>>#testEnableHandleAndDisable'' > ''AioEventHandlerTestCase>>#testSocketReadableEvent'' > ''AioEventHandlerTestCase>>#testHandleForSocket'' > ''AioEventHandlerTestCase>>#testPrimAioModuleVersionString'' > > *********************** CommandShell tests... > > All pass in ExpressionEvaluatorTestCase, InternalPipeTestCase, > PipelineEventsTestCase, ShellSyntaxTestCase > > PipeableOSProcessTestCase > testForkHeadlessSqueakReadAndWriteReferenceStream, testForkSqueak, > testForkSqueakReadAndWriteReferenceStream, testForkSqueakReferenceStream > give warning "forkSqueak requires XDisplayControlPlugin" > testForkHeadlessSqueak, testForkHeadlessSqueak2, > testForkHeadlessSqueakReferenceStream give same warning, and then hang > > CommandShellTestCase - all pass, except testPipeline65 fails. > Sean > > -- > View this message in context: http://forum.world.st/OSProcess-on-1-2-tp3569458p3570538.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

June 3, 2011

[Pharo-project] [update 1.3] #13239

by Marcus Denker

13239 ----- Issue 4338: testAllDictionariesAreHealthy sometimes fails... http://code.google.com/p/pharo/issues/detail?id=4338 -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

June 3, 2011

Re: [Pharo-project] OSProcess on 1.2

by Sean P. DeNigris

Okay, many of the problems were being caused by another squeak vm on my machine highjacking the image. With a fresh 4.2.5, ***********************OSProcess test results are... UnixProcessTestCase - it seems like tests that fork (e.g. UnixProcessTestCase>>testClassForkHeadlessSqueakAndDo) hang forever and then things that were working don't work anymore (there is often a warning "forkSqueak requires XDisplayControlPlugin" before something bad happens, but it seems like it gets screwed up whether you hit proceed or abandon). This seems to be the major issue. All pass in OSPipeTestCase, UnixProcessFileLockTestCase, UnixProcessUnixFileLockingTestCase, UnixProcessWin32FileLockingTestCase UnixProcessAccessorTestCase Failures: testChDir testIsExecutableForUserInGroup testIsReadableForUserInGroup testIsWritableForUserInGroup AioEventHandlerTestCase: Errors: '#(''AioEventHandlerTestCase>>#testPrimAioModuleName'' Failures: ''AioEventHandlerTestCase>>#testFileReadableEvent'' ''AioEventHandlerTestCase>>#testFileWritableEvent'' ''AioEventHandlerTestCase>>#testSuspendAioForSocketReadableEvent'' ''AioEventHandlerTestCase>>#testHandleForFile'' ''AioEventHandlerTestCase>>#testEnableHandleAndDisable'' ''AioEventHandlerTestCase>>#testSocketReadableEvent'' ''AioEventHandlerTestCase>>#testHandleForSocket'' ''AioEventHandlerTestCase>>#testPrimAioModuleVersionString'' *********************** CommandShell tests... All pass in ExpressionEvaluatorTestCase, InternalPipeTestCase, PipelineEventsTestCase, ShellSyntaxTestCase PipeableOSProcessTestCase testForkHeadlessSqueakReadAndWriteReferenceStream, testForkSqueak, testForkSqueakReadAndWriteReferenceStream, testForkSqueakReferenceStream give warning "forkSqueak requires XDisplayControlPlugin" testForkHeadlessSqueak, testForkHeadlessSqueak2, testForkHeadlessSqueakReferenceStream give same warning, and then hang CommandShellTestCase - all pass, except testPipeline65 fails. Sean -- View this message in context: http://forum.world.st/OSProcess-on-1-2-tp3569458p3570538.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

June 3, 2011

Re: [Pharo-project] [GS/SS Beta] serializing object graphs / ordering graph anchors

by Norbert Hartl

Am 03.06.2011 um 11:03 schrieb Henrik Sperre Johansen: > On 03.06.2011 11:00, Henrik Sperre Johansen wrote: >> >> On 03.06.2011 10:38, Norbert Hartl wrote: >>> >>> >>> Am 03.06.2011 um 10:20 schrieb Mariano Martinez Peck: >>> >>>> >>>> >>>>> If I look at the serializers I know the mechanics are simple: >>>>> >>>>> 1. take an object and look it up in a table. >>>>> 2. if the object is in the table it has already been serialized. We take a reference from the table and write it down >>>>> 3. if it isn't in the table it means the object has not been serialized and the contents need to be written. After that the object with a reference representation is written to the table >>>>> 4. while writing the content of an object (inst vars) I encounter simple objects (direct string representation) or complex objects (composite). In the latter case we start over from 1. >>>>> >>>>> If the object graph is well interconnected than the odds are high that a stack will grow high until the first reference can be written. With a small pier kernel I already matched a stack size of 1000. >>>>> >>>>> >>>>> In Fuel we traverse the graph but instead of using a recursion we use our own simple stack implementation where we push and pop objects. >>>>> But Martin may explaint better than me. >>>> >>>> I'm interested in details how it works and if it avoids the deep stack. Is there additional information about that? >>>> >>>> >>>> In 4. you said "while writing the content of an object (inst vars) I encounter simple objects (direct string representation) or complex objects (composite). In the latter case we start over from 1.". >>>> So... Imagine object X with two instVars Y and Z. Imagine the method of the traverse is called #analye:. So you do #analize: X. Then, in such method you check whether X has regular pointers to regular objects, and if true, you analize them. So in this case you would send #analyze: Y and #analize: Z, generating the recursion. Right ? >>> >>> yes, the time between analyse: Y and analyse: Z is dependent on the graph that is attached to Y. Y can have objects that have further objects etc. So leaving X aside, Y can be the first object to serialize and Z the last. >>>> >>>> Ok, instead of sending #analyze: Y and #analize: Z what we do is just to do a push on a stack: #push: Y and #push: Z. And then we are done with X, so we pop from the stack and we continue with the next object (at some point in the future we will pop Y and Z) When there are no more objects in the stack it means we are done. >>> >>> How do you write X? I can see that you turn a recursive trace into depth-by-depth trace but the difficult part is to write X. In X you need a reference representation of any sort. How do you derive that from the stack? >>> >>>> For performance (I think) we did FLSimpleStack. You can check also FLSimpleStackTest. Both are in Fuel repo. >>>> >>>> Would something like that help for the stack in GemStone? >>>> >>> Yes. With this approach the resulting stack size is much smaller. To exceed the stack setting you need a graph containing an object which has a shortest route that is larger than the stack limit. And I think this is very unlikely :) >>> I would need to change Sixx in order to have it work like this. I need to think about it. >>> >>> Thanks, >>> >>> Norbert >> Yes, using a specific stack in the way Fuel does relies on there being a separate analyze-phase before the actual serialization of the objects. >> (Due to wanting to group objects of the same type together when serializing) >> >> You could do the same in a "raw" serializer like SIXX: >> 1) pop first object from stack >> 2) if any of the instvars need to be serialized, and their ids can not be found in cache, push self + missing objects >> 3) if not, serialize self, then goto 1 >> >> The key difference is you can not considering an object "done" during an analysis phase, but rather push it back on the stack for reevaluation after its dependencies have been handled in the same way. >> >> So the resulting stack will be much larger than what you see in Fuel, but still kept outside the call stack. >> >> Cheers, >> Henry > Note: This never grows the call stack. > You're basically left with: > > [stack isEmpty ] whileFalse: [self serialize: stack pop] > where serialize: either pushes objects and exits, or does actual serialization. Should we call it a "serialization trampoline" ?? :) Agreed, you can separate working stack and call stack to avoid the problem in total. thanks, Norbert

June 3, 2011