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

Re: [Pharo-users] [Pharo-dev] InfoWorld on Redline Smalltalk

by Johan Fabry

I donât know the entire context of the discussion (iâm not following Pharo-dev, where this came from apparently.) But I would like to point out that it is wrong to think of Spec as an abandoned project! Spec is here to stay, and hopefully for a very long time. > On Jan 15, 2015, at 09:08, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: > > I wouldn't do a PR campaign mentioning VW's Pollock UI, Pharo's Spec or any other abandoned project whatsoever. ---> Save our in-boxes! http://emailcharter.org <--- Johan Fabry - http://pleiad.cl/~jfabry PLEIAD lab - Computer Science Department (DCC) - University of Chile

Jan. 15, 2015

Re: [Pharo-users] [Pharo-dev] InfoWorld on Redline Smalltalk

by Esteban A. Maringolo

El ene 15, 2015 8:55 AM, "Sebastian Sastre" <sebastian(a)flowingconcept.com> escribiÃ³: > > >> On Jan 14, 2015, at 9:44 PM, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: >> >> Shaking the hive can certainly have a positive outcome, but you can also get you bitten. :) > > > And whatâs the news on that? > > The world is full of people paralysed by fear. > > Scared people is not worth following (they are not going to invent any interesting future). > > The ones who dear to do different are way more interesting. > I totally agree with you. But the mentioned project was a viable option two years ago, when it was trying to get developer traction and the "runs on JVM" was a hyped feature (not to mention the bad experience almost everyone had with such things). Amber is, IMO, way more valuable and with a greater feature than Redline. And I never used any of them. I wouldn't do a PR campaign mentioning VW's Pollock UI, Pharo's Spec or any other abandoned project whatsoever. A different thing is a project of which you can expect to move at a slow pace, but uninterruptedly. Regards,

Jan. 15, 2015

InfoWorld on Redline Smalltalk

by Stephan Eggermont

continued from pharo-dev, please keep discussion here. The smalltalk on jvm situation is exactly like it shouldn't be. There are three implementations, not working together: - RTalk - Gravel - Redline The first two are driven by existing commercial smalltalk users coming from a platform that they feel is not sufficiently developing (different ones). This amount of fragmentation is ridiculous. Of course they have different priorities and needs, but it should be possible to share the work that all three feel they have to do. The result is that at least two of them move forward very slowly. Stephan

Jan. 15, 2015

Re: [Pharo-users] Making objects persistent

by Ben Coman

Store the objects in an array in a class variable. To delete, just nil the class variable. On Thu, Jan 15, 2015 at 3:44 PM, jtuchel(a)objektfabrik.de < jtuchel(a)objektfabrik.de> wrote: > Sergio, > > I'D say you first need to define what you mean by "persistent" If all you > need is to have them survive a Garbage Collection, you just need to make > sure these objects are referenced by som eother objects. Depending on your > use case, this can be Seaside Sessions, Global variables (probably the > worst idea), TestCase subclasses or even a TestResource. > > If you want to persist them for longer, we are talking about storage of > objects, which is another beast. What comes to mind are options like Fuel, > STON, Json, Voyage/Mongo or Glorp with some Database - the choices are > endless. > > Joachim > > > Am 15.01.15 um 08:32 schrieb phil(a)highoctane.be: > > On Thu, Jan 15, 2015 at 6:06 AM, sergio_101 <sergio.rrd(a)gmail.com> wrote: > >> I am building a seaside application, and am in the process of building my >> models and unit tests. >> >> I have a few objects that build up my data by creating objects. >> >> when i run the data creation methods, everything is fine. immediately >> afterward, since these objects to belong to anything, they are cleaned up >> by garbage collection. >> >> > >> is there a way to create these objects so that they persist? >> > > > They should belong to your session if you want them to live for the > session. > > Otherwise, I guess you can put them in a global var to make it available > everywhere, or in > > GRObject>>application, session, or requestContext depending on how long > you want them to live. > > > >> if this is possible, how would you go about deleting such a tenacious >> object? >> > > Session expiry for session vars. The other ones, standard Smalltalk way, > replacing the reference with something else innocuous if you can't get rid > of them the normal gc way. > > Like, x become: String new. (and not x become: nil, which would make nil > become x...) > >> >> thanks! >> > > > > > > > > > > > > > -- > ----------------------------------------------------------------------- > Objektfabrik Joachim Tuchel mailto:jtuchel@objektfabrik.de <jtuchel(a)objektfabrik.de> > Fliederweg 1 http://www.objektfabrik.de > D-71640 Ludwigsburg http://joachimtuchel.wordpress.com > Telefon: +49 7141 56 10 86 0 Fax: +49 7141 56 10 86 1 > > >

Jan. 15, 2015

Re: [Pharo-users] Could we keep Pharo-dev for Pharo-dev?

by Norbert Hartl

To me it goes like that: - pharo-dev is used by people that discuss, develop, bug fix the pharo image itself - pharo-users is used by people that maybe just want to download pharo and work with it not interested in the detailed internal things - a pharo-dev person is very likely subscribed to pharo-users, too - a lot pharo-users persons are not subscribed to pharo-dev Now what information is interesting to people that want to use pharo? I'd say that new tools and new features of their environment are interesting things for them. So, I would put everything on pharo-users that a plain user of the environment might want to know off. Norbert > Am 15.01.2015 um 10:07 schrieb kilon alios <kilon.alios(a)gmail.com>: > > does that mean that announcing new pharo tools that are included in the standard pharo distribution should go to pharo-users ? > > On Thu, Jan 15, 2015 at 9:24 AM, stepharo <stepharo(a)free.fr <mailto:stepharo@free.fr>> wrote: > Hi guys > > I will start to be picky about the mails to which I reply or even read. > We should be more disciplined. Pharo-dev should be about Pharo-dev this is important > for our concentration. > I really like the other discussions but we should have them in Pharo-users. > I think that it makes sense. > > Stef > >

Jan. 15, 2015

Re: [Pharo-users] Could we keep Pharo-dev for Pharo-dev?

by kilon alios

does that mean that announcing new pharo tools that are included in the standard pharo distribution should go to pharo-users ? On Thu, Jan 15, 2015 at 9:24 AM, stepharo <stepharo(a)free.fr> wrote: > Hi guys > > I will start to be picky about the mails to which I reply or even read. > We should be more disciplined. Pharo-dev should be about Pharo-dev this is > important > for our concentration. > I really like the other discussions but we should have them in Pharo-users. > I think that it makes sense. > > Stef > >

Jan. 15, 2015

Re: [Pharo-users] [Pharo-dev] Could we keep Pharo-dev for Pharo-dev?

by Serge Stinckwich

On Thu, Jan 15, 2015 at 9:38 AM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > >> On 15 Jan 2015, at 08:24, stepharo <stepharo(a)free.fr> wrote: >> >> Hi guys >> >> I will start to be picky about the mails to which I reply or even read. >> We should be more disciplined. Pharo-dev should be about Pharo-dev this is important >> for our concentration. >> I really like the other discussions but we should have them in Pharo-users. >> I think that it makes sense. >> >> Stef > > YES ! > > We should also ourselves use the right mailing list when asking our own questions. > > And we should point people using the wrong list to the right one. +1 and point to Pharo StackOverflow questions/answers if necessary. -- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/

Jan. 15, 2015

Re: [Pharo-users] Could we keep Pharo-dev for Pharo-dev?

by Sven Van Caekenberghe

> On 15 Jan 2015, at 08:24, stepharo <stepharo(a)free.fr> wrote: > > Hi guys > > I will start to be picky about the mails to which I reply or even read. > We should be more disciplined. Pharo-dev should be about Pharo-dev this is important > for our concentration. > I really like the other discussions but we should have them in Pharo-users. > I think that it makes sense. > > Stef YES ! We should also ourselves use the right mailing list when asking our own questions. And we should point people using the wrong list to the right one.

Jan. 15, 2015

Re: [Pharo-users] Could we keep Pharo-dev for Pharo-dev?

by Norbert Hartl

Absolutely! Norbert > Am 15.01.2015 um 08:24 schrieb stepharo <stepharo(a)free.fr>: > > Hi guys > > I will start to be picky about the mails to which I reply or even read. > We should be more disciplined. Pharo-dev should be about Pharo-dev this is important > for our concentration. > I really like the other discussions but we should have them in Pharo-users. > I think that it makes sense. > > Stef >

Jan. 15, 2015

Re: [Pharo-users] [Pharo-dev] Could we keep Pharo-dev for Pharo-dev?

by Serge Stinckwich

+1 On Thu, Jan 15, 2015 at 8:24 AM, stepharo <stepharo(a)free.fr> wrote: > Hi guys > > I will start to be picky about the mails to which I reply or even read. > We should be more disciplined. Pharo-dev should be about Pharo-dev this is > important > for our concentration. > I really like the other discussions but we should have them in Pharo-users. > I think that it makes sense. > > Stef > -- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/

Jan. 15, 2015