June 2015 - Pharo-dev - lists.pharo.org

[ann] moose 5.1

by Tudor Girba

We are happy to announce version 5.1 of the Moose Suite: *http://moosetechnology.org/#install* [image: Inline image 1] Description --- This is a minor release. The key highlights are: - It is based on Pharo 4.0. - Roassal2 comes with several new builder, most notably the new Mondrian builder (RTMondrian) and the chart drawing engine (RTGrapher). - GTSpotter has preview abilities and was extended for multiple search use cases including the navigation through Moose models. - GTPlayground was extended with sharing possibilities and transparent backup. - GTExample now offers support for documenting classes with example instances. - Moose Finder and GTInspector come with more custom presentations. - PetitParser has seen performance corrections and has been extended with the ability to parse whitespace languages. Installation --- The Moose Suite 5.1 comes for each platform as a separate bundle: - Moose Suite 5.1 for Mac http://moosetechnology.org/res/download/moose_suite_5_1-mac.zip - Moose Suite 5.1 for Windows http://moosetechnology.org/res/download/moose_suite_5_1-win.zip - Moose Suite 5.1 for Linux http://moosetechnology.org/res/download/moose_suite_5_1-linux.zip The Moose Suite 5.1 can also be loaded in a Pharo 4.0 image either from the Configuration Browser, or by executing the following script: Gofer new smalltalkhubUser: 'Moose' project: 'Moose'; configuration; loadStable Enjoy, The Moose team

June 4, 2015

Re: [Pharo-dev] [Moose-dev] Re: Fwd: Magritte = Auto-GT Presentation

by Tudor Girba

Hi, Indeed. We already had a similar discussion in the context of XMLParser. The current idea is to package GT extensions directly in the project, and not in GT. In the case of Magritte this is a bit more elaborate because it implies packaging the MagrittePresentation there as well, but that should be doable, and I would prefer this route. Cheers, Doru On Sun, May 31, 2015 at 7:43 PM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > Sean P. DeNigris wrote > > BTW: To get this in Pharo 5.0, load the Glamour-Magritte-Presentations > > package from the Moose repo > > To be more specific (since I had to look it up again to figure out what the > above meant!): > Gofer it > smalltalkhubUser: 'Moose' project: 'Glamour'; > package: 'Glamour-Magritte-Presentations'; > load. > > I wonder what the best way to load this would be... maybe add it to the > default group in a Pharo40-specific block in the Magritte3 config? > > > > ----- > Cheers, > Sean > -- > View this message in context: > http://forum.world.st/Re-Moose-dev-Re-Fwd-Magritte-Auto-GT-Presentation-tp4… > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > > -- www.tudorgirba.com "Every thing has its own flow"

June 4, 2015

Re: [Pharo-dev] TWM in Pharo 4.0

by phil＠highoctane.be

Not using 4.0 yet. Phil On Wed, Jun 3, 2015 at 10:53 PM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > I tried to load it from the Configuration Browser, and was notified that > there was no stable version for the platform. I declared the stable version > for Pharo 3.0 as that for Pharo 4.0 and it seems to work (i.e. the toolbar > shows up). How have people been loading TWM in 4.0? Or is no one using this > great tool?! > > > > ----- > Cheers, > Sean > -- > View this message in context: > http://forum.world.st/TWM-in-Pharo-4-0-tp4830313.html > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > >

June 3, 2015

Re: [Pharo-dev] Mongo and aggregation framework

by phil＠highoctane.be

On Wed, Jun 3, 2015 at 10:50 PM, Christophe Demarey < Christophe.Demarey(a)inria.fr> wrote: > > Le 3 juin 2015 Ã 19:32, phil(a)highoctane.be a Ã©crit : > > > Le 3 juin 2015 17:45, "Christophe Demarey" <christophe.demarey(a)inria.fr> > a Ã©crit : > > > > Hello, > > > > I would like to use set operators defined in mongo but it looks like > there is no support for the aggregation framework in the mongo driver. > > Does anyone has information about this? > > Search the list as I posted an example before. > > ok, I finally found your example : > > mongo := Mongo default open. > db := mongo databaseNamed: 'somedb'. > > aCommandDict := { 'distinct' -> 'somecollection'. 'key' -> 'XYZ'. 'query' > -> nil } asDictionary. > > reply := db command: aCommandDict. > > (CollectionValidation on: reply) isOK. > > distinct := reply at: #values. > > There is no OO support in the driver for that. > > So aggregate can be run as a command with the Mongo driver. > I checked the following code: > Mongo>>command: aDictionary database: aDatabase > | query | > query := MongoQuery new > database: aDatabase; > collection: (MongoMetaCollection name: '$cmd'); > where: aDictionary; > yourself. > ^self queryOne: query. > > I do not understand why a MongoQuery is used there and why it is supposed > to return only one element (queryOne)? > Because $cmd is a special collection that one uses for issuing such requests. You always have to pass a collection to mongo. QueryOne is issuing the query. HTH Phil > > Thanks, > Christophe >

June 3, 2015

Re: [Pharo-dev] Versionner Wipes per-package #repository: setting

by Christophe Demarey

Hi Sean, Le 3 juin 2015 Ã 22:29, Sean P. DeNigris a Ã©crit : > If you have a config with e.g.: > spec package: 'MyPackage' with: [ spec repository: aString ]; > And then save it with Versionner, it gets truncated to: > spec package: 'MyPackage'; > > Should I file a bug? Ideally, Versionner would support Metacello's full API, Versionner is not thought to support Metacello full API but rather a subset and provide guidelines. > but in the mean time, at least leaving unknown options alone would be a big > improvement. Fully agree with that. Even if not supported in the UI, Versionner should not discard data. > As it stands now, once one has something like the above in a > config, one can't use Versionner anymore. In the meantime, I find very strange to have packages of a project in different repositories. When I saw this kind of things, it was in configurations using packages from another project without declaring this external project in the config. Maybe in some cases, it is needed but it is not something that we want to encourage. Could you tell me more about your use case? Cheers, Christophe

June 3, 2015

Re: [Pharo-dev] TWM in Pharo 4.0

by Sean P. DeNigris

Sean P. DeNigris wrote > there was no stable version for the platform Oops! I apparently had switched to MetaRepoForPharo30. Sorry for the noise... ----- Cheers, Sean -- View this message in context: http://forum.world.st/TWM-in-Pharo-4-0-tp4830313p4830314.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

June 3, 2015

TWM in Pharo 4.0

by Sean P. DeNigris

I tried to load it from the Configuration Browser, and was notified that there was no stable version for the platform. I declared the stable version for Pharo 3.0 as that for Pharo 4.0 and it seems to work (i.e. the toolbar shows up). How have people been loading TWM in 4.0? Or is no one using this great tool?! ----- Cheers, Sean -- View this message in context: http://forum.world.st/TWM-in-Pharo-4-0-tp4830313.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

June 3, 2015

Re: [Pharo-dev] Versionner Wipes per-package #repository: setting

by Sean P. DeNigris

demarey wrote > I find very strange to have packages of a project in different > repositories. When I saw this kind of things, it was in configurations > using packages from another project without declaring this external > project in the config... Could you tell me more about your use case? Hee hee, you caught me ;) I agree that we shouldn't encourage such irresponsible behavior, and request only that we limit the punishment to having to hand-write, instead of decapitation! ----- Cheers, Sean -- View this message in context: http://forum.world.st/Versionner-Wipes-per-package-repository-setting-tp483… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

June 3, 2015

Re: [Pharo-dev] Mongo and aggregation framework

by Christophe Demarey

Le 3 juin 2015 Ã 19:32, phil(a)highoctane.be a Ã©crit : > > Le 3 juin 2015 17:45, "Christophe Demarey" <christophe.demarey(a)inria.fr> a Ã©crit : > > > > Hello, > > > > I would like to use set operators defined in mongo but it looks like there is no support for the aggregation framework in the mongo driver. > > Does anyone has information about this? > > Search the list as I posted an example before. > ok, I finally found your example : mongo := Mongo default open. db := mongo databaseNamed: 'somedb'. aCommandDict := { 'distinct' -> 'somecollection'. 'key' -> 'XYZ'. 'query' -> nil } asDictionary. reply := db command: aCommandDict. (CollectionValidation on: reply) isOK. distinct := reply at: #values. > There is no OO support in the driver for that. > So aggregate can be run as a command with the Mongo driver. I checked the following code: Mongo>>command: aDictionary database: aDatabase | query | query := MongoQuery new database: aDatabase; collection: (MongoMetaCollection name: '$cmd'); where: aDictionary; yourself. ^self queryOne: query. I do not understand why a MongoQuery is used there and why it is supposed to return only one element (queryOne)? Thanks, Christophe

June 3, 2015

Versionner Wipes per-package #repository: setting

by Sean P. DeNigris

If you have a config with e.g.: spec package: 'MyPackage' with: [ spec repository: aString ]; And then save it with Versionner, it gets truncated to: spec package: 'MyPackage'; Should I file a bug? Ideally, Versionner would support Metacello's full API, but in the mean time, at least leaving unknown options alone would be a big improvement. As it stands now, once one has something like the above in a config, one can't use Versionner anymore. ----- Cheers, Sean -- View this message in context: http://forum.world.st/Versionner-Wipes-per-package-repository-setting-tp483… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

June 3, 2015