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

Re: [Pharo-users] [Pharo-dev] installing gtoolkit

by Tudor Girba

Hi, On Tue, Mar 25, 2014 at 10:02 AM, phil(a)highoctane.be <phil(a)highoctane.be>wrote: > On Tue, Mar 25, 2014 at 8:17 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > >> Hi, >> >> If you want to install GToolkit (the project that contains GTInspector, >> GTPlayground and GTDebugger) in your image, you can follow one of the >> options as described here: >> http://www.humane-assessment.com/blog/installing-gtoolkit >> >> If you give it a try, please let us know how it works for you. >> > > Looks *very* nice. Takes a while to get used to. > Happy. > Now, the gtoolkit image I used didn't respected the Pharo3 keybindings > that allow one to open a workspace (Alt-o Alt-w / Cmd-o Cmd-w). > It would be nice to have them so that opening the Playground is done in a > snap. > The global shortcuts are disabled because they conflict with the Cmd+o shortcuts used everywhere in the GTInspector and GTPlayground. We have an issue open on this, but we did not yet come to a conclusion. It would be useful to have more eyeballs looking at it: https://pharo.fogbugz.com/f/cases/13102/Sequences-of-bindings-hide-individu… > Question: if one has opened a Miller column too far, how can we close that > one? It was annoying to have to use to precisely use the scrollbar down > there to get back to where I was. And if the column is not out of view, it > keeps on updating and moves the thing to the right. Kind of ping-pong style. > You cannot :(. The current implementation of the Miller column widget is not at all optimal. I have a new design that does not rely on a scrollbar at all, but to get that to work, we would need a bit more effort involved in building the necessary widgets. It would be great to have more contributions there. If anyone is interested, please let me know. > I'll load it in my current development project and see how it goes (that > superwhite theme of Moose is just an eye killer for me). > Great. Let me know how it works and what quirks you get into. Cheers, Doru > Phil > > >> >> Cheers, >> Doru >> >> -- >> www.tudorgirba.com >> >> "Every thing has its own flow" >> > > -- www.tudorgirba.com "Every thing has its own flow"

March 25, 2014

Re: [Pharo-users] [Pharo-dev] installing gtoolkit

by Sven Van Caekenberghe

On 25 Mar 2014, at 10:02, phil(a)highoctane.be wrote: > Question: if one has opened a Miller column too far, how can we close that one? It was annoying to have to use to precisely use the scrollbar down there to get back to where I was. And if the column is not out of view, it keeps on updating and moves the thing to the right. Kind of ping-pong style. I have had a similar remark in the past: I want to be able to close the extra columns. It all takes so much space and it a distraction once you no longer need them.

March 25, 2014

Re: [Pharo-users] [Pharo-dev] installing gtoolkit

by phil＠highoctane.be

On Tue, Mar 25, 2014 at 8:17 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi, > > If you want to install GToolkit (the project that contains GTInspector, > GTPlayground and GTDebugger) in your image, you can follow one of the > options as described here: > http://www.humane-assessment.com/blog/installing-gtoolkit > > If you give it a try, please let us know how it works for you. > Looks *very* nice. Takes a while to get used to. Now, the gtoolkit image I used didn't respected the Pharo3 keybindings that allow one to open a workspace (Alt-o Alt-w / Cmd-o Cmd-w). It would be nice to have them so that opening the Playground is done in a snap. Question: if one has opened a Miller column too far, how can we close that one? It was annoying to have to use to precisely use the scrollbar down there to get back to where I was. And if the column is not out of view, it keeps on updating and moves the thing to the right. Kind of ping-pong style. I'll load it in my current development project and see how it goes (that superwhite theme of Moose is just an eye killer for me). Phil > > Cheers, > Doru > > -- > www.tudorgirba.com > > "Every thing has its own flow" >

March 25, 2014

installing gtoolkit

by Tudor Girba

Hi, If you want to install GToolkit (the project that contains GTInspector, GTPlayground and GTDebugger) in your image, you can follow one of the options as described here: http://www.humane-assessment.com/blog/installing-gtoolkit If you give it a try, please let us know how it works for you. Cheers, Doru -- www.tudorgirba.com "Every thing has its own flow"

March 25, 2014

Re: [Pharo-users] neo json and valueSchema for integer attributes ...

by Sven Van Caekenberghe

Hi Marten, It took a while, but I implemented a new feature that should solve your issue. You can now do the following: String streamContents: [ :out | (NeoJSONWriter on: out) for: #StringAsHex customDo: [ :mapping | mapping encoder: [ :x | x asByteArray hex asUppercase ]; decoder: [ :x | (ByteArray readHexFrom: x) asString ] ]; nextPut: 'Foo bar!' as: #StringAsHex ]. (NeoJSONReader on: '"466F6F2062617221"' readStream) for: #StringAsHex customDo: [ :mapping | mapping encoder: [ :x | x asByteArray hex asUppercase ]; decoder: [ :x | (ByteArray readHexFrom: x) asString ] ]; nextAs: #StringAsHex. As well as: String streamContents: [ :out | (NeoJSONWriter on: out) for: Point do: [ :mapping | (mapping mapProperty: #x getter: [ :object | object x ] setter: [ :object :value | object setX: value setY: object y ]) valueSchema: #AsString. (mapping mapProperty: #y getter: [ :object | object y ] setter: [ :object :value | object setX: object x setY: value ]) valueSchema: #AsString ]; for: #AsString customDo: [ :mapping | mapping encoder: [ :x | x asString ]; decoder: [ :x | x asNumber ] ]; nextPut: 1@2 ]. (NeoJSONReader on: '{"x":"1","y":"2"}' readStream) for: Point do: [ :mapping | (mapping mapProperty: #x getter: [ :object | object x ] setter: [ :object :value | object setX: value setY: object y ]) valueSchema: #AsString. (mapping mapProperty: #y getter: [ :object | object y ] setter: [ :object :value | object setX: object x setY: value ]) valueSchema: #AsString ]; for: #AsString customDo: [ :mapping | mapping encoder: [ :x | x asString ]; decoder: [ :x | x asNumber ] ]; nextAs: Point. In #bleedingEdge of NeoJSON: === Name: Neo-JSON-Core-SvenVanCaekenberghe.26 Author: SvenVanCaekenberghe Time: 24 March 2014, 12:18:21.026173 pm UUID: 41d2075d-bca4-4c08-bdf8-ed0c8da9bcf2 Ancestors: Neo-JSON-Core-SvenVanCaekenberghe.25 Added new feature NeoJSONWriter>>#nextPutAs: symmetrical to NeoJSONReader>>#next:as: More specifically NeoJSONPropertyMapping>>#writeObjectOn: now respects the valueSchema if it exists using NeoJSONStreamingWriter>>#writeKey:value:as: and NeoJSONWriter>>#encodeKey:value:as: Made both the reader and writer blocks in NeoJSONCustomMapping optional with a fallback to default behavior Refactoring: added NeoJSONMapping abstract superclass above NeoJSONObjectMapping and NeoJSONCustomMapping to better clarify the design === Name: Neo-JSON-Tests-SvenVanCaekenberghe.24 Author: SvenVanCaekenberghe Time: 24 March 2014, 12:19:53.503067 pm UUID: 4c7461c1-82ea-4126-8b5c-ef307168120a Ancestors: Neo-JSON-Tests-SvenVanCaekenberghe.23 Added new feature NeoJSONWriter>>#nextPutAs: symmetrical to NeoJSONReader>>#next:as: Added 4 unit test to exercise the new options === Regards, Sven On 21 Feb 2014, at 15:00, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > Hi Marten, > > There is indeed something currently not completely implemented: #valueSchema: and #nextAs: were added afterwards for reading (for example a collection of Points), the use of this concept for writing is simply not there. (compare NeoJSONPropertyMapping>>#readObject:from: to NeoJSONPropertyMapping>>#writeObject:on:) > > I will think about this a bit first. > > On the other hand, I am not so sure your solution is good, because you cannot write a generic #AsString for reading (going from String to ?). So I would suggest one of the other solutions mentioned in this thread. > > Thanks for the feedback. > > Sven > > On 21 Feb 2014, at 13:56, itlists(a)schrievkrom.de wrote: > >> Hmm, I think that something is definitly missing here. >> >> The same code but instead of using #AsString I use DateAndTime and it >> works as expected - and that's what I would expect: use for that >> property mapping a valueSchema named "AsString". >> >> It seems to work for all classes, when there is no predefined encoding >> available in the running system:Integer has a mathod, DateAndTime not. >> >> Is there any reason why is works that way ? >> >> Marten >> >> >> >> >> >> Am 21.02.2014 12:07, schrieb Sven Van Caekenberghe: >>> >>> On 21 Feb 2014, at 09:18, Norbert Hartl <norbert(a)hartl.name> wrote: >>> >>>> Am 21.02.2014 um 07:50 schrieb itlists(a)schrievkrom.de: >>>> >>>>> I have a class with an instance attribute "x" and this one contains an >>>>> integer value. >>>>> >>>>> No when exporting this to json I want to write a string instead of this >>>>> number to the json string ... >>>>> >>>>> neoJsonMapping: mapper >>>>> mapper for: self do: [ :mapping | >>>>> (mapping mapInstVar: #x to: 'x') valueSchema: #AsString. >>>>> ]. >>>>> >>>>> mapper for: #AsString customDo: [ :mapping | >>>>> mapping encoder: [ :anInteger | x asString ]. >>>>> mapping decoder: [ :aString | ... ] ]. >>>>> >>>>> But whatever I do ... only numbers are written out ... and yes of course >>>>> I could add additional accessors doing the conversion. >>>> >> >> >> -- >> Marten Feldtmann >

March 24, 2014