- Pharo-dev - lists.pharo.org

[Pharo-project] Portugese translation :)

by stephane ducasse

Hi guys A portuguese speaking person (Christian GuimarÃ£es) asks if it was possible to translated pharo by example. We will host the translations (as we are doing for the french, spanish ones) and give access to bern infrastructure. Now may be some other people want to join in this effort. Stef >> Hi Dr. Andrew >> >> First of all, congratulation for the excelent work with Pharo and the book "Pharo By Example". >> >> My name is Christian Guimaraes, I'm an electrical engineer with strong background in software development. Nowadays I work as consultant for Fujitsu (in Europe) and in many other projects. >> >> I've started my studies in Smalltalk, for my pleasure and I've interested in translate the book "Pharo By Example" to the portuguese (I'm brazilian). I saw that already have some thing in this sense. Who is the responsible? Maybe I could help him. >> >> Thanks. >> >> - Christian

Feb. 18, 2010

Re: [Pharo-project] databases

by Miguel Enrique CobÃ¡ Martinez

El jue, 18-02-2010 a las 16:51 +0100, Levente Uzonyi escribiÃ³: > On Wed, 17 Feb 2010, laurent laffont wrote: > > > Really great informations : > > ScenarioËËs > > > > In different situations, there are different storage needs > > > > 1. You are writing a small demonstration program to show your customers, > > and want to populate the system with some representative data. Add a class > > instance variable to store the instances, and simply save the image. > > 2. You have a small system with a few hundred/thousand objects, and are > > not dependent on external systems. A prevayler-like system like SandstoneDB > > might be a perfect fit. Each object save means a disk access, so scaling > > ends with disk speed. A few old versions of the data are kept around, so > > backing up or reverting is easy. If you want a readable representation, SIXX > > might help. > > 3. You have a legacy (relational) database, with extensive reporting > > written for it. Use an ORM. > > Relational databases are not legacy, they have features which "modern" > key-value stores don't (and won't). I don't think he is refering to RDBMS as legacy, as we know that they aren't. I think that he meant that when you have a fully populated database (legacy) and you are building a new seaside/pharo application to exploit that data, the best is to use an ORM for simple querys and direct querys for complex ones. > ORMs may ease the programmer's work, > but they tend to have bad runtime performance and can't use (all) the > features of todays RDBMSs. That is true but also the right thing, it isn't expected that an ORM standardize a way to backup a database, partition a table, replication, node management, user sessions and transaction monitoring, change index types and in general everything that is considered metadata or simply database administration. An ORM is for user stuff querys, insertions, deletion, etc. Cheers > > > Levente > > > 4. You have a complex and large object model that has to support changing > > the object model while developing. The solution is an OODB. Gemstone is the > > large and proven commercial offering. It has a free version for smaller > > databases (4GB data, 1 core, 1G ram), and has proven scalability to 500 > > machines. Magma is an open source OODB, seeing active development and > > growing more and more advanced functionality. > > > > > > > > Laurent Laffont > > > > > > On Wed, Feb 17, 2010 at 3:07 PM, laurent laffont > > <laurent.laffont(a)gmail.com>wrote: > > > >> No :) Thanks for the link ! > >> > >> Laurent Laffont > >> > >> > >> > >> On Wed, Feb 17, 2010 at 2:23 PM, Stephan Eggermont <stephan(a)stack.nl>wrote: > >> > >>> Hello Laurent, > >>> > >>> I assume you are aware of: > >>> > >>> http://www.seaside.st/documentation/persistence > >>> > >>> Stephan > >>> > >>> _______________________________________________ > >>> 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

Feb. 18, 2010

[Pharo-project] Pharo User Group?

by Alexandre Bergel

Stef, Few weeks ago you said you will meet some layers at inria to know whether something like ESUG may be set for Pharo. Do you have any news? I am just curious. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Feb. 18, 2010

Re: [Pharo-project] databases

by Levente Uzonyi

On Wed, 17 Feb 2010, laurent laffont wrote: > Really great informations : > ScenarioËËs > > In different situations, there are different storage needs > > 1. You are writing a small demonstration program to show your customers, > and want to populate the system with some representative data. Add a class > instance variable to store the instances, and simply save the image. > 2. You have a small system with a few hundred/thousand objects, and are > not dependent on external systems. A prevayler-like system like SandstoneDB > might be a perfect fit. Each object save means a disk access, so scaling > ends with disk speed. A few old versions of the data are kept around, so > backing up or reverting is easy. If you want a readable representation, SIXX > might help. > 3. You have a legacy (relational) database, with extensive reporting > written for it. Use an ORM. Relational databases are not legacy, they have features which "modern" key-value stores don't (and won't). ORMs may ease the programmer's work, but they tend to have bad runtime performance and can't use (all) the features of todays RDBMSs. Levente > 4. You have a complex and large object model that has to support changing > the object model while developing. The solution is an OODB. Gemstone is the > large and proven commercial offering. It has a free version for smaller > databases (4GB data, 1 core, 1G ram), and has proven scalability to 500 > machines. Magma is an open source OODB, seeing active development and > growing more and more advanced functionality. > > > > Laurent Laffont > > > On Wed, Feb 17, 2010 at 3:07 PM, laurent laffont > <laurent.laffont(a)gmail.com>wrote: > >> No :) Thanks for the link ! >> >> Laurent Laffont >> >> >> >> On Wed, Feb 17, 2010 at 2:23 PM, Stephan Eggermont <stephan(a)stack.nl>wrote: >> >>> Hello Laurent, >>> >>> I assume you are aware of: >>> >>> http://www.seaside.st/documentation/persistence >>> >>> Stephan >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >> >> >

Feb. 18, 2010

Re: [Pharo-project] databases

by StÃ©phane Ducasse

we are working on setting up a pier book so that you guys can structure this information in a nice way. On Feb 18, 2010, at 12:43 AM, csrabak(a)bol.com.br wrote: > All those interesting pieces of information about what works and what does not is very valuable. > > Is there a means of having a place in Pharo Wiki where we could publish and update this? > > -- > Cesar Rabak > > > Em 17/02/2010 13:05, GermÃ¡n Arduino < garduino(a)gmail.com > escreveu: > > > > 2010/2/17 Dave Woodward <davewoodward(a)promedmedical.net> > > > > > On 2/17/10 6:46 AM, GermÃ¡n Arduino wrote: > > > > 2010/2/17 laurent laffont <laurent.laffont(a)gmail.com> > > Hi, > > I would like to learn on Pharo + databases. I've seen there's several solutions in both object and relational databases. > - Which (open source) object database should I start with (most used) ? > > > > Magma is the option I select, but not tried yet on Pharo. > > > > > Magma 1.0v43 works on Pharo, > > > > Good to know. > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Feb. 18, 2010

[Pharo-project] [update 1.1] #11215

by Marcus Denker

11215 ----- Issue 1945: registration mechanism for the menu (2nd try) Issue 1989: fix #labelled: Issue 1974: remove #disableSubmorphFocusForHand: (part 2) -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

Feb. 18, 2010

Re: [Pharo-project] Fwd: [squeak-dev] Window resize

by StÃ©phane Ducasse

ok :) Stef On Feb 18, 2010, at 2:23 PM, Gary Chambers wrote: > I think Torsten meant the main Pharo host window... > > Regards, Gary > ----- Original Message ----- > From: StÃ©phane Ducasse > To: Pharo-project Development > Sent: Thursday, February 18, 2010 12:36 PM > Subject: [Pharo-project] Fwd: [squeak-dev] Window resize > > > > Begin forwarded message: > >> From: pharo-project-owner(a)lists.gforge.inria.fr >> Date: February 18, 2010 1:33:02 PM GMT+01:00 >> To: stephane.ducasse(a)gmail.com >> Subject: Re: [squeak-dev] Window resize >> >> You are not allowed to post to this mailing list, and your message has >> been automatically rejected. If you think that your messages are >> being rejected in error, contact the mailing list owner at >> pharo-project-owner(a)lists.gforge.inria.fr. >> >> >> From: stephane ducasse <stephane.ducasse(a)gmail.com> >> Date: February 18, 2010 1:32:56 PM GMT+01:00 >> To: Pharo-project Development <pharo-project(a)lists.gforge.inria.fr> >> Subject: Re: [squeak-dev] Window resize >> >> >> I thought that events has been added in 1.1. >> Which version of pharo are you referring to. >> Alex I thought that we merged your changes >> Issue 1785: Window event notification >> but I cannot find them >> Probably not integrated. I checked and the code is still in PharoTaskForces. >> Alex can you have a look because your package contains reference to PackageNode... >> >> >> Stef >> >> On Feb 18, 2010, at 12:39 PM, Torsten Bergmann wrote: >> >>> Is there an event when the Squeak window is resized, >>> so one can react and resize morphs accordingly? >>> >>> Thx >>> T. >>> -- >>> NEU: Mit GMX DSL Ã¼ber 1000,- Â¿ sparen! >>> http://portal.gmx.net/de/go/dsl02 >>> >> >> >> >> > > > > _______________________________________________ > 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

Feb. 18, 2010

Re: [Pharo-project] So your working on a cool project andPharocrashes

by Gary Chambers

Attached (after Pharofication (was for Squeak 3.9))... Also has an menu option to remove items not matching an author, not sure how useful that is in pratice. Regards, Gary ----- Original Message ----- From: "Fernando olivero" <oliverof(a)lu.unisi.ch> To: <Pharo-project(a)lists.gforge.inria.fr> Sent: Thursday, February 18, 2010 12:33 PM Subject: Re: [Pharo-project] So your working on a cool project andPharocrashes yes please! Cuis has class definition change reification, and i found it very useful to be able to do "remove DoIts" , when programming in CUIS. On Feb 18, 2010, at 1:18 PM, Gary Chambers wrote: > We have a few simple enhancements for ChangeList/ChangeRecord that > identifies class defs, method removals etc. > That way one can "remove doits" while keeping class definitions etc. > > I can post a changeset if anyone is interested. > > Regards, Gary > > ----- Original Message ----- > From: "StÃ©phane Ducasse" <stephane.ducasse(a)inria.fr> > To: <Pharo-project(a)lists.gforge.inria.fr> > Sent: Thursday, February 18, 2010 10:58 AM > Subject: Re: [Pharo-project] So your working on a cool project and > Pharocrashes > > >> I imagine that you can also recoever from another image. >> At least in VW we could do that. >> Nathan the first thing to do is to copy your image/changes because each >> time to receover you add >> new info to you changes. >> >> So if you screw it up now. Go back to before the first time you crashed >> because all your changes are >> still there. This is juts a matter of identifying them. Pay attention >> that >> we do not have classDefinition >> as in Cuis and VW so doit for class definition should be replayed too. >> >> finally did you save your code with monticello? >> Because this is the best way, publish often. >> >> Stef >> >> >> >> On Feb 18, 2010, at 7:25 AM, Alexandre Bergel wrote: >> >>> The change file needs to have the same name than the image to have it >>> listed when you do a recover lost changes. >>> Else, you can simply edit the .changes using any (robust) text editor. >>> Cut and paste what you feel relevant into a new file that you name >>> yourchanges.cs >>> You then have created a changeset file, which can be easily loaded >>> with a drag and drop from your OS desktop to the Pharo image. >>> Alternatively, you can use the file loader. >>> >>> Hope it helps. >>> >>> Cheers, >>> Alexandre >>> >>> On 18 Feb 2010, at 03:13, Nathan Tuttle wrote: >>> >>>> One thing. It looks like there is a changes file that has more up to >>>> date information. How do I pull this in? >>>> >>>> On Wed, Feb 17, 2010 at 11:44 PM, Alexandre Bergel <alexandre(a)bergel.eu >>>>> wrote: >>>> I also had the very same feeling the first times I used the "recover >>>> lost changes" option. Now that I gained experience, I live >>>> comfortably with it. >>>> >>>> Cheers, >>>> Alexandre >>>> >>>> On 18 Feb 2010, at 02:37, Nathan Tuttle wrote: >>>> >>>>> actually, to tell the truth I figured out how to get most of my >>>>> methods back. But not the right versions. I wonder if I can back out >>>>> the changes and try to select the ones that I do need, but there are >>>>> soo many. >>>>> >>>>> It does throw an error when I select multiple changesets. When I use >>>>> the "remove do it" that helps the most. >>>>> >>>>> its just such a mess right now >>>>> >>>>> On Wed, Feb 17, 2010 at 11:23 PM, Alexandre Bergel >>>>> <alexandre(a)bergel.eu >>>>>> wrote: >>>>> Hi Nathan, >>>>> >>>>>> Is there any way to do a recovery besides the Recover Lost Changes >>>>>> option that doesn't seem to work? >>>>> >>>>> What do you mean by "doesn't seem to work"? I have always been happy >>>>> with it. >>>>> Does it raise an error? >>>>> >>>>>> It seems the change log that was left behind has some promising >>>>>> things in it. >>>>> >>>>> >>>>> You can directly inspect the .changes file next to your image. >>>>> >>>>> Cheers, >>>>> Alexandre >>>>> -- >>>>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>>>> Alexandre Bergel http://www.bergel.eu >>>>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> 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 >>>> >>>> -- >>>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>>> Alexandre Bergel http://www.bergel.eu >>>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>>> >>>> >>>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> 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 >>> >>> -- >>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>> Alexandre Bergel http://www.bergel.eu >>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>> >>> >>> >>> >>> >>> >>> _______________________________________________ >>> 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 _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Feb. 18, 2010

Re: [Pharo-project] Fwd: [squeak-dev] Window resize

by Gary Chambers

I think Torsten meant the main Pharo host window... Regards, Gary ----- Original Message ----- From: StÃ©phane Ducasse To: Pharo-project Development Sent: Thursday, February 18, 2010 12:36 PM Subject: [Pharo-project] Fwd: [squeak-dev] Window resize Begin forwarded message: From: pharo-project-owner(a)lists.gforge.inria.fr Date: February 18, 2010 1:33:02 PM GMT+01:00 To: stephane.ducasse(a)gmail.com Subject: Re: [squeak-dev] Window resize You are not allowed to post to this mailing list, and your message has been automatically rejected. If you think that your messages are being rejected in error, contact the mailing list owner at pharo-project-owner(a)lists.gforge.inria.fr. From: stephane ducasse <stephane.ducasse(a)gmail.com> Date: February 18, 2010 1:32:56 PM GMT+01:00 To: Pharo-project Development <pharo-project(a)lists.gforge.inria.fr> Subject: Re: [squeak-dev] Window resize I thought that events has been added in 1.1. Which version of pharo are you referring to. Alex I thought that we merged your changes Issue 1785: Window event notification but I cannot find them Probably not integrated. I checked and the code is still in PharoTaskForces. Alex can you have a look because your package contains reference to PackageNode... Stef On Feb 18, 2010, at 12:39 PM, Torsten Bergmann wrote: Is there an event when the Squeak window is resized, so one can react and resize morphs accordingly? Thx T. -- NEU: Mit GMX DSL Ã¼ber 1000,- Â¿ sparen! http://portal.gmx.net/de/go/dsl02 ------------------------------------------------------------------------------ _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Feb. 18, 2010

[Pharo-project] cull: protocol

by Henrik Johansen

Refactoring the AXAnnouncements abit so there's no separate classes for 0-, 1-, and 2-arg blocks, and really missing these methods from VisualWorks... cull: is equivalent to value: protocol except they accept block with N or less blockArgs Yes, I know valueWithEnoughArguments:/valueWithPossibleArgs: provide the same functionality, but the code looks much less nice using them, you end up constructing arrays needlessly etc. Look at the senders of valueWithPossibleArgs: for examples, very few of those actually need the ability to accept blocks with more arguments than they provide, and would also look nicer with cull:. Would anyone object strongly to adding the cull:, cull:cull: methods in core instead of putting them as extension methods? Cheers, Henry

Feb. 18, 2010