August 2010 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Which options do we have to persist?

by GÃ¶ran Krampe

On 08/12/2010 06:56 PM, Guillermo Polito wrote: > I want to document this a bit and I don't know if there's something > written somewhere. > > I already know SqueakDBX, Magma, Omnibase. Is there something else? > What about ORMs? Glorp? Some other stuff off the top of my head from SqueakSource.com: - SCouchDB and CouchDB: Two clients for CouchDB. - TokyoTyrant: My binding for TokyoTyrant, possibly worlds fastest single machine key/value store. See: http://goran.krampe.se/blog/Squeak/TokyoTyrant.rdoc - CassandraClient: A binding for Cassandra using Thrift, don't know more. - SqueakSave: An ORM I think, Steph knows more. - SandstoneDB: Not sure, some kind of lightweight ORM I think. And there are tons more, just check "persistence" tag on SS. Also search the old Squeak Swiki for persistence. One thing I am coding on is a binding to Riak, will put it on SS as soon as it can "do anything". :) regards, GÃ¶ran

Aug. 12, 2010

Re: [Pharo-project] Which options do we have to persist?

by Norbert Hartl

On 12.08.2010, at 20:42, Adrian Lienhard wrote: > - Gemstone > - Image segments > - Reference streams > - Postgres driver (and I think also MySQL) > - SIXX > - CouchDB > - GOODS > - ...probably more, e.g., MongoDB, but its alpha > SandstoneDB http://onsmalltalk.com/sandstonedb-simple-activerecord-style-persistence-in… Norbert > I cannot recommend Omnibase. > > Adrian > > On Aug 12, 2010, at 18:56 , Guillermo Polito wrote: > >> I want to document this a bit and I don't know if there's something written >> somewhere. >> >> I already know SqueakDBX, Magma, Omnibase. Is there something else? >> What about ORMs? Glorp? >> >> If you can provide me also links, metacello configs, and what's the status >> of them for each version of pharo, it shoud be great! :D >> >> Thanks! >> Guille >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Aug. 12, 2010

Re: [Pharo-project] Which options do we have to persist?

by Adrian Lienhard

- Gemstone - Image segments - Reference streams - Postgres driver (and I think also MySQL) - SIXX - CouchDB - GOODS - ...probably more, e.g., MongoDB, but its alpha I cannot recommend Omnibase. Adrian On Aug 12, 2010, at 18:56 , Guillermo Polito wrote: > I want to document this a bit and I don't know if there's something written > somewhere. > > I already know SqueakDBX, Magma, Omnibase. Is there something else? > What about ORMs? Glorp? > > If you can provide me also links, metacello configs, and what's the status > of them for each version of pharo, it shoud be great! :D > > Thanks! > Guille > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Aug. 12, 2010

Re: [Pharo-project] Inter-image communication

by GÃ¶ran Krampe

On 08/11/2010 10:26 AM, StÃ©phane Ducasse wrote: > rst? > > RemoteSmalltalk? Yes, and there are multiple other packages too. A few other things that might be interesting in "inter image communication": - D-Bus. Bert and the guys made a rather ambitious plugin for libdbus and stuff above it. This is not interesting for Squeak2Squeak, but definitely interesting for cross language stuff. - Message Queues. There are tons of these today, like RabbitMQ, ActiveMQ etc etc. And there is an AMQP protocol implementation on SS, and yesterday I released a first shot at a STOMP implementation too! These message queues implement publish/subscribe models etc so they are different beasts, but IMHO possible more interesting than "straight RPC". - If you go for a transport level that is "non Smalltalk", like say a message queue above, then Tirade (also on SS) could work as a fast way to "serialize messages" through such a transport. When I get STOMP finished I will make a simple demo of that. Also, writing a forking Socket server is really simple in Squeak. The Blackfoot package on SS can act as a really simple and documented example of such a server. Also, if you want to play around with character/byte-streams between Squeak Processes (in one image) then the SharedStreams package is neat - in fact, I think it should be included in the "standard library", and probably also replace SharedQueue. regards, GÃ¶ran

Aug. 12, 2010

Re: [Pharo-project] Which options do we have to persist?

by Diogenes Moreira

GlorpDBX with MSSQL..too... well some times.. (in 32 bits works fine, but 64 bit so so) On Thu, Aug 12, 2010 at 3:27 PM, Esteban Lorenzano <estebanlm(a)gmail.com>wrote: > for ORM's, you have Glorp (who works with Postgresql), and GlorpDBX, who > works (for now), with: Postgresql, MySQL and Oracle. > > > On 2010-08-12 13:56:30 -0300, Guillermo Polito <guillermopolito(a)gmail.com> > said: > > >> >> I want to document this a bit and I don't know if there's something >> written >> somewhere. >> >> I already know SqueakDBX, Magma, Omnibase. Is there something else? >> What about ORMs? Glorp? >> >> If you can provide me also links, metacello configs, and what's the status >> of them for each version of pharo, it shoud be great! :D >> >> Thanks! >> Guille >> >> >> I want to document this a bit and I don't know if there's >> something= >> written somewhere. I already know SqueakDBX, Magma, Omnibase.=A0 >> Is= >> there something else? What about ORMs?=A0 Glorp? If you can >> prov= >> ide me also links, metacello configs, and what's the status of them >> for= >> each version of pharo, it shoud be great! :D >> Thanks! Guille >> >> >> >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Aug. 12, 2010

Re: [Pharo-project] Which options do we have to persist?

by Esteban Lorenzano

for ORM's, you have Glorp (who works with Postgresql), and GlorpDBX, who works (for now), with: Postgresql, MySQL and Oracle. On 2010-08-12 13:56:30 -0300, Guillermo Polito <guillermopolito(a)gmail.com> said: > > > I want to document this a bit and I don't know if there's something written > somewhere. > > I already know SqueakDBX, Magma, Omnibase. Is there something else? > What about ORMs? Glorp? > > If you can provide me also links, metacello configs, and what's the status > of them for each version of pharo, it shoud be great! :D > > Thanks! > Guille > > > I want to document this a bit and I don't know if there's something= > written somewhere. I already know SqueakDBX, Magma, Omnibase.=A0 Is= > there something else? What about ORMs?=A0 Glorp? If you can prov= > ide me also links, metacello configs, and what's the status of them for= > each version of pharo, it shoud be great! :D > Thanks! Guille > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Aug. 12, 2010

Re: [Pharo-project] Inter-image communication

by GÃ¶ran Krampe

On 08/12/2010 03:58 PM, Ralph Boland wrote: > Some time back I posted (to Squeak) the idea of doing development using > two images. One image would be your development image, i.e. the image > you would eventually release as your product. It would be a > restricted version of the > image you have in Squeak/Pharo now. > The other image would be your software development tool image, > roughly analogous to what the Eclipse development environment is. > The advantage of such a set up would be that changes to your development image > would not blow up your tool image. You could also leave out anything from your > development image you didn't actually need in you product such as > perhaps editors, debuggers, windows, etc. depending upon what software > your product actually needed. > I have no plans to actually try this anytime soon. > But I am wondering: > > Would RemoteSmalltalk be helpful in (be a foundation for) creating > such a utility? In fact, the most ambitious effort in this direction is the stuff Craig Latta did in Spoon. He created a "umbilical cord" on the VM level so he could do really transparent remote debugging etc. This was needed since he wanted to create a real minimal image, and he got down below 100kb, but that was probably very hard to do without these special "remote" tools. regards, GÃ¶ran

Aug. 12, 2010

Re: [Pharo-project] Cleaning morphic - Step 1 - About "Morphic-Ballon" and the Ballon category

by Mariano Martinez Peck

2010/8/12 Guillermo Polito <guillermopolito(a)gmail.com> > What's RFB? :D How can I download it? > It is a client and server Smalltalk implementation of the VNC protocol. Thus, you can deploy a Pharo image (suppose that it is even running seaside), in a headless mode, and with a VNC client you can connect and you "see" the world...thus, you can control and do whjatever you want in the deployed image. it is in http://source.lukas-renggli.ch/unsorted/ there is a conf http://forum.world.st/ANN-ConfigurationOfRFB-td1295400.html#a1295400 also read this: http://forum.world.st/Ann-RFB-VNC-fully-configurable-by-code-td1303613.html… what I recommend you is that you search in the archives of the mailing list: http://forum.world.st/Pharo-Smalltalk-f1294837.html cheers mariano > 2010/7/19 Miguel Enrique CobÃ¡ MartÃnez <miguel.coba(a)gmail.com> > > El lun, 19-07-2010 a las 15:58 -0300, Guillermo Polito escribiÃ³: >> > HAhah, thanks :). >> > >> > Anyway, my idea is not to remove those packages. I want to put them >> > in separate monticello packages, so we don't need have it in the core >> > if we don't use it. >> > >> > So, I download Seaside, Moose, and what else? >> >> Magma, RFB, Pier, Magritte. >> :) >> >> > >> > 2010/7/19 Mariano Martinez Peck <marianopeck(a)gmail.com> >> > Guille: one thing you can do before removing the code, is to >> > prepare an DEV image with Seaside, Moose and all those big >> > projects. So that when you search senders/references you can >> > do it also there. I don't mean that we shouldn't remove them >> > if they are used in those projects, but just to be aware. >> > >> > but for "coding" and commiting, yes, use latest PharoCore, not >> > dev. >> > >> > And yes, if you don't receive feedback, go ahead! >> > >> > Cheers >> > >> > Mariano >> > >> > 2010/7/19 Guillermo Polito <guillermopolito(a)gmail.com> >> > >> > Ok, I opened an Issue for this... >> > >> > http://code.google.com/p/pharo/issues/detail?id=2696 >> > >> > >> > >> > On Thu, Jul 15, 2010 at 8:18 PM, Guillermo Polito >> > <guillermopolito(a)gmail.com> wrote: >> > Hi! >> > >> > Does anyone know what the Ballon category and >> > its related morphs are for? Someone uses it? >> > Is it useful in the Core of pharo? >> > >> > Did Someone try previously to remove it and >> > failed? why? >> > >> > thanks in advance :) >> > Guille >> > >> > >> > >> > >> > _______________________________________________ >> > Pharo-project mailing list >> > Pharo-project(a)lists.gforge.inria.fr >> > >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > >> > >> > _______________________________________________ >> > Pharo-project mailing list >> > Pharo-project(a)lists.gforge.inria.fr >> > >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > >> > _______________________________________________ >> > Pharo-project mailing list >> > Pharo-project(a)lists.gforge.inria.fr >> > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> -- >> Miguel CobÃ¡ >> http://miguel.leugim.com.mx >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Aug. 12, 2010

Re: [Pharo-project] Cleaning morphic - Step 1 - About "Morphic-Ballon" and the Ballon category

by Guillermo Polito

What's RFB? :D How can I download it? 2010/7/19 Miguel Enrique CobÃ¡ MartÃnez <miguel.coba(a)gmail.com> > El lun, 19-07-2010 a las 15:58 -0300, Guillermo Polito escribiÃ³: > > HAhah, thanks :). > > > > Anyway, my idea is not to remove those packages. I want to put them > > in separate monticello packages, so we don't need have it in the core > > if we don't use it. > > > > So, I download Seaside, Moose, and what else? > > Magma, RFB, Pier, Magritte. > :) > > > > > 2010/7/19 Mariano Martinez Peck <marianopeck(a)gmail.com> > > Guille: one thing you can do before removing the code, is to > > prepare an DEV image with Seaside, Moose and all those big > > projects. So that when you search senders/references you can > > do it also there. I don't mean that we shouldn't remove them > > if they are used in those projects, but just to be aware. > > > > but for "coding" and commiting, yes, use latest PharoCore, not > > dev. > > > > And yes, if you don't receive feedback, go ahead! > > > > Cheers > > > > Mariano > > > > 2010/7/19 Guillermo Polito <guillermopolito(a)gmail.com> > > > > Ok, I opened an Issue for this... > > > > http://code.google.com/p/pharo/issues/detail?id=2696 > > > > > > > > On Thu, Jul 15, 2010 at 8:18 PM, Guillermo Polito > > <guillermopolito(a)gmail.com> wrote: > > Hi! > > > > Does anyone know what the Ballon category and > > its related morphs are for? Someone uses it? > > Is it useful in the Core of pharo? > > > > Did Someone try previously to remove it and > > failed? why? > > > > thanks in advance :) > > Guille > > > > > > > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > -- > Miguel CobÃ¡ > http://miguel.leugim.com.mx > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Aug. 12, 2010

Re: [Pharo-project] Working on Pharo 1.2

by Henrik Sperre Johansen

On 12.08.2010 18:23, James Foster wrote: > All, > > I'm having trouble finding 1.2. > > http://pharo-project.org/home contains the following: 'If you want to use all the new features and improvements that have been added to Pharo lately, and you don't mind living on the bleeding edge, download the current Pharo 1.2.' Clicking on the 'download' link takes me to http://pharo-project.org/pharo-download, but I can't find any place to download 1.2. There's a link at the bottom of the Download page, called "PharoCore images and other files", leading to the inria group, search 1.2 and you should find it. IIRC, it was impossible to reorder the groups, so it's quite far down. > I've tried enabling the update menu in a 1.1 image, but there seem to be no updates. Updates are only for each Pharo1.X version, none have been released for 1.0 or 1.1 as no issues have been considered critical enough. > I've briefly searched the archives for a thread on 'How to contribute to 1.2' but haven't found anything. > > I've been to http://www.squeaksource.com/PharoInbox.html, but don't see any instructions beyond 'just publish it here.' > From the community page, there is a link called "Pharo Google code project". On the google code page, "How to contribute" is listed as a Featured wiki page in the right column. > Where do I go to get the current (unstable) 1.2 build? What do I need to do to contribute (beyond adding to the PharoInbox)? Send mail? In addition to posting a SLICE (ie collection of modified monticello packages, with commit comment describing what it adresses)to the inbox, you'd need to create an issue on the google code tracker. Posting to this list that an issue is ready to be reviewed/integrated certainly does not hurt either. (especially if you can't change status to Fixed yourself) Cheers, Henry

Aug. 12, 2010