March 2015 - Pharo-users - lists.pharo.org

Re: [Pharo-users] practices in storing users application level variables

by jtuchel＠objektfabrik.de

Giving this another thought, you may want to think about dividing between user-specific and "global" state in general. This is not so important if you don't want to persist the data, but if you do, you can store user-specific data seperately. So this is not only helpful when multiple users can use the application in parallel (web apps), but also if people use it one after the other. So make it two objects: one associated to the app, one for each user. In some cases, there may not be "global" state, everything is probably user-specific Then we're back to your initial idea ;-) Joachim Am 20.03.15 um 14:58 schrieb jtuchel(a)objektfabrik.de: > Sanjay, > > I am not a big fan of Dictionaries for these kinds of things, but if > you need "named slots" for a previously unknown list of settings, the > approach you describe is perfectly okay, IMO. > This approach can also be extended into a database or any other kind > of storage and also stands the test of web apps, in so far as you can > distribute things between an application centric (global) and > user-centric (session) objects. > > Joachim > > Am 20.03.15 um 14:14 schrieb Sanjay Minni: >> Hi >> >> What is the usual practices in storing values of variables / >> parameters the >> persist through an users usage of an application. >> >> e.g. say the user logs in and then selects a current printer, current >> company, accounting year and then moves between various application >> options >> and eventually logs out. What is a good practice of storing the values >> >> ... one way could be to keep a separate application level object with a >> dictionary for all the variables ... would that be ok or there are other >> better ways >> >> regards >> Sanjay >> >> >> >> >> >> >> ----- >> --- >> Regards, Sanjay >> -- >> View this message in context: >> http://forum.world.st/practices-in-storing-users-application-level-variable… >> Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >> >> > > >

March 20, 2015

Re: [Pharo-users] practices in storing users application level variables

by jtuchel＠objektfabrik.de

Sanjay, I am not a big fan of Dictionaries for these kinds of things, but if you need "named slots" for a previously unknown list of settings, the approach you describe is perfectly okay, IMO. This approach can also be extended into a database or any other kind of storage and also stands the test of web apps, in so far as you can distribute things between an application centric (global) and user-centric (session) objects. Joachim Am 20.03.15 um 14:14 schrieb Sanjay Minni: > Hi > > What is the usual practices in storing values of variables / parameters the > persist through an users usage of an application. > > e.g. say the user logs in and then selects a current printer, current > company, accounting year and then moves between various application options > and eventually logs out. What is a good practice of storing the values > > ... one way could be to keep a separate application level object with a > dictionary for all the variables ... would that be ok or there are other > better ways > > regards > Sanjay > > > > > > > ----- > --- > Regards, Sanjay > -- > View this message in context: http://forum.world.st/practices-in-storing-users-application-level-variable… > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > >

March 20, 2015

practices in storing users application level variables

by Sanjay Minni

Hi What is the usual practices in storing values of variables / parameters the persist through an users usage of an application. e.g. say the user logs in and then selects a current printer, current company, accounting year and then moves between various application options and eventually logs out. What is a good practice of storing the values ... one way could be to keep a separate application level object with a dictionary for all the variables ... would that be ok or there are other better ways regards Sanjay ----- --- Regards, Sanjay -- View this message in context: http://forum.world.st/practices-in-storing-users-application-level-variable… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

March 20, 2015

Re: [Pharo-users] ZeroConf: Download Specific Update

by Marcus Denker

> On 20 Mar 2015, at 13:17, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > Is there a way to get e.g. #40556 specifically? > no

March 20, 2015

Re: [Pharo-users] ZeroConf: Download Specific Update

by Peter UhnÃ¡k

This? http://files.pharo.org/image/40/ Peter On Fri, Mar 20, 2015 at 1:17 PM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > Is there a way to get e.g. #40556 specifically? > > > > ----- > Cheers, > Sean > -- > View this message in context: > http://forum.world.st/ZeroConf-Download-Specific-Update-tp4813583.html > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > >

March 20, 2015

ZeroConf: Download Specific Update

by Sean P. DeNigris

Is there a way to get e.g. #40556 specifically? ----- Cheers, Sean -- View this message in context: http://forum.world.st/ZeroConf-Download-Specific-Update-tp4813583.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

March 20, 2015

Re: [Pharo-users] searching for protocols

by Sean P. DeNigris

Forwarding. Apparently never made it to list... BriceG wrote > Hi > > I don't know if there is a graphical way to do it but in the play ground > you can try the following piece of code: > > > protocolName := 'as yet unclassified'. > Smalltalk allClasses select:[:class| > (class organization protocolOrganizer allProtocols collect:#name) > includes:protocolName ]. > > > Regards > > > -------------- > Brice Govin > PhD student in RMoD research team at INRIA Lille > Software Engineer at THALES AIR SYSTEMS Rungis > ENSTA-Bretagne ENSI2014 > 64 chemin des boeufs 91220 PALAISEAU ----- Cheers, Sean -- View this message in context: http://forum.world.st/searching-for-protocols-tp4813356p4813565.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

March 20, 2015

Re: [Pharo-users] New random generator

by Werner Kassens

On 03/20/2015 09:32 AM, stepharo wrote: > Now I saw that the postload invoke this method but > DhbMaximumLikelihoodHistogramFit does not exist. > So the postload should be removed. Hi Stephane, hi Serge, this postload was made by someone as a kind of improvised depreciation (DhbMaximumLikelihoodHistogramFit does exist). but it certainly is not necessary anymore. i can update the config accordingly, if thats ok with you. i would keep the #alias... method nevertheless so that the older versions still work. and i noticed that you did not change the stable version for pharo3 to the new version, but i could not find any incompatibilities in the new rngs with 3.0. i guess i could change the stable version for 3.0 too, is that correct? werner

March 20, 2015

Re: [Pharo-users] New random generator

by Serge Stinckwich

On Fri, Mar 20, 2015 at 9:32 AM, stepharo <stepharo(a)free.fr> wrote: > Ok I added the two RNG in Math-Random. > I cleaned also the hierarchy. > - no need to have initialize as abstract to force all the subclass to > define an empty method. Strange design > - tab a bit the code and comments. > > I produced a new configuration based on SergeStinkwich 20 (which was not in > the latest configurationOf). > > > Now I saw that the postload invoke this method but > DhbMaximumLikelihoodHistogramFit does not exist. > So the postload should be removed. > > > aliasToTypoClassNameDhbMaximumLikekihoodHistogramFit > > Smalltalk at: #DhbMaximumLikekihoodHistogramFit put: > DhbMaximumLikelihoodHistogramFit > Thank you Stephane ! I will have a look to your modifications. At the moment, distributions and RNG are little messy. There is some distributions/RNGs in Math-Random, others in DHB packages. The API is not really the same between them. I have to clean everything in order to have a clean and standard API. -- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/

March 20, 2015

Re: [Pharo-users] New random generator

by stepharo

Ok I added the two RNG in Math-Random. I cleaned also the hierarchy. - no need to have initialize as abstract to force all the subclass to define an empty method. Strange design - tab a bit the code and comments. I produced a new configuration based on SergeStinkwich 20 (which was not in the latest configurationOf). Now I saw that the postload invoke this method but DhbMaximumLikelihoodHistogramFit does not exist. So the postload should be removed. aliasToTypoClassNameDhbMaximumLikekihoodHistogramFit Smalltalk at: #DhbMaximumLikekihoodHistogramFit put: DhbMaximumLikelihoodHistogramFit

March 20, 2015