- Pharo-users - lists.pharo.org

Re: [Pharo-users] Mongo with Voyage

by Asbath Sama biyalou

Thanks. On 17/11/2016 13:25, Norbert Hartl wrote: > > > Am 17.11.2016 um 13:12 schrieb Asbath Sama biyalou > <asamabiyalou(a)yahoo.com <mailto:asamabiyalou@yahoo.com>>: > >> Please Not very clear. Then I just execute that method in the >> playground and It is good. >> >> > yes > > Norbert >> On 17/11/2016 12:55, Norbert Hartl wrote: >>> Ahh, I see. Your initializeMongo is actually a configuration of the >>> system. That configuration you do once in the image, hence the name >>> #enableSingleton because it is accessible as singleton from >>> everywhere. >>> >>> Norbert >>> >>>> Am 17.11.2016 um 12:44 schrieb Asbath Sama biyalou >>>> <asamabiyalou(a)yahoo.com <mailto:asamabiyalou@yahoo.com>>: >>>> >>>> Thanks. Just look my function look like this: >>>> >>>> initializeMongo >>>> | repository | >>>> repository := VOMongoRepository >>>> host: 'example.com <http://example.com>' >>>> port: 27017 >>>> database: 'example_name'. >>>> repository enableSingleton. >>>> >>>> "Collections are created automatically as soon as you access them >>>> the first time." That is true but to connect to the >>>> database. >>>> >>>> In which I have to implement that method : all the root classes or >>>> what. >>>> >>>> On 17/11/2016 12:34, Norbert Hartl wrote: >>>>> I'm not sure what you mean with initialize. If you think about >>>>> creating the collections in mongo then you have to do nothing. >>>>> Collections are created automatically as soon as you access them >>>>> the first time. >>>>> >>>>> Norbert >>>>> >>>>> >>>>>> Am 17.11.2016 um 12:29 schrieb Asbath Sama biyalou via >>>>>> Pharo-users <pharo-users(a)lists.pharo.org >>>>>> <mailto:pharo-users@lists.pharo.org>>: >>>>>> >>>>>> >>>>>> *Von: *Asbath Sama biyalou <asamabiyalou(a)yahoo.com >>>>>> <mailto:asamabiyalou@yahoo.com>> >>>>>> *Betreff: **Mongo with Voyage* >>>>>> *Datum: *17. November 2016 um 12:29:24 MEZ >>>>>> *An: *pharo-users(a)lists.pharo.org >>>>>> <mailto:pharo-users@lists.pharo.org> >>>>>> >>>>>> >>>>>> Hello. >>>>>> I'am using pharo 4.0 with external mongo database (mongolab.com >>>>>> <http://mongolab.com/>) >>>>>> I have like 7 classes which are voyageRoot. >>>>>> I want to know if I will initialize mongo in each class or in which >>>>>> class I can implement it. >>>>>> Thanks >>>>>> >>>>>> >>>>>> >>>>> >>>> >>> >>

Nov. 17, 2016

Re: [Pharo-users] Mongo with Voyage

by Norbert Hartl

> Am 17.11.2016 um 13:12 schrieb Asbath Sama biyalou <asamabiyalou(a)yahoo.com>: > > Please Not very clear. Then I just execute that method in the playground and It is good. > yes Norbert >> On 17/11/2016 12:55, Norbert Hartl wrote: >> Ahh, I see. Your initializeMongo is actually a configuration of the system. That configuration you do once in the image, hence the name #enableSingleton because it is accessible as singleton from everywhere. >> >> Norbert >> >>> Am 17.11.2016 um 12:44 schrieb Asbath Sama biyalou <asamabiyalou(a)yahoo.com>: >>> >>> Thanks. Just look my function look like this: >>> initializeMongo >>> | repository | >>> repository := VOMongoRepository >>> host: 'example.com' >>> port: 27017 >>> database: 'example_name'. >>> repository enableSingleton. >>> >>> "Collections are created automatically as soon as you access them the first time." That is true but to connect to the >>> database. >>> >>> In which I have to implement that method : all the root classes or what. >>>> On 17/11/2016 12:34, Norbert Hartl wrote: >>>> I'm not sure what you mean with initialize. If you think about creating the collections in mongo then you have to do nothing. Collections are created automatically as soon as you access them the first time. >>>> >>>> Norbert >>>> >>>> >>>>> Am 17.11.2016 um 12:29 schrieb Asbath Sama biyalou via Pharo-users <pharo-users(a)lists.pharo.org>: >>>>> >>>>> >>>>> Von: Asbath Sama biyalou <asamabiyalou(a)yahoo.com> >>>>> Betreff: Mongo with Voyage >>>>> Datum: 17. November 2016 um 12:29:24 MEZ >>>>> An: pharo-users(a)lists.pharo.org >>>>> >>>>> >>>>> Hello. >>>>> I'am using pharo 4.0 with external mongo database (mongolab.com) >>>>> I have like 7 classes which are voyageRoot. >>>>> I want to know if I will initialize mongo in each class or in which >>>>> class I can implement it. >>>>> Thanks >>>>> >>>>> >>>>> >>>> >>> >> >

Nov. 17, 2016

Re: [Pharo-users] Mongo with Voyage

by Asbath Sama biyalou

Please Not very clear. Then I just execute that method in the playground and It is good. On 17/11/2016 12:55, Norbert Hartl wrote: > Ahh, I see. Your initializeMongo is actually a configuration of the > system. That configuration you do once in the image, hence the name > #enableSingleton because it is accessible as singleton from everywhere. > > Norbert > >> Am 17.11.2016 um 12:44 schrieb Asbath Sama biyalou >> <asamabiyalou(a)yahoo.com <mailto:asamabiyalou@yahoo.com>>: >> >> Thanks. Just look my function look like this: >> >> initializeMongo >> | repository | >> repository := VOMongoRepository >> host: 'example.com <http://example.com>' >> port: 27017 >> database: 'example_name'. >> repository enableSingleton. >> >> "Collections are created automatically as soon as you access them the >> first time." That is true but to connect to the >> database. >> >> In which I have to implement that method : all the root classes or what. >> >> On 17/11/2016 12:34, Norbert Hartl wrote: >>> I'm not sure what you mean with initialize. If you think about >>> creating the collections in mongo then you have to do nothing. >>> Collections are created automatically as soon as you access them the >>> first time. >>> >>> Norbert >>> >>> >>>> Am 17.11.2016 um 12:29 schrieb Asbath Sama biyalou via Pharo-users >>>> <pharo-users(a)lists.pharo.org <mailto:pharo-users@lists.pharo.org>>: >>>> >>>> >>>> *Von: *Asbath Sama biyalou <asamabiyalou(a)yahoo.com >>>> <mailto:asamabiyalou@yahoo.com>> >>>> *Betreff: **Mongo with Voyage* >>>> *Datum: *17. November 2016 um 12:29:24 MEZ >>>> *An: *pharo-users(a)lists.pharo.org <mailto:pharo-users@lists.pharo.org> >>>> >>>> >>>> Hello. >>>> I'am using pharo 4.0 with external mongo database (mongolab.com >>>> <http://mongolab.com/>) >>>> I have like 7 classes which are voyageRoot. >>>> I want to know if I will initialize mongo in each class or in which >>>> class I can implement it. >>>> Thanks >>>> >>>> >>>> >>> >> >

Nov. 17, 2016

Re: [Pharo-users] Mongo with Voyage

by Norbert Hartl

Ahh, I see. Your initializeMongo is actually a configuration of the system. That configuration you do once in the image, hence the name #enableSingleton because it is accessible as singleton from everywhere. Norbert > Am 17.11.2016 um 12:44 schrieb Asbath Sama biyalou <asamabiyalou(a)yahoo.com>: > > Thanks. Just look my function look like this: > initializeMongo > | repository | > repository := VOMongoRepository > host: 'example.com' > port: 27017 > database: 'example_name'. > repository enableSingleton. > > "Collections are created automatically as soon as you access them the first time." That is true but to connect to the > database. > > In which I have to implement that method : all the root classes or what. > On 17/11/2016 12:34, Norbert Hartl wrote: >> I'm not sure what you mean with initialize. If you think about creating the collections in mongo then you have to do nothing. Collections are created automatically as soon as you access them the first time. >> >> Norbert >> >> >>> Am 17.11.2016 um 12:29 schrieb Asbath Sama biyalou via Pharo-users <pharo-users(a)lists.pharo.org <mailto:pharo-users@lists.pharo.org>>: >>> >>> >>> Von: Asbath Sama biyalou <asamabiyalou(a)yahoo.com <mailto:asamabiyalou@yahoo.com>> >>> Betreff: Mongo with Voyage >>> Datum: 17. November 2016 um 12:29:24 MEZ >>> An: pharo-users(a)lists.pharo.org <mailto:pharo-users@lists.pharo.org> >>> >>> >>> Hello. >>> I'am using pharo 4.0 with external mongo database (mongolab.com <http://mongolab.com/>) >>> I have like 7 classes which are voyageRoot. >>> I want to know if I will initialize mongo in each class or in which >>> class I can implement it. >>> Thanks >>> >>> >>> >> >

Nov. 17, 2016

Re: [Pharo-users] Mongo with Voyage

by Asbath Sama biyalou

Thanks. Just look my function look like this: initializeMongo | repository | repository := VOMongoRepository host: 'example.com' port: 27017 database: 'example_name'. repository enableSingleton. "Collections are created automatically as soon as you access them the first time." That is true but to connect to the database. In which I have to implement that method : all the root classes or what. On 17/11/2016 12:34, Norbert Hartl wrote: > I'm not sure what you mean with initialize. If you think about > creating the collections in mongo then you have to do nothing. > Collections are created automatically as soon as you access them the > first time. > > Norbert > > >> Am 17.11.2016 um 12:29 schrieb Asbath Sama biyalou via Pharo-users >> <pharo-users(a)lists.pharo.org <mailto:pharo-users@lists.pharo.org>>: >> >> >> *Von: *Asbath Sama biyalou <asamabiyalou(a)yahoo.com >> <mailto:asamabiyalou@yahoo.com>> >> *Betreff: **Mongo with Voyage* >> *Datum: *17. November 2016 um 12:29:24 MEZ >> *An: *pharo-users(a)lists.pharo.org <mailto:pharo-users@lists.pharo.org> >> >> >> Hello. >> I'am using pharo 4.0 with external mongo database (mongolab.com >> <http://mongolab.com>) >> I have like 7 classes which are voyageRoot. >> I want to know if I will initialize mongo in each class or in which >> class I can implement it. >> Thanks >> >> >> >

Nov. 17, 2016

Re: [Pharo-users] Mongo with Voyage

by Norbert Hartl

I'm not sure what you mean with initialize. If you think about creating the collections in mongo then you have to do nothing. Collections are created automatically as soon as you access them the first time. Norbert > Am 17.11.2016 um 12:29 schrieb Asbath Sama biyalou via Pharo-users <pharo-users(a)lists.pharo.org>: > > > Von: Asbath Sama biyalou <asamabiyalou(a)yahoo.com> > Betreff: Mongo with Voyage > Datum: 17. November 2016 um 12:29:24 MEZ > An: pharo-users(a)lists.pharo.org > > > Hello. > I'am using pharo 4.0 with external mongo database (mongolab.com) > I have like 7 classes which are voyageRoot. > I want to know if I will initialize mongo in each class or in which > class I can implement it. > Thanks > > >

Nov. 17, 2016

Mongo with Voyage

by Asbath Sama biyalou

Hello. I'am using pharo 4.0 with external mongo database (mongolab.com) I have like 7 classes which are voyageRoot. I want to know if I will initialize mongo in each class or in which class I can implement it. Thanks

Nov. 17, 2016

Re: [Pharo-users] QCMagritte question- does it have undo?

by stepharo

Paul there is an undo framework inside Pharo I imagine that you can use it to build your ideas. Stef Le 11/11/16 Ã 18:31, Paul DeBruicker a Ã©crit : > Thanks Norbert. > > I'm not sure of the feasibility/value but I think it would be nice to be > able to undo back to a clean slate and redo all the way to a fully fleshed > out system. Or at least some sane way in a multi-user environment. > > > I wonder how etherpad.org has their undo structured. I'll go check it out. > > > Paul > > > > > > > > NorbertHartl wrote >>> Am 11.11.2016 um 06:03 schrieb PAUL DEBRUICKER < >> pdebruic@ >> >: >>> I've never used magritte or QC magritte and was wondering whether with >>> the momento it qas also possible to get multi step undo cheaply if it >>> didn't already exist. >>> >> I don't know if it exists. But you just need to save the current memento, >> copy it (make sure the dictionary inside is another instance) and use >> that. This would work before a commit has been done. Do you want to undo >> even commited stuff? >> >> Norbert > > > > > -- > View this message in context: http://forum.world.st/QCMagritte-question-does-it-have-undo-tp4922643p49227… > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > >

Nov. 17, 2016

Re: [Pharo-users] Pier3 with latest Pillar?

by stepharo

For me, Pillar was a package in Pier, and Pier was a tool that I used for all my presentations, prototyping, and small or short-lived community and not-for-profit projects. I do not get why you cannot use Pharo for that. Le 17/11/16 Ã 02:04, Jupiter Jones a Ã©crit : > Hey Stephane, > >>> It would be nice to see Pillar return to being a cross platform project as well. One of the beautiful things about Seaside/Magritte/Pier was itâs compatibility across many dialects of Smalltalk. The âdevelop in Pharo and deploy in GemStoneâ was a big draw for me :) One of my clients uses VW so it was great to have these projects there as well. >> Yes but at the end of the day. You see we cannot work for free and in addition got constraints that are dragging us behind. > Absolutely! Luckily the hard work of cross-compatability has already been done for Pier. Iâm just hoping we can keep the parts of Pillar on which Pier is reliant working across dialects - Pharo and GemStone at least. From memory, the only thing that made it hard was PRTParametrizable. > > I imagine very few of us are being paid for the contributions we make. In my case, itâs only when I have a paid project that allows me to work in Smalltalk, that I can invest some of that paid time in contributing towards the packages Iâm using for that project. > > I also feel my smalltalk-ability isnât up to the standard of so many of the amazing people contributing, which makes me a little reticent to get involved in the more complex projects. > >> I will see if the trait usage make sense and can be removed. But you see if everything we do has to be compatible better be dead. > Maybe not a matter of code or die, but certainly a matter of style and most likely a commitment to more pain. it is (sometimes much) harder working with community projects since it takes working with that community - and everyone has their own use case, and at least three opinions. :) > > Iâve experienced this many time in non-software projects. It may take a little longer to get there, but itâs definitely worth the extra pain it in the end. > >> I would prefer to see GS having an infrastructure to load Pharo kernels. We are pushing the bootstrap for this reasons. > Dale and the GemStone team are doing a great job moving towards that ideal. Their constraints are even greater since they have a large commercial install base supporting many platforms. We should be able to be more flexible and dynamic > >> Because you see Pharo will use more and more slots because they are really really cool and powerful. >> What do you do with Pillar? Because I write books, slides, and websites so this is an important piece of software for me. > For me, Pillar was a package in Pier, and Pier was a tool that I used for all my presentations, prototyping, and small or short-lived community and not-for-profit projects. > >>> Iâd like to see Pier get some love - itâs an awesome tool. How can I help? >> Join and hack. > Iâd love to! I noticed that the issue tracker and other Pillar related stuff is now on GitHub which is awesome. Is there any chance that the Smalltalk project could also move there? It would make it easier to fork and hack and make versions available to test before deciding what might be valuable pushed back to the core project. > > Thanks for all your excellent work with Pillar - not to mention everything else! > > Have fun! > > Jupiter > >

Nov. 17, 2016

Re: [Pharo-users] Pier3 with latest Pillar?

by stepharo

>>> It would be nice to see Pillar return to being a cross platform project as well. One of the beautiful things about Seaside/Magritte/Pier was itâs compatibility across many dialects of Smalltalk. The âdevelop in Pharo and deploy in GemStoneâ was a big draw for me :) One of my clients uses VW so it was great to have these projects there as well. >> Yes but at the end of the day. You see we cannot work for free and in addition got constraints that are dragging us behind. > Absolutely! Luckily the hard work of cross-compatability has already been done for Pier. Iâm just hoping we can keep the parts of Pillar on which Pier is reliant working across dialects - Pharo and GemStone at least. From memory, the only thing that made it hard was PRTParametrizable. > > I imagine very few of us are being paid for the contributions we make. In my case, itâs only when I have a paid project that allows me to work in Smalltalk, that I can invest some of that paid time in contributing towards the packages Iâm using for that project. Which packages? > I also feel my smalltalk-ability isnât up to the standard of so many of the amazing people contributing, which makes me a little reticent to get involved in the more complex projects. You see fixing a comment or adding a test should be possible. Don't hide yourself behind this argument. >> I will see if the trait usage make sense and can be removed. But you see if everything we do has to be compatible better be dead. > Maybe not a matter of code or die, but certainly a matter of style and most likely a commitment to more pain. it is (sometimes much) harder working with community projects since it takes working with that community - and everyone has their own use case, and at least three opinions. :) > > Iâve experienced this many time in non-software projects. It may take a little longer to get there, but itâs definitely worth the extra pain it in the end. > >> I would prefer to see GS having an infrastructure to load Pharo kernels. We are pushing the bootstrap for this reasons. > Dale and the GemStone team are doing a great job moving towards that ideal. Their constraints are even greater since they have a large commercial install base supporting many platforms. Come on. Pharo too and we have far less ressources!!! > We should be able to be more flexible and dynamic > >> Because you see Pharo will use more and more slots because they are really really cool and powerful. >> What do you do with Pillar? Because I write books, slides, and websites so this is an important piece of software for me. > For me, Pillar was a package in Pier, and Pier was a tool that I used for all my presentations, prototyping, and small or short-lived community and not-for-profit projects. Ok then you can still use an old version of Pier and hope that others will do what you want. >>> Iâd like to see Pier get some love - itâs an awesome tool. How can I help? >> Join and hack. > Iâd love to! I noticed that the issue tracker and other Pillar related stuff is now on GitHub which is awesome. Is there any chance that the Smalltalk project could also move there? It would make it easier to fork and hack and make versions available to test before deciding what might be valuable pushed back to the core project. Why easier? You cannot produce a slice? Seriously I will not move pillar to github before Pharo has a fully working solution. And I will maintain pillar but I need time. > > Thanks for all your excellent work with Pillar - not to mention everything else! > > Have fun! > > Jupiter > >

Nov. 17, 2016