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

Re: [Pharo-project] Which Mondrian ?

by David RÃ¶thlisberger

>> ps: David, concerning the graph button bar in OB, I'll suggest showing >> it only in the comment view. > > It depends... I seldom press the comment button, except if there is a > comment in it, which is rare. yes, I also think it would be too hidden there. What would be possible is to add a button to the panel at the top labelled 'visualizations' that give you a list of available visualizations for the selected entity. Similar as the 'view' button. This would save some space. David

Feb. 26, 2009

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

by Lukas Renggli

> 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 -- Lukas Renggli http://www.lukas-renggli.ch

Feb. 26, 2009

Re: [Pharo-project] MIMEdatabase fix?

by Michael Rueger

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, but I need a little of your help on the Seaside side of things, at least a bit of testing. 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. Michael 'From Pharo0.1 of 16 May 2008 [Latest update: #10243] on 26 February 2009 at 10:50:21 am'! !MIMEDocument class methodsFor: 'compatibility' stamp: 'michael.rueger 2/25/2009 13:05'! guessContentTypeFromExtension: ext "guesses a content type from the extension" ^(self guessTypeFromExtension: ext) asString! !

Feb. 26, 2009

[Pharo-project] lisencing

by Esteban Lorenzano

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

Feb. 26, 2009

Re: [Pharo-project] MIMEdatabase fix?

by Philippe Marschall

Michael Rueger wrote: > Michael Rueger wrote: >> OK, here we go... >> in the Pharo inbox there is a new version of Network-MIME and >> KomHTTPServer. The Kom package should also work on Squeak. > > ok, one more thing ;-) > 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. If you absolutely have to you can make some unholy, brittle hacks like we currently do for author initials to figure out if we're Squeak or Pharo. Maybe even an #isPharo method. Cheers Philippe

Feb. 26, 2009

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

by Michael Rueger

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. Tell me about it ;-) Is there anything to look at though, just curious from a Sophie point of view how you approached the problem. Michael

Feb. 26, 2009

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

by Lukas Renggli

>>> 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. Lukas -- Lukas Renggli http://www.lukas-renggli.ch

Feb. 26, 2009

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

by Dale Henrichs

Stef, I posted a more detailed problem description to the OmniBrowser list and David has an update that fixes the problem (in OmniBrowser-dr.442). I'll verify the fix later today. Presumably OmniBrowser-dr.442 will be included in the next development drop, if not I will submit a bug. Dale ----- "StÃ©phane Ducasse" <stephane.ducasse(a)inria.fr> wrote: | Ok dale | this is probably related to the problems I see too during the lab. | if you have fix open an issue in the bugtracker and post here so that | | we get aware of it. | | Stef

Feb. 26, 2009

Re: [Pharo-project] Announcements for Pharo?

by StÃ©phane Ducasse

>> >> >>>> We will include it. >>>> >>>> >>>> Thanks, we will try with Pharo then. >>>> Lautaro FernÃ¡ndez >>> I am confused. Surely you would expect a loadable package to remain >>> loadable and only be called up if needed? >> >> Although I'm normally the first to argue against including more stuff >> into the core image I think Announcements need to be part of core. >> This will allow us to have *one* mechanism for signaling/ >> subscribing and >> can over time replace the different variants that are now used and >> provide a solid base for anyone needing such a mechanism. >> In the experimental forks I have worked on having Announcements >> available made all the difference. >> > Does that mean that the EventManager, package System-Object Events and > the methods in Object will be replaced by that? If yes I'm all for it! Would be nice. I think that this is a reaslistic goal. But not for 1.0 :) > > > Norbert > > > _______________________________________________ > 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] Announcements for Pharo?

by StÃ©phane Ducasse

But announcements are really core. :) Stef > On Thu, Feb 26, 2009 at 4:45 PM, Michael Rueger <m.rueger(a)acm.org> > wrote: >> Although I'm normally the first to argue against including more stuff >> into the core image I think Announcements need to be part of core. > > I have to disagree. The less we have the core, the easier it will be > to maintain it. However, Announcements may be included in the Pharo > distribution (currently named pharo-dev). I think we should discuss > that. I've added it to http://code.google.com/p/pharo/wiki/Packages > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > _______________________________________________ > 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