- Pharo-users - lists.pharo.org

Re: [Pharo-users] (no subject)

by Stephane Ducasse

Christophe did a pass because he faced the same problem and he improved the situation. Now he left on vacation (and was stopped because of a huge jenkins crash because he left) and I do not know the status. (because we are also annoyed and sorry than you by the situation). Stef On Sun, Aug 13, 2017 at 10:31 AM, Vityou . <zlee314(a)gmail.com> wrote: > I recently discovered the pharo launcher. However, it only gives me options > to use outdated images, and I'm not sure about the vm. Is there any way to > change this?

Aug. 13, 2017

Re: [Pharo-users] Probably a bug in Garage SQLite

by Stephane Ducasse

Hi Herby On which version of Pharo are you trying? Because lot of changes happened on Pharo 60 FFI. Stef On Sun, Aug 13, 2017 at 6:11 PM, Herby VojÄÃk <herby(a)mailbox.sk> wrote: > Hello! > > This testing code: > > | databaseFile login accessor sqlString | > databaseFile := Smalltalk imageDirectory asFileReference / > 'play.sqlite'. > login := Login new > database: SQLite3Platform new; > host: ''; > port: ''; > username: ''; > password: ''; > databaseName: databaseFile fullPath asZnUrl > asString; > yourself. > accessor := DatabaseAccessor forLogin: login. > accessor login. > sqlString := 'SELECT * FROM AGENT'. > (accessor basicExecuteSQLString: sqlString) contents inspect. > > fails (Pharo 6.1, GarageGlorp #stable loaded a week ago as a project > dependency) with: > > Error: Unable to resolve external type: sqlite3 > > FFICallout(Object)>>error: > FFICallout>>resolveType: > FFICallout>>typeName:pointerArity: > FFICallout>>argName:indirectIndex:type:ptrArity: > FFIFunctionParser>>parseArgument > FFIFunctionParser>>parseArguments > FFIFunctionParser>>parseNamedFunction: > FFICalloutMethodBuilder>>parseSignature: > FFICalloutMethodBuilder>>generate > FFICalloutMethodBuilder>>build: > FFICalloutAPI>>function:module: > GASqlite3FFI(Object)>>ffiCall:module: > GASqlite3FFI>>apiErrorMessage: > GASqlite3FFI>>signal:with:on: > GASqlite3FFI>>checkForOk:on: > GASqlite3FFI>>prepare:on:with: > GASqlite3Statement>>prepare > GASqlite3Driver>>prepare: > GASqlite3ResultSet>>prepareStatement: > GASqlite3ResultSet>>execute:withCollection: > GASqlite3ResultSet>>execute:with:on: > GASqlite3Driver>>execute:with: > GASqlite3Driver>>execute: > GAGlorpDriver>>basicExecuteSQLString: > PharoDatabaseAccessor>>basicExecuteSQLString: > UndefinedObject>>DoIt > OpalCompiler>>evaluate > [..snip..] > > Problem seems to be that in FFICallout >> resolveType:, the line > > binding := resolver ffiBindingOf: name asSymbol. > > actually produces nil, resolver being GASqlite3FFI class. If looking at the > class side of GaSqlite3FFI, there is no ffiBindingOf: at all; there is > > nbBindingOf: aTypeName > ^ TypeMap at: aTypeName ifAbsent: [ super nbBindingOf: aTypeName ] > > though. If I copy near-mindlessly and add: > > ffiBindingOf: aTypeName > ^ TypeMap at: aTypeName ifAbsent: [ super ffiBindingOf: aTypeName ] > > then the code above fails correctly with: 'no such table: AGENT'. > > Am I missing some nb<->ffi bridge? Or is there a bug in Garage SQLite > driver? > > Herby >

Aug. 13, 2017

Re: [Pharo-users] pharo config problem

by Stephane Ducasse

Hi johannes I do not know how to help you but this is strange. We managed our synectique private code on STHub and it works. Now STHub is getting stranger and stranger. So may be your passwrd got desync. Esteban? if you read this mail. Can you check when you are back from vacation? Stef On Sun, Aug 13, 2017 at 7:20 PM, jb <brauer(a)nordakademie.de> wrote: > Hi, > > I have a problem with connection to a private smalltalkhub rep from the > command line with pharo config. > I think I set the --username and --password options correctly, but I always > get: > ZnHttpUnsuccessful: 403 Forbidded > > If I make the rep public then there is no access problem. > > Any hints what is going wrong? > > Johannes > > > > -- > View this message in context: http://forum.world.st/pharo-config-problem-tp4960715.html > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >

Aug. 13, 2017

pharo config problem

by jb

Hi, I have a problem with connection to a private smalltalkhub rep from the command line with pharo config. I think I set the --username and --password options correctly, but I always get: ZnHttpUnsuccessful: 403 Forbidded If I make the rep public then there is no access problem. Any hints what is going wrong? Johannes -- View this message in context: http://forum.world.st/pharo-config-problem-tp4960715.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Aug. 13, 2017

Probably a bug in Garage SQLite

by Herby VojÄÃk

Hello! This testing code: | databaseFile login accessor sqlString | databaseFile := Smalltalk imageDirectory asFileReference / 'play.sqlite'. login := Login new database: SQLite3Platform new; host: ''; port: ''; username: ''; password: ''; databaseName: databaseFile fullPath asZnUrl asString; yourself. accessor := DatabaseAccessor forLogin: login. accessor login. sqlString := 'SELECT * FROM AGENT'. (accessor basicExecuteSQLString: sqlString) contents inspect. fails (Pharo 6.1, GarageGlorp #stable loaded a week ago as a project dependency) with: Error: Unable to resolve external type: sqlite3 FFICallout(Object)>>error: FFICallout>>resolveType: FFICallout>>typeName:pointerArity: FFICallout>>argName:indirectIndex:type:ptrArity: FFIFunctionParser>>parseArgument FFIFunctionParser>>parseArguments FFIFunctionParser>>parseNamedFunction: FFICalloutMethodBuilder>>parseSignature: FFICalloutMethodBuilder>>generate FFICalloutMethodBuilder>>build: FFICalloutAPI>>function:module: GASqlite3FFI(Object)>>ffiCall:module: GASqlite3FFI>>apiErrorMessage: GASqlite3FFI>>signal:with:on: GASqlite3FFI>>checkForOk:on: GASqlite3FFI>>prepare:on:with: GASqlite3Statement>>prepare GASqlite3Driver>>prepare: GASqlite3ResultSet>>prepareStatement: GASqlite3ResultSet>>execute:withCollection: GASqlite3ResultSet>>execute:with:on: GASqlite3Driver>>execute:with: GASqlite3Driver>>execute: GAGlorpDriver>>basicExecuteSQLString: PharoDatabaseAccessor>>basicExecuteSQLString: UndefinedObject>>DoIt OpalCompiler>>evaluate [..snip..] Problem seems to be that in FFICallout >> resolveType:, the line binding := resolver ffiBindingOf: name asSymbol. actually produces nil, resolver being GASqlite3FFI class. If looking at the class side of GaSqlite3FFI, there is no ffiBindingOf: at all; there is nbBindingOf: aTypeName ^ TypeMap at: aTypeName ifAbsent: [ super nbBindingOf: aTypeName ] though. If I copy near-mindlessly and add: ffiBindingOf: aTypeName ^ TypeMap at: aTypeName ifAbsent: [ super ffiBindingOf: aTypeName ] then the code above fails correctly with: 'no such table: AGENT'. Am I missing some nb<->ffi bridge? Or is there a bug in Garage SQLite driver? Herby

Aug. 13, 2017

Re: [Pharo-users] (no subject)

by Guillermo Polito

On Sun, Aug 13, 2017 at 10:31 AM, Vityou . <zlee314(a)gmail.com> wrote: > I recently discovered the pharo launcher. However, it only gives me > options to use outdated images, and I'm not sure about the vm. Is there > any way to change this? > Usually it will download the right vm for your image so you don't have to care. -- Guille Polito Research Engineer French National Center for Scientific Research - *http://www.cnrs.fr* <http://www.cnrs.fr> *Web:* *http://guillep.github.io* <http://guillep.github.io> *Phone: *+33 06 52 70 66 13

Aug. 13, 2017

Re: [Pharo-users] including Pillar in Pharo image by default

by Norbert Hartl

Hi, > Am 11.08.2017 um 21:10 schrieb Esteban Lorenzano <estebanlm(a)gmail.com>: > > hi, > >> On 11 Aug 2017, at 18:57, Cyril Ferlicot D. <cyril.ferlicot(a)gmail.com <mailto:cyril.ferlicot@gmail.com>> wrote: >> >> Another step would be to get a minimal parser not relying on >> PetitParser. > > Letâs think differently: why not to include a tiny PetitParser? > Then we can think on: > > - pillar sintax (better than just a restricted version) > - simplify other âsmall parsersâ that are already on the image. > - we provide a tool to o cool stuff (instead relying as always in regexp, etc.) > +1 I like that. I always feel bad if I use regex in pharo because I think I can do better. But then installing petit parser just to do some parsing sounds heavy weight. And parsing is such central functionality that it would be good to have a small parser near the core. For pillar I would like to see that class comments are a layer on top of the image core. It is metadata that can be optional and pillar could be a dependency to that layer. This would make it possible to strip out on deployment, too. Because I don't need class comments on my server :) Norbert

Aug. 13, 2017

(no subject)

by Vityou .

I recently discovered the pharo launcher. However, it only gives me options to use outdated images, and I'm not sure about the vm. Is there any way to change this?

Aug. 13, 2017

[ann] moldable editor - syntax highlighting ... with a twist

by Tudor Girba

Hi, After another intense week, we are happy to announce that the Brick editor now supports some advanced syntax highlighting. To put it in perspective, let us take a look at one screenshot showing an inspector presentation containing a Brick editor opened on a Pillar file that includes some text, a code snippet and a reference to a picture: This shows both that we style the text based on the Pillar grammar, but also that we can style Smalltalk code (in fact, we have two nested stylers here). But, the more interesting thing is that below the picture reference, we get to see the actual picture (which happens to be another inspector screenshot). In fact, this picture is actually just another text attribute (we call it an adornment) that can be dynamically added to any text elements. This opens up a whole lot of expression power and it is all easily compose-able. This is another reason why we say that this editor is moldable and you should expect new applications making use of this moldability and combining it with the liveliness of Pharo. The latest Brick code is loadable through: Metacello new baseline: 'Brick'; repository: 'github://pharo-graphics/Brick/src'; load: #development. If you want to play with Pillar, load the following extra code and just inspect a Pillar file: Metacello new smalltalkhubUser: 'Pier' project: 'Pillar'; configuration: 'Pillar'; version: #development; load. ((IceRepository registry detect: [ :each | each name = 'Brick' ]) packageNamed: 'Brick-Editor-Pillar') loadLatest. One other thing to mention is performance. What Alex (Syrel) managed to do is quite remarkable. To see the impact in practice, try editing the largest method in Pharo (UnicodeDefinitions class >> #data) in both the built-in editor and in the Brick editor by inspecting: BrTextEditor onMethod: UnicodeDefinitions class >> #data There are still issues left to deal with and we will focus on them in the following weeks. But, we can safely say that the most important challenges are now behind us and that the design of the editor code is stable and robust. Please do let us know what you think. Cheers, The feenk team -- www.tudorgirba.com www.feenk.com "If you interrupt the barber while he is cutting your hair, you will end up with a messy haircut."

Aug. 12, 2017

Re: [Pharo-users] including Pillar in Pharo image by default

by Esteban Lorenzano

> On 12 Aug 2017, at 18:22, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > > Esteban, I think that when Stef says "a mini version of pillar" he does not mean a mini version of the parser or the AST, but a version that does not have the exporting to html/latex/â¦ I know that. But Cyril talked about âgetting a parser without PPâ. That's where my comment belongs :) Esteban > > On Sat, Aug 12, 2017 at 4:37 PM, Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>> wrote: > and btw, this kind of threads belongs to pharo-dev, not to pharo-users :) > > Esteban > > > On 12 Aug 2017, at 16:35, Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>> wrote: > > > > > >> On 12 Aug 2017, at 12:46, Tudor Girba <tudor(a)tudorgirba.com <mailto:tudor@tudorgirba.com>> wrote: > >> > >> Hi, > >> > >> I would very much like this path. What would constitute tiny? > > > > no idea, we need to think on it :) > > but I see no point in create a new (even small) parser/scanner each time we need one. At the end you have several small parsers that repeat always same process when PetitParser is good for most of our problems (and if you need to improve it. you can always load PP compiler, etc.). > > > > Esteban > > > >> > >> Cheers, > >> Doru > >> > >> > >>> On Aug 11, 2017, at 9:10 PM, Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>> wrote: > >>> > >>> hi, > >>> > >>>> On 11 Aug 2017, at 18:57, Cyril Ferlicot D. <cyril.ferlicot(a)gmail.com <mailto:cyril.ferlicot@gmail.com>> wrote: > >>>> > >>>> Another step would be to get a minimal parser not relying on > >>>> PetitParser. > >>> > >>> Letâs think differently: why not to include a tiny PetitParser? > >>> Then we can think on: > >>> > >>> - pillar sintax (better than just a restricted version) > >>> - simplify other âsmall parsersâ that are already on the image. > >>> - we provide a tool to o cool stuff (instead relying as always in regexp, etc.) > >>> > >>> cheers, > >>> Esteban > >> > >> -- > >> www.tudorgirba.com <http://www.tudorgirba.com/> > >> www.feenk.com <http://www.feenk.com/> > >> > >> "Beauty is where we see it." > >> > >> > >> > >> > >> > > > > > > > > -- > > Guille Polito > > Research Engineer > French National Center for Scientific Research - http://www.cnrs.fr <http://www.cnrs.fr/> > > > Web: http://guillep.github.io <http://guillep.github.io/> > Phone: +33 06 52 70 66 13

Aug. 12, 2017