Hi, cleaned up MongoTalk a little bit: - added a new baseline 1.7 with separate test packages for "BSON" and "Core", so tests are now separately loadable - more comments and more/better categorizations - printOn: in database and collections to print the name - MongoQueries is now "Mongo-Queries" and "Mongo-Tests-Queries" (hence the name of the first to be in alignment with other packages) - make Config aware/loadable for upcoming Pharo 4 - the Config now is working and saved with Versionner - the Config also includes groups (Core, Tests and default) - it is now available in MetaRepoForPharo40 so it is in the config browser of Pharo4 - all 55 tests are green in latest Pharo 4.0 #40534 Just cleanups, no behavior changes Bye T.
Is it in 3.0 repo too? Le 4 mars 2015 11:25, "Torsten Bergmann" <astares@gmx.de> a écrit :
Hi,
cleaned up MongoTalk a little bit:
- added a new baseline 1.7 with separate test packages for "BSON" and "Core", so tests are now separately loadable - more comments and more/better categorizations - printOn: in database and collections to print the name - MongoQueries is now "Mongo-Queries" and "Mongo-Tests-Queries" (hence the name of the first to be in alignment with other packages) - make Config aware/loadable for upcoming Pharo 4 - the Config now is working and saved with Versionner - the Config also includes groups (Core, Tests and default) - it is now available in MetaRepoForPharo40 so it is in the config browser of Pharo4 - all 55 tests are green in latest Pharo 4.0 #40534
Just cleanups, no behavior changes
Bye T.
Thanks Torsten, are the *-Tests-* package for compatibility reasons for pharo 2? Otherwise they should be called *-Tests, right? Norbert
Am 04.03.2015 um 11:25 schrieb Torsten Bergmann <astares@gmx.de>:
Hi,
cleaned up MongoTalk a little bit:
- added a new baseline 1.7 with separate test packages for "BSON" and "Core", so tests are now separately loadable - more comments and more/better categorizations - printOn: in database and collections to print the name - MongoQueries is now "Mongo-Queries" and "Mongo-Tests-Queries" (hence the name of the first to be in alignment with other packages) - make Config aware/loadable for upcoming Pharo 4 - the Config now is working and saved with Versionner - the Config also includes groups (Core, Tests and default) - it is now available in MetaRepoForPharo40 so it is in the config browser of Pharo4 - all 55 tests are green in latest Pharo 4.0 #40534
Just cleanups, no behavior changes
Bye T. <mongotalk.png>
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 ;) You can try out and adopt to your needs, I use Pharo 4 already. 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.
Am 04.03.2015 um 13:04 schrieb Torsten Bergmann <astares@gmx.de>:
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 ;)
You can try out and adopt to your needs, I use Pharo 4 already.
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.
That is because monticello deals packages based on substring match. Should IMHO be changed in the not so far future. Norbert
On 04 Mar 2015, at 14:05, Norbert Hartl <norbert@hartl.name> wrote:
Am 04.03.2015 um 13:04 schrieb Torsten Bergmann <astares@gmx.de>:
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 ;)
You can try out and adopt to your needs, I use Pharo 4 already.
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.
That is because monticello deals packages based on substring match. Should IMHO be changed in the not so far future.
that already changed now you can have PackageA PackageA-X PackageA-X-Y PackageA-X-Y-Z all as different packages (and PackageA will not include any of the others) is like that since Pharo3 Esteban
Norbert
Am 04.03.2015 um 14:26 schrieb Esteban Lorenzano <estebanlm@gmail.com>:
On 04 Mar 2015, at 14:05, Norbert Hartl <norbert@hartl.name> wrote:
Am 04.03.2015 um 13:04 schrieb Torsten Bergmann <astares@gmx.de>:
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 ;)
You can try out and adopt to your needs, I use Pharo 4 already.
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.
That is because monticello deals packages based on substring match. Should IMHO be changed in the not so far future.
that already changed now you can have
PackageA PackageA-X PackageA-X-Y PackageA-X-Y-Z
all as different packages (and PackageA will not include any of the others)
is like that since Pharo3
I know. That's the reason I was asking. I think that having a suffix of -Tests is better but we still have to live with the potential prefix string matching behaviour from earlier versions or other smalltalks. Norbert
On Wed, Mar 4, 2015 at 1:04 PM, Torsten Bergmann <astares@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.
1.7.0 loads fine in 3.0 and my code works nicely. Phil On Wed, Mar 4, 2015 at 1:04 PM, Torsten Bergmann <astares@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 ;)
You can try out and adopt to your needs, I use Pharo 4 already.
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.
Thanks torsten This little steps are really important! Stef Le 4/3/15 11:25, Torsten Bergmann a écrit :
Hi,
cleaned up MongoTalk a little bit:
- added a new baseline 1.7 with separate test packages for "BSON" and "Core", so tests are now separately loadable - more comments and more/better categorizations - printOn: in database and collections to print the name - MongoQueries is now "Mongo-Queries" and "Mongo-Tests-Queries" (hence the name of the first to be in alignment with other packages) - make Config aware/loadable for upcoming Pharo 4 - the Config now is working and saved with Versionner - the Config also includes groups (Core, Tests and default) - it is now available in MetaRepoForPharo40 so it is in the config browser of Pharo4 - all 55 tests are green in latest Pharo 4.0 #40534
Just cleanups, no behavior changes
Bye T.
I have been writing more extensive class comments for MongoTalk and Mapless+MongoMapless. Will release next week. Need to remix the Voyage pool with tye Mapless pool and it will quite neat. Note: we need a full features pool once and for all, like JEE DataSources. What we have is okay but still half baked vs the DataSource. MaplessMongo and Roassal2 are very nice to work with! Phil Le 14 mars 2015 14:23, "stepharo" <stepharo@free.fr> a écrit :
Thanks torsten This little steps are really important!
Stef
Le 4/3/15 11:25, Torsten Bergmann a écrit :
Hi,
cleaned up MongoTalk a little bit:
- added a new baseline 1.7 with separate test packages for "BSON" and "Core", so tests are now separately loadable - more comments and more/better categorizations - printOn: in database and collections to print the name - MongoQueries is now "Mongo-Queries" and "Mongo-Tests-Queries" (hence the name of the first to be in alignment with other packages) - make Config aware/loadable for upcoming Pharo 4 - the Config now is working and saved with Versionner - the Config also includes groups (Core, Tests and default) - it is now available in MetaRepoForPharo40 so it is in the config browser of Pharo4 - all 55 tests are green in latest Pharo 4.0 #40534
Just cleanups, no behavior changes
Bye T.
Sent from my iPhone
On 14 mars 2015, at 14:41, "phil@highoctane.be" <phil@highoctane.be> wrote:
I have been writing more extensive class comments for MongoTalk and Mapless+MongoMapless.
Will release next week.
Need to remix the Voyage pool with tye Mapless pool and it will quite neat.
Note: we need a full features pool once and for all, like JEE DataSources. What we have is okay but still half baked vs the DataSource.
MaplessMongo and Roassal2 are very nice to work with!
We will definitively need that for the datathon in Paris. Any documentation how to setup Mongo and Roassal ? Thank you Phil !
Phil
Le 14 mars 2015 14:23, "stepharo" <stepharo@free.fr> a écrit :
Thanks torsten This little steps are really important!
Stef
Le 4/3/15 11:25, Torsten Bergmann a écrit :
Hi,
cleaned up MongoTalk a little bit:
- added a new baseline 1.7 with separate test packages for "BSON" and "Core", so tests are now separately loadable - more comments and more/better categorizations - printOn: in database and collections to print the name - MongoQueries is now "Mongo-Queries" and "Mongo-Tests-Queries" (hence the name of the first to be in alignment with other packages) - make Config aware/loadable for upcoming Pharo 4 - the Config now is working and saved with Versionner - the Config also includes groups (Core, Tests and default) - it is now available in MetaRepoForPharo40 so it is in the config browser of Pharo4 - all 55 tests are green in latest Pharo 4.0 #40534
Just cleanups, no behavior changes
Bye T.
I can make a video for that. Stay tuned! Phil Le 14 mars 2015 17:45, "Serge Stinckwich" <serge.stinckwich@gmail.com> a écrit :
Sent from my iPhone
On 14 mars 2015, at 14:41, "phil@highoctane.be" <phil@highoctane.be> wrote:
I have been writing more extensive class comments for MongoTalk and Mapless+MongoMapless.
Will release next week.
Need to remix the Voyage pool with tye Mapless pool and it will quite neat.
Note: we need a full features pool once and for all, like JEE DataSources. What we have is okay but still half baked vs the DataSource.
MaplessMongo and Roassal2 are very nice to work with!
We will definitively need that for the datathon in Paris. Any documentation how to setup Mongo and Roassal ? Thank you Phil !
Phil Le 14 mars 2015 14:23, "stepharo" <stepharo@free.fr> a écrit :
Thanks torsten This little steps are really important!
Stef
Le 4/3/15 11:25, Torsten Bergmann a écrit :
Hi,
cleaned up MongoTalk a little bit:
- added a new baseline 1.7 with separate test packages for "BSON" and "Core", so tests are now separately loadable - more comments and more/better categorizations - printOn: in database and collections to print the name - MongoQueries is now "Mongo-Queries" and "Mongo-Tests-Queries" (hence the name of the first to be in alignment with other packages) - make Config aware/loadable for upcoming Pharo 4 - the Config now is working and saved with Versionner - the Config also includes groups (Core, Tests and default) - it is now available in MetaRepoForPharo40 so it is in the config browser of Pharo4 - all 55 tests are green in latest Pharo 4.0 #40534
Just cleanups, no behavior changes
Bye T.
I do not know if it is related and may help but olivier auverlot did FasterThanLight a pool sharing library. MCHttpRepository location: 'http://www.smalltalkhub.com/mc/RMoD/FasterThanLight/main' user: '' password: '' Stef Le 14/3/15 14:41, phil@highoctane.be a écrit :
I have been writing more extensive class comments for MongoTalk and Mapless+MongoMapless.
Will release next week.
Need to remix the Voyage pool with tye Mapless pool and it will quite neat.
Note: we need a full features pool once and for all, like JEE DataSources. What we have is okay but still half baked vs the DataSource.
MaplessMongo and Roassal2 are very nice to work with!
Phil
Le 14 mars 2015 14:23, "stepharo" <stepharo@free.fr <mailto:stepharo@free.fr>> a écrit :
Thanks torsten This little steps are really important!
Stef
Le 4/3/15 11:25, Torsten Bergmann a écrit :
Hi,
cleaned up MongoTalk a little bit:
- added a new baseline 1.7 with separate test packages for "BSON" and "Core", so tests are now separately loadable - more comments and more/better categorizations - printOn: in database and collections to print the name - MongoQueries is now "Mongo-Queries" and "Mongo-Tests-Queries" (hence the name of the first to be in alignment with other packages) - make Config aware/loadable for upcoming Pharo 4 - the Config now is working and saved with Versionner - the Config also includes groups (Core, Tests and default) - it is now available in MetaRepoForPharo40 so it is in the config browser of Pharo4 - all 55 tests are green in latest Pharo 4.0 #40534
Just cleanups, no behavior changes
Bye T.
Excellent news. I'll look at that tomorrow afternoon. Phil On Sun, Mar 15, 2015 at 9:57 PM, stepharo <stepharo@free.fr> wrote:
I do not know if it is related and may help but olivier auverlot did FasterThanLight a pool sharing library.
MCHttpRepository location: 'http://www.smalltalkhub.com/mc/RMoD/FasterThanLight/main' user: '' password: ''
Stef
Le 14/3/15 14:41, phil@highoctane.be a écrit :
I have been writing more extensive class comments for MongoTalk and Mapless+MongoMapless.
Will release next week.
Need to remix the Voyage pool with tye Mapless pool and it will quite neat.
Note: we need a full features pool once and for all, like JEE DataSources. What we have is okay but still half baked vs the DataSource.
MaplessMongo and Roassal2 are very nice to work with!
Phil
Le 14 mars 2015 14:23, "stepharo" <stepharo@free.fr> a écrit :
Thanks torsten This little steps are really important!
Stef
Le 4/3/15 11:25, Torsten Bergmann a écrit :
Hi,
cleaned up MongoTalk a little bit:
- added a new baseline 1.7 with separate test packages for "BSON" and "Core", so tests are now separately loadable - more comments and more/better categorizations - printOn: in database and collections to print the name - MongoQueries is now "Mongo-Queries" and "Mongo-Tests-Queries" (hence the name of the first to be in alignment with other packages) - make Config aware/loadable for upcoming Pharo 4 - the Config now is working and saved with Versionner - the Config also includes groups (Core, Tests and default) - it is now available in MetaRepoForPharo40 so it is in the config browser of Pharo4 - all 55 tests are green in latest Pharo 4.0 #40534
Just cleanups, no behavior changes
Bye T.
participants (7)
-
Esteban Lorenzano -
Norbert Hartl -
phil＠highoctane.be -
Serge Stinckwich -
Stephan Eggermont -
stepharo -
Torsten Bergmann