- Pharo-users - lists.pharo.org

When to use Versionner and when to use Monticello

by Sergio Fedi

Great, now that I saw these screencasts of Versionner (which I'm still trying to have a hang on) I would like to ask: When do we use Versionner and when do we use Monticello? Putting it in another way: What tasks are only possible through Monticello? What tasks you should be doing in Versionner?

April 30, 2015

Re: [Pharo-users] Reading rows in a database table (select * from ...)

by Sergio Fedi

I haven't worked myself with this part of the code, but I can show you how we did it. Sergio - which database driver are you using and what is the expression to > read in multiple rows > FreeTDS This is how we performed a query: *clientes* | rows lista | rows := (self executeSQL: 'SELECT * from GVA14 order by NOM_COM') rows. lista := Dictionary new. rows do: [ :row | lista at: (row valueNamed: 'COD_CLIENT') put: (Cliente fromRow: row) ]. ^ lista *executeSQL: aSQLStatement* self ensureDBConnection. self dbType = 'MYSQL' ifTrue: [ ^ (self conn prepare: aSQLStatement) execute: #() ]. self dbType = 'ODBC' ifTrue: [ ^ (self conn query: aSQLStatement) execute asTable ] ifFalse: [ ^ self conn execute: aSQLStatement ] But the driver had several quirks, so we had to do this on ensureDBConnection *ensureDBConnection* [self dbType isNil ifTrue: [ self conn isConnected ifFalse: [ self conn connect ]. self conn isOpen ifFalse: [ [ self conn open ] on: DBXError do: [ self error: 'Error de conexion con la base de datos.' ]. self conn execute: 'SET ANSI_NULLS ON'. self conn execute: 'SET ANSI_WARNINGS ON' ]. ^* (self conn execute: 'select 1') rows first rawValues first = '1']* ifFalse: [^self ensureDBConnectionFor: self dbType]] on: Error do: [self error: 'Error de conexion con la base de datos']

April 30, 2015

Re: [Pharo-users] [ANN] Screencast on Versionner

by Sergio Fedi

Excellent work Esteban! âQuestion for the list: What are groups? What do they model? What problem do they solve? (or why are they useful)

April 30, 2015

Re: [Pharo-users] RPackage extension methods using normal protocol names

by Ben Coman

On Thu, Apr 30, 2015 at 11:18 PM, Stephan Eggermont <stephan(a)stack.nl> wrote: > On 30/04/15 17:12, Ben Coman wrote: > >> Importing from VW to Pharo... >> VW package A extended by package B method #b in protocol 'accessing' >> will become >> Pharo package A extended by package B method #b in protocol '*B'. >> >> then trying to synchronise from Pharo back to VW will need to somehow >> reconstruct #b being in protocol 'accessing' >> > > Just add a conversion mapping class to the package > > > To be run manually after the package is loaded in each platform ? cheers -ben

April 30, 2015

Re: [Pharo-users] RPackage extension methods using normal protocol names

by Stephan Eggermont

On 30/04/15 17:12, Ben Coman wrote: > Importing from VW to Pharo... > VW package A extended by package B method #b in protocol 'accessing' > will become > Pharo package A extended by package B method #b in protocol '*B'. > > then trying to synchronise from Pharo back to VW will need to somehow > reconstruct #b being in protocol 'accessing' Just add a conversion mapping class to the package Stephan

April 30, 2015

Re: [Pharo-users] [ANN] Screencast on Versionner

by Stephan Eggermont

On 30/04/15 16:06, Esteban Lorenzano wrote: > mostly because I wanted to keep the screencast short an easy. > advanced configurations might need package dependencies, but other times > you do not need them. Well, it either is 1st steps in configurations, and then you can keep them out, or it is about configuration management, and then we want to see the required complexity. That can be in several videos, solving the different problems different users might run into. Stephan

April 30, 2015

Re: [Pharo-users] RPackage extension methods using normal protocol names

by Ben Coman

On Thu, Apr 30, 2015 at 10:56 PM, stepharo <stepharo(a)free.fr> wrote: > I'm not sure that it will really help. Importing from VW to Pharo... VW package A extended by package B method #b in protocol 'accessing' will become Pharo package A extended by package B method #b in protocol '*B'. then trying to synchronise from Pharo back to VW will need to somehow reconstruct #b being in protocol 'accessing' > The * is handy and we have many other things to improve first. > Yes I understand (but lowering the barrier of entry from VW may bring applications and money to the table (P.S. I know you know that)) cheers -ben > > > Le 30/4/15 16:44, Ben Coman a Ã©crit : > > I saw recently how VisualWorks extensions use normal protocol names >> >> http://ia902605.us.archive.org/25/items/St4u181ClassExtensionsInVisualworks… >> >> Now that Pharo has got real package objects with RPackage, how possible >> is the VW convention? It would facilitate porting code. >> >> cheers -ben >> > > >

April 30, 2015

Re: [Pharo-users] RPackage extension methods using normal protocol names

by Esteban Lorenzano

> On 30 Apr 2015, at 17:07, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > >> On 30 Apr 2015, at 16:44, Ben Coman <btc(a)openInWorld.com <mailto:btc@openInWorld.com>> wrote: >> >> I saw recently how VisualWorks extensions use normal protocol names >> http://ia902605.us.archive.org/25/items/St4u181ClassExtensionsInVisualworks… <http://ia902605.us.archive.org/25/items/St4u181ClassExtensionsInVisualworks…> >> >> Now that Pharo has got real package objects with RPackage, how possible is the VW convention? It would facilitate porting code. >> > > I would like toâ¦ the * is really not nice. > But we have a really long TODO already. yesâ¦ it was (and it is) in our TODO. Sadly there are things with more priority now :( Esteban > > Marcus >

April 30, 2015

Re: [Pharo-users] RPackage extension methods using normal protocol names

by Marcus Denker

> On 30 Apr 2015, at 16:44, Ben Coman <btc(a)openInWorld.com> wrote: > > I saw recently how VisualWorks extensions use normal protocol names > http://ia902605.us.archive.org/25/items/St4u181ClassExtensionsInVisualworks… <http://ia902605.us.archive.org/25/items/St4u181ClassExtensionsInVisualworks…> > > Now that Pharo has got real package objects with RPackage, how possible is the VW convention? It would facilitate porting code. > I would like toâ¦ the * is really not nice. But we have a really long TODO already. Marcus

April 30, 2015

Re: [Pharo-users] MagicMagritte in Pharo 40.

by stepharo

Great I should still look at magic magritte :) holidays are good Stef Le 29/4/15 17:43, Sean P. DeNigris a Ã©crit : > Sean P. DeNigris wrote >> It looks like a bug in ConfigurationOfSeaside3... I reported to their >> list... > Johan Brichau informed me that Seaside configs now live at > http://smalltalkhub.com/mc/Seaside/MetacelloConfigurations > > The config now loads without warning in Pharo 3.0 and 4.0 :) > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/MagicMagritte-in-Pharo-40-tp4821956p4822970.html > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > >

April 30, 2015