- Pharo-dev - lists.pharo.org

Re: [Pharo-project] SimpleLiteralArrayParser

by StÃ©phane Ducasse

Mariano read the metacello mailing list mails I sent. I hate hate hate repeating myself. I started to work on the LIteralArrayParser so that we do not have the problem in the future. Stef On Apr 24, 2012, at 12:52 PM, Mariano Martinez Peck wrote: > > > On Tue, Apr 24, 2012 at 12:43 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > > Hi guys > > > > We should develop a simple Literal Array parser that is dialect independant > > so that we can avoid using JSON for meta data. So I will start to develop. I will start to write some tests and do it test first. > > > > Gofer new > > repository: 'http://ss3.gemstone.com/ss/SimpleLiteralArrayParser'; > > package: 'SimpleLiteralArrayParser'; > > load > > > > Now I still wonder what do we do about floats. May be the situation changed but Squeak and VW floats were not the same. > > > > I don't get it. You define your own float format, and then each dialect parses it and converts it to their correspondant format... Now, I do not know the format > > differences so I do not know which one take :). > > It can work for simple scenario but if you save a float with e120 and save it and you get e70 > then you are in trouble. > > You are not in trouble. And if you are, then you are exactlty the same as if you were using a literal parser. > You have a specification. You say that floats are written in THIS XXX text representation. Nobody cares how your floats are represented inside your Smalltalk. For JSON you write floats in a particular way, explained by the JSON specification. > Then, when you code the parser, you will need to crate an instance of Float from the string. Each dialect will know how to do that. > So, again, where is the problem? > And how the literal parser would solve it? because I think it will happen the same. > > Cheers, > > > > Stef > > > > -- > Mariano > http://marianopeck.wordpress.com >

April 24, 2012

Re: [Pharo-project] Do we get rid of the KeyDecodeTable in InputEventSensor?

by Mark Smith

On 22 Apr 2012, at 21:41, StÃ©phane Ducasse wrote: > > On Apr 22, 2012, at 8:13 PM, phil(a)highoctane.be wrote: > >> May I add that some Cmd-Q on OSX really sucks for autocompletion? > > indeed :) > This is why ecompletion and ocompletion propose other ways > >> >> And Alt-Shift for Halos when you have multiple keyboards setup in Windows? (It is the system shortcut for toggle language (like FR->EN). Using the middle button like in Cuis would be much better methinks. > > no it was like that in squeak and it always went in our way. > now in Pharo20 we will change revisit all the logic of key mapping and probably use the work on guillermo to be able to plug the binding people want. I want emacs binding for text for example :) +50 for emacs-style keybindings. I would love feel as fluid in Pharo as I do in emacs :). Mark >> >> Phil >> >> 2012/4/22 Guillermo Polito <guillermopolito(a)gmail.com> >> It's supposed to do some conversions, but sometimes, it just screws up the use input. It's main responsibility is to change ctrl into alt: >> >> installDuplicateKeyEntryFor: c >> | key | >> key := c asInteger. >> "first do control->alt key" >> KeyDecodeTable at: { key bitAnd: 16r9F . 2 } put: { key . 8 }. >> "then alt->alt key" >> KeyDecodeTable at: { key . 8 } put: { key . 8 } >> >> >> And then it confuses stuff. For example, Ctrl + tab is decoded as ctrl + $i, since >> >> $i asInteger bitAnd: 16r9F = Character tab asInteger >> >> >> And btw, I love my ctrl key and want to have more fancy and sexy shortcuts, so this F*** table is bothering :). >> >> Opinions? >> Guille >> >> >> >> -- >> Philippe Back >> "Helping you hit the top 3 outcomes you really want to achieve" >> >> Mob: +32(0) 478 650 140 | Fax: +32 (0) 70 408 027 Mail: phil(a)highoctane.be | Web: http://philippeback.eu | Blog: >> http://philippeback.be >> >> High Octane SPRL >> rue cour Boisacq 101 >> 1301 Bierges >> > >

April 24, 2012

Re: [Pharo-project] Do we get rid of the KeyDecodeTable in InputEventSensor?

by Mark Smith

On 22 Apr 2012, at 19:13, phil(a)highoctane.be wrote: > May I add that some Cmd-Q on OSX really sucks for autocompletion? > > And Alt-Shift for Halos when you have multiple keyboards setup in Windows? (It is the system shortcut for toggle language (like FR->EN). Using the middle button like in Cuis would be much better methinks. +1, although I don't have a middle button on my trackpad :). Cmd-click would be good for halos on OS X. It i recall this is used in Xcode (interface builder) when manipulating graphical elements etc. > Phil > > 2012/4/22 Guillermo Polito <guillermopolito(a)gmail.com> > It's supposed to do some conversions, but sometimes, it just screws up the use input. It's main responsibility is to change ctrl into alt: > > installDuplicateKeyEntryFor: c > | key | > key := c asInteger. > "first do control->alt key" > KeyDecodeTable at: { key bitAnd: 16r9F . 2 } put: { key . 8 }. > "then alt->alt key" > KeyDecodeTable at: { key . 8 } put: { key . 8 } > > > And then it confuses stuff. For example, Ctrl + tab is decoded as ctrl + $i, since > > $i asInteger bitAnd: 16r9F = Character tab asInteger > > > And btw, I love my ctrl key and want to have more fancy and sexy shortcuts, so this F*** table is bothering :). > > Opinions? > Guille > > > > -- > Philippe Back > "Helping you hit the top 3 outcomes you really want to achieve" > > Mob: +32(0) 478 650 140 | Fax: +32 (0) 70 408 027 Mail: phil(a)highoctane.be | Web: http://philippeback.eu | Blog: > http://philippeback.be > > High Octane SPRL > rue cour Boisacq 101 > 1301 Bierges >

April 24, 2012

Re: [Pharo-project] STON (was Re: SimpleLiteralArray Spec)

by Sven Van Caekenberghe

Philippe, On 24 Apr 2012, at 22:20, Philippe Back wrote: > How to ship binary around? It works ;-) But I must say that this is/was not my primary use case. I think that a binary format like Fuel is better (more efficient, better/deeper system integration). Anyway, here is an example: Here is the Pharo logo ZnEasy get: 'http://www.pharo-project.org/images/pharo.png' This is a PNG of about 180Kb. Now get is as a form ZnEasy getPng: 'http://www.pharo-project.org/images/pharo.png' If you already want to look at it now (ZnEasy getPng: 'http://www.pharo-project.org/images/pharo.png') asMorph openInHand Now serialize it in STON STON toStringPretty: (ZnEasy getPng: 'http://www.pharo-project.org/images/pharo.png') Or directly to a file FileStream newFileNamed: '/tmp/form.ston' do: [ :stream | stream lineEndConvention: #lf. STON put: (ZnEasy getPng: 'http://www.pharo-project.org/images/pharo.png') onStreamPretty: stream ] The result is 200Kb text file that looks like ColorForm { #bits : Bitmap [ 4294967295, 4294967295, 4294967295, ... 4294967295, 4294967040 ], #width : 375, #height : 135, #depth : 8, #offset : nil, #colors : [ TranslucentColor { #rgb : 1010156636, #cachedDepth : nil, #cachedBitPattern : nil, #alpha : 241 â¦ TranslucentColor { #rgb : 0, #cachedDepth : nil, #cachedBitPattern : nil, #alpha : 0 } ], #cachedDepth : nil, #cachedColormap : nil } It goes on with numbers in between for a very long time. Note that this is strictly based on the generic serialization behavior. I attach a bzip2 compressed copy of the file to this mail (form.ston.bz2). Uncompress it with bunzip2 and try (FileStream oldFileNamed: '/tmp/form.ston' do: [ :stream | STON fromStream: stream ]) asMorph openInHand Let me know if that works for you. Sven -- Sven Van Caekenberghe http://stfx.eu Smalltalk is the Red Pill

April 24, 2012

[Pharo-project] Slime with Nautilus?

by blake

Yo, I'm trying to run Slime (per the Seaside book) but I don't see "refactoring scope" in my menu options. I'm guessing "Browse restricted" serves the same purpose. But with (or without) that open, I don't have a "code critics" in my browser submenu. I'm not really sure I even have Slime installed. I do have the following classes installed: GRSlimeBlockLintRule GRSlimeParseTreeLintRule GRSlimeTest GRSlimeTransformationRule WASlime WASlimeTest ===Blake===

April 24, 2012

Re: [Pharo-project] Suggestion: introducing a fixme/issue/todo pragma

by Mark Smith

On 22 Apr 2012, at 19:10, phil(a)highoctane.be wrote: > I kind of like dirty corners. Especially for cleaning them up and turn them into shiny new orbs of glory. > > Jokes aside, there is an awful lot of potential in Pharo. Just being exposed to it for a while shows in my other coding activities (other languages). > > I would be perfect if we could grasp the whole system given enough attention (like the "Feel of Cuis" which is real). The challenge is to hit the sweet spot. Too much convolutions and we are doomed. Too little features and we can't be considered a contender. Agreed, but I'm fine with loading the features I want. The more features there are at the core of the system the more we need to fit into our heads. I would like to see a small and `tidy' core (not dissimilar to that defined for Spoon :)). Mark. > KR > Philippe > > 2012/4/22 Mariano Martinez Peck <marianopeck(a)gmail.com> > > > On Sun, Apr 22, 2012 at 3:53 PM, phil(a)highoctane.be <phil(a)highoctane.be> wrote: > Ok. > > Looks like there is still a lot of dirty corners under the hood by looking at this list of senders... > > Indeed. But the first step is to identify them, right? So at least we know those dirty corners ;) > > > > Phil > > 2012/4/22 Mariano Martinez Peck <marianopeck(a)gmail.com> > > > On Sun, Apr 22, 2012 at 11:55 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > we use self flag: #fixMe > you can then query either #fixMe or flag: > > and yes this is a good idea to mark things and create bug entries. > > Stef > > > On Apr 22, 2012, at 11:18 AM, phil(a)highoctane.be wrote: > > > While looking around in the image, I am in need of knowing where I found thngs that either puzzle me or are "wrong" (well, a code smell). > > > > What I do is that I put pragmas in there like this (not that this sample is meant to be representative) > > > > privCleanTextConstants > > <fixme> > > TextConstants TextSharedInformation removeKey: #DefaultTextStyle. > > TextConstants TextSharedInformation removeKey: #DefaultMultiStyle. > > TextConstants TextSharedInformation removeKey: #DefaultFixedTextStyle. > > TextConstants TextSharedInformation removeKey: StrikeFont defaultFontKey. > > > > Smalltalk allClasses select: [:c | c sharedPools includes: TextConstants] thenDo: [:c | c compileAll ]. > > > > And I can then find back the things with: > > > > pc := (PragmaCollector filter: [:prg | prg keyword = 'fixme']) reset. > > pc collected size. "(Print It: 1)" > > pc collected explore. > > > > And then finding back the Class and Method Name > > > > Building upon that, why not do what is done in other environments (well, I've got that in PHP, Java, ...) and use: > > > > <todo:do this and that> or plain <todo> > > <fixme: this and that> or plain <fixme> > > <issue:issue#> > > > > As Stef said, we usually use #flag: Normal cases are #flag:todo, #flag:fixMe, etc .. and the browser is aware of that and shows you a flag in the icon of the method. > > > > > And have a specific tool to help the navigation (explore is fine for a moment but...) > > > > This would allow us to have an idea on the technical debt inside the system, broken down by areas if we start leveraging Packages. > > > > What I do not know is how much stress this would put on the system. Are pragmas eating a lot or a just markers? > > > > Phil > > > > > > > > -- > Mariano > http://marianopeck.wordpress.com > > > > > -- > Philippe Back > "Helping you hit the top 3 outcomes you really want to achieve" > > Mob: +32(0) 478 650 140 | Fax: +32 (0) 70 408 027 Mail: phil(a)highoctane.be | Web: http://philippeback.eu | Blog: > http://philippeback.be > > High Octane SPRL > rue cour Boisacq 101 > 1301 Bierges > > > > > -- > Mariano > http://marianopeck.wordpress.com > > > > > -- > Philippe Back > "Helping you hit the top 3 outcomes you really want to achieve" > > Mob: +32(0) 478 650 140 | Fax: +32 (0) 70 408 027 Mail: phil(a)highoctane.be | Web: http://philippeback.eu | Blog: > http://philippeback.be > > High Octane SPRL > rue cour Boisacq 101 > 1301 Bierges >

April 24, 2012

Re: [Pharo-project] STON (was Re: SimpleLiteralArray Spec)

by Dale Henrichs

Very cool! Let's see ... export the pharo implementation of STON in Cypress package format (using FileTree), then port STON to other dialects and voila:) the next generation of Cypress can use STON in place of JSON! Dale ----- Original Message ----- | From: "Sven Van Caekenberghe" <sven(a)beta9.be> | To: Pharo-project(a)lists.gforge.inria.fr | Sent: Tuesday, April 24, 2012 1:14:08 PM | Subject: Re: [Pharo-project] STON (was Re: SimpleLiteralArray Spec) | | | On 24 Apr 2012, at 21:40, Sven Van Caekenberghe wrote: | | > Apart from the fact that I used single quotes for strings in STON, | > it already works (and I could enhance the parser to accept both I | > guess). | | --- | Name: Ston-Core-SvenVanCaekenberghe.27 | Author: SvenVanCaekenberghe | Time: 24 April 2012, 10:13:07 pm | UUID: dd7c16b2-950c-4246-bf60-130de447cddf | Ancestors: Ston-Core-SvenVanCaekenberghe.26 | | extended the parser to allow either single or double quotes as String | delimiters which gives us JSON backward compatibilty ! (thanks Dale | Henrichs for this great idea). | --- | | | |

April 24, 2012

[Pharo-project] RE : Re: STON (was Re: SimpleLiteralArray Spec)

by Philippe Back

Wow this is great. How to ship binary around? Use case: forms EnvoyÃ© depuis un mobile Samsung Sven Van Caekenberghe <sven(a)beta9.be> a Ã©critÂ : On 24 Apr 2012, at 21:40, Sven Van Caekenberghe wrote: > Apart from the fact that I used single quotes for strings in STON, it already works (and I could enhance the parser to accept both I guess). --- Name: Ston-Core-SvenVanCaekenberghe.27 Author: SvenVanCaekenberghe Time: 24 April 2012, 10:13:07 pm UUID: dd7c16b2-950c-4246-bf60-130de447cddf Ancestors: Ston-Core-SvenVanCaekenberghe.26 extended the parser to allow either single or double quotes as String delimiters which gives us JSON backward compatibilty ! (thanks Dale Henrichs for this great idea). ---

April 24, 2012

Re: [Pharo-project] STON (was Re: SimpleLiteralArray Spec)

by Sven Van Caekenberghe

On 24 Apr 2012, at 21:40, Sven Van Caekenberghe wrote: > Apart from the fact that I used single quotes for strings in STON, it already works (and I could enhance the parser to accept both I guess). --- Name: Ston-Core-SvenVanCaekenberghe.27 Author: SvenVanCaekenberghe Time: 24 April 2012, 10:13:07 pm UUID: dd7c16b2-950c-4246-bf60-130de447cddf Ancestors: Ston-Core-SvenVanCaekenberghe.26 extended the parser to allow either single or double quotes as String delimiters which gives us JSON backward compatibilty ! (thanks Dale Henrichs for this great idea). ---

April 24, 2012

Re: [Pharo-project] STON (was Re: SimpleLiteralArray Spec)

by Sven Van Caekenberghe

On 24 Apr 2012, at 21:05, Dale Henrichs wrote: > Sven, > > Just an off-the-wall thought... If JSON were a subset of STON ... or possibly STON would recognize JSON and parse despite the different syntax...we'd have a nice multipurpose parser/writer that could speak JSON or STON interchangeably... > > Dale That is a great idea, Dale, I never thought of that ! Apart from the fact that I used single quotes for strings in STON, it already works (and I could enhance the parser to accept both I guess). Here is an example using a JSON REST call to convert IP addresses to countries: *nix Shell: $ curl http://easy.t3-platform.net/rest/geo-ip?address=205.140.197.101 {"latitude":38.0,"address":"205.140.197.101","country":"US","longitude":-97.0} Smalltalk: ZnClient new systemPolicy; beOneShot; url: 'http://easy.t3-platform.net/rest/geo-ip'; queryAt: 'address' put: '205.140.197.101'; accept: ZnMimeType applicationJson; contentReader: [ :entity | STON fromString: (entity contents replaceAll: $" with: $') ]; get. a Dictionary('address'->'205.140.197.101' 'country'->'US' 'latitude'->38.0 'longitude'->-97.0 ) Thx, Sven

April 24, 2012