- Pharo-users - lists.pharo.org

Re: [Pharo-users] Voyage, Magritte descriptions, and nil exceptions

by Esteban Lorenzano

Hi Tommaso, that might be a bugâ¦ which version are you using? if latest, can you fill a bug here: https://github.com/estebanlm/voyage/issues (so I do not forget it)? thanks, Esteban > On 08 Mar 2016, at 16:25, Tommaso Dal Sasso <tommaso.dalsasso(a)gmail.com> wrote: > > Hi, > > thanks for your answer, I also tried with One>>mongoContainer, but sadly that does not solve the issue. > I think it works in your case because you have the One object cached from the previous query, but if you inspect the "link" field, it should be nil. > > If you reset the repository connection, it should give the exception again. > > I'll keep trying :-) > Tommaso > > > > On 07/03/16 14:07, Sabine Manaa wrote: >> Hi Tommaso, >> >> you did not define a One>>mongoContainer. I defined it and then it seems to work. >> >> Regards >> >> 2016-03-06 1:42 GMT+01:00 Tommaso DS [via Smalltalk] <[hidden email] <x-msg://133/user/SendEmail.jtp?type=node&node=4882948&i=0>>: >> Hi, >> >> I am having troubles with Voyage and Mongo. >> I have some Classes that I save in Mongo, say "One", "Two", and "Three". >> All three classes and are voyage roots, so the objects from each class >> are stored in different collections. >> One objects has a reference to Two or Three objects. >> >> The problem arises when I use a Magritte description and define a Mongo >> container to optimize the storage: since each class is stored in its own >> collection, there is no point in storing the #instanceOf attribute as well. >> >> Two>>mongoContainer >> <mongoContainer> >> >> ^ VOMongoContainer new >> kind: Two; >> yourself >> >> If I add this method, when I try to load an object One, I get the >> exception: "KeyNotFound: key #nil not found in SystemDictionary". >> It looks like Voyage is not able to understand the type of the objects >> stored in the collection Two, when loaded from a reference. >> >> Am I missing something? Do I need to specify something more to make it work? >> >> I reproduced the scenario in an image that can be downloaded here: >> https://dl.dropboxusercontent.com/u/11506662/VoyageMongo-Link-Test.zip <https://dl.dropboxusercontent.com/u/11506662/VoyageMongo-Link-Test.zip> >> >> Do you have any idea? Should I report this on the issue tracker? >> >> Thanks! >> Tommaso >> >> >> >> If you reply to this email, your message will be added to the discussion below: >> http://forum.world.st/Voyage-Magritte-descriptions-and-nil-exceptions-tp488… <http://forum.world.st/Voyage-Magritte-descriptions-and-nil-exceptions-tp488…> >> To start a new topic under Pharo Smalltalk Users, email [hidden email] <x-msg://133/user/SendEmail.jtp?type=node&node=4882948&i=1> >> To unsubscribe from Pharo Smalltalk Users, click here <applewebdata://F53A575C-598C-4B5D-B41C-A90723498F14>. >> NAML <http://forum.world.st/template/NamlServlet.jtp?macro=macro_viewer&id=instan…> >> >> View this message in context: Re: Voyage, Magritte descriptions, and nil exceptions <http://forum.world.st/Voyage-Magritte-descriptions-and-nil-exceptions-tp488…> >> Sent from the Pharo Smalltalk Users mailing list archive <http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html> at Nabble.com. >

March 8, 2016

Re: [Pharo-users] [ANN] SelectEntity, a new widget for Spec

by Stephan Eggermont

On 08-03-16 13:52, Johan Fabry wrote: > That looks very cool, how about adding it to the standard distribution? That is definitely the goal. Now is the time to point out stupid names, bad design decisions, missed use cases and ugly layout. I would welcome feedback. While building it, I found out I don't like the way an EntryCompletion is connected to its PluggableTextFieldMorph. It makes it difficult to deal with objects that are not strings. PluggableTextFieldMorph>>entryCompletion: anEntryCompletion entryCompletion := anEntryCompletion. entryCompletion ifNotNil: [ entryCompletion chooseBlock isNil ifTrue: [entryCompletion chooseBlock: [:v | self setText: v. self acceptTextInModel ]] ifFalse: [ | blk | blk := entryCompletion chooseBlock. entryCompletion chooseBlock: [:v | self setText: v. self acceptTextInModel. blk value: v]]]. In the demo code it also is clear that the ListModel is incomplete, I couldn't find ho wto open a selected item with the keyboard (unless I implement click on the item, but that then does not have enough context to actually know what to do). Stephan

March 8, 2016

Re: [Pharo-users] [Ann] DemoFFI

by Stephan Eggermont

On 08-03-16 15:20, Pierce Ng wrote: > I wrote these to figure out how to port NBSQLite3 from NativeBoost to the new > FFI. I hope others will find them helpful too. Thanks, Pierce. I find this kind of demos very helpful. Stephan

March 8, 2016

Re: [Pharo-users] Voyage, Magritte descriptions, and nil exceptions

by Tommaso Dal Sasso

Hi, thanks for your answer, I also tried with One>>mongoContainer, but sadly that does not solve the issue. I think it works in your case because you have the One object cached from the previous query, but if you inspect the "link" field, it should be nil. If you reset the repository connection, it should give the exception again. I'll keep trying :-) Tommaso On 07/03/16 14:07, Sabine Manaa wrote: > Hi Tommaso, > > you did not define a One>>mongoContainer. I defined it and then it > seems to work. > > Regards > > 2016-03-06 1:42 GMT+01:00 Tommaso DS [via Smalltalk] <[hidden email] > </user/SendEmail.jtp?type=node&node=4882948&i=0>>: > > Hi, > > I am having troubles with Voyage and Mongo. > I have some Classes that I save in Mongo, say "One", "Two", and > "Three". > All three classes and are voyage roots, so the objects from each > class > are stored in different collections. > One objects has a reference to Two or Three objects. > > The problem arises when I use a Magritte description and define a > Mongo > container to optimize the storage: since each class is stored in > its own > collection, there is no point in storing the #instanceOf attribute > as well. > > Two>>mongoContainer > <mongoContainer> > > ^ VOMongoContainer new > kind: Two; > yourself > > If I add this method, when I try to load an object One, I get the > exception: "KeyNotFound: key #nil not found in SystemDictionary". > It looks like Voyage is not able to understand the type of the > objects > stored in the collection Two, when loaded from a reference. > > Am I missing something? Do I need to specify something more to > make it work? > > I reproduced the scenario in an image that can be downloaded here: > https://dl.dropboxusercontent.com/u/11506662/VoyageMongo-Link-Test.zip > > Do you have any idea? Should I report this on the issue tracker? > > Thanks! > Tommaso > > > > ------------------------------------------------------------------------ > If you reply to this email, your message will be added to the > discussion below: > http://forum.world.st/Voyage-Magritte-descriptions-and-nil-exceptions-tp488… > > To start a new topic under Pharo Smalltalk Users, email [hidden > email] </user/SendEmail.jtp?type=node&node=4882948&i=1> > To unsubscribe from Pharo Smalltalk Users, click here. > NAML > <http://forum.world.st/template/NamlServlet.jtp?macro=macro_viewer&id=instan…> > > > > > ------------------------------------------------------------------------ > View this message in context: Re: Voyage, Magritte descriptions, and > nil exceptions > <http://forum.world.st/Voyage-Magritte-descriptions-and-nil-exceptions-tp488…> > Sent from the Pharo Smalltalk Users mailing list archive > <http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html> at Nabble.com.

March 8, 2016

[Ann] DemoFFI

by Pierce Ng

Hi all, I've published libffidemo on Github, https://github.com/PierceNg/libffidemo, and DemoFFI on STH, http://smalltalkhub.com/#!/~PierceNg/DemoFFI. Together, they show how to use Pharo 5's Unified FFI to obtain an "opaque" pointer to a C-level struct, in the two usual styles: passing in a pointer pointer as a parameter, and via a pointer returned by a C function. They also show how to retrieve an integer through the opaque pointer in two usual styles: passing in a pointer to integer as a parameter, which involves creating an integer value holder on the Smalltalk side, and via an integer returned by a C function. Apart from that, the library does nothing. :-) To compile libffidemo for Pharo's use: $ gcc -shared -m32 -o libffidemo.so libffidemo.c I wrote these to figure out how to port NBSQLite3 from NativeBoost to the new FFI. I hope others will find them helpful too. Pierce

March 8, 2016

Re: [Pharo-users] Using the new OSProcess still no Stdout string

by Pierce Ng

On Sat, Mar 05, 2016 at 02:19:10PM +0000, Dimitris Chloupis wrote: > thanks for freezing my image !!! Argggg !!!! :D > > On Sat, Mar 5, 2016 at 10:44 AM john pfersich <jpfersich(a)gmail.com> wrote: > > p := (PipeableOSProcess command: 'netstat -a | grep LISTEN | grep 27017'). netstat -an Option n avoids DNS lookup which is the likely cause of the delay. Pierce

March 8, 2016

Re: [Pharo-users] [ANN] SelectEntity, a new widget for Spec

by Thierry Goubier

2016-03-07 20:21 GMT+01:00 Stephan Eggermont <stephan(a)stack.nl>: > When using data entry applications, > we often have to select one entity out of a large list. > Spec provides the entryCompletion option for text fields for that. > That works well for small lists > When the number of different entities grows large however, > or when we want to be able to add a new entity, > the traditional solution is to combine an entry completion field > with a button that opens a dialog. This is what SelectEntity provides. > In addition, it supports limiting the choices shown based on > the context in which the field is shown. > Elegant and cool. More nice looking, professional widgets: yes! Thierry > > https://vimeo.com/158063568 > > I've created a small demo application that can be found on smalltalkhub: > > Gofer it > smalltalkhubUser: 'StephanEggermont' > project:'Ancestry'; > package: 'Ancestry'; > load. > > It can be started with: > > ANPersonList new openWithSpec. > > Stephan > > Thanks to Peter Uhnak for the design comments & debugging > > > >

March 8, 2016

Re: [Pharo-users] [ANN] SelectEntity, a new widget for Spec

by Esteban Lorenzano

> On 08 Mar 2016, at 13:52, Johan Fabry <jfabry(a)dcc.uchile.cl> wrote: > > > That looks very cool, how about adding it to the standard distribution? not now. Pharo 6: +1 > >> On Mar 7, 2016, at 16:21, Stephan Eggermont <stephan(a)stack.nl> wrote: >> >> When using data entry applications, >> we often have to select one entity out of a large list. >> Spec provides the entryCompletion option for text fields for that. >> That works well for small lists >> When the number of different entities grows large however, >> or when we want to be able to add a new entity, >> the traditional solution is to combine an entry completion field >> with a button that opens a dialog. This is what SelectEntity provides. >> In addition, it supports limiting the choices shown based on >> the context in which the field is shown. >> >> https://vimeo.com/158063568 >> >> I've created a small demo application that can be found on smalltalkhub: >> >> Gofer it >> smalltalkhubUser: 'StephanEggermont' >> project:'Ancestry'; >> package: 'Ancestry'; >> load. >> >> It can be started with: >> >> ANPersonList new openWithSpec. >> >> Stephan >> >> Thanks to Peter Uhnak for the design comments & debugging >> >> >> >> > > > > ---> Save our in-boxes! http://emailcharter.org <--- > > Johan Fabry - http://pleiad.cl/~jfabry > PLEIAD and RyCh labs - Computer Science Department (DCC) - University of Chile > >

March 8, 2016

Re: [Pharo-users] [ANN] SelectEntity, a new widget for Spec

by Johan Fabry

That looks very cool, how about adding it to the standard distribution? > On Mar 7, 2016, at 16:21, Stephan Eggermont <stephan(a)stack.nl> wrote: > > When using data entry applications, > we often have to select one entity out of a large list. > Spec provides the entryCompletion option for text fields for that. > That works well for small lists > When the number of different entities grows large however, > or when we want to be able to add a new entity, > the traditional solution is to combine an entry completion field > with a button that opens a dialog. This is what SelectEntity provides. > In addition, it supports limiting the choices shown based on > the context in which the field is shown. > > https://vimeo.com/158063568 > > I've created a small demo application that can be found on smalltalkhub: > > Gofer it > smalltalkhubUser: 'StephanEggermont' > project:'Ancestry'; > package: 'Ancestry'; > load. > > It can be started with: > > ANPersonList new openWithSpec. > > Stephan > > Thanks to Peter Uhnak for the design comments & debugging > > > > ---> Save our in-boxes! http://emailcharter.org <--- Johan Fabry - http://pleiad.cl/~jfabry PLEIAD and RyCh labs - Computer Science Department (DCC) - University of Chile

March 8, 2016

Re: [Pharo-users] [Moose-dev] Re: Call for action for Roassal

by Johan Fabry

Excellent, thanks a lot! I will take a look at that tomorrow. > On Mar 7, 2016, at 11:34, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > > Hi Johan, > > I've just commited RTAnchorConstraint to latest Roassal, see class-side example there. > > I've been using it for my class diagrams where it works quite well, however class diagrams are usually orthogonal-ish, which makes it a bit nicer. > <uml.png> > > The Anchor will avoid intersecting it's own line, and one of the end shapes (it should both but apparently I have a bug there...). > It doesn't look at other lines, however you can specify on which side it should be. > > (You can also put the node label inside the circle with `el @ (RTLabelled new center)` but you probably know that.) > <anchor.png> > â > I have also a global edge labeling layout which produces good placementâ¦ but it's slow as hellâ¦ I need to write a fast flow alogrithmâ¦ > > Also the Anchor currently doesn't work with self-edges. On the other hand Roassal doesn't have self-edges yet so it shouldn't be a problem. :) > > Peter > > > On Mon, Mar 7, 2016 at 2:34 PM, Johan Fabry <jfabry(a)dcc.uchile.cl <mailto:jfabry@dcc.uchile.cl>> wrote: > > Better late than never :-) (working on the holidays backlog) > > I only have one request: better positioning on labels of nodes and edges. For example see the image: three of the four labels are badly positioned because the bounding box of their text is intersected by one or more edges. > > <Screen Shot 2016-03-07 at 10.31.24.png> > I know that to solve this generally is hard, but for simple cases like this it should be possible. > > Ah, and it should work well with animations and dragging of course ;-) > >> On Feb 24, 2016, at 05:51, Alexandre Bergel <alexandre.bergel(a)me.com <mailto:alexandre.bergel@me.com>> wrote: >> >> Dear community, >> >> As you may have seen, Roassal has entered a stabilization phase. The book AgileVisualization.com <http://agilevisualization.com/> will soon be released. After its release, Roassal will go over a new development phase. In order to prepare it, I am asking this question: >> >> What are the 3 aspects you would like to see improved in Roassal? >> >> You can answer publicly or by sending private messages. >> >> Kind regards, >> Alexandre >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu <http://www.bergel.eu/> >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> _______________________________________________ >> Moose-dev mailing list >> Moose-dev(a)list.inf.unibe.ch <mailto:Moose-dev@list.inf.unibe.ch> >> https://www.list.inf.unibe.ch/listinfo/moose-dev <https://www.list.inf.unibe.ch/listinfo/moose-dev> >> > > > > ---> Save our in-boxes! http://emailcharter.org <http://emailcharter.org/> <--- > > Johan Fabry - http://pleiad.cl/~jfabry <http://pleiad.cl/~jfabry> > PLEIAD and RyCh labs - Computer Science Department (DCC) - University of Chile > > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)list.inf.unibe.ch <mailto:Moose-dev@list.inf.unibe.ch> > https://www.list.inf.unibe.ch/listinfo/moose-dev <https://www.list.inf.unibe.ch/listinfo/moose-dev> > > ---> Save our in-boxes! http://emailcharter.org <--- Johan Fabry - http://pleiad.cl/~jfabry PLEIAD and RyCh labs - Computer Science Department (DCC) - University of Chile

March 8, 2016