- Pharo-users - lists.pharo.org

Re: [Pharo-users] Roassal & Spec?

by Tudor Girba

You could also try to use Glamour for that: Here is an example that renders something along the wished lines. You can run it in a Moose image: https://ci.inria.fr/moose/job/moose-latest-dev-4.8/lastSuccessfulBuild/arti… composer := GLMCompositePresentation new. composer tabulator with: [ :t | t row: #visualization; row: #list; row: #details. t transmit to: #visualization; andShow: [ :a | a roassal title: 'Visualization'; painting: [ :view :collection | view nodes: collection. view edgesFrom: [ :x | x // 5 ]. view radialNarrowTreeLayout ] ]. t transmit from: #visualization; to: #list; andShow: [ :a | a list title: 'List'; display: [ :number | 1 to: number ] ]. t transmit from: #list; to: #details; andShow: [ :a | a text title: 'Details'; display: [ :number | number asString ] ] ]. composer openOn: (1 to: 420) Cheers, Doru On May 30, 2013, at 11:40 AM, MartinW <wm(a)fastmail.fm> wrote: > Hi, > how can i combine a Roassal visualization and a Spec UI? > Is there already some Roassal-Spec? > See attached screenshot for what i am trying to get. > M. > > <http://forum.world.st/file/n4690745/GraphAndList.jpeg> > > > > -- > View this message in context: http://forum.world.st/Roassal-Spec-tp4690745.html > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > -- www.tudorgirba.com "Problem solving efficiency grows with the abstractness level of problem understanding."

May 30, 2013

Re: [Pharo-users] Roassal & Spec?

by ClÃ©ment Bera

Hello, How is your Roassal visualization ? Is it a morph ? If it is a morph I guess you would need to do a ComposableModel wrapper to integrate it in a spec. 2013/5/30 MartinW <wm(a)fastmail.fm> > Hi, > how can i combine a Roassal visualization and a Spec UI? > Is there already some Roassal-Spec? > See attached screenshot for what i am trying to get. > M. > > <http://forum.world.st/file/n4690745/GraphAndList.jpeg> > > > > -- > View this message in context: > http://forum.world.st/Roassal-Spec-tp4690745.html > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > > -- ClÃ©ment BÃ©ra Mate Virtual Machine Engineer BÃ¢timent B 40, avenue Halley 59650 *Villeneuve d'Ascq*

May 30, 2013

Re: [Pharo-users] Roassal & Spec?

by StÃ©phane Ducasse

Ben is on holiday. Now I imagine that we should get a model that encapsulates a roassal easel is the way to go and it would be cool to have. > Hi, > how can i combine a Roassal visualization and a Spec UI? > Is there already some Roassal-Spec? > See attached screenshot for what i am trying to get. > M. > > <http://forum.world.st/file/n4690745/GraphAndList.jpeg> > > > > -- > View this message in context: http://forum.world.st/Roassal-Spec-tp4690745.html > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >

May 30, 2013

Spec & Roassal?

by MartinW

=Seems one has to resubscribe to the new mailing-lists? sorry if this comes as a duplicate= Hi, how can i combine a Roassal visualization and a Spec UI? Is there already some Roassal-Spec? See attached screenshot for what i am trying to get. M. <http://forum.world.st/file/n4690746/GraphAndList.jpeg> -- View this message in context: http://forum.world.st/Spec-Roassal-tp4690746.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

May 30, 2013

Roassal & Spec?

by MartinW

Hi, how can i combine a Roassal visualization and a Spec UI? Is there already some Roassal-Spec? See attached screenshot for what i am trying to get. M. <http://forum.world.st/file/n4690745/GraphAndList.jpeg> -- View this message in context: http://forum.world.st/Roassal-Spec-tp4690745.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

May 30, 2013

Re: [Pharo-users] Object database

by Boris SpasojeviÄ

Thanks all, I will look in to MongoDB (with and without Voyage) and GemStone, and report problems or lack there of :) all the best, Boris SpasojeviÄ - ÐÐ¾ÑÐ¸Ñ Ð¡Ð¿Ð°ÑÐ¾ÑÐµÐ²Ð¸Ñ *Research assistant* Software Composition Group <http://scg.unibe.ch> Institute of Computer Science and Applied Mathematics <http://www.iam.unibe.ch> University of Bern <http://www.unibe.ch> email: spasojev(a)iam.unibe.ch <mailto:spasojev@iam.unibe.ch> office phone: +41 (0)31 511 7636 mobile: +41 (0)76 66 88 175 webpage: http://scg.unibe.ch/staff/Boris-Spasojevic On 28/5/13 4:11 PM, Boris SpasojeviÄ wrote: > Hi all, > > I have a need to persist a really large and funny object structure in > Pharo (a huge Dictionary of Dictionaries) and I would like to be able > to query this data from a remote image. > > Basically what I am looking for is some form of database that would > allow me to input elements in to this structure from one image, and > read them out in another image with queries like i.e. > > dictionaryOfDictionaries select: [ :each | > (each keys includes: key1) and: [ each keys includes: key2 ] > ] > > It does not have to be strictly an OO database, anything that could > enable me to do this fast and easy would be nice. > > > Any suggestions/ideas/comments? > > > Boris SpasojeviÄ - ÐÐ¾ÑÐ¸Ñ Ð¡Ð¿Ð°ÑÐ¾ÑÐµÐ²Ð¸Ñ > > *Research assistant* > Software Composition Group <http://scg.unibe.ch> > Institute of Computer Science and Applied Mathematics > <http://www.iam.unibe.ch> > University of Bern <http://www.unibe.ch> > > email: spasojev(a)iam.unibe.ch <mailto:spasojev@iam.unibe.ch> > office phone: +41 (0)31 511 7636 > mobile: +41 (0)76 66 88 175 > webpage: http://scg.unibe.ch/staff/Boris-Spasojevic >

May 29, 2013

Re: [Pharo-users] Spec #add:withSpec: Bug?

by Sean P. DeNigris

Sean P. DeNigris wrote > leads to: > DNU SpecLayoutAddWithSpec(Object)>>doesNotUnderstand: #subwidget: That was in 2.0, in 30172, I get: MessageNotUnderstood: DynamicComposableModel>>getText ----- Cheers, Sean -- View this message in context: http://forum.world.st/Spec-add-withSpec-Bug-tp4690523p4690525.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

May 28, 2013

Spec #add:withSpec: Bug?

by DeNigris Sean

| layout | model := DynamicComposableModel new. model instantiateModels: {#accessor. #TextInputFieldModel}. layout := SpecLayout composed. layout add: #accessor withSpec: TextInputFieldModel defaultSpec. model openWithSpecLayout: layout. leads to: DNU SpecLayoutAddWithSpec(Object)>>doesNotUnderstand: #subwidget: After I added it, I got: DNU SpecLayoutAddWithSpec(Object)>>doesNotUnderstand: #layoutFrame: After I added that, I got: UndefinedObject(Object)>>doesNotUnderstand: #asSymbol SpecInterpreter>>interpretASpec: What do you think? Thanks, Sean

May 28, 2013

Spec: custom layouts for sub-models

by Sean P. DeNigris

I have a UI, let's call it ParentUI, which includes ChildUI - another ComposableModel. In the default layout, ChildUI includes a toolbar. When embedded in the ParentUI, I want the toolbars to be merged. It is easy to include the ChildUI tools in the ParentUI bar by adding ParentUI>>childTools, which I can then #add: to the layout. But the ChildUI tools also still show up in ChildUI (so they appear twice). I ended up defining ChildUI>>#noToolbarSpec, which I can pass to the layout like "add: #(#currentScenario. #noToolbarSpec)", and which delegates to ChildUI class>>#noToolbarSpec. I want to have the default ChildUI spec simply extend noToolbarSpec, but I didn't look into that yet. Anyway my question is: is this the best way to do what I'm trying to do? Thanks! ----- Cheers, Sean -- View this message in context: http://forum.world.st/Spec-custom-layouts-for-sub-models-tp4690508.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

May 28, 2013

Re: [Pharo-users] PettitParser approach help

by Juan Ignacio Vaccarezza

Hi Doru, I did it the other way to avoid the "if" inside the ParseResult>>add: . Regards, Juan On Tue, May 28, 2013 at 11:55 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi, > > I would more do it the other way around (from large to small): > > niceObject := ParseResult new. > result do: [:eachResult | niceObject add: eachResult ] > > Cheers, > Doru > > > > > On Tue, May 28, 2013 at 2:23 PM, Juan Ignacio Vaccarezza < > juanvaccarezza(a)gmail.com> wrote: > >> Doru, >> thanks for the answer. >> >> I'm doing it in the way you suggest. >> >> What I ment by know how to add to the result is the following: (Modifing >> a bit the example you gave me) >> >> a := 'AAA' asParser flatten ==> [:token | ResultSelfAdder new >> objectToAdd: token; selector:#addA ]. >> b := 'BBB' asParser flatten ==> [:token | ResultSelfAdder new >> objectToAdd: token; selector:#addB ]. >> c := 'CCC' asParser flatten ==> [:token | ResultSelfAdder new >> objectToAdd: token; selector:#addC ]. >> >> meaningful := a / b / c. >> other := (meaningful / #newline asParser) negate star flatten. >> log := (meaningful / other) delimitedBy: #newline asParser. >> >> result := log end parse: 'AAA >> AAA >> BBB >> CCC >> AAA >> other text >> CCC >> BBB >> other text'. >> >> niceObject := ParseResult new. >> result do: [:eachResult | eachResult addYourselfTo: niceObject] >> >> >> ResutlSelfAdder>>addYourselfTo: aParseResult >> aParseResult perform: self selector with: self objectToAdd. >> >> I hope is clear now, Im pretty new at asking on mailists, and sometimes I >> forget to add crucial information >> Thanks again for your time! >> >> Juan >> >> >> On Tue, May 28, 2013 at 2:08 AM, Tudor Girba <tudor(a)tudorgirba.com>wrote: >> >>> Hi, >>> >>> I am not sure what you mean when you say an object that knows how to add >>> to the result. Basically, you would need to build for each production the >>> object and collect the meaningful ones in the outer scope. >>> >>> Here is something that would work for your example: >>> >>> a := 'AAA' asParser ==> [:token | #a]. >>> b := 'BBB' asParser ==> [:token | #b]. >>> c := 'CCC' asParser ==> [:token | #c]. >>> meaningful := a / b / c. >>> other := (meaningful / #newline asParser) negate star flatten. >>> log := (meaningful / other) delimitedBy: #newline asParser. >>> >>> result := log end parse: 'AAA >>> AAA >>> BBB >>> CCC >>> AAA >>> other text >>> CCC >>> BBB >>> other text'. >>> result select: #isSymbol >>> >>> I am CC-ing the moose mailing list because these questions tend to find >>> better answers there. >>> >>> Cheers, >>> Doru >>> >>> >>> On May 27, 2013, at 11:07 PM, Juan Ignacio Vaccarezza < >>> juanvaccarezza(a)gmail.com> wrote: >>> >>> > Hi all, >>> > >>> > First of all thanks for the amazing work and aswers to all. Having >>> said that, the problem: >>> > >>> > I need to parse a log, a model that represents the lo is the following: >>> > >>> > ' >>> > AAA >>> > AAA >>> > BBB >>> > Line I don't care which can contain anything that is not AAA BBB or CCC >>> > CCC >>> > AAA >>> > CCC >>> > BBB >>> > Line I don't care which can contain anything that is not AAA BBB or CCC >>> > ' >>> > >>> > I manage to write the grammar which parses this, but then I would >>> lilke to have all the log info digested on a result object which behaves >>> something like this: >>> > >>> > resutlObject as size --> 3 >>> > resultObject bs size --> 2 >>> > restulIbject cs size -->2 >>> > >>> > The option that im using now is that individual parsers (meaning the >>> parser for AAA,BBB,CCC,etc) actually retunrs an object that knows how to >>> add themselves to the result and then, I iterate over the parser's array >>> result asking to each object to add itself to the result. >>> > >>> > Is there a better solution? >>> > >>> > Thanks to all, >>> > Juan. >>> >>> -- >>> www.tudorgirba.com >>> >>> "It's not how it is, it is how we see it." >>> >>> >>> >> > > > -- > www.tudorgirba.com > > "Every thing has its own flow" >

May 28, 2013