February 2009 - Pharo-dev - lists.pharo.org

[Pharo-project] Text editing (was: Re: Aaah, the pain or ParagraphEditor refactoring)

by Michael Rueger

Lukas Renggli wrote: >> Is there anything to look at though, just curious from a Sophie point of >> view how you approached the problem. > > Documentation: > > http://vst.ensm-douai.fr/Esug2008Media/uploads/1/safara-EsugAwards2008.pdf > > Implementation (a lot of work will be required): > > http://www.squeaksource.com/Safara.html Interesting! Quite a few of the concepts can be found in Sophie too (a bit different, but nonetheless), so there seems to be some merit to those :-) Can you explain where the performance problems are in your approach? And how do you define "too slow"? MIchael

Feb. 27, 2009

Re: [Pharo-project] MIMEdatabase fix?

by Michael Rueger

Philippe Marschall wrote: >> There is actually on more method (attached) that we need to add to >> either Kom or Seaside to make Pharo and Squeak compatible on the API level. > > Sorry but no, see previous posts. Have a look at Seaside2.8a1-pmm.583 > for what I would find acceptable. OK, can you explain how I should make Seaside work on both Pharo and Squeak? I spent two days figuring out a minimal set of changes that would not require doing some ugly hack testing for which underlying platform you are dealing with and you say that is not acceptable? You *want* ugly hacks? I don't understand... I'm not even touching seaside (except the one method rename/addition for a method being called by Seaside). Michael

Feb. 27, 2009

Re: [Pharo-project] Guys please sign the license agreement so that

by Rob Rothwell

Ok...it may take a while to get there from the United States! Rob On Thu, Feb 26, 2009 at 6:19 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > we do not have problem in the future... > > http://pharo.gforge.inria.fr/licenseDocuments/ > > Thanks > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Feb. 27, 2009

Re: [Pharo-project] Aaah, the pain or ParagraphEditor refactoring ; -)

by Igor Stasenko

2009/2/26 Lukas Renggli <renggli(a)gmail.com>: >> Is there anything to look at though, just curious from a Sophie point of >> view how you approached the problem. > > Documentation: > > Â http://vst.ensm-douai.fr/Esug2008Media/uploads/1/safara-EsugAwards2008.pdf > > Implementation (a lot of work will be required): > > Â http://www.squeaksource.com/Safara.html > Lukas, can you make a more detailed overview,please, at what stage it is, and why it too slow. I wasn't aware it even exists! > Lukas > > -- > Lukas Renggli > http://www.lukas-renggli.ch > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Best regards, Igor Stasenko AKA sig.

Feb. 26, 2009

Re: [Pharo-project] lisencing

by John M McIntosh

>> Hi, >> I just saw the list of pending packages for pharo-dev and I noted >> that >> there is a package made by me (OB-Algernon), it is a little package >> with few changes to algernon... I if I might make a suggestion, in my left hand I have a database of names and initials of people who have signed up, in the right some code that looks at each method in the Pharo image, and tags any with a pragma if it can't figure out who owns it, or if the author isn't in the database. Run it before each release, post exceptions somewhere. Frankly any centralized initial, name registration going forward should capture an email address for later usage.... -- = = = ======================================================================== John M. McIntosh <johnmci(a)smalltalkconsulting.com> Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com = = = ========================================================================

Feb. 26, 2009

Re: [Pharo-project] lisencing

by henrik.s.johansen＠veloxit.no

Speaking of which, I have a related question: The issues marked with "Check:", which are mostly Mantis bug fixes to Squeak, what's the procedure for those? 1. Use the code submitted as fixes as a starting point, and assume it's under a valid licence? 1a. If so, how do we submit as the contributer for unaltered methods the person who made the Squeak patch instead of the person checking it? 1b. For derived/removed/extended changes made by the checker, who do we tag as the change author? 2. Read the bug descriptions and make corresponding changes to Pharo? Cheers, Henry Siterer "Esteban Lorenzano" <estebanlm(a)gmail.com>: > Hi, > I just saw the list of pending packages for pharo-dev and I noted that > there is a package made by me (OB-Algernon), it is a little package > with few changes to algernon... but I have not signed the agreement > (because I thought that none of my codes was included in pharo) > So I ask: I have to sign the agreement? how? > (In any case, I want to sign the agreement "just in case" -that will > allow me to contribute to pharo, if I find the time-... is that > possible?) > > Cheers, > Esteban > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Feb. 26, 2009

Re: [Pharo-project] MIMEdatabase fix?

by Philippe Marschall

Michael Rueger wrote: > Philippe Marschall wrote: >>> Newer version of MIME package plus the attached change for Seaside makes >>> at least the tests pass. >> >> -1 >> >> I don't have any interest at all to have a version of Seaside 2.8 for >> Squeak and one for Pharo. > > That's what I'm currently trying to avoid, It's better than monkey patching the system which is guaranteed to break again in the future. > but I need a little of your > help on the Seaside side of things, at least a bit of testing. Sure. > There is actually on more method (attached) that we need to add to > either Kom or Seaside to make Pharo and Squeak compatible on the API level. Sorry but no, see previous posts. Have a look at Seaside2.8a1-pmm.583 for what I would find acceptable. Cheers Philippe

Feb. 26, 2009

Re: [Pharo-project] Some issues with Pharo-dev build #10243

by David RÃ¶thlisberger

> OB-Tools-dkh.62 > OmniBrowser-dr.441 > OB-Standard-dr.339 > OB-Enhancements-dr.310 Just curious: Did you load this versions by hand? Because those versions of OB are still alpha, so we have to expect dev-dev behavior in those. ;) David

Feb. 26, 2009

Re: [Pharo-project] Some issues with Pharo-dev build #10243

by Dale Henrichs

----- "Dale Henrichs" <dale.henrichs(a)gemstone.com> wrote: | Okay, | | I've been able to reproduce the spurious bug that Igor was seeing | ('aContext not in process chain' error). | | It seems to be related to the fact that the OTDebugger uses an | OBFixedButtonPanel and the buttons are not getting updated correctly | (or at all), so the buttons are operating on stale contexts. The menu | items for the debugger appear to work okay - although the short cut | keys may not work - I'll look into this one:). You'll hit the | 'aContext not in process chain' as soon as you step out of the | original method context. | | The problem was introduced with pharo0.1-10243dev09.02.3 | (pharo0.1-10236dev09.02.2 doesn't have the sticky button problem). | | I also have fixes for the extra junk on the stack (for create method | and for halts/errors), but until the OBFixedButtonPanel issue gets | fixed you might want to revert to the non-ob debugger. | | Dale If you want to try the OTDebugger in pharo0.1-10243dev09.02.3 or later you can manually update OmniBrowser-dr.442 and OB-Tools-dkh.65 (which has fixes for the bugs reported by Igor). Dale

Feb. 26, 2009

Re: [Pharo-project] Aaah, the pain or ParagraphEditor refactoring ; -)

by StÃ©phane Ducasse

On Feb 26, 2009, at 7:00 PM, Lukas Renggli wrote: >>>> Just for information, couldn't SafarÃ a be introduced here ? >>> >>> SafarÃ is not useable yet. It is too slow :-( >> >> So is it killed by over-engineering or over flexibility? > > Writing an editor is not trivial. I did not mean it was. I just wanted to know. Stef > > > Lukas > > -- > Lukas Renggli > http://www.lukas-renggli.ch > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Feb. 26, 2009