March 2015 - Pharo-users - lists.pharo.org

Reading an SQL db on OS X

by Alexandre Bergel

Hi! I would like to read a SQL .db file. The page http://smalltalkhub.com/#!/~PharoExtras/NBSQLite3 mention how to do this on Windows and Linux, but not on OSX. What should I do to read a SQL file on OS X? I tried google, but it did not work. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

March 4, 2015

Re: [Pharo-users] Some MongoTalk cleanups

by phil＠highoctane.be

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(a)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. > >

March 4, 2015

Roassal scroll bar builder

by Pierre CHANSON

Hi all, RTScrollBarBuilder allows you to add a scalable scroll bar or scroll pad to your Roassal view. see examples in RTScrollBarBuilderExamples, or try to execute this in a workspace: -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= b := RTMondrian new. b shape rectangle withBorder; width: [ :cls | cls numberOfVariables * 5]; height: #numberOfMethods; linearFillColor: #numberOfLinesOfCode within: RTObject withAllSubclasses. b nodes: RTObject withAllSubclasses. b edges connectFrom: #superclass. b layout tree. b build. b2 := RTScrollBarBuilder new. b2 view: b view. b2 objects: b view elements. b2 build inspect -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Feedbacks are welcome ! cheers, Pierre â

March 4, 2015

Re: [Pharo-users] Some MongoTalk cleanups

by Norbert Hartl

> Am 04.03.2015 um 14:26 schrieb Esteban Lorenzano <estebanlm(a)gmail.com>: > >> >> On 04 Mar 2015, at 14:05, Norbert Hartl <norbert(a)hartl.name> wrote: >> >> >>> Am 04.03.2015 um 13:04 schrieb Torsten Bergmann <astares(a)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

March 4, 2015

Re: [Pharo-users] Some MongoTalk cleanups

by Esteban Lorenzano

> On 04 Mar 2015, at 14:05, Norbert Hartl <norbert(a)hartl.name> wrote: > > >> Am 04.03.2015 um 13:04 schrieb Torsten Bergmann <astares(a)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

March 4, 2015

Re: [Pharo-users] Linux and Windows 3.0 differences

by phil＠highoctane.be

On Wed, Mar 4, 2015 at 1:17 PM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > Sebastian Heidbrink-2 wrote >> I just returned from a one on one Smalltalk introduction I gave tonight. > > Cool!! > > > Sebastian Heidbrink-2 wrote >> Date fromString: method >> contains a method comment on Windows and on Ubuntu it doesn't even >> include an implementation. > > Could you give more details about this? #fromString: contains no VM > primitives and so should be bit identical on all platforms. > > > Sebastian Heidbrink-2 wrote >> copy&paste from Chrome to Pharo 4.0 workspace/Playground on Ubuntu did >> not work either. Beware, sometimes it is a Chrome problem, not a Pharo one. > > IIRC this is a well-known problem with no solution yet :/ > > > Sebastian Heidbrink-2 wrote >> Tonight we setup pharo-launcher and two images.... 5 minutes later: >> "Wow,... that was fast! And we can start now?" >> :-D > > Yes, a /lot/ of work has gone into cleaning, simplifying, redesigning. > Thanks for the encouragement :) > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/Linux-and-Windows-3-0-differences-tp4809369p4809414.h… > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > > -- --- Philippe Back Visible Performance Improvements Mob: +32(0) 478 650 140 | Fax: +32 (0) 70 408 027 Mail:phil@highoctane.be | Web: http://philippeback.eu Blog: http://philippeback.be | Twitter: @philippeback Youtube: http://www.youtube.com/user/philippeback/videos High Octane SPRL rue cour Boisacq 101 | 1301 Bierges | Belgium Pharo Consortium Member - http://consortium.pharo.org/ Featured on the Software Process and Measurement Cast - http://spamcast.libsyn.com Sparx Systems Enterprise Architect and Ability Engineering EADocX Value Added Reseller

March 4, 2015

Re: [Pharo-users] Some MongoTalk cleanups

by phil＠highoctane.be

On Wed, Mar 4, 2015 at 1:04 PM, Torsten Bergmann <astares(a)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. > >

March 4, 2015

Re: [Pharo-users] Some MongoTalk cleanups

by Norbert Hartl

> Am 04.03.2015 um 13:04 schrieb Torsten Bergmann <astares(a)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

March 4, 2015

Re: [Pharo-users] Linux and Windows 3.0 differences

by Sean P. DeNigris

Sebastian Heidbrink-2 wrote > I just returned from a one on one Smalltalk introduction I gave tonight. Cool!! Sebastian Heidbrink-2 wrote > Date fromString: method > contains a method comment on Windows and on Ubuntu it doesn't even > include an implementation. Could you give more details about this? #fromString: contains no VM primitives and so should be bit identical on all platforms. Sebastian Heidbrink-2 wrote > copy&paste from Chrome to Pharo 4.0 workspace/Playground on Ubuntu did > not work either. IIRC this is a well-known problem with no solution yet :/ Sebastian Heidbrink-2 wrote > Tonight we setup pharo-launcher and two images.... 5 minutes later: > "Wow,... that was fast! And we can start now?" > :-D Yes, a /lot/ of work has gone into cleaning, simplifying, redesigning. Thanks for the encouragement :) ----- Cheers, Sean -- View this message in context: http://forum.world.st/Linux-and-Windows-3-0-differences-tp4809369p4809414.h… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

March 4, 2015

Re: [Pharo-users] Some MongoTalk cleanups

by Torsten Bergmann

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.

March 4, 2015