February 2012 - Pharo-dev - lists.pharo.org

[Pharo-project] SmalltalkHub news (was: It would be me first)

by Nicolas Petton

Hi all! As GÃ¶ran said, he recently joined our forces on SmalltalkHub. We're used to working together and he has great Riak knowledge. He's mainly working on the Riak-backed Monticello repository. Currently, timelines, users, projects, settings, user dashboard and profile are ported for Riak. As soon as the Riak Monticello repository will be ready, we'll release and put it online. That means taht the issue tracker and project statistics probably won't be there at first, but as Stef said to me several times already, release release early, release often, it doesn't have to be perfect from the start :) So I'm gonna listen to Stef, and make it publicly available. On 28/02/12 10:13, GÃ¶ran Krampe wrote: > The latest stack looks very promising though - and the reason I can > describe it is because I am trying to help out a bit with it - though > haven't had much time yet. > > The client is a full Amber app built with Bootstrap 2 from Twitter. It > is very nice looking and responsive. It communicates with the backend > using plain jQuery REST. > > The server side is built with Seaside-REST which then uses a domain > model described with Magritte 3 (Nicolas just switched) which is > persisted using RiakDocument + Phriak for persistency. An interesting > twist here is that Magritte is being used to produce the JSON > RiakDocuments to store. > > End result? A very strong and interesting architecture and the > performance looks outstanding so far. Riak also buys us really strong > robustness since it has redundancy built in. I couldn't have said it better, thanks GÃ¶ran :) Cheers, Nico -- Nicolas Petton http://nicolas-petton.fr

Feb. 28, 2012

Re: [Pharo-project] It would be me first

by Nicolas Petton

On 28/02/12 14:05, Igor Stasenko wrote: > On 28 February 2012 10:38, Norbert Hartl<norbert(a)hartl.name> wrote: >> >> Am 28.02.2012 um 10:13 schrieb GÃ¶ran Krampe: >> >>> Hi folks! >>> >>> Nicolas will of course reply - I think he was planning to write a post the other day but might have forgotten - but I can chip in some info: >>> >>> SmalltalkHub has gone through some technical evolution which has taken some time. Especially various persistence schemes were tested and most of them ended up problematic, Nicolas tested a LOT of variations I think. >>> >>> The latest stack looks very promising though - and the reason I can describe it is because I am trying to help out a bit with it - though haven't had much time yet. >>> >>> The client is a full Amber app built with Bootstrap 2 from Twitter. It is very nice looking and responsive. It communicates with the backend using plain jQuery REST. >>> >>> The server side is built with Seaside-REST which then uses a domain model described with Magritte 3 (Nicolas just switched) which is persisted using RiakDocument + Phriak for persistency. An interesting twist here is that Magritte is being used to produce the JSON RiakDocuments to store. >>> >>> End result? A very strong and interesting architecture and the performance looks outstanding so far. Riak also buys us really strong robustness since it has redundancy built in. >>> >>> All questions regarding availability, time schedule etc I will leave for Nicolas to answer. :) >>> >> Sounds good. I work with Seaside-Rest and Magritte3 on a daily base. This time with MongoDB using MongoTalk. So I'm quite confident that the choice of the stack is superb :) I decided to use MongoDB because it did not want to be content agnostic. My client approach however is the opposite using seaside with jquery extension. Using amber with Rest style access is surely the better approach for a site like SmallHub. >> What puzzles me is what RiakDocument is doing in this mix. Is it published somewhere? >> > i think it just a json with data, which riak server can swallow :) Exactly, it's a tiny layer on top of Riak that uses Magritte descriptions to produce JSON, validates it, and makes link walking, etc easier. Cheers, Nico > >> Norbert >> >> >> > > > -- Nicolas Petton http://nicolas-petton.fr

Feb. 28, 2012

[Pharo-project] shorten petitparser expressions

by Igor Stasenko

Why i need to put #asParser everywhere? $a asParser / $b asParser / #foo asParser a proper implementation of #/ makes the above to just: $a asParser / $b / #foo which is much more cleaner and convenient. Or, is there a reason to not send #asParser to every argument where parser expected? -- Best regards, Igor Stasenko.

Feb. 28, 2012