- Pharo-dev - lists.pharo.org

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

by Sean P. DeNigris

Tudor Girba-2 wrote > Thank you, Marcus. + 100 ----- Cheers, Sean -- View this message in context: http://forum.world.st/30838-and-837-REVERTED-tp4756773p4756799.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 Mariano Martinez Peck

> > > Great to hear of small successes in reception of Pharo in the broader > community. Some ideas... > > 1. The most kick ass thing I can think of would go something like this... > a. Set up two computers nominally "customer" (or "webserver") and > "support team". Start the same image on each. > b. On the "customer" computer run some code that cause an error. In the > debugger Fuel-out to a USB stick. Show them the small size of the file. > c. On the "support team" computer, insert the USB stick and drag the > Fuel file into the image and start debugging. > Or the CI example were test failures are fueled out. This is a nice extension to the typical CI behavior. > Even better if the code that was running was a morph stepping across the > screen with some text inside counting up, and that counter and morph > position were maintained in the transition to the second computer - but I'm > not sure if Fuel would handle that. > > There is no way to know it but trying. The only problem could be that during the serialization, the traversed graph to serialize may be to big if it reaches to the display and all its world and related objects. Also, you may arrive to places that change so frequently like mouse position etc... This normally happens when you end up serializing the whole UI. In this case, it is likely the graph will change while you are serializing it...so you will be screw. Of course, if can hook a bit and cut the graph...but you should know in which place of your morph to cut. > 2. Parts of the Zinc quick start might be worthwhile... > http://zn.stfx.eu/zn/build-and-deploy-1st-webapp/ > > 3. Pull up halos on a menu and drag a duplicate a menu item onto the > background, then show that it still works when it is clicked. Bring up the > halos again and inspect the morph where you can change the name of that > menu item. Exit Pharo and restart to show that the renamed menu item is > still there. > > 4. Some of Doru's "build a custom browser" demos of Glamorous Toolkit are > inspiring for how few lines of code are needed, but I don't have references. > > good luck, > cheers -ben > > -- Mariano http://marianopeck.wordpress.com

April 28, 2014

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

by Sean P. DeNigris

Sean P. DeNigris wrote > I improved the API a bit. Now, the mapping is done via class-side > #addNeoJsonMapTo: aNeoJSONReader. Of course, if I had RTFM (more thoroughly), I would've noticed that Sven already implemented that ;) So the hook is simply a default Class>>#neoJsonMapping: which brings up the helper if no class-side mapping is defined. ----- Cheers, Sean -- View this message in context: http://forum.world.st/ANN-Little-NeoJSON-Helper-tp4756763p4756798.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

April 28, 2014

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

by Tudor Girba

Thank you, Marcus. Doru On Mon, Apr 28, 2014 at 4:39 PM, Marcus Denker <marcus.denker(a)inria.fr>wrote: > > 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 > > > -- www.tudorgirba.com "Every thing has its own flow"

April 28, 2014

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

by Ben Coman

April 28, 2014

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