June 2011 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] [PBE-Spanish] Status update 2011-06-21

by Clara Allende

LOL :D now I understand what Guille Polito just said to me :) I'll be glad to help ^^ just let me know what has to be done :) 2011/6/22 Mariano Martinez Peck <marianopeck(a)gmail.com> > With that surename sure you can help!!! ;) > > I cc'ed Nicolas Paez, in charge of the translation.... > > best regards, > > mariano > > > On Wed, Jun 22, 2011 at 8:10 PM, Clara Allende <clari.allende(a)gmail.com>wrote: > >> I would like to help with the translation if I can :) and if you wish :O >> >> >> 2011/6/21 Diogenes Moreira <diogenes.moreira(a)gmail.com> >> >>> Thank you very muchhhhhhhh. for your efforts >>> >>> D >>> (and the english wrong readers ) >>> >>> >>> On Tue, Jun 21, 2011 at 8:52 PM, Nicolas Paez <nicopaez(a)gmail.com>wrote: >>> >>>> ** >>>> Hello everyone, >>>> >>>> Here is the weekly update of the Spanish translation of Pharo By Example >>>> book. >>>> >>>> *Summary* >>>> >>>> - Just 4 charpters remaining to complete the rough translation. >>>> - During this week we will focus on completing the translation of >>>> the remaining chapters and on fixing the compilation errors we are getting. >>>> - We have also started to define the revision process. >>>> - By end of June we will publish a new drop with the completed >>>> chapters. >>>> >>>> *Chapters drill down* >>>> >>>> Chapter 01: 80% >>>> Chapter 02: completed, but not published yet and with compilation errors >>>> Chapter 03: completed, already published >>>> Chapter 04: completed, already published >>>> Chapter 05: completed, but not published yet and with compilation errors >>>> Chapter 06: 21% >>>> Chapter 07: completed, and with compilation errors >>>> Chapter 08: completed, and with compilation errors >>>> Chapter 09: completed, and with compilation errors >>>> Chapter 10: just started >>>> Chapter 11: completed, already published >>>> Chapter 12: 52% >>>> Chapter 13: completed, and with compilation errors >>>> Chapter 14: completed >>>> >>>> Regards, >>>> NicoPaez >>>> http://nicopaez.wordpress.com >>>> >>> >>> >> > > > -- > Mariano > http://marianopeck.wordpress.com > >

June 22, 2011

Re: [Pharo-project] [PBE-Spanish] Status update 2011-06-21

by Mariano Martinez Peck

With that surename sure you can help!!! ;) I cc'ed Nicolas Paez, in charge of the translation.... best regards, mariano On Wed, Jun 22, 2011 at 8:10 PM, Clara Allende <clari.allende(a)gmail.com>wrote: > I would like to help with the translation if I can :) and if you wish :O > > > 2011/6/21 Diogenes Moreira <diogenes.moreira(a)gmail.com> > >> Thank you very muchhhhhhhh. for your efforts >> >> D >> (and the english wrong readers ) >> >> >> On Tue, Jun 21, 2011 at 8:52 PM, Nicolas Paez <nicopaez(a)gmail.com> wrote: >> >>> ** >>> Hello everyone, >>> >>> Here is the weekly update of the Spanish translation of Pharo By Example >>> book. >>> >>> *Summary* >>> >>> - Just 4 charpters remaining to complete the rough translation. >>> - During this week we will focus on completing the translation of the >>> remaining chapters and on fixing the compilation errors we are getting. >>> - We have also started to define the revision process. >>> - By end of June we will publish a new drop with the completed >>> chapters. >>> >>> *Chapters drill down* >>> >>> Chapter 01: 80% >>> Chapter 02: completed, but not published yet and with compilation errors >>> Chapter 03: completed, already published >>> Chapter 04: completed, already published >>> Chapter 05: completed, but not published yet and with compilation errors >>> Chapter 06: 21% >>> Chapter 07: completed, and with compilation errors >>> Chapter 08: completed, and with compilation errors >>> Chapter 09: completed, and with compilation errors >>> Chapter 10: just started >>> Chapter 11: completed, already published >>> Chapter 12: 52% >>> Chapter 13: completed, and with compilation errors >>> Chapter 14: completed >>> >>> Regards, >>> NicoPaez >>> http://nicopaez.wordpress.com >>> >> >> > -- Mariano http://marianopeck.wordpress.com

June 22, 2011

Re: [Pharo-project] [PBE-Spanish] Status update 2011-06-21

by Clara Allende

I would like to help with the translation if I can :) and if you wish :O 2011/6/21 Diogenes Moreira <diogenes.moreira(a)gmail.com> > Thank you very muchhhhhhhh. for your efforts > > D > (and the english wrong readers ) > > > On Tue, Jun 21, 2011 at 8:52 PM, Nicolas Paez <nicopaez(a)gmail.com> wrote: > >> ** >> Hello everyone, >> >> Here is the weekly update of the Spanish translation of Pharo By Example >> book. >> >> *Summary* >> >> - Just 4 charpters remaining to complete the rough translation. >> - During this week we will focus on completing the translation of the >> remaining chapters and on fixing the compilation errors we are getting. >> - We have also started to define the revision process. >> - By end of June we will publish a new drop with the completed >> chapters. >> >> *Chapters drill down* >> >> Chapter 01: 80% >> Chapter 02: completed, but not published yet and with compilation errors >> Chapter 03: completed, already published >> Chapter 04: completed, already published >> Chapter 05: completed, but not published yet and with compilation errors >> Chapter 06: 21% >> Chapter 07: completed, and with compilation errors >> Chapter 08: completed, and with compilation errors >> Chapter 09: completed, and with compilation errors >> Chapter 10: just started >> Chapter 11: completed, already published >> Chapter 12: 52% >> Chapter 13: completed, and with compilation errors >> Chapter 14: completed >> >> Regards, >> NicoPaez >> http://nicopaez.wordpress.com >> > >

June 22, 2011

Re: [Pharo-project] Merge tool. No way to cherry pick the changes?

by Igor Stasenko

On 22 June 2011 20:00, Igor Stasenko <siguctua(a)gmail.com> wrote: > On 22 June 2011 17:43, Gary Chambers <gazzaguru2(a)btinternet.com> wrote: >> Perhaps the "non-applicable" could be streamlined. >> I.e., "keep current version" = not applicable. >> > yes, could be.. > but that logic are only for conflics.. and i didn't wanted to mess > with it because its a lot more work. btw, Stephane, this is a good topic for dealing with it on friday, if you don't have anything else in mind. > > Because strangely , instead of using field to indicate a conflict (in > MCPatchOperation record) it does something strange and overly > complicated > (MCConflict). > > So, then each entry could contain > 'isApplicable' > and > 'isConflicting' > > and once user resolves the conflict, the isConflicting should be set to false, > while isApplicable are uniformly to indicate which version to use > (current or incoming one), when merging. > > >> No need for the extra menu item then. >> >> Regards, Gary >> >> ----- Original Message ----- From: "Igor Stasenko" <siguctua(a)gmail.com> >> To: <Pharo-project(a)lists.gforge.inria.fr> >> Sent: Wednesday, June 22, 2011 3:40 PM >> Subject: Re: [Pharo-project] Merge tool. No way to cherry pick the changes? >> >> >>> Here the code >>> http://code.google.com/p/pharo/issues/detail?id=4439 >>> >>> please tell me if it works for you. >>> I tested on simple merge and it works fine (the changes which i marked >>> as not applicable are not loaded). >>> >>> -- >>> Best regards, >>> Igor Stasenko AKA sig. >>> >> >> > > > > -- > Best regards, > Igor Stasenko AKA sig. > -- Best regards, Igor Stasenko AKA sig.

June 22, 2011

Re: [Pharo-project] Merge tool. No way to cherry pick the changes?

by Igor Stasenko

On 22 June 2011 17:43, Gary Chambers <gazzaguru2(a)btinternet.com> wrote: > Perhaps the "non-applicable" could be streamlined. > I.e., "keep current version" = not applicable. > yes, could be.. but that logic are only for conflics.. and i didn't wanted to mess with it because its a lot more work. Because strangely , instead of using field to indicate a conflict (in MCPatchOperation record) it does something strange and overly complicated (MCConflict). So, then each entry could contain 'isApplicable' and 'isConflicting' and once user resolves the conflict, the isConflicting should be set to false, while isApplicable are uniformly to indicate which version to use (current or incoming one), when merging. > No need for the extra menu item then. > > Regards, Gary > > ----- Original Message ----- From: "Igor Stasenko" <siguctua(a)gmail.com> > To: <Pharo-project(a)lists.gforge.inria.fr> > Sent: Wednesday, June 22, 2011 3:40 PM > Subject: Re: [Pharo-project] Merge tool. No way to cherry pick the changes? > > >> Here the code >> http://code.google.com/p/pharo/issues/detail?id=4439 >> >> please tell me if it works for you. >> I tested on simple merge and it works fine (the changes which i marked >> as not applicable are not loaded). >> >> -- >> Best regards, >> Igor Stasenko AKA sig. >> > > -- Best regards, Igor Stasenko AKA sig.

June 22, 2011

Re: [Pharo-project] Fwd: [Seaside] Comparison of Aida/Web, Seaside and Iliad web frameworks

by Schwab,Wilhelm K

Referring to the thread on the Seaside list, the objections over some bias in the original comparison are well taken. One thing I was hoping to see was a rebuttal showing how easy it is to authenticate users; I have hacked such things into systems, but I would really like to see turn key (or nearly so) ways to have app-specific ("home grown"), LDAP, and Shibboleth based authentication/authorization. One can always dream :) As powerful as Seaside is overall, it **appears** to be lacking in this area - or maybe I simply have more to learn. Re the condensed comparision graphic, "one window" is both a strength and a weakness. While I have never particularly enjoyed using it, VW certainly has its points. Bill ________________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Sven Van Caekenberghe [sven(a)beta9.be] Sent: Wednesday, June 22, 2011 7:50 AM To: An open mailing list to discuss any topics related to an open-source Smalltalk Subject: [Pharo-project] Fwd: [Seaside] Comparison of Aida/Web, Seaside and Iliad web frameworks This was posted on the Seaside mailing list, I think it is both funny and hitting several points. I am not sure about the last item though ;-) Sven Begin forwarded message: On 22 Jun 2011, at 04:58, Boris Popov, DeepCove Labs wrote: http://dl.dropbox.com/u/2737880/screenshots/pharovsvisualworks.png [cid:image001.png@01CC3066.C79FAE30]

June 22, 2011

Re: [Pharo-project] PharoKernel 13269

by Eliot Miranda

Hi All, On Tue, Jun 21, 2011 at 12:29 PM, StÃ©phane Ducasse < stephane.ducasse(a)inria.fr> wrote: > what we should pay attention (to be verified) is that igor told me that he > does not understand why > the latest code of the vm published by eliot does not include some fixes he > did for 1.2. May be the code was never integrated. > In addition the latest vm produced by eliot does not include a long list of > fixes made by igor and mariano. > Igor asked in the vm mailing-list what will happen to his changes and there > were no reaction so far. > I feel some ownership of the Cog branch. It would be nice to have a chance to review code before it gets in instead of having to merge. You might think of sending me changesets for the more complex sets of changes (e.g. finalization) so that the merge is easier. Finally, you might understand that I'm busy at work and for personal reasons have essentially no time at the weekends to work on Cog. Criticising me in public like this does not make me any more eager to find the time. > So we should pay attention that using the latest vm from eliot may also > break our system. We should also think about the fact that > may be we will have to burn igor's time to merge vm fixes when other people > don't do it. > I asked igor to continue to work on the windows build because we want to > run regression tests at the VM level. We should be able to trace > vm changes and control the impact they have on us and not run after > different versions and releases. To have a process in a sense. > > Stef > > yeah.. harmonization, it would be good, Eliot if you take a look of > changes made in > VMMaker-oscog-MarianoMartinezPeck.66 > and integrate them, so we will use common version. > > They have a common ancestor - > VMMaker-oscog.54 > > Without this all of the following work will be lost: > > Name: VMMaker-oscog-IgorStasenko.54 > Author: IgorStasenko > Time: 23 March 2011, 5:30:42 pm > UUID: c98a0b6c-7f68-4af7-9012-85d3dfdf29ae > Ancestors: VMMaker-oscog-IgorStasenko.53 > > - added disabling module loading support > > > Name: VMMaker-oscog.dtl.56 > Author: dtl > Time: 4 April 2011, 10:06:00.292 pm > UUID: c1d30608-00e8-53b7-209a-34f7a46c1508 > Ancestors: VMMaker-IgorStasenko.55 > > Add tests from VMMaker trunk to document various issues and verify > presence of primitives. > > Name: VMMaker-oscog.dtl.57 > Author: dtl > Time: 11 April 2011, 10:13:51.668 pm > UUID: c1d30608-04dd-53b7-209a-34f7a46c1508 > Ancestors: VMMaker-oscog.dtl.56 > > Generate C code for #repeat. > Implementation by Igor Stasenko and Nicolas Cellier. > That's already integrated. > > Name: VMMaker-oscog-dtl.58 > Author: dtl > Time: 17 April 2011, 10:22:12.174 pm > UUID: c1d30608-04b3-a5b7-20ca-2bf7a46c1508 > Ancestors: VMMaker-oscog-dtl.57, VMMaker-oscog.dtl.57 > > Merge VMMaker-oscog.dtl.57 > > Generate C code for #repeat. > Implementation by Igor Stasenko and Nicolas Cellier. > ditto. > > Name: VMMaker-oscog-dtl.59 > Author: dtl > Time: 17 April 2011, 10:32:55.018 pm > UUID: c1d30608-042d-4bb7-20ca-2bf7a46c1508 > Ancestors: VMMaker-oscog-dtl.58 > > Merge VMMaker-oscog.dtl.58, and add #primitiveImageFormatVersion > Since there's a VM parameter I question the need for yet-another-primitive. > > Add primitiveMillisecondClockMask, an optional named primitive used in > conjunction with primitiveMillisecondClock for duration calculations. > The image assumes a value for this constant that is assumed to > correspond to the actual value used in the VM. This primitive permits > the VM to report the actual value being used. > Already integrated. > > Add primitiveImageFormatVersion, an optional named primitive answering > the image format number of the current image. This is the value stored > in the first word of an image file header when the image is saved, and > possibly modified on image load if the VM adds or removes capabilities > for the running image. This primitive was added to VMMaker trunk in > VMMaker-dtl.169. Rationale: supports float word order handing for > image segments, reference > http://lists.squeakfoundation.org/pipermail/vm-dev/2011-April/007712.html Not integrating this. The VM parameter (41) has been in Cog since the beginning. Instead why not merge the VM parameter back into Interpreter? > > > Name: VMMaker-oscog-dtl.64 > Author: dtl > Time: 21 April 2011, 8:24:32.46 pm > UUID: c1d30608-30ec-50b7-208a-31f7a46c1508 > Ancestors: VMMaker-oscog-dtl.59 > > Re-save from VMMaker-oscog-EstebanLorenzano.62 because > VMMaker-oscog-dtl.61 and VMMaker-oscog-dtl.60 were saved without > correct ancestry. This version incorporates the changes from > VMMaker-oscog-EstebanLorenzano.62, VMMaker-oscog-dtl.61, and > VMMaker-oscog-dtl.60. > > Name: VMMaker-oscog-EstebanLorenzano.62 > -added ClipboardExtendedPlugin as a regular plugin (taken from the > InterpreterVM branch) > I don't know if it works right now, but at least it compiles :) > > Name: VMMaker-oscog-dtl.61 > A second batch of updates from VMM trunk, primarily cosmetic but also > a class comment update and a couple of methods that had not previously > been pragmatized in oscog. > > Name: VMMaker-oscog-dtl.60 > These changes are methods from the main VMM branch for which > <#var:#type:> declarations have been formatted with proper spacing. By > updating these in the oscog branch, all of these methods are identical > in both branches. All changes are cosmetic (no functional changes to > the methods). > > Name: VMMaker-oscog-MarianoMartinezPeck.65 > Author: MarianoMartinezPeck > Time: 23 April 2011, 1:50:19 pm > UUID: 944f5c54-f2f5-4cc7-b693-b4db9320cff8 > Ancestors: VMMaker-oscog-dtl.64 > > blah > > Name: VMMaker-oscog-MarianoMartinezPeck.66 > Author: MarianoMartinezPeck > Time: 23 April 2011, 2:17:26 pm > UUID: 97bab5b0-51d6-4deb-8b58-5bcedd4747dc > Ancestors: VMMaker-oscog-MarianoMartinezPeck.65 > > Adapt VMMakerTool so that it doesnt try to register in the menu if > TheWorldMenu is not present, like the case of Pharo. This change was > already integrated in the main trunk of VMMaker but since Eliot forked > VMMaker-oscog before that, it was not there. > > It doesn't affect Squeak > > > -- > Best regards, > Igor Stasenko AKA sig. > -- best, Eliot

June 22, 2011

Re: [Pharo-project] [Tiling Window Manager ] could not load it

by laurent laffont

On Wed, Jun 22, 2011 at 5:53 PM, Bernardo Ezequiel Contreras < vonbecmann(a)gmail.com> wrote: > Hi > i could not load TWM on pharo unstable core.(see below) > what am i doing wrong? any idea? > Nothing wrong, but I've added (then removed) an extension to OBCodeBrowser so it matches Browser colors when using TWMTheme. Click proceed and it will load. Or load development version: ConfigurationOfTilingWindowManager loadDevelopment. Laurent. > > thanks > > > Pharo image: Pharo1.3#13272 > Virtual machine used: Croquet Closure Cog VM [CoInterpreter > VMMaker-oscog.54] > Platform Name: unix > Class browser used (if applicable): Browser > > Steps to reproduce: > #. Gofer it squeaksource: 'TilingWindowManager'; > package: 'ConfigurationOfTilingWindowManager'; > load. > #.ConfigurationOfTilingWindowManager load. > #. Actual Result > This package depends on the following classes: > OBCodeBrowser > You must resolve these dependencies before you will be able > to load these definitions: > OBCodeBrowser classSide>>pathworkUIThemeColor > #. Expected Result > to load it successfully >

June 22, 2011

[Pharo-project] [Tiling Window Manager ] could not load it

by Bernardo Ezequiel Contreras

Hi i could not load TWM on pharo unstable core.(see below) what am i doing wrong? any idea? thanks Pharo image: Pharo1.3#13272 Virtual machine used: Croquet Closure Cog VM [CoInterpreter VMMaker-oscog.54] Platform Name: unix Class browser used (if applicable): Browser Steps to reproduce: #. Gofer it squeaksource: 'TilingWindowManager'; package: 'ConfigurationOfTilingWindowManager'; load. #.ConfigurationOfTilingWindowManager load. #. Actual Result This package depends on the following classes: OBCodeBrowser You must resolve these dependencies before you will be able to load these definitions: OBCodeBrowser classSide>>pathworkUIThemeColor #. Expected Result to load it successfully

June 22, 2011

Re: [Pharo-project] Merge tool. No way to cherry pick the changes?

by Gary Chambers

Perhaps the "non-applicable" could be streamlined. I.e., "keep current version" = not applicable. No need for the extra menu item then. Regards, Gary ----- Original Message ----- From: "Igor Stasenko" <siguctua(a)gmail.com> To: <Pharo-project(a)lists.gforge.inria.fr> Sent: Wednesday, June 22, 2011 3:40 PM Subject: Re: [Pharo-project] Merge tool. No way to cherry pick the changes? > Here the code > http://code.google.com/p/pharo/issues/detail?id=4439 > > please tell me if it works for you. > I tested on simple merge and it works fine (the changes which i marked > as not applicable are not loaded). > > -- > Best regards, > Igor Stasenko AKA sig. >

June 22, 2011