March 2019 - Pharo-users - lists.pharo.org

Re: [Pharo-users] OS X bundle, some progress

by Hilaire

One useful information will be to know where stdout file is created by default? VM, image, home, folder, ... Obviously there is situation with problem creating stdout files. Can it be shutdown? For the record, the error is REPEATABLE, Pharo started from the CLI or from an installed Application. Once the image started: error with stdout does not exist, force recursive file creation, filename "stdout" This occures with stock OS X 32bits VM and Image. Any one willing to do serious deliverable Pharo Application with Mac will be hit by this error. Is OS X making situation more difficult? Hilaire Le 01/03/2019 Ã 23:19, Hilaire a Ã©critÂ : Hi, > I did some progress on the Dr.Geo bundle for OS X. > > The Mac admin of my school told me to download from Safari and > authorized the drgeo.eu web site (not sure what this exactly does), then > we installed the DrGeo.app at the Application location. > > DrGeo started fine but emit a startup error at the image level, related > to stdout. It looks like a stdout file can not be created. The stack is > enclosed here. When looking at the execution stack, I could not > determine (I have to go teaching) where the image wants to create this > stdout file. > > Any idea or opinion on this stdout matter? -- Dr. Geo http://drgeo.eu

March 3, 2019

Re: [Pharo-users] why do I not see the right text here (seaside)

by Esteban Maringolo

Please apologize my "write in Gmail" syntax errors. The #beFixedHeader was a wrong transcription, it should be #fixedHeader. And the unimplemented method was because of a missing period at the end. It should have been: html render: header. html mdlLayoutContainer: [ self renderPageContentOn: html ] Regards, Esteban A. Maringolo El sÃ¡b., 2 mar. 2019 a las 16:03, Roelof Wobben (<r.wobben(a)home.nl>) escribiÃ³: > > Op 2-3-2019 om 19:36 schreef Esteban Maringolo: > > renderContentOn: html > > html render: header > > html mdlLayoutContainer: [ self renderPageContentOn: html ] > > Are you sure. > > If I do your changes I see these error messages > > renderContentOn: html > html mdlLayout > beFixedHeader; > with: main > > > befixedHeader is not known > > renderContentOn: html > html > render: header html > mdlLayoutContainer: [ self renderPageContentOn: html ] > > I see this error message : > > render: mdlLayoutContainer messages send but not implemented. > > > >

March 2, 2019

Re: [Pharo-users] why do I not see the right text here (seaside)

by Roelof Wobben

Op 2-3-2019 om 19:36 schreef Esteban Maringolo: > renderContentOn: html > html render: header > html mdlLayoutContainer: [ self renderPageContentOn: html ] Are you sure. If I do your changes I see these error messages renderContentOn: html Â Â Â html mdlLayout Â Â Â Â Â Â beFixedHeader; Â Â Â Â Â Â with: main befixedHeader is not known renderContentOn: html Â Â Â html Â Â Â Â Â Â render: header html Â Â Â Â Â Â mdlLayoutContainer: [ self renderPageContentOn: html ] I see this error message : render: mdlLayoutContainerÂ messages send but not implemented.

March 2, 2019

Re: [Pharo-users] why do I not see the right text here (seaside)

by Esteban Maringolo

I haven't used MDL before, but moving code around I found that you are not nesting the MDL tags properly. The #mdlLayout must contain all the other elements, including the header. So using your own classes the best way would be to do the following: TBApplicationRootComponent>>renderContentOn: html html mdlLayout beFixedHeader; with: main TBSScreenComponent>>renderContentOn: html html render: header html mdlLayoutContainer: [ self renderPageContentOn: html ]. TBSScreenComponent>>renderPageContentOn: html self subclassResponsibility TBPostsListComponent>>renderPageContentOn: html html heading level:2 ; with: 'Here comes the sun' Regards. Esteban A. Maringolo El sÃ¡b., 2 mar. 2019 a las 13:33, Roelof Wobben (<r.wobben(a)home.nl>) escribiÃ³: > > Hello, > > I try to make my first seaside project. > But I ran into a problem that I do not see how to solve, > > The image can be found here : > *https://www.dropbox.com/s/8dt7xj1y6na5jog/Paintings.image?dl=0 > *and the changes file here : > *https://www.dropbox.com/s/dnsslrnpxgy0ha8/Paintings.changes?dl=0 > > *The problem is that I do not see the text "Blog post here" under my > header. > > I use Pharo version 7 on Windows 10, Seaside latest and MDL latest. > > I hope someone can help me figure out why this happen and how to solve this > > Regards, > > Roelof Wobben >

March 2, 2019

why do I not see the right text here (seaside)

by Roelof Wobben

Hello, I tryÂ to make my first seaside project. But I ran into a problem that I do not see how to solve, The image can be found here : *https://www.dropbox.com/s/8dt7xj1y6na5jog/Paintings.image?dl=0 *and the changes file here : *https://www.dropbox.com/s/dnsslrnpxgy0ha8/Paintings.changes?dl=0 *The problem is that I do not see the text "Blog post here" under my header. I use Pharo version 7 on Windows 10, Seaside latest and MDL latest. I hope someone can help me figure out why this happen and how to solve this Regards, Roelof Wobben

March 2, 2019

Re: [Pharo-users] [ANN] Pharo-SQLite even more multilingual

by Hilaire

Thanks! Hilaire Le 02/03/2019 Ã 14:16, Pierce Ng a Ã©critÂ : > I've enhanced the Pharo SQLite library to be even more multilingual. It has -- Dr. Geo http://drgeo.eu

March 2, 2019

Re: [Pharo-users] [ANN] Pharo-SQLite even more multilingual

by Esteban Maringolo

Wow! I wasn't aware SQLite supported that. Thank you from bringing such powerful, yet small, database to Pharo. Esteban A. Maringolo El sÃ¡b., 2 mar. 2019 a las 10:17, Pierce Ng (<pierce(a)samadhiweb.com>) escribiÃ³: > > Hi all, > > I've enhanced the Pharo SQLite library to be even more multilingual. It has > always supported data elements that are Pharo WideString instances, these > being converted to/from UTF8 transparently by the library. Now the library > also handles multilingual table names, column names and default column > values; in other words, multilingual SQL statements. > > To install in Pharo 7, load GlorpSQLite from the Catalog Browser. > > Example: > > | db | > db := UDBCSQLite3Connection openOn: '/tmp/ml.db'. > [ "Chinese table name, column names, and default column value." > db basicExecute: 'create table è¡¨ä¸ (é®ä¸ integer primary key, åäº text default ''ä¸æ'');'. > "Insert a row, taking default column value for the 2nd column." > db basicExecute: 'insert into è¡¨ä¸ (é®ä¸) values (NULL)'. > "Insert another row, specifying a value in Chinese for the 2nd column." > db execute: 'insert into è¡¨ä¸ values (NULL, ?)' > with: (Array with: 'å¼äº'). > (db execute: 'select * from è¡¨ä¸') rows inspect. > ] ensure: [ db close ] > > From the SQLite shell: > > % sqlite3 /tmp/ml.db > SQLite version 3.27.2 2019-02-25 16:06:06 > Enter ".help" for usage hints. > sqlite> .header on > sqlite> .schema > CREATE TABLE è¡¨ä¸ (é®ä¸ integer primary key, åäº text default 'ä¸æ'); > sqlite> select * from è¡¨ä¸; > é®ä¸|åäº > 1|ä¸æ > 2|å¼äº > sqlite> > > Testing and feedback welcome, especially on which other parts of the > library needing internationalization. > > Pierce > >

March 2, 2019

[ANN] Pharo-SQLite even more multilingual

by Pierce Ng

Hi all, I've enhanced the Pharo SQLite library to be even more multilingual. It has always supported data elements that are Pharo WideString instances, these being converted to/from UTF8 transparently by the library. Now the library also handles multilingual table names, column names and default column values; in other words, multilingual SQL statements. To install in Pharo 7, load GlorpSQLite from the Catalog Browser. Example: | db | db := UDBCSQLite3Connection openOn: '/tmp/ml.db'. [ "Chinese table name, column names, and default column value." db basicExecute: 'create table è¡¨ä¸ (é®ä¸ integer primary key, åäº text default ''ä¸æ'');'. "Insert a row, taking default column value for the 2nd column." db basicExecute: 'insert into è¡¨ä¸ (é®ä¸) values (NULL)'. "Insert another row, specifying a value in Chinese for the 2nd column." db execute: 'insert into è¡¨ä¸ values (NULL, ?)' with: (Array with: 'å¼äº'). (db execute: 'select * from è¡¨ä¸') rows inspect. ] ensure: [ db close ] >From the SQLite shell: % sqlite3 /tmp/ml.db SQLite version 3.27.2 2019-02-25 16:06:06 Enter ".help" for usage hints. sqlite> .header on sqlite> .schema CREATE TABLE è¡¨ä¸ (é®ä¸ integer primary key, åäº text default 'ä¸æ'); sqlite> select * from è¡¨ä¸; é®ä¸|åäº 1|ä¸æ 2|å¼äº sqlite> Testing and feedback welcome, especially on which other parts of the library needing internationalization. Pierce

March 2, 2019

Re: [Pharo-users] [Pharo-dev] looking for an author of a Beginning Pharo or related

by Ben Coman

Cool. Thx Stef On Sat, 2 Mar 2019 at 15:27, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Ok I will contact the editor telling that there are some wishes from the > community to do something. > After we can brainstorm on what should be purpose and outline. > > Stef > > On 1 Mar 2019, at 18:21, Ben Coman <btc(a)openinworld.com> wrote: > > Obviously its good to be circumspect at such an earlier stage, > but I can imagine a few "good" editors who publishing a book would really > lend some legitimacy and exposure to Pharo. > That would be overall beneficial even if the book is not free. > > Stef, I am interested to know more. > > cheers -ben > > On Fri, 1 Mar 2019 at 17:01, Thomas Dupriez <tdupriez(a)ens-paris-saclay.fr> > wrote: > >> Hello, >> >> The timing of this mail is interesting, because just yesterday I stumbled >> on the "Free Software Needs Free Documentation" preface of the GDB >> documentation. >> >> It's a dozen paragraph so not exactly a short read, but the gist of it is >> that the author urges other authors to use free documentation licenses for >> the documentations/manuals they are writing, so that they can be modified >> and grown by the community along with the free software they talk about. >> >> I've attached the full version if some people are interested in reading >> it. >> >> Sorry for this tangent, StÃ©phane. The timing was just too perfect. :) >> >> Thomas >> On 01/03/2019 08:09, StÃ©phane Ducasse wrote: >> >> Hi guys >> >> We have been contacted by a (good) editor that would like to publish on >> Beginning Pharo or related. >> I have a lot of material that I can give but no energy to write such book >> :) >> >> If one of you in interested, let me know. I could even be a co-author. >> >> Stef >> >> >> -------------------------------------------- >> StÃ©phane Ducasse >> http://stephane.ducasse.free.fr >> http://www.synectique.eu / http://www.pharo.org >> 03 59 35 87 52 >> Assistant: Julie Jonas >> FAX 03 59 57 78 50 >> TEL 03 59 35 86 16 >> S. Ducasse - Inria >> 40, avenue Halley, >> Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza >> Villeneuve d'Ascq 59650 >> France >> >> > -------------------------------------------- > StÃ©phane Ducasse > http://stephane.ducasse.free.fr > http://www.synectique.eu / http://www.pharo.org > 03 59 35 87 52 > Assistant: Julie Jonas > FAX 03 59 57 78 50 > TEL 03 59 35 86 16 > S. Ducasse - Inria > 40, avenue Halley, > Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza > Villeneuve d'Ascq 59650 > France > >

March 2, 2019

Re: [Pharo-users] How to write out simple Json?

by Sven Van Caekenberghe

Come on, no it does not. It generates invalid JSON (as it should, but doing so silently is wrong). Json render: { 'track' -> 'pharo'. 'language' -> 'smalltalk'. 'exercises' -> { 'slug' -> 'hello'. 'id' -> 55. 'topics' -> #('a' 'b' 'c') } }. => '["track": "pharo","language": "smalltalk","exercises": ["slug": "hello","id": 55,"topics": ["a","b","c"]]]' You see this is wrong, do you ? BTW, the package you mentioned did not load in Pharo, it can if you make the following change: Json class>>#initialise "Json initialize." escapeArray := Array new: 128. (0 to: 31), #(127) do: [ :each | escapeArray at: each + 1 put: '\u', (each printStringHex padLeftTo: 4 with: $0) ]. { $" -> '\"'. $\ -> '\\'. Character backspace -> '\b'. Character lf -> '\n'. Character newPage -> '\f'. Character cr -> '\r'. Character tab -> '\t'. } do: [ :each | escapeArray at: each key asciiValue + 1 put: each value ]. > On 2 Mar 2019, at 06:37, Paul DeBruicker <pdebruic(a)gmail.com> wrote: > > Of you load the JSON package from Squeaksource > (http://www.squeaksource.com/JSON.html) > > You can do a > > JSON render: { > 'track' -> 'pharo'. > 'language' -> 'smalltalk'. > 'exercises' -> { > 'slug' -> 'hello'. > 'id' -> 55. > 'topics' -> #('a' 'b' 'c') } > } > > > > and get a Json string or add e.g. > > Object>>#asJsonString > ^JSON render: self > > > > > > > Tim Mackinnon wrote >>> On 1 Mar 2019, at 10:35, Sven Van Caekenberghe < > >> sven@ > >> > wrote: >>> >>> Forget about the way you are trying to implement it, to what would >>> >>> { #key->#value. 1. true } >>> >>> be rendered in JSON ? >>> >>> { "key":"value", 1, true } >>> >>> or >>> >>> [ "key":"value", 1, true ] >>> >>> Both are illegal JSON. >> >> >> You didnât read what I said - with those 2 tiny changes - both of those >> given an exception just like STONJSON - the only difference is that I >> donât have to put asDictionary everywhere. >> >> Anyway - I think Iâve learned a lot from this discussion - and as Pharo is >> malleable I can do my little nasty subclass until I get burned and then I >> will probably adopt a proper Config object like Henrik mentioned ;) >> >> Just as a small additional question - when you do : >> >> ex := { >> #track->#pharo. >> #language->#smalltalk. >> #exercises->{ >> #slug->'hello'. >> #id->55. >> #topics->#('a' 'b' 'c') } asDictionary } asDictionary. >> >> Am I right in thinking that with asDictionary the order wonât be >> deterministic (which is valid for JSON dictionaries, but annoying for >> diffing config files). This is why I was doing asOrderedDictionary as I >> though I had seen it change on me a few times when I was generating >> output. >> >> Tim > > > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

March 2, 2019