April 2014 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [ANN]: Little NeoJSON Helper

by Sean P. DeNigris

Sean P. DeNigris wrote > "Assuming Neo-JSON-Core is loaded" > To aid in writing mappings, send "reader mapHelperFor: MyDomainClass" I improved the API a bit. Now, the mapping is done via class-side #addNeoJsonMapTo: aNeoJSONReader. The default (defined in class) brings up the helper. So now you can write: MyClass addNeoJsonMapTo: aNeoJSONReader. The first time you do this, you will get an inspector on the helper object, which you still send #generateInstVars. But for the second step, you now send #generateMapping, which compiles MyClass class>>#addNeoJsonMapTo: with the necessary mapping. If you're mapping a collection, you probably have to close the halt debugger now and restart, because the default behavior of inspecting the helper is cached in the reader. Otherwise, you can proceed and map the next class. I like the class side methods because they decompose monolithic mapping declarations and can be reused. ----- Cheers, Sean -- View this message in context: http://forum.world.st/ANN-Little-NeoJSON-Helper-tp4756763p4756791.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

April 28, 2014

Re: [Pharo-dev] Amber-Pharo based coding dojo in a coworking space

by Nicolas Petton

Awesome! It's really cool to see you pushing like this! Keep going! Cheers, Nico Sebastian Sastre writes: > Hi guys, > > I thought you might like to hear that after presenting a case on Smalltalk using these slides: > > http://dinos.flowingconcept.com > > to an for an heterogeneous audience ~(10% devel 10% creatives a couple of angel investors and most people with administration profile) in a coworking space. > > Many things happened after that session, one of those was that developers there started to ask for more but only after Iâve shown them availability for a demoing / coding session together. > > So, that coworking has scheduled a friday night coding dojo in a couple of weeks where they expect that I show them how to use Smalltalk to kick some ass > > sebastian > > o/ -- Nicolas Petton http://nicolas-petton.fr

April 28, 2014

Re: [Pharo-dev] 30838 and 837 *REVERTED*

by Marcus Denker

On 28 Apr 2014, at 16:31, Marcus Denker <marcus.denker(a)inria.fr> wrote: > Hi, > > if you downloaded 30 838 (from today) or 30 837 please re-download 837. > > Both images where broken due to things that have to be done âjust before the releaseâ, > which are, of course, broken as they are only done just before the release once a year. > The 837 available now is ok: https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-4-Publish/ http://files.pharo.org/image/30/latest.zip Marcus

April 28, 2014

30838 and 837 *REVERTED*

by Marcus Denker

Hi, if you downloaded 30 838 (from today) or 30 837 please re-download 837. Both images where broken due to things that have to be done âjust before the releaseâ, which are, of course, broken as they are only done just before the release once a year. Marcus

April 28, 2014

Re: [Pharo-dev] [Pharo3] 30837 has new sources file

by Marcus Denker

On 28 Apr 2014, at 16:21, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > On 28 Apr 2014, at 16:12, Marcus Denker <marcus.denker(a)inria.fr> wrote: > >> A close examination shows that *all* class side Traits methods have broken source pointersâ¦ > > Maybe that is just an oversight and easily fixed ? I revertedâ¦ the condenser needs to be fixed and after we should waste another hours on doing all this again. Marcus

April 28, 2014

Re: [Pharo-dev] [Pharo3] 30837 has new sources file

by Sven Van Caekenberghe

On 28 Apr 2014, at 16:12, Marcus Denker <marcus.denker(a)inria.fr> wrote: > A close examination shows that *all* class side Traits methods have broken source pointersâ¦ Maybe that is just an oversight and easily fixed ?

April 28, 2014

Re: [Pharo-dev] [Pharo3] 30837 has new sources file

by Sven Van Caekenberghe

On 28 Apr 2014, at 15:58, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On 28 Apr 2014, at 15:34, Marcus Denker <marcus.denker(a)inria.fr> wrote: > >> Hi, >> >> So we did >> >> -> an update 30837 to remove a bit of Scriploader methods so the do not end up in the .sources file (60.000 LOCâ¦) >> -> then we condensed the sources and changes and re-uploaded that file. >> -> Zeroconf has been updated. Now it download V1, V2 and V3 sourcesâ¦ (which is far from niceâ¦ but works). >> -> the sources files is here: http://files.pharo.org/sources/ >> >> Overall, the whole sources and changes mechanism again showed that it was not designed with the idea in mind >> to be able to ârelease at any pointâ. Our goal has to be that the build server artefact is the release artefact. >> Concerning .sources and .changes this is not the caseâ¦ we really need another design. >> > > e.g. now we have three tests failing: > >> SlotTests.SlotTraitsTest.testClassWithTrait2 >> Tests.Files.SourceFileArrayTest.testProtocol It seems that there is a minor difference in the method timestamp: testProtocol "Test that we can access protocol correctly" "self debug: #testProtocol" | okCm notOkCm | okCm := Point>>#dist: . self assert: (SourceFiles sourcedDataAt: okCm sourcePointer) = 'Point methodsFor: ''point functions'' stamp: ''lr 7/4/2009 10:42'''. while SourceFiles sourcedDataAt: okCm sourcePointer equals 'Point methodsFor: ''point functions'' stamp: ''lr 7/4/2009 10:42'' prior: 0' it is just the prior: 0 >> Tests.Files.SourceFileArrayTest.testTimeStamp same here, the rest is OK > I think the first goal of Pharo4 should be to make the artefact from the build server a true release > artefactâ¦ > > Marcus

April 28, 2014

Re: [Pharo-dev] [Pharo3] 30837 has new sources file

by Marcus Denker

On 28 Apr 2014, at 15:58, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On 28 Apr 2014, at 15:34, Marcus Denker <marcus.denker(a)inria.fr> wrote: > >> Hi, >> >> So we did >> >> -> an update 30837 to remove a bit of Scriploader methods so the do not end up in the .sources file (60.000 LOCâ¦) >> -> then we condensed the sources and changes and re-uploaded that file. >> -> Zeroconf has been updated. Now it download V1, V2 and V3 sourcesâ¦ (which is far from niceâ¦ but works). >> -> the sources files is here: http://files.pharo.org/sources/ >> >> Overall, the whole sources and changes mechanism again showed that it was not designed with the idea in mind >> to be able to ârelease at any pointâ. Our goal has to be that the build server artefact is the release artefact. >> Concerning .sources and .changes this is not the caseâ¦ we really need another design. >> > > e.g. now we have three tests failing: > >> SlotTests.SlotTraitsTest.testClassWithTrait2 >> Tests.Files.SourceFileArrayTest.testProtocol >> Tests.Files.SourceFileArrayTest.testTimeStamp > > > I think the first goal of Pharo4 should be to make the artefact from the build server a true release > artefactâ¦ > A close examination shows that *all* class side Traits methods have broken source pointersâ¦ So letâs revert everythingâ¦ (and I guess we do not need any other proof that *THE BUILD SERVER ARTEFACT NEEDS TO BE THE ARTEFACT OF RELEASE*. Marcus.

April 28, 2014

[ANN]: Little NeoJSON Helper

by Sean P. DeNigris

"Assuming Neo-JSON-Core is loaded" Gofer it smalltalkhubUser: 'SeanDeNigris' project: 'SeansPlayground'; package: 'Neo-JSON-Utilities'; load. To aid in writing mappings, send "reader mapHelperFor: MyDomainClass", where MyDomainClass need not even exist. This will halt inside the mapping, and bring up an inspector on a NeoJSONMapHelper object. >From here, you can #generateInstVars to map the json keys to inst vars, translating underscores to camel case. Then you can inspect #mappingSnippet, which will give you the code to replace "reader mapHelperFor: MyDomainClass" with the new mappings to inst vars. For example: mapper for: DoDropletSize do: [ :m | m mapInstVars: #(name cpu slug memory id disk); mapInstVar: #costPerHour to: #cost_per_hour; mapInstVar: #costPerMonth to: #cost_per_month ]. It could be enhanced, especially with a UI to further customize the mappings (e.g. maybe you want to map the boolean "required" key to a more Smalltalkish "isRequired" inst var, but it makes the common cases a bit easier. HTH :) ----- Cheers, Sean -- View this message in context: http://forum.world.st/ANN-Little-NeoJSON-Helper-tp4756763.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

April 28, 2014

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/30838 Home: https://github.com/pharo-project/pharo-core

April 28, 2014