- Pharo-users - lists.pharo.org

Re: [Pharo-users] Voyage: Circular references

by Sabine KnÃ¶fel

Hi Esteban, thank you for the solution with the VOMongoToOneDescription. This works perfect for me. I have to come back to the circular references. I am not sure if this is a bug. I have the following model: Trip ->> Day <->> VehicleTrip One Trip has N Days. One Day has N VehicleTrips. The VehicleTrip points back to its Day. The Trip is voyageRoot. But I dont want Day or VehicleTrip to be voyageRoot, too. (In my opinion this does not make sense). If I try to save the trip, I get the endless loop. Attention, the Image freezes then. :-) How would you solve this? Also with the VOMongoToOneDescription solution? You can reproduce it with the fileout below. Regards Sabine This is the fileout: Object subclass: #Day instanceVariableNames: 'date vehicleTrips' classVariableNames: '' poolDictionaries: '' category: 'RKA24-Demo'! !Day methodsFor: 'accessing' stamp: 'sabineknoefel 8/12/2013 11:13'! date: anObject date := anObject! ! !Day methodsFor: 'accessing' stamp: 'sabineknoefel 8/12/2013 11:15'! vehicleTrips: anObject vehicleTrips := anObject! ! Object subclass: #VehicleTrip instanceVariableNames: 'day description' classVariableNames: '' poolDictionaries: '' category: 'RKA24-Demo'! !VehicleTrip methodsFor: 'accessing' stamp: 'sabineknoefel 8/12/2013 11:13'! day: anObject day := anObject! ! !VehicleTrip methodsFor: 'accessing' stamp: 'sabineknoefel 8/12/2013 11:14'! description: anObject description := anObject! ! Object subclass: #Trip instanceVariableNames: 'days description' classVariableNames: '' poolDictionaries: '' category: 'RKA24-Demo'! !Trip methodsFor: 'accessing' stamp: 'sabineknoefel 8/12/2013 11:14'! days: anObject days := anObject! ! !Trip methodsFor: 'accessing' stamp: 'sabineknoefel 8/12/2013 10:12'! description: anObject description := anObject! ! "-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- "! Trip class instanceVariableNames: ''! !Trip class methodsFor: 'as yet unclassified' stamp: 'sabineknoefel 8/12/2013 11:15'! demo |theTrip theDay theVehicleTrip| theTrip := Trip new description: 'Trip to Munic'. theDay := Day new date: Date today. theVehicleTrip := VehicleTrip new description: 'with car to fair'. theVehicleTrip day: theDay. theTrip days: (OrderedCollection with: theDay). theDay vehicleTrips: (OrderedCollection with: theVehicleTrip ). theTrip halt save ! ! !Trip class methodsFor: 'as yet unclassified' stamp: 'sabineknoefel 8/12/2013 09:47'! isVoyageRoot ^true! ! |theTrip theDay theVehicleTrip| theTrip := Trip new description: 'Trip to Munic'. theDay := Day new date: Date today. theVehicleTrip := VehicleTrip new description: 'with car to fair'. theVehicleTrip day: theDay. theTrip days: (OrderedCollection with: theDay). theDay vehicleTrips: (OrderedCollection with: theVehicleTrip ). theTrip inspect -- View this message in context: http://forum.world.st/Voyage-Circular-references-tp4691940p4703303.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Aug. 12, 2013

Re: [Pharo-users] Pharo-users Digest, Vol 4, Issue 23

by vinref＠gmail.com

Thank you Mariano and Stephane. I am going to look at VoyageMongo and PostgreSQL first.

Aug. 10, 2013

Re: [Pharo-users] Databases for Pharo that do not use FFI

by Dale K. Henrichs

GemStone's GCI library uses FFI, but the GCI layer has an option to make non-blocking FFI calls (you end up polling for response) so the vm is free to spin away while polling ... unfortunately, the current GCI API is also single threaded (we're planning to change this in an upcoming release) so you can make only one concurrent non-blocking call. Dale ----- Original Message ----- | From: vinref(a)gmail.com | To: pharo-users(a)lists.pharo.org | Sent: Saturday, August 10, 2013 6:44:06 AM | Subject: [Pharo-users] Databases for Pharo that do not use FFI | | Hello | | I have been tinkering with Pharo long enough now to contemplate | writing a "serious" applications with it. An important consideration | is databases. I have been looking at SQLite but realise since it | works through FFI it probably blocks the VM whilst processing a | query. Is this correct? | | VoyageMongo looks interesting. PostgreSQL is supported too. Do either | of | these work through FFI? | | Many thanks in advance. | |

Aug. 10, 2013

Re: [Pharo-users] Databases for Pharo that do not use FFI

by Mariano Martinez Peck

On Sat, Aug 10, 2013 at 12:46 PM, StÃ©phane Ducasse < stephane.ducasse(a)inria.fr> wrote: > > > Hello > > > > I have been tinkering with Pharo long enough now to contemplate writing > a "serious" applications with it. An important consideration is databases. > > Esteban will start to work on the threaded vm with eliot for such typical > case. > > That would be great. There are some big players like Oracle whose library does not support async queries :( > > I have been looking at SQLite but realise since it works through FFI it > probably blocks the VM whilst processing a query. Is this correct? > > > > VoyageMongo looks interesting. PostgreSQL is supported too. Do either of > > these work through FFI? > > > > Many thanks in advance. > > > > > -- Mariano http://marianopeck.wordpress.com

Aug. 10, 2013

Re: [Pharo-users] Databases for Pharo that do not use FFI

by StÃ©phane Ducasse

> Hello > > I have been tinkering with Pharo long enough now to contemplate writing a "serious" applications with it. An important consideration is databases. Esteban will start to work on the threaded vm with eliot for such typical case. > I have been looking at SQLite but realise since it works through FFI it probably blocks the VM whilst processing a query. Is this correct? > > VoyageMongo looks interesting. PostgreSQL is supported too. Do either of > these work through FFI? > > Many thanks in advance. >

Aug. 10, 2013

Re: [Pharo-users] Databases for Pharo that do not use FFI

by Mariano Martinez Peck

On Sat, Aug 10, 2013 at 10:44 AM, <vinref(a)gmail.com> wrote: > Hello > > I have been tinkering with Pharo long enough now to contemplate writing a > "serious" applications with it. An important consideration is databases. I > have been looking at SQLite but realise since it works through FFI it > probably blocks the VM whilst processing a query. Is this correct? > Yes. > > VoyageMongo looks interesting. PostgreSQL is supported too. Do either of > these work through FFI? > > Both Mongo and PostgreSQL Native Driver (implemented in Smalltalk), end up using sockets (no FFI), so from what I know, they do not lock the whole VM as with FFI. OpenDBXDriver uses OpenDBX library (using FFI) but at least OpenDBX supports async queries when the database backend supports them. That means that from Pharo we do a kind of busy waiting allowing other processes to be executed. But if the backend doesn't support async queries, then yes, OpenDBX will lock the Pharo VM while the query is being processed. I can give more details about this busy waiting in DBXTalk if you want. Cheers, > Many thanks in advance. > > -- Mariano http://marianopeck.wordpress.com

Aug. 10, 2013

Databases for Pharo that do not use FFI

by vinref＠gmail.com

Hello I have been tinkering with Pharo long enough now to contemplate writing a "serious" applications with it. An important consideration is databases. I have been looking at SQLite but realise since it works through FFI it probably blocks the VM whilst processing a query. Is this correct? VoyageMongo looks interesting. PostgreSQL is supported too. Do either of these work through FFI? Many thanks in advance.

Aug. 10, 2013

Re: [Pharo-users] New version of PharoSound

by StÃ©phane Ducasse

> Hi Stephane, > > I'm always using fresh stable version with latest updates. > Here it's Pharo 2.0 summer edition on Unbutu 12.04 64bits. > > In fact, there are a lot of wrong ways to load packages and i use them all > :) (i'm novice !!) > no problem. > So i try to use the wright way doing : > > ((Smalltalk at: #ConfigurationOfPharoSound) project version:'5.2') load. > > Sound work well. ok good to know. > Version 5.3 and more don't seem to work for 2.0. This is strange because I loaded 5.3 (I will retry). > > Stable version doesn't work with > > ConfigurationOfPharoSound project load: #stable. can you check the stable method? because > > So ... i will update my blog to give better informations ! > > Thanks for your advices ! > > Xavier. > > > > > > > -- > View this message in context: http://forum.world.st/New-version-of-PharoSound-tp4702032p4702994.html > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >

Aug. 9, 2013

Re: [Pharo-users] New version of PharoSound

by Xavier MESSNER

Hi Stephane, I'm always using fresh stable version with latest updates. Here it's Pharo 2.0 summer edition on Unbutu 12.04 64bits. In fact, there are a lot of wrong ways to load packages and i use them all :) (i'm novice !!) So i try to use the wright way doing : ((Smalltalk at: #ConfigurationOfPharoSound) project version:'5.2') load. Sound work well. Version 5.3 and more don't seem to work for 2.0. Stable version doesn't work with ConfigurationOfPharoSound project load: #stable. So ... i will update my blog to give better informations ! Thanks for your advices ! Xavier. -- View this message in context: http://forum.world.st/New-version-of-PharoSound-tp4702032p4702994.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Aug. 9, 2013

Re: [Pharo-users] New version of PharoSound

by StÃ©phane Ducasse

Hi Xavier on which version of Pharo are you working? How to do you load the code? do you use stable? Because if you read the class comment of the configuration you will see that the latest version works only for Pharo30 while the previous one works on both Pharo 20 and pharo 30. The configuration handles that well when you load the stable it should load the corresponding one. Let me know if this is not the case Stef > Hi Stef, > > I've used smalltalkhub instead of squeaksource and it still work with the > same packages i used in my tests, but when i load latest version sound stop > working. > After trying all packages i can tell that sound stop working after loading > package Sound-janniklaval.74.mcz or Sound-StephaneDucasse.72.mcz. > > When i look into changes i can see that in resumePlaying:quickStart > > BaseSoundSystem soundEnabled ifFalse: [^ self]. > ... > BaseSoundSystem soundQuickStart ifFalse: [doQuickStart := false]. > > In Sound-jannikaval.72.mcz it was > > SoundService soundEnabled ifFalse: [^ self]. > ... > self soundQuickStart ifFalse: [doQuickStart := false]. > > Not really big changes but this make sound not working anymore. > If i rollback only these 2 lines, sound work again. > > I suppose these changes are there for cleaning purpose and to have a more > uptodate sound system. I think that some stuff still missing for the moment. > It's just a question of time and hard work. > > For the moment i'll stay with Sound-Jannikaval.72. It will help me start > some sound stuff in Pharo. > I keep an eye on new versions in the same time :) > > Xavier. > > > > -- > View this message in context: http://forum.world.st/New-version-of-PharoSound-tp4702032p4702934.html > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >

Aug. 9, 2013