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

Re: [Pharo-project] MIMEdatabase fix?

by Damien Cassou

On Fri, Feb 27, 2009 at 12:02 PM, Lukas Renggli <renggli(a)gmail.com> wrote: > The problem is that people load released versions from SqueakMap or > Package Universe. As long as Pharo shares the Squeak Package Universe > there is no way of cleanly deciding which version of Kom to load. Pharo will probably have its own copy of Universe. -- Damien Cassou http://damiencassou.seasidehosting.st

Feb. 27, 2009

Re: [Pharo-project] MIMEdatabase fix?

by Keith Hodges

> Second the fix is not that ugly. It just sends #asString to something it > expects to be a String. This is not a that uncommon idiom. And we > already have to do something way uglier for ensuring author initials. > How about taking the Author initials stuff from pharo, and publishing it as a package that will load into squeak. Then coding seaside to the new api. This is something I plan to do for squeak anyway at some point, but if you have a need for it now. Also if you have any pressing fixes that squeak needs we can put that fix into lpf for all images 3.7+ Keith

Feb. 27, 2009

Re: [Pharo-project] MIMEdatabase fix?

by Lukas Renggli

On Fri, Feb 27, 2009 at 10:30 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > I have problems to understand why this would be not reasonable that > people load a give kom version for seaside on squeak > and one for seaside on pharo. The problem is that people load released versions from SqueakMap or Package Universe. As long as Pharo shares the Squeak Package Universe there is no way of cleanly deciding which version of Kom to load. In the long term (for upcoming version) we will have to decide what platform to support. I guess this will be Pharo 1.0 as soon as it has been released. It is too much trouble to keep the installers up-to-date and try to test and make them work on different versions and platforms. I suggest that people stick with Squeak 3.9.1 or early versions of Pharo for now. Lukas -- Lukas Renggli http://www.lukas-renggli.ch

Feb. 27, 2009

Re: [Pharo-project] method missing installing Seaside

by Lukas Renggli

That's a known problem, see "[Pharo-project] MIMEdatabase fix?". As a workaround use an old Pharo image from around December. Lukas -- Lukas Renggli http://www.lukas-renggli.ch

Feb. 27, 2009

[Pharo-project] method missing installing Seaside

by Esteban Lorenzano

Hi, I downloaded latest pharo-dev from the downloads page, and executed this: Installer universe install: 'Seaside'. But it fails, I'm getting a DNU on MIMEDocument>>resetMIMEdatabase... :( Cheers, Esteban

Feb. 27, 2009

Re: [Pharo-project] Announcements for Pharo?

by Igor Stasenko

2009/2/26 Norbert Hartl <norbert(a)hartl.name>: > On Thu, 2009-02-26 at 07:45 -0800, Michael Rueger wrote: >> Keith Hodges wrote: >> >> >> Â Â 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! > I will examine it more closely. > Norbert > > > _______________________________________________ > 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. 27, 2009

Re: [Pharo-project] lisencing

by StÃ©phane Ducasse

Hi henrik (I should check that your fax arrived :) Ideally we should check that the guy sign the squeak MIT agreement but this is not clear where this information here to me Matthew? do you know? I could add that next to the list of ok committers. If the code is not MIT we do not look at it. > 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? you merge with the most recent versions and publish the code in the inbox the method tags of the methods that did not change will be the one of the original author. After any modification is a modification so :) > > 1b. For derived/removed/extended changes made by the checker, who > do we tag as the change author? the guy doing them. > 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 >> > > > _______________________________________________ > 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] Announcements for Pharo?

by JÃ©rÃ´me

I agree. Am 26.02.2009 um 17:19 schrieb Janko MivÅ¡ek: > > Announcements will soon become as core as Morphic, actually even more, > because they can replace the existing event mechanism in Morphic. VW > guys actually did that in their GUI, so this is proven in practice. > > Therefore it is good for Announcements to become part of core, because > it will enable so many things, which is the main goal of the core > anyway: to contain a functionality useful as broadly as possible. > > So, make an exception, include Announcements in core, noone will > regret > that! >

Feb. 27, 2009

Re: [Pharo-project] lisencing

by StÃ©phane Ducasse

Yes... time time time... Stef On Feb 26, 2009, at 11:30 PM, John M McIntosh wrote: >>> 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 > = > = > = > = > = > ====================================================================== > > > > > _______________________________________________ > 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 StÃ©phane Ducasse

On > Luigi was one of the best students I ever worked with. He worked very > hard on SafarÃ and I am impressed by the result, especially given that > he was relatively new to Smalltalk and Squeak when the project > started. He has a strong background in Lisp and Emacs and therefore > has good knowledge on the workings of an editor. I heard that he is > interested to continue working on SafarÃ this summer. Excellent! Lukas can you make sure that the follow up project will be part of the GSOC topics. Else we could have a Summertalk as fallback. ESUG wants projects that have real use for the community (since this was not the case with some previous projects).

Feb. 27, 2009