- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Small mini howto on moving a project to SmalltalkHub

by GÃ¶ran Krampe

On 12/18/2012 02:49 PM, Mariano Martinez Peck wrote: > Thanks Goran. > Something related I wrote several months ago: > http://marianopeck.wordpress.com/2011/11/08/migrating-projects-to-squeaksou… Ah! Nice! :) Probably didn't google that one... Now... things are getting quite confused - for example, where is ConfigurationOfXMLSupport these days? I mean, the *canonical* version that I should use for Pharo 1.4? It doesn't seem clear to me - SS seems fresher than SS3 for this package... Which is why I think it is VERY important to put a due notice on the project description if it HAS MOVED :) regards, GÃ¶ran

Dec. 18, 2012

Re: [Pharo-project] Small mini howto on moving a project to SmalltalkHub

by Mariano Martinez Peck

Thanks Goran. Something related I wrote several months ago: http://marianopeck.wordpress.com/2011/11/08/migrating-projects-to-squeaksou… On Tue, Dec 18, 2012 at 8:28 AM, GÃ¶ran Krampe <goran(a)krampe.se> wrote: > Hey! > > I just moved one of my projects from Squeaksource.com to SmalltalkHub.com > and realized others may want to know how to do this: > > 1. Create new corresponding Project on Smalltalkhub. Using the same name > and tags is probably smart. Also, I added a BOLD little remark with a date > claiming this is now the PRIMARY repository for Phriak, if people wonder. I > also added the following on top of the project on Squeaksource (you can > still edit stuff): > > NOTE: This project has been moved to <a href="http://smalltalkhub.com/* > *#!/~gokr/Phriak <http://smalltalkhub.com/#!/~gokr/Phriak>">http://** > smalltalkhub.com/#!/~gokr/**Phriak<http://smalltalkhub.com/#!/~gokr/Phriak> > </a>!!! > > > 2. Add contributors (I just looked through my commits to figure out who > they all are) by going to "Settings" (or press "Edit info" button) on the > Project. World writeable is not available. I also sent an email to my > contributors mentioning this move :) > > 3. Copy over all old snapshots, using code like this (thanks Nicolas, > although it should be "fetch" not "pull" and one needs "/main" at end of > hub URL): > > Gofer it > squeaksource: 'Phriak'; > package: 'Phriak'; > package: 'ConfigurationOfPhriak'; > fetch. > Gofer it > url: 'http://smalltalkhub.com/mc/**gokr/Phriak/main<http://smalltalkhub.com/mc/gokr/Phriak/main> > ' > username: 'gokr' password: 'secret'; > package: 'Phriak'; > package: 'ConfigurationOfPhriak'; > push. > > > ...and that's it I think! > > regards, GÃ¶ran > > -- Mariano http://marianopeck.wordpress.com

Dec. 18, 2012

Re: [Pharo-project] Feature requests and a tip for SmalltalkHub

by StÃ©phane Ducasse

Read the gofer chapter :) Stef

Dec. 18, 2012

Re: [Pharo-project] Persistence Options

by Norbert Hartl

Am 17.12.2012 um 19:08 schrieb Torsten Bergmann <astares(a)gmx.de>: > Persisting data is crucial for any application and there > are many ways to do it. Be it RDBMS, NoSQL stuff or in-image > persistency. There are many pre-built solutions: Gemstone, OpenDBX, SandstoneDB, Mongo, ... > > From time to time I ask the question here on the list > to see how it evolves and what people actually use in > their Pharo applications: > > 1. What persistence option do we currently have I like to add plain fuel. I store e.g. configurations with it as these change rarely. For reliability I applied a sequence file to it. Meaning I write files with .fl.1, .fl.2, etc. and a file seq containing the last written number extension. The mechanic is to first write the fuel file and then overwrite the seq file with the actual sequence number (if a write fails the seq file isn't changed). Reads are reading first the seq file and then the fuel file. > 2. What persistence is used in your Pharo application today GemStone, MongoTalk (maybe soon it will be voyage, too), Fuel, Sixx. And in testing phase riak (no phriak, yet). > 3. Which persistence solution you want to use/would you > like to see in Pharo's future A decent implementation of LOOM. I think as long as there are different types of memory (main memory, disc storage,..) this is something nice to have. > 4. What would you recommend. > Reify object references :) Norbert

Dec. 18, 2012

[Pharo-project] Small mini howto on moving a project to SmalltalkHub

by GÃ¶ran Krampe

Hey! I just moved one of my projects from Squeaksource.com to SmalltalkHub.com and realized others may want to know how to do this: 1. Create new corresponding Project on Smalltalkhub. Using the same name and tags is probably smart. Also, I added a BOLD little remark with a date claiming this is now the PRIMARY repository for Phriak, if people wonder. I also added the following on top of the project on Squeaksource (you can still edit stuff): NOTE: This project has been moved to <a href="http://smalltalkhub.com/#!/~gokr/Phriak">http://smalltalkhub.com/#!/~gokr/Phriak</a>!!! 2. Add contributors (I just looked through my commits to figure out who they all are) by going to "Settings" (or press "Edit info" button) on the Project. World writeable is not available. I also sent an email to my contributors mentioning this move :) 3. Copy over all old snapshots, using code like this (thanks Nicolas, although it should be "fetch" not "pull" and one needs "/main" at end of hub URL): Gofer it squeaksource: 'Phriak'; package: 'Phriak'; package: 'ConfigurationOfPhriak'; fetch. Gofer it url: 'http://smalltalkhub.com/mc/gokr/Phriak/main' username: 'gokr' password: 'secret'; package: 'Phriak'; package: 'ConfigurationOfPhriak'; push. ...and that's it I think! regards, GÃ¶ran

Dec. 18, 2012

Re: [Pharo-project] Persistence Options

by StÃ©phane Ducasse

tx goran for the list! Stef On Dec 18, 2012, at 9:35 AM, GÃ¶ran Krampe wrote: > Hey! > > On 12/17/2012 07:08 PM, Torsten Bergmann wrote: >> Persisting data is crucial for any application and there >> are many ways to do it. Be it RDBMS, NoSQL stuff or in-image >> persistency. There are many pre-built solutions: Gemstone, OpenDBX, SandstoneDB, Mongo, ... >> >>> From time to time I ask the question here on the list >> to see how it evolves and what people actually use in >> their Pharo applications: >> >> 1. What persistence option do we currently have >> 2. What persistence is used in your Pharo application today >> 3. Which persistence solution you want to use/would you >> like to see in Pharo's future >> 4. What would you recommend. > > I can give some light on a few options that I have been involved in: > > TokyoTyrant > =========== > The "binding" I wrote hasn't been touched since I wrote it, but it is binary over SocketStream and VERY fast. There is now a new similar database called KyotoTycoon from the same author that he recommends as superior. Some differences: > > http://stackoverflow.com/questions/4178414/what-is-the-difference-between-t… > > I am not using nor maintaining this library anymore though. Still the raw speed is amazing and if that is what you want then this one is hard to beat. > > NOTE: Not sure how it operates under Pharo but since it runs on top of SocketStream I suspect it just works. If someone tries it out, let me know. > > > Phriak > ====== > This is a binding to Riak, perhaps the most insanely cool NoSQL database IMHO. Yeah, MongoDB is also very nice, but some aspects of Riak really makes me comfy and warm inside. > > The binding was started by Runar Jordahl called "EpigentRiakInterface", then I did a friendly fork and improved it even more, and then Nicolas Petton joined and improved it LOTS more, and now lately Paul De Bruicker has also joined with commits. > > Phriak is intentionally focused on Pharo and uses the Zinc components to implement the API which is HTTP based. Riak has protocol buffers too, but we haven't looked at that. > > This binding is maintained, pretty complete and very easy to use. Riak is also extremely easy to install. > > > Oak > === > This is a not so well known little side project from Nicolas Petton that I also am messing around with now. Oak is an "OODBish layer" that first was written abstractly to work on top of Riak, MongoDB etc. Now we are refocusing it on Riak only, possibly keeping optional Memcache support. > > Oak uses two other very nice new technologies in Pharo: Fuel and Ghost. Fuel is well known, very good serialization library basically. Ghost is a new small library for making well behaving proxies, using a smarter approach than the old "subclass ProtoObject and implement #doesNotUnderstand:". > > Net result is a semi transparent OODB which stores objects as Fuel blobs in Riak with UUIDs as keys. The auto faulting is done using Ghost proxies (so parts of your domain model are loaded "on demand" when you send messages to them). Oak is not super automagic like Magma - it doesn't do GC for example. But it is quite fast, small codebase and since it has a very simple model you can use other aspects of Riak through Phriak on the side. > > Oak is live and kicking and we are improving it by the day. So consider it a very interesting alpha, but still, small and simple codebase so you can use it already if you are not afraid to get your hands dirty. > > > > regards, GÃ¶ran >

Dec. 18, 2012

Re: [Pharo-project] Feature requests and a tip for SmalltalkHub

by GÃ¶ran Krampe

On 12/18/2012 11:17 AM, Nicolas Petton wrote: > > GÃ¶ran Krampe <goran(a)krampe.se> writes: > >> Hey! >> >> On 12/18/2012 10:55 AM, Nicolas Petton wrote:[SNIP of nice answers] >> >> PS. Yeah, I might check if I can help out with this... >> > >> > Sure. I'll be planning a release with Stef today, maybe we could talk on >> > IRC if you're available :) >> >> Sure, I am there. And oh, one more question that others may be >> interested in: >> >> - Is there a resonably simple way of copying over all snapshots in a >> project on say SS to StHub? >> >> Ehm, of course there is - but do you happen to have such a snippet? >> Otherwise I figure it out :) > > Have you tried using Gofer? > > Gofer it > squeaksource: 'foo'; > package: 'Foo-Bar'; > package: 'Foo-Baz'; > pull. > > Gofer it > url: 'http://smalltalkhub.com/mc/Me/Foo' username: 'me' password: > 'blah'; > package: 'Foo-Bar'; > package: 'Foo-Baz; > push. Great, thanks! Perhaps there are others out there wondering the same :) regards, GÃ¶ran

Dec. 18, 2012

Re: [Pharo-project] is the date of 8th of February good for a sprint

by StÃ©phane Ducasse

We could now I will not be present that week. On Dec 17, 2012, at 11:02 AM, Stephan Eggermont wrote: > Hi Stef, > > 2-3 Februari is FOSDEM, with a smalltalk devroom on sunday. > (I would welcome ideas to present something there, btw) > 1 or 4 would allow me to combine the trip. > > Cheers, > Stephan Eggermont >

Dec. 18, 2012

Re: [Pharo-project] Feature requests and a tip for SmalltalkHub

by Nicolas Petton

GÃ¶ran Krampe <goran(a)krampe.se> writes: > Hey! > > On 12/18/2012 10:55 AM, Nicolas Petton wrote:[SNIP of nice answers] > >> PS. Yeah, I might check if I can help out with this... > > > > Sure. I'll be planning a release with Stef today, maybe we could talk on > > IRC if you're available :) > > Sure, I am there. And oh, one more question that others may be > interested in: > > - Is there a resonably simple way of copying over all snapshots in a > project on say SS to StHub? > > Ehm, of course there is - but do you happen to have such a snippet? > Otherwise I figure it out :) Have you tried using Gofer? Gofer it squeaksource: 'foo'; package: 'Foo-Bar'; package: 'Foo-Baz'; pull. Gofer it url: 'http://smalltalkhub.com/mc/Me/Foo' username: 'me' password: 'blah'; package: 'Foo-Bar'; package: 'Foo-Baz; push. Cheers, Nico

Dec. 18, 2012

Re: [Pharo-project] Feature requests and a tip for SmalltalkHub

by GÃ¶ran Krampe

Hey! On 12/18/2012 10:55 AM, Nicolas Petton wrote:[SNIP of nice answers] >> PS. Yeah, I might check if I can help out with this... > > Sure. I'll be planning a release with Stef today, maybe we could talk on > IRC if you're available :) Sure, I am there. And oh, one more question that others may be interested in: - Is there a resonably simple way of copying over all snapshots in a project on say SS to StHub? Ehm, of course there is - but do you happen to have such a snippet? Otherwise I figure it out :) regards, GÃ¶ran

Dec. 18, 2012