On Wed, Mar 4, 2015 at 1:04 PM, Torsten Bergmann <asta...@gmx.de> wrote: > Phil wrote: >>Is it in 3.0 repo too? > > No, even when you copy it the #stable for 3.0 points to the old one > because I do not work with such an outdated Pharo version ;)
Well, should work anyway, I'll dump a copy in my own repo and work from there. The best part of what you mentioned are the docs. While we are at it, one thing that I see of value is to have a pool that would be implemented in MongoTalk and not in all projects. e.g. VoyageMongo has a pool and MaplessMongo has another implementation (obviously incompatible). I'd love to see the VOMongoPool go into the MongoTalk and become a MongoPool. This is needed anyway. Thanks for taking the time to write comments, we should at one point write a chapter about MongoTalk as it is not that clear on how one does special things (mailing lists work for me but it takes longer than read a chapter). As I am going to spend a month on Mongo related stuff, I hope to be able to write a couple of things about that. > > You can try out and adopt to your needs, I use Pharo 4 already. In production? With a ton of configurations loaded? Wow. Just not working for me I am afraid. Pharo3.0 is the released version. Pharo4.0 is a moving target. Phil > > Norbert wrote: >> are the *-Tests-* package for compatibility reasons for pharo 2? Otherwise >> they should be called *-Tests, right? > > No, I just follow the regular naming convention of Seaside packages here that > once was also agreed to > use for Pharo as well: https://code.google.com/p/seaside/wiki/PackageNaming > > It is used by Pharo (not on all places yet) and most projects (Glamour, GT, > Seaside, Bootstrap, Artefact, ... YouNameIt) and > MongoTalk should follow as well. > > Bye > T. > >
