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

Re: [Pharo-project] question about O2 vs OB

by Mariano Martinez Peck

O2 used to depend and override some stuff from OB. Thus, we have lot of bugs related to this. Right now, after the ANN of David and Alexandre, O2 does not depend or overrides anything from OB. So, you can load both of them in a core image without needing the other, and they can even coexist. I mean, you can install both without problems. But...they don't share code, at all. At least, that's what I understood. Cheers Mariano On Wed, Jan 20, 2010 at 2:40 PM, Torsten Bergmann <astares(a)gmx.de> wrote: > Lukas wrote > >because O2 makes incompatible changes to the OmniBrowser framework. > >The way O2 is implemented makes it impossible to run both together on the > >same core model without conflicts. > > OK, but Alexandre wrote in [1]: > "O2 has now no dependencies to OB anymore." > > so is Lukas' statement still true and both are in conflict or are > these conflicts now resolved and it is possible to run both together? > > Thanks > T. > > > [1] > http://lists.gforge.inria.fr/pipermail/pharo-project/2010-January/020475.ht… > -- > GRATIS fÃ¼r alle GMX-Mitglieder: Die maxdome Movie-FLAT! > Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01 > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Jan. 20, 2010

[Pharo-project] Something I don't understand with Method Finder

by Mariano Martinez Peck

Hi folks! If you look for example "gently" in Method Finder, you will see that it lists, for example, "enableGently:" and "disableGently:" However, those methods are not implemented, there are no senders, and I even did a "method source with it " and I found nothing. In my final shut, I read the .changes and I found: "Preferences class removeSelector: #enableGently:!" Now I wonder...is this a feature of Method Finder to look also in .changes or it is a bug ? Anyway, it is not clear when you find a message but you don't have implementros or senders, it means that it was in .changes. What do you think? Thanks Mariano

Jan. 20, 2010

[Pharo-project] question about O2 vs OB

by Torsten Bergmann

Lukas wrote >because O2 makes incompatible changes to the OmniBrowser framework. >The way O2 is implemented makes it impossible to run both together on the >same core model without conflicts. OK, but Alexandre wrote in [1]: "O2 has now no dependencies to OB anymore." so is Lukas' statement still true and both are in conflict or are these conflicts now resolved and it is possible to run both together? Thanks T. [1] http://lists.gforge.inria.fr/pipermail/pharo-project/2010-January/020475.ht… -- GRATIS fÃ¼r alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01

Jan. 20, 2010

Re: [Pharo-project] question about O2 vs OB

by Lukas Renggli

O2 is a fork of OB. The duplication of the complete code-base is necessary, because O2 makes incompatible changes to the OmniBrowser framework. The way O2 is implemented makes it impossible to run both together on the same core model without conflicts. Lukas -- Lukas Renggli http://www.lukas-renggli.ch

Jan. 20, 2010

Re: [Pharo-project] [Seaside] Re: Seaside + TDD

by Mariano Abel Coca

Thanks Bart, i'll take a look at it. Kind Regards, Mariano. On Wed, Jan 20, 2010 at 8:30 AM, Bart Gauquie <bart.gauquie(a)gmail.com>wrote: > Hi, > > I'm creating http://www.squeaksource.com/WebTester. This is a general > purpose tool which tests websites; using selenium rc. > So it does not directly works on Selenium, but tests any web site. > > You can try it. Its unfinished, but the parts already developed are > working. > > Kind Regards, > > Bart > > 2010/1/19 Mariano Abel Coca <marianoabelcoca(a)gmail.com> > >> Hi everyone, >> >> I'm trying to develop using TDD with seaside 3.0, but honestly, I couldn't >> find any framework or package that works fine with it. I've tried Albatross >> and Seaside Testing, both of them work great with Seaside 2.8, but fails to >> run or even to load in seaside 3.0. >> >> Any other suggestions? >> >> Thanks in advance. >> >> Mariano. >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > > -- > imagination is more important than knowledge - Albert Einstein > Logic will get you from A to B. Imagination will take you everywhere - > Albert Einstein > Learn from yesterday, live for today, hope for tomorrow. The important > thing is not to stop questioning. - Albert Einstein > The true sign of intelligence is not knowledge but imagination. - Albert > Einstein > However beautiful the strategy, you should occasionally look at the > results. - Sir Winston Churchill > It's not enough that we do our best; sometimes we have to do what's > required. - Sir Winston Churchill > > _______________________________________________ > seaside mailing list > seaside(a)lists.squeakfoundation.org > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside > >

Jan. 20, 2010

Re: [Pharo-project] Scripts that should be run after a slice and ScriptLoader

by Mariano Martinez Peck

On Wed, Jan 20, 2010 at 1:25 PM, Simon Denier <Simon.Denier(a)inria.fr> wrote: > > On 20 janv. 2010, at 11:29, Mariano Martinez Peck wrote: > > > Hi: I found that several times, we need to run some piece of code after a > slide. The only way I see doing this is to write it in a txt , and, > hopefully (many times, the commiter or the integrator forget about it), > remember to put that in the email or issue, when I let you know the fix is > ready. Is there a better way ? > > > > What about having a method in ScriptLoader where we can commit that > together with the slice? Then when someone integrates that, it will see > that, and will move that piece of code, from there, to the update or script > methods. > > > > I don't know. What do you think ? > > > If I understood correctly, Monticello already has this feature for package > so I guess it should work for slices. > > Click on a package in MC browser, then click on the 'Scripts' button in the > toolbar, you get menu to edit the preamble, postscript, as well as > preambleOfRemoval and postscriptOfRemoval > > Thanks Simon. I wasn't aware of that. However, I think it doesn't fix completely what I mean. Suppose an integrator load that slice. Ok, the script will be automatically run, BUT in his PC. Then, suppose he load some others scripts and he finally do a new release. If WE want to update trough the update stream to the image, it won't work. That's why we have the update methods in ScriptLoader (I think). So, in such case, they have to put it there also, I they have to be aware of that. > > > > > Would be cool, maybe, to reify the "slice" concept, where you can have: > pre-doits, a collections of "pieces of code" (several times we have, part1, > part2, tc), post-doits, etc...But I guess that requires a lot of effort. > > > > Cheers > > > > Mariano > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > -- > Simon > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Jan. 20, 2010

Re: [Pharo-project] Scripts that should be run after a slice and ScriptLoader

by Henrik Johansen

On Jan 20, 2010, at 1:25 09PM, Simon Denier wrote: > > On 20 janv. 2010, at 11:29, Mariano Martinez Peck wrote: > >> Hi: I found that several times, we need to run some piece of code after a slide. The only way I see doing this is to write it in a txt , and, hopefully (many times, the commiter or the integrator forget about it), remember to put that in the email or issue, when I let you know the fix is ready. Is there a better way ? >> >> What about having a method in ScriptLoader where we can commit that together with the slice? Then when someone integrates that, it will see that, and will move that piece of code, from there, to the update or script methods. >> >> I don't know. What do you think ? > > > If I understood correctly, Monticello already has this feature for package so I guess it should work for slices. > > Click on a package in MC browser, then click on the 'Scripts' button in the toolbar, you get menu to edit the preamble, postscript, as well as preambleOfRemoval and postscriptOfRemoval Preamble/Postscripts don't work anymore in Pharo though, following the procedure you outlined I get a DNU when selecting the script I want to edit. Not sure when they were removed, but probably it was part of some PackageInfo cleaning. Cheers, Henry

Jan. 20, 2010

Re: [Pharo-project] Looking for your license agreement.

by George Herolyants

OK. Thank you.

Jan. 20, 2010

[Pharo-project] question about O2 vs OB

by Fernando olivero

Hi, was wondering why we need O2 and OB as two different frameworks?, and why O2 is not an extension to OB, are they structurally different in design and implementation? I was wondering about this since i read the last emails about O2 and OB decoupling. Because now if we reintegrate O2, the system will have much more complexity. Thanks, Fernando

Jan. 20, 2010

Re: [Pharo-project] What are Owners ???

by Mariano Martinez Peck

Also, can I remove Morph >> allOwners ? I checked and it has no sender neither in: Dev, Moose, Seaside, Pier... On Wed, Jan 20, 2010 at 1:26 PM, Mariano Martinez Peck < marianopeck(a)gmail.com> wrote: > I checked in squeak 2.6, 3.9 and 3.10. What is that class ? > > They have references in PharoCore. For example, look ImageSegment >> > findOwnersOutPtrs > > I will probably remove that method, but I want to learn what Owners > are/were. > > Does someone know ? > > Thanks > > Mariano >

Jan. 20, 2010