July 2017 - Pharo-users - lists.pharo.org

Using SandstoneDB for persistance. Getting error.

by sergio ruiz

Hi, all.. I am finally ready to work on the persistence end of my project. I am having a little bit of an issue, though.. I have very simple set of models: Customers Orders LineItems more.. The Customer has a variable called âordersâ which is just an OrderedCollection of Orders. The trick is, this is an SMS bot, so the order has a StateMachine (SsStateMachine) that, after it receives an SMS.. it processes it, and moves (or doesnât) along in state. the problem I have is, when I save the customer, I need to save the orders first (I got an error stating this). When I try to save the order, I get the following error: Â 'An ActiveRecord can not reference any sub instances of instruction stream. Â Make sure you are not saving blocks. â This looks like itâs happening at the point where it is trying to save the StateMachine.. Here is the full error.. Thanks!: Context(InstructionStream)>>sandstoneDeepCopyVisits: BlockClosure(Object)>>sandstoneDeepCopyVisits: SsState(Object)>>sandstoneDeepCopyVisits: SsStateMachine(Object)>>sandstoneDeepCopyVisits: Order(Object)>>sandstoneDeepCopyVisits: Order(SDActiveRecord)>>sandstoneDeepCopy SDFileStore>>storeObject: [ self validate. (isFirstSave := isNew) ifTrue: [ self onBeforeFirstSave ]. self onBeforeSave. isFirstSave ifTrue: [ Store storeObject: self ] ifFalse: [ Store updateObject: self ]. isFirstSave ifTrue: [ self onAfterFirstSave ]. self onAfterSave. self ] in Order(SDActiveRecord)>>save [ self enter. aBlock value ] in Monitor>>critical: BlockClosure>>ensure: Monitor>>critical: Order(SDActiveRecord)>>critical: Order(SDActiveRecord)>>save UndefinedObject>>DoIt OpalCompiler>>evaluate RubSmalltalkEditor>>evaluate:andDo: RubSmalltalkEditor>>highlightEvaluateAndDo: [ textMorph textArea editor highlightEvaluateAndDo: ann action. textMorph shoutStyler style: textMorph text ] in [ textMorph textArea handleEdit: [ textMorph textArea editor highlightEvaluateAndDo: ann action. textMorph shoutStyler style: textMorph text ] ] in GLMMorphicPharoScriptRenderer(GLMMorphicPharoCodeRenderer)>>actOnHighlightAndEvaluate: RubEditingArea(RubAbstractTextArea)>>handleEdit: [ textMorph textArea handleEdit: [ textMorph textArea editor highlightEvaluateAndDo: ann action. textMorph shoutStyler style: textMorph text ] ] in GLMMorphicPharoScriptRenderer(GLMMorphicPharoCodeRenderer)>>actOnHighlightAndEvaluate: WorldState>>runStepMethodsIn: WorldMorph>>runStepMethods WorldState>>doOneCycleNowFor: WorldState>>doOneCycleFor: WorldMorph>>doOneCycle WorldMorph class>>doOneCycle [ [ WorldMorph doOneCycle. Processor yield. false ] whileFalse: [ Â ] ] in MorphicUIManager>>spawnNewProcess [ self value. Processor terminateActive ] in BlockClosure>>newProcess ---- peace, sergio photographer, journalist, visionary Public Key:Â http://bit.ly/29z9fG0 #BitMessageÂ BM-NBaswViL21xqgg9STRJjaJaUoyiNe2dV http://www.Village-Buzz.com http://www.ThoseOptimizeGuys.com http://www.coffee-black.com http://www.painlessfrugality.com http://www.twitter.com/sergio_101 http://www.facebook.com/sergio101

July 11, 2017

Re: [Pharo-users] The method Form>>rotateBy: slows down if applied several times to the same form

by Nicolai Hess

2017-07-04 23:54 GMT+02:00 Matteo via Pharo-users < pharo-users(a)lists.pharo.org>: > > > ---------- Weitergeleitete Nachricht ---------- > From: Matteo <matteob8(a)yahoo.it> > To: "Pharo is welcome (ML)" <pharo-users(a)lists.pharo.org> > Cc: > Bcc: > Date: Tue, 4 Jul 2017 23:54:06 +0200 > Subject: The method Form>>rotateBy: slows down if applied several times to > the same form > Dears, > applying the method "Form>>rotateBy:" several times, to the same > form, the system slows down dramatically, even imposing a 0Â° rotation. > > Below you can find a code snippet, to be run on the playground: > > |aForm | > aForm:= ImageReadWriter formFromFileNamed: 'pharo.png'. > 10 timesRepeat: [ aForm := aForm rotateBy:90 ]. > > > Increasing the number of repetitions the delay get worse. > > Does someone else get the same issue? > Is there something wrong on my code, or in the way I'm using the method? > > > Hi Matteo, thanks for this contribution. It is good that you found out the reason for the slowing down (repeatly creating a bigger form is of course not good). I looked at your fix, it seems to work but both new methods are nearly identically, maybe it would be better to create another method for the common parts. And I saw that there is another method Form rotateBy: direction centerAt: aPoint with direction could be either #left or #right and it will rotate cw/ccw by 90 degree would this be useable for your use case? nicolai > > The test has been launched in a Pharo 6.0 image, Latest update: #60499, > under Linux 64bit. > > > For this question I opened the FogBugz case nÂ°20216 > > https://pharo.fogbugz.com/f/cases/20216#BugEvent.190469 > > > Thanks, > Matteo > > >

July 10, 2017

Re: [Pharo-users] [Pharo-dev] integrating FileDialog into Pharo 7

by Pavel Krivanek

Can you try to prepare a pull requeast that will integrate it? The PR will need to: - add the packages into the repository - add them into the baseline (BaselineOfUI) - remove old FileDialogWindow (becuase when we add something, we should remove something too ;-)) If you need help, let me know -- Pavel 2017-07-10 20:01 GMT+02:00 Peter Uhnak <i.uhnak(a)gmail.com>: > Done. What next? > > Peter > > > On Mon, Jul 10, 2017 at 12:46:50PM +0200, Pavel Krivanek wrote: > > We should work on integration of it. Firstly please move tests to a > > separate package. > > > > Cheers, > > -- Pavel > > > > 2017-07-10 12:34 GMT+02:00 Peter Uhnak <i.uhnak(a)gmail.com>: > > > > > Hi, > > > > > > some people expressed interest in integrating File Dialog > > > https://github.com/peteruhnak/file-dialog into Pharo as the default > file > > > dialog. > > > > > > Is it something people are interested in, or is the current solution > > > sufficient for them? > > > > > > Peter > > > > > > > >

July 10, 2017

Re: [Pharo-users] [Pharo-dev] integrating FileDialog into Pharo 7

by Peter Uhnak

Done. What next? Peter On Mon, Jul 10, 2017 at 12:46:50PM +0200, Pavel Krivanek wrote: > We should work on integration of it. Firstly please move tests to a > separate package. > > Cheers, > -- Pavel > > 2017-07-10 12:34 GMT+02:00 Peter Uhnak <i.uhnak(a)gmail.com>: > > > Hi, > > > > some people expressed interest in integrating File Dialog > > https://github.com/peteruhnak/file-dialog into Pharo as the default file > > dialog. > > > > Is it something people are interested in, or is the current solution > > sufficient for them? > > > > Peter > > > >

July 10, 2017

Re: [Pharo-users] Version code Iceberg

by Cyril Ferlicot D.

Le 10/07/2017 Ã 19:28, Benoit Verhaeghe a Ã©crit : > Hi, > > Do you know how to create project with a stable version and a development version with Iceberg ( git ). > Hi, In the configurations of Metacello you need to define the dependencies of your project and the versions because Monticello does not manage this. With git, the versions are managed by git. Thus, the baselines of Metacello only define the dependencies. So, #stable and #development versions are managed by git features. In my project I have a #master branch that should always be stable and a #development branch. I also have 1 branch/ big feature to implement. Then, when you load your code or add a dependency in a baseline, you can use an URL like: 'github://user/project:x/dir' Here x can be: - The SHA of a commit (as a31a869) - The name of a branch (as #master or #development) - A tag/release (as #v1.2.5) > I didn't find example on the internet. > > Thanks a lot > Benoit Verhaeghe > -- Cyril Ferlicot https://ferlicot.fr http://www.synectique.eu 2 rue Jacques PrÃ©vert 01, 59650 Villeneuve d'ascq France

July 10, 2017

Re: [Pharo-users] Version code Iceberg

by serge.stinckwich＠gmail.com

Like all git projects with 2 branches: one master and one dev. EnvoyÃ© de mon iPhone > Le 10 juil. 2017 Ã 18:28, Benoit Verhaeghe <benoit.verhaeghe(a)inria.fr> a Ã©crit : > > Hi, > > Do you know how to create project with a stable version and a development version with Iceberg ( git ). > > I didn't find example on the internet. > > Thanks a lot > Benoit Verhaeghe >

July 10, 2017

Version code Iceberg

by Benoit Verhaeghe

Hi, Do you know how to create project with a stable version and a development version with Iceberg ( git ). I didn't find example on the internet. Thanks a lot Benoit Verhaeghe

July 10, 2017

Re: [Pharo-users] [Pharo-dev] integrating FileDialog into Pharo 7

by Alexandre Bergel

Hi Peter! I have been using your file dialog for some time already. I really like it. Here some ideas of improvement. - double click instead of single click to dive in a folder? Single clicking feels a bit weird to me - Saving on the disk for preference folders? Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > On Jul 10, 2017, at 12:34 PM, Peter Uhnak <i.uhnak(a)gmail.com> wrote: > > Hi, > > some people expressed interest in integrating File Dialog https://github.com/peteruhnak/file-dialog into Pharo as the default file dialog. > > Is it something people are interested in, or is the current solution sufficient for them? > > Peter >

July 10, 2017

Re: [Pharo-users] [Pharo-dev] integrating FileDialog into Pharo 7

by Pavel Krivanek

We should work on integration of it. Firstly please move tests to a separate package. Cheers, -- Pavel 2017-07-10 12:34 GMT+02:00 Peter Uhnak <i.uhnak(a)gmail.com>: > Hi, > > some people expressed interest in integrating File Dialog > https://github.com/peteruhnak/file-dialog into Pharo as the default file > dialog. > > Is it something people are interested in, or is the current solution > sufficient for them? > > Peter > >

July 10, 2017

integrating FileDialog into Pharo 7

by Peter Uhnak

Hi, some people expressed interest in integrating File Dialog https://github.com/peteruhnak/file-dialog into Pharo as the default file dialog. Is it something people are interested in, or is the current solution sufficient for them? Peter

July 10, 2017