Re: [Pharo-users] GTTools and Mongo

And now for 2 images... Pharo 4 for tools like this. Pharo 3 for production code... Any way to get this on 3 you think? MongoTalk works fine there. Am switching betweeen Pharo and Robomongo all the time here :-) FWIW Mapless and its mongo support is quite awesome. I am using it for a feature an

Re: [Pharo-users] GTTools and Mongo

Hi Phil, Le 11 mars 2015 à 08:48, p...@highoctane.be a écrit : > FWIW Mapless and its mongo support is quite awesome. I am using it for a > feature and it has tremendous potential. > I would be interested to have a small comparison between voyage and mapless (pros and cons). Do you have enoug

Re: [Pharo-users] GTTools and Mongo

Hi Phil, The extensions should without problems on the stable version of GTInspector for Pharo 3. Cheers, Doru On Wed, Mar 11, 2015 at 8:48 AM, p...@highoctane.be wrote: > And now for 2 images... > > Pharo 4 for tools like this. > Pharo 3 for production code... > > Any way to get this on 3 yo

[Pharo-users] Jenkins build trigger

Thanks to Esteban add-on on Smalltalkhub, it is now possible to notify Jenkins that there is a new package published for your project. What we do for now is to poll very often (each minute) smalltalkub to check if there is an update. It is a big waste of resources! Now we can do better! It would

Re: [Pharo-users] GTTools and Mongo

Hi, On Wed, Mar 11, 2015 at 7:41 PM, Torsten Bergmann wrote: > Ben wrote: > >A blog article on that would be cool :) > > This was already in the pipe: > https://medium.com/@astares/building-a-mongo-browser-in-pharo-fe2104052843 > but dont tell anyone otherwise our community will be even cooler ;

[Pharo-users] using spotter to navigate through the file system

Hi, Here is a little post that describes how you can use GTSpotter to navigate through the file system: http://www.humane-assessment.com/blog/searching-file-system-with-gtspotter/ If you combine this with the GTInspector ability of allowing you interact with the file references, you get a pretty

[Pharo-users] Pillar parser rewrite: PetitParser or not?

Hi, The current pillar parser has several problems: - it is hard to understand and change - it discards input locations I think a refactor or rewrite is necessary. What are the pros and cons of using PetitParser to do that? Best

[Pharo-users] [ANN] TODO List of Requested Features

I've just written a list of nice features we miss in Pillar: http://www.smalltalkhub.com/#!/~Pier/Pillar Please contribute by either making the list longer or, and I would prefer that, making it shorter.

Re: [Pharo-users] Pillar parser rewrite: PetitParser or not?

I completely agree. I think there are mostly pros. It can be that the parsing will be slower, but I do not think this is a critical issue for Pillar. It would be more important to have an extensible parser. Cheers, Doru On Wed, Mar 11, 2015 at 11:03 PM, Damien Cassou wrote: > Hi, > > The cur

Re: [Pharo-users] Pillar parser rewrite: PetitParser or not?

> Am 11.03.2015 um 23:03 schrieb Damien Cassou : > > Hi, > > The current pillar parser has several problems: > > - it is hard to understand and change > - it discards input locations > > I think a refactor or rewrite is necessary. What are the pros and cons of > using PetitParser to do that?