- Pharo-users - lists.pharo.org

Re: [Pharo-users] [launcher] fixed layout of tollbar buttons

by Benjamin

I was referencing to the LaTeX command \hfill http://en.wikibooks.org/wiki/TeX/hfill Ben On 12 Dec 2013, at 14:48, btc(a)openinworld.com wrote: > Thanks Ben. But why is it required? I think I am missing some basic info how layouts work on the Morph side, and the few references to #hFill in the image don't tell me much. > > btw, adding a method #hFill would make it look like less of a hack. > > cheers -ben > > Benjamin wrote: >> >> The empty column is used as a \hFill :) >> >> Ben >> >> On 12 Dec 2013, at 13:57, btc(a)openinworld.com wrote: >> >>> Hi Damien, Benjamin.V.R. >>> >>> I see in "PharoLauncher-Spec-DamienCassou.17" that the layout of the toolbar buttons is fixed, which is really great. However in trying to learn from that for future reference, seeing it relies on an empty column being added "seems" like a hack to workaround some issue with Spec. Should that be logged as a bug? Or is there some greater architectural background for this that I am missing? >>> >>> PhLCommandTooldbar>>dynamicLayout "(newer)" >>> "Create a spec layout with 1 row, and as many columns as there are command classes" >>> ^ SpecLayout composed newRow: >>> [ :r | >>> r newColumn: [ :col | ]. "<--------FIX" >>> self commandClasses do: >>> [ :commandClass | >>> r add: commandClass specId width: self class toolbarHeight >>> ] >>> ] >>> >>> >>> I tried digging into Spec to look at this myself, and my naive intuition felt it was something to do with initialization of LayoutFrames, but that was my first exposure to LayoutFrame and I quickly got lost. However I was reminded of Igor commenting "i only know that if you using proportional layout, then if you want submorphs to be laid down properly, you must use addMorph:fullFrame: instead of just addMorph:" [1] I tried this with a few hacks, but tit was really shooting in the dark and unsuccessful. >>> >>> [1] https://www.mail-archive.com/pharo-dev@lists.pharo.org/msg08838.html >>> >>> cheers -ben >>> <PharoLauncher-fixed-button-layout.png> >> >

Dec. 12, 2013

Re: [Pharo-users] Is OpenDBX alive?

by Esteban Lorenzano

is not incredibly used, but it is not completely dead :) anyway... one of our many many projects is to drop opendbx (by moving that layer to pharo itself)... but that's for the future (probably far future). Esteban On Thu, Dec 12, 2013 at 2:30 PM, Esteban A. Maringolo <emaringolo(a)gmail.com>wrote: > As a side question about my dependency issues... > > Is the OpenDBX project still active? Not its Smalltalk side, I mean... > the core project. > > To me it seems like it was a great attempt to have something similar > to ODBC but for all platforms. > But I'm not seeing a wide usage of it in the wild. > > Seems like everybody else is happy with their JDBC, DBI and similar > "DB layers" on the language side. > > > Regards, > > Esteban A. Maringolo > >

Dec. 12, 2013

Re: [Pharo-users] [launcher] fixed layout of tollbar buttons

by btc＠openinworld.com

Dec. 12, 2013

Re: [Pharo-users] [launcher] fixed layout of tollbar buttons

by Benjamin

The empty column is used as a \hFill :) Ben On 12 Dec 2013, at 13:57, btc(a)openinworld.com wrote: > Hi Damien, Benjamin.V.R. > > I see in "PharoLauncher-Spec-DamienCassou.17" that the layout of the toolbar buttons is fixed, which is really great. However in trying to learn from that for future reference, seeing it relies on an empty column being added "seems" like a hack to workaround some issue with Spec. Should that be logged as a bug? Or is there some greater architectural background for this that I am missing? > > PhLCommandTooldbar>>dynamicLayout "(newer)" > "Create a spec layout with 1 row, and as many columns as there are command classes" > ^ SpecLayout composed newRow: > [ :r | > r newColumn: [ :col | ]. "<--------FIX" > self commandClasses do: > [ :commandClass | > r add: commandClass specId width: self class toolbarHeight > ] > ] > > > I tried digging into Spec to look at this myself, and my naive intuition felt it was something to do with initialization of LayoutFrames, but that was my first exposure to LayoutFrame and I quickly got lost. However I was reminded of Igor commenting "i only know that if you using proportional layout, then if you want submorphs to be laid down properly, you must use addMorph:fullFrame: instead of just addMorph:" [1] I tried this with a few hacks, but tit was really shooting in the dark and unsuccessful. > > [1] https://www.mail-archive.com/pharo-dev@lists.pharo.org/msg08838.html > > cheers -ben > <PharoLauncher-fixed-button-layout.png>

Dec. 12, 2013

Is OpenDBX alive?

by Esteban A. Maringolo

As a side question about my dependency issues... Is the OpenDBX project still active? Not its Smalltalk side, I mean... the core project. To me it seems like it was a great attempt to have something similar to ODBC but for all platforms. But I'm not seeing a wide usage of it in the wild. Seems like everybody else is happy with their JDBC, DBI and similar "DB layers" on the language side. Regards, Esteban A. Maringolo

Dec. 12, 2013

Re: [Pharo-users] Glorp PostgreSQL Drivers in Ubuntu 12.04

by Sven Van Caekenberghe

On 12 Dec 2013, at 14:20, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: > 2013/12/12 Sven Van Caekenberghe <sven(a)stfx.eu>: >> Hi Esteban, >> >> Itâs a mess ;-) > > Don't get me started... ;-) > > >> PharoDatabaseAccessor DefaultDriver is NativePostgresDriver. > > Not in my installation. > > I'm using this to install my Glorp+Postgres combo: > > Gofer it > squeaksource: 'MetacelloRepository'; > package: 'ConfigurationOfGlorp'; > load. > > Gofer it > squeaksource: 'MetacelloRepository'; > package: 'ConfigurationOfPostgresV2'; > load. > > ((Smalltalk at: #ConfigurationOfGlorpDBX) > project version: '2.5') load. > > ((Smalltalk at: #ConfigurationOfPostgresV2 ) > project version: '2.1') load. > > > I'm using ConfigurationOfGlorpDBX instead of ConfigurationOfGlorp > because somebody told me so several months ago when I asked. > ConfigurationOfGlorp seems really outdated. > > If you can send me the NativePostgresDriver class I'll test if that > solves the problem. The class NativePostgresDriver is in a package called GlorpDriverPostgreSQL. It seems to have come from MCSqueaksourceRepository location: 'http://squeaksource.com/PostgresV2' user: '' password: â' I have this version in my (older) image (it seems to be the latest): Name: GlorpDriverPostgreSQL-GuillermoPolito.3 Author: GuillermoPolito Time: 12 June 2011, 1:33:54 am UUID: 770cafdc-c5e4-4f39-a52d-63e4b3aee6d8 Ancestors: GlorpDriverPostgreSQL-MarianoMartinezPeck.2 Sven > Now I see the 2.5 spec of ConfigurationOfGlorpDBX tries to load the > NativePostgresDriver... but from the 1.0... > >> Anyway, other advantages of this driver are that you can go from one machine to another, over ssh, double-check with psql, >> You can even go from your dev machine / image to your production server db (over ssh) over the internet â¦ > > I know, I rather go with self-contained solutions whenever possible. > > > Regards, >

Dec. 12, 2013

Re: [Pharo-users] [Pharo-dev] [Pharo Trick: #0009] 'Enable halt/inspect once' button

by btc＠openinworld.com

Dec. 12, 2013

Re: [Pharo-users] Glorp PostgreSQL Drivers in Ubuntu 12.04

by Esteban A. Maringolo

2013/12/12 Sven Van Caekenberghe <sven(a)stfx.eu>: > Hi Esteban, > > Itâs a mess ;-) Don't get me started... ;-) > PharoDatabaseAccessor DefaultDriver is NativePostgresDriver. Not in my installation. I'm using this to install my Glorp+Postgres combo: Gofer it squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfGlorp'; load. Gofer it squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfPostgresV2'; load. ((Smalltalk at: #ConfigurationOfGlorpDBX) project version: '2.5') load. ((Smalltalk at: #ConfigurationOfPostgresV2 ) project version: '2.1') load. I'm using ConfigurationOfGlorpDBX instead of ConfigurationOfGlorp because somebody told me so several months ago when I asked. ConfigurationOfGlorp seems really outdated. If you can send me the NativePostgresDriver class I'll test if that solves the problem. Now I see the 2.5 spec of ConfigurationOfGlorpDBX tries to load the NativePostgresDriver... but from the 1.0... > Anyway, other advantages of this driver are that you can go from one machine to another, over ssh, double-check with psql, > You can even go from your dev machine / image to your production server db (over ssh) over the internet â¦ I know, I rather go with self-contained solutions whenever possible. Regards,

Dec. 12, 2013

Re: [Pharo-users] Glorp PostgreSQL Drivers in Ubuntu 12.04

by Esteban A. Maringolo

I think what problem I have... it's a big mess. :) I thought I was using native (Smalltalk) Postgres driver, but in fact I was using the OpenDBX driver, which in turns depends on the native C Postgres library (libqp.dll in Windows). So now my dependency is not with libpq.so directy, but with OpenDBX. That's my dependency to resolve. The following page, has dead links in how to install it http://dbxtalk.smallworks.com.ar/DBXTalkDrivers/compiling-and-installing-op… Esteban A. Maringolo 2013/12/12 Esteban A. Maringolo <emaringolo(a)gmail.com>: > 2013/12/12 Sven Van Caekenberghe <sven(a)stfx.eu>: >> Maybe a stupid question, but why not use the PostgresV2 ânativeâ driver. This one is network based, it needs no (annoying) libraries, just a socket connection ? >> >> And it works perfectly with Glorp. > > I thought I was using it, in fact I load as one of my prerequisites. > > My app only depends on the GlorpSession, which is instantiated as shown before: > > | login accessor session | > login := Login new > database: (PostgreSQLPlatform new characterEncoding: (config at: > 'encoding' ifAbsent: [ 'utf8' ])); > username: (config at: 'username'); > password: (config at: 'password'); > connectString: (config at: 'hostname') , '_' , (config at: 'database'); > encodingStrategy: (DBXStaticEncoding newForEncoding:'utf8'). > > accessor := DatabaseAccessor forLogin: login. > accessor login. > > The DBXStaticEncoding doesn't seem to instantiate any connection > related classes, but if I remove the line I get the same error. > > But the DefaultDriver of PharoDatabaseAccesor is GlorpOpenDBXDriver, > which is the only direct subclass of Glorp's DatabaseDriver class. I > don't know if there is a DatabaseDriver for Glorp that uses the native > Driver (doesn't seem hard to implement either). > > Now I don't know which path to take. If to properly implement/install > (repo?) the native DatabaseDriver or configure the required external > library. > > Regards.

Dec. 12, 2013

Re: [Pharo-users] Glorp PostgreSQL Drivers in Ubuntu 12.04

by Sven Van Caekenberghe

Hi Esteban, Itâs a mess ;-) This is what I do (but the code is at least a year old, if not 2 - on the other hand, this stuff hardly changes): T3DatabaseStorageAccessor>>#session ^ session ifNil: [ session := T3StorageDatabaseResource createSession. session accessor login. session accessor logging: self logSQL. session accessor basicExecuteSQLString: 'set timezone to ''utc'''. session ] T3StorageDatabaseResource class>>#createSession ^ T3StorageSchema sessionForLogin: self login T3StorageDatabaseResource class>>#login ^ DatabaseLogin ifNil: [ DatabaseLogin := self defaultLogin ] T3StorageDatabaseResource class>>#defaultLogin ^(Login new) database: PostgreSQLPlatform new; username: 't3'; password: âXXXX'; connectString: 'localhost:5432_t3-storage'; secure: false; yourself PharoDatabaseAccessor DefaultDriver is NativePostgresDriver. Does this help ? Anyway, other advantages of this driver are that you can go from one machine to another, over ssh, double-check with psql, ... You can even go from your dev machine / image to your production server db (over ssh) over the internet â¦ Regards, Sven On 12 Dec 2013, at 13:49, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: > 2013/12/12 Sven Van Caekenberghe <sven(a)stfx.eu>: >> Maybe a stupid question, but why not use the PostgresV2 ânativeâ driver. This one is network based, it needs no (annoying) libraries, just a socket connection ? >> >> And it works perfectly with Glorp. > > I thought I was using it, in fact I load as one of my prerequisites. > > My app only depends on the GlorpSession, which is instantiated as shown before: > > | login accessor session | > login := Login new > database: (PostgreSQLPlatform new characterEncoding: (config at: > 'encoding' ifAbsent: [ 'utf8' ])); > username: (config at: 'username'); > password: (config at: 'password'); > connectString: (config at: 'hostname') , '_' , (config at: 'database'); > encodingStrategy: (DBXStaticEncoding newForEncoding:'utf8'). > > accessor := DatabaseAccessor forLogin: login. > accessor login. > > The DBXStaticEncoding doesn't seem to instantiate any connection > related classes, but if I remove the line I get the same error. > > But the DefaultDriver of PharoDatabaseAccesor is GlorpOpenDBXDriver, > which is the only direct subclass of Glorp's DatabaseDriver class. I > don't know if there is a DatabaseDriver for Glorp that uses the native > Driver (doesn't seem hard to implement either). > > Now I don't know which path to take. If to properly implement/install > (repo?) the native DatabaseDriver or configure the required external > library. > > Regards. >

Dec. 12, 2013