- Pharo-users - lists.pharo.org

DNS change files.pharo.org

by Marcus Denker

Hello, We will switch the DNS entry from an A type to a CNAME that points to a different server (for caching) this afternoon at 1pm local time. It should all continue to work (and hopefully faster) Marcus

March 5, 2015

Re: [Pharo-users] Fixed tool bar in pharo, similar to the one in Squeak

by Nicolai Hess

2015-03-05 3:49 GMT+01:00 Offray Vladimir Luna CÃ¡rdenas <offray(a)riseup.net>: > Hi, > > I would like to add a fixed tool bar in the upper side of the word in > Pharo, similar to the one that is in Squeak. I think that having this kind > of fixed places with tools help newbies to find help and launch stuff. > There is any place where I can install or look for a functionality like > this one? > > Thanks, > > Offray > > There is DockingBarMorph, for example: |d| "World deleteDockingBars." d:= DockingBarMorph new. World worldMenu items copy select:[:i| i hasSubMenu] thenDo:[:i| d add: i contents icon: i icon help: i contents subMenu: i subMenu]. d adhereToTop; openInWorld. Although this does not work at the moment due to issue 14829 <https://pharo.fogbugz.com/default.asp?14829> Spec MenuModel submenu not working

March 5, 2015

Fixed tool bar in pharo, similar to the one in Squeak

by Offray Vladimir Luna CÃ¡rdenas

Hi, I would like to add a fixed tool bar in the upper side of the word in Pharo, similar to the one that is in Squeak. I think that having this kind of fixed places with tools help newbies to find help and launch stuff. There is any place where I can install or look for a functionality like this one? Thanks, Offray

March 5, 2015

Re: [Pharo-users] Roassal scroll bar builder

by Offray Vladimir Luna CÃ¡rdenas

Hi, Seems pretty interesting. I have an odd behaviour though. Besides the lateral view in the playground, a new window called "Inspector on a RTView" is created. When I move the scroller on that new window, the view in the right part of the playgrond starts to move. Please test what happens when you move the scroller in the new window to see it for yourself. Hope it helps, Offray El 04/03/15 a las 09:21, Pierre CHANSON escribiÃ³: > 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 5, 2015

Re: [Pharo-users] Some MongoTalk cleanups

by Stephan Eggermont

On 04/03/15 11:25, Torsten Bergmann wrote: > cleaned up MongoTalk a little bit: Nice, thank you. You might want to change baseline17, baseline18 and version170 to point at #'release1.1' of Grease instead of stable c.q. 1.1.9. Stephan

March 4, 2015

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