August 2017 - Pharo-users - lists.pharo.org

Re: [Pharo-users] Glorp: `session login` fails for Garage SQLite

by Alistair Grant

Hi Herby, On 5 August 2017 at 18:09, Herby VojÄÃk <herby(a)mailbox.sk> wrote: > Hello! > > First of all, what is preferred way to (first time) login into database? I > had the impression that `aDatabaseAccessor login` is sorta low-level, and > one should do `session login` (after all, it is session you get to work > with, not an accessor). > > But with Garage SQLite, `session login`, when accessor is not logged, always > fails with "MessageNotUnderstood: GASqlite3Driver>>queryEncoding". > > Should one not use `session login` at all, then (when accessor is logged, it > just does nothing, if it isn't, it connects the accessor, but tries to do > some additional work which always fails)? > > Herby >From memory this is caused by differences between VisualWorks and Pharo. Anyway, it is discussed and resolved in: http://forum.world.st/Glorp-SQLite3-issue-td4899792.html Cheers, Alistair

Aug. 5, 2017

Re: [Pharo-users] problem with FLMaterializer

by Johannes Brauer

In the EnterprisePharo Book there is a chapter "Fuel Format Migration". There the format migration form Fuel version 1.7 to 1.9 is shown. I ask me if there is a similar possibility for the migration between Fuel in Pharo 4 and 6. Johannes Am 05.08.2017 um 15:08 schrieb Cyril Ferlicot <cyril.ferlicot(a)gmail.com<mailto:cyril.ferlicot@gmail.com>>: On sam. 5 aoÃ»t 2017 at 13:10, Johannes Brauer <brauer(a)nordakademie.de<mailto:brauer@nordakademie.de>> wrote: Peter Your suggestion is correct. I correct the expression to (FLMaterializer materializeFromFileNamed: aFileRefence fullName) Now I get another exception. KeyNotFound: key #'ositive8SmallIntegerClusterJ 4Ã 1â Ã°+ â( %? "< 9 Âª 6P M Â¾0 d *ÃD ''x ! Å 8' not found in SystemDictionary I think this is a compatibility problem between different Fuel versions. Hi, If you use Fuel to serialize objects with Pharo 4, then you can only materialize them with a Fuel from Pharo 4. Other versions of Fuel will not be able to read them. Johannes -- Cyril Ferlicot https://ferlicot.fr http://www.synectique.eu 2 rue Jacques PrÃ©vert 01, 59650 Villeneuve d'ascq France

Aug. 5, 2017

Re: [Pharo-users] about a pillar based output format for Epicea

by Stephane Ducasse

This is question of time and energy. I should restart to work and make it smaller and nicer. I want ecstatic too. On Wed, Aug 2, 2017 at 10:21 PM, Tim Mackinnon <tim(a)testit.works> wrote: > Out of curiosity (as Pillar - well actually Ecstatic, was on my next hitlist > to research), but is it so different from something like JavaScripts > Metalsmith.io ? I found metalsmithâs publishing pipeline and plugin system > quite intuitive and easy to use but I just didnât like nodejs so much (and > the crappy webpack/brunch auto reloading systems). > > It struck me that what they were doing was quite trivial in Smalltalk and I > assumed Pillar (and Ecstatic) were similar in concept. However when I had a > peak it did look quite complicated and made me think that porting Metalsmith > might be easier and in interesting personal project. > > Anyway, might be worth a look if you want architectural inspiration. > > Tim > > Sent from my iPhone > > > On 2 Aug 2017, at 18:19, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > > I'm because Pillar is central to all my writings around Pharo (books, > slides,...). > We also want to use it for a lecture on open-source development. > > Pillar got too complex and we should simplify its architecture. > > I'm working on a new version of Cocoon but this tedious and I got > stuck in managing > initialisation of fields (from text to objects). now I will continue > to work but task switching is killing me. > Guillermo is helping me from time to time and damien helps me with the > makefile/latex. > > I will first finish all the slides for my lectures at Prague first. > > Now we made > - sure that we can run archetype without being forced to passed by the > command-line. > - and many changes and cleanup. > Now we should work on > > - Make sure that we identify for real bugs showing up in the three > different archetypes (slides, books...). > - Avoid to convert to JSON files to apply mustache. > > - Rethink the architecture. > - Like removing the dependency on magritte from the core. > - Avoid a lot of strange behavior related to metadata handling. > > Stef > > > On Wed, Aug 2, 2017 at 6:15 PM, Alexandre Bergel > <alexandre.bergel(a)me.com> wrote: > > Pillar is becoming central in the way I produce documents. > Is there anyone working on improving Pillar? > > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > On Aug 2, 2017, at 11:55 AM, Stephane Ducasse <stepharo.self(a)gmail.com> > wrote: > > Hi martin > > I would like to wlak over epicea objects and save the changed methods > to be able to write booklets faster. > What advices can you give me? > Create a special visitor? > > Stef > > > >

Aug. 5, 2017

Re: [Pharo-users] Best Practices for Bundling Documentation

by Stephane Ducasse

Hi Evan Depending on the size of the documentation. - if you have a kind of tutorial I would go (and I can help) for a pillar booklet or a chapter. - else class comments are simply cool with examples stef On Sat, Aug 5, 2017 at 2:19 AM, Evan Donahue <emdonahu(a)gmail.com> wrote: > Hello, > > I'm working on cleaning up a couple of projects for release, and I was > wondering what the best practices were for including appropriate > documentation with projects. Should I just drop a text blob in a prominent > class comment? Is there a tool for structuring documentation? Is > documentation typically kept separate from the code? Seems natural to > include it so you never have to leave the image, but I'm not sure what most > people do. > > Thanks, > Evan

Aug. 5, 2017

Glorp: `session login` fails for Garage SQLite

by Herby VojÄÃk

Hello! First of all, what is preferred way to (first time) login into database? I had the impression that `aDatabaseAccessor login` is sorta low-level, and one should do `session login` (after all, it is session you get to work with, not an accessor). But with Garage SQLite, `session login`, when accessor is not logged, always fails with "MessageNotUnderstood: GASqlite3Driver>>queryEncoding". Should one not use `session login` at all, then (when accessor is logged, it just does nothing, if it isn't, it connects the accessor, but tries to do some additional work which always fails)? Herby

Aug. 5, 2017

Re: [Pharo-users] problem with FLMaterializer

by Cyril Ferlicot

On sam. 5 aoÃ»t 2017 at 13:10, Johannes Brauer <brauer(a)nordakademie.de> wrote: > Peter > > Your suggestion is correct. I correct the expression to > > (FLMaterializer materializeFromFileNamed: aFileRefence *fullName*) > > Now I get another exception. > KeyNotFound: key #'ositive8SmallIntegerClusterJ 4Ã 1â Ã°+ â( %? "< 9 Âª 6P M > Â¾0 d *ÃD ''x ! Å 8' not found in SystemDictionary > I think this is a compatibility problem between different Fuel versions. > Hi, If you use Fuel to serialize objects with Pharo 4, then you can only materialize them with a Fuel from Pharo 4. Other versions of Fuel will not be able to read them. > Johannes > > -- Cyril Ferlicot https://ferlicot.fr http://www.synectique.eu 2 rue Jacques PrÃ©vert 01, 59650 Villeneuve d'ascq France

Aug. 5, 2017

Re: [Pharo-users] problem with FLMaterializer

by Johannes Brauer

Peter Your suggestion is correct. I correct the expression to (FLMaterializer materializeFromFileNamed: aFileRefence fullName) Now I get another exception. KeyNotFound: key #'ositive8SmallIntegerClusterJ4Ã1âÃ°+â( %?Â"<9Âª6PMÂ¾0d*ÃD ''x!Å8' not found in SystemDictionary I think this is a compatibility problem between different Fuel versions. Johannes Am 05.08.2017 um 11:13 schrieb PBKResearch <peter(a)pbkresearch.co.uk<mailto:peter@pbkresearch.co.uk>>: Johannes Just a suggestion: FLMaterializer class >>materializeFromFileNamed: requires as argument aFilename, not aFileRefence. Presumably this means the name as a string. This makes sense, because #convertToWithConverter: is the name of a method understood by strings. If your invocation of the materializer includes asFileReference, try again without that. Hope this helps Peter Kenny From: Pharo-users [mailto:pharo-users-bounces@lists.pharo.org] On Behalf Of Johannes Brauer Sent: 04 August 2017 23:56 To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org<mailto:pharo-users@lists.pharo.org>> Subject: [Pharo-users] problem with FLMaterializer Hi everyone, trying to migrate a Seaside application from Pharo4 to Pharo6 I get a problem with FLMaterializer. An expression like (FLMaterializer materializeFromFileNamed: aFileRefence) results in MessageNotUnderstood: FileReference>>convertToWithConverter: The same file can be materialized in Pharo4 without problems. Johannes

Aug. 5, 2017

Re: [Pharo-users] problem with FLMaterializer

by PBKResearch

Johannes Just a suggestion: FLMaterializer class >>materializeFromFileNamed: requires as argument aFilename, not aFileRefence. Presumably this means the name as a string. This makes sense, because #convertToWithConverter: is the name of a method understood by strings. If your invocation of the materializer includes asFileReference, try again without that. Hope this helps Peter Kenny From: Pharo-users [mailto:pharo-users-bounces@lists.pharo.org] On Behalf Of Johannes Brauer Sent: 04 August 2017 23:56 To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> Subject: [Pharo-users] problem with FLMaterializer Hi everyone, trying to migrate a Seaside application from Pharo4 to Pharo6 I get a problem with FLMaterializer. An expression like (FLMaterializer materializeFromFileNamed: aFileRefence) results in MessageNotUnderstood: FileReference>>convertToWithConverter: The same file can be materialized in Pharo4 without problems. Johannes

Aug. 5, 2017

Best Practices for Bundling Documentation

by Evan Donahue

Hello, I'm working on cleaning up a couple of projects for release, and I was wondering what the best practices were for including appropriate documentation with projects. Should I just drop a text blob in a prominent class comment? Is there a tool for structuring documentation? Is documentation typically kept separate from the code? Seems natural to include it so you never have to leave the image, but I'm not sure what most people do. Thanks, Evan

Aug. 5, 2017

problem with FLMaterializer

by Johannes Brauer

Hi everyone, trying to migrate a Seaside application from Pharo4 to Pharo6 I get a problem with FLMaterializer. An expression like (FLMaterializer materializeFromFileNamed: aFileRefence) results in MessageNotUnderstood: FileReference>>convertToWithConverter: The same file can be materialized in Pharo4 without problems. Johannes

Aug. 4, 2017