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

Re: [Pharo-project] Loading Curl Pb

by Michael Rueger

StÃ©phane Ducasse wrote: > I like the idea to have to load speech to get curl :) > But this would be nice to fix that There is also a curl implementation in Sophie by Steven Riggins, not sure what it originally was based on. Michael

Feb. 12, 2009

Re: [Pharo-project] Fwd: Workspace API

by Lukas Renggli

> When I took up the role of maintaining MC1.5, I did so with the express > purpose of integrating all of the MC forks for the benefit of the whole > community. If I had known that this idea was conceptually a waste of > time then I wouldn't have bothered. I did it because I wanted overrides > to actually work, and because I thought people would be enthusiastic for > it to actually work. How on earth do you do anything practical with MC1? > It drove me nuts. I have a hard time to trust a system that references 6 undefined variables and that sends twice as many undefined messages (see attached screenshot). > Perhaps you guys are still not understanding what LPF is for. I honestly do not understand what LPF means. It is probably because I am not a native speaker. > I am just speaking up because I found code in Pier that was not > compatible with Squeak, so I worry where this is all going. I still don't know what kind of problem you encountered with Pier? Please file a bug at <http://code.google.com/p/pier/>. I exclusively use Pharo for the development and deployment of Pier, Seaside and my other public and commercial projects. I know and trust the people that are behind Pharo, they push forward in the right direction. They maintain a good balance between clean-up, new features and building a trustworthy stable system. It obvious that external packages will break sooner or later and that framework developers have to pay attention to portability. At some point there will probably be no way around a Squeak specific platform class, if people want to use Seaside in Squeak? Lukas -- Lukas Renggli http://www.lukas-renggli.ch

Feb. 12, 2009

[Pharo-project] Loading Curl Pb

by StÃ©phane Ducasse

I like the idea to have to load speech to get curl :) But this would be nice to fix that Begin forwarded message: > From: Paul DeBruicker <pdebruic(a)gmail.com> > Date: February 12, 2009 6:35:53 PM CEST > To: Seaside - general discussion <seaside(a)lists.squeakfoundation.org> > Subject: Re: [Seaside] Loading Curl Pb (was: Google Maps API > Services Geocoding ( resend for wrong format )) > Reply-To: Seaside - general discussion <seaside(a)lists.squeakfoundation.org > > > > The missing bits for CurlPlugin are in VMMaker, which needs Speech and > FFI. All of which can be found on squeaksource or the Universe > browser. VMMaker is under System. Speech is under Uncategorized and > FFI is under System. > > But I'm not sure they'll load properly. I tend to get errors and go > back to using HTTPSocket. I've tried with Squeak 3.10.2 and Damiens > Pharo and Squeak-web images. > > > But if you load them and don't get errors let me know and I'll try > again. > > Thanks > > Paul > > > > > > On Thu, Feb 12, 2009 at 12:23 PM, CÃ©drick BÃ©ler <cdrick65(a)gmail.com> > wrote: >> Hi >> >>> >>> Or >>> Curl new getContentsUrl: '....' >> >> long time I wanted to give Curl a try. >> When I try to load CurlPlugin from squeaksource, I get: >> >> This package depends on the following classes: >> SmartSyntaxInterpreterPlugin >> You must resolve these dependencies before you will be able to load >> these >> definitions: >> CurlPlugin >> >> I use seasde 2.9 and Pharo 10231. >> >> Any ideas what I'm missing ? >> >> Thx >> >> >>> >>> Cheers >>> Philippe >>> _______________________________________________ >>> seaside mailing list >>> seaside(a)lists.squeakfoundation.org >>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside >> >> >> >> -- >> CÃ©drick >> >> _______________________________________________ >> seaside mailing list >> seaside(a)lists.squeakfoundation.org >> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside >> >> > _______________________________________________ > seaside mailing list > seaside(a)lists.squeakfoundation.org > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside >

Feb. 12, 2009

Re: [Pharo-project] 10233 drag and drop a file -> DNU MIMEType

by Michael Rueger

StÃ©phane Ducasse wrote: > apparently there was a problem when I did 10233 so your fixe works. Great :-) Michael

Feb. 12, 2009

Re: [Pharo-project] 10233 drag and drop a file -> DNU MIMEType

by StÃ©phane Ducasse

apparently there was a problem when I did 10233 so your fixe works. Stef On Feb 12, 2009, at 6:25 PM, StÃ©phane Ducasse wrote: > Hi mike > > I integrated your changes but I still get a problem when I drag and > drop a file. > Can you check that you changes are really in? > and let us know > > Tx > Stef > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Feb. 12, 2009

Re: [Pharo-project] Workspace API

by StÃ©phane Ducasse

No idea >> time >> time time >> have you seen that adrian is working on trait sharing and that we are >> waiting for that >> since a couple of months or more. >> >> Stef >> > Will it load into 3.10? > > Keith > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Feb. 12, 2009

Re: [Pharo-project] Fwd: Workspace API

by Keith Hodges

> > We believe your work (MC, SUnit, Sake and Packages) is important > enough for an integration into Pharo. We don't want to consider it as > an external package. I think that you should consider it as an external package, because it IS an external package. And it is used by code that is not Pharo code. I think in an open source environment where everyone is short on time and energy it is rude not to. Those who fixed it before, invested their time and energy contributing to a solution and to an ideal, knowing that others would fix it in future and do the same, and it would continue to be useful. I consider the fact that Pharo team ignored Edgars contribution to squeak as extremely rude for the same reason. When I took up the role of maintaining MC1.5, I did so with the express purpose of integrating all of the MC forks for the benefit of the whole community. If I had known that this idea was conceptually a waste of time then I wouldn't have bothered. I did it because I wanted overrides to actually work, and because I thought people would be enthusiastic for it to actually work. How on earth do you do anything practical with MC1? It drove me nuts. There should be one stream of development for MC, any more makes no sense. Again this is a philosophical choice, you either see the sense in it or you don't. The fact that you will not adopt the choice of treating MC as an external package for the benefit of all, and you continue to develop MC1 within pharo is in by book extremely insulting to the amount of effort that has been made on your behalf. I say again it is an external package, and the repo is OPEN, so use it, and if you find it isnt up to scratch (the tests arent), then join in and fix it. Instead you appear to be cocking a snook at everyones contributions, and going your own way. Perhaps you guys are still not understanding what LPF is for. If you want to change something to make it integrate well with Pharo but this would make it incompatible with other squeak, then we have a mechanism for backporting compatibility to older users. That mechanism is LPF, and S/P, thats what it is there for. If you maintain it as an external package. > But for that, Pharo's maintainers must have a > look at the code and decide if it is safe to include. Why? As I said its not their package, its an external package. > Your code is not > of lower quality. > Thanks, my code quality really depends on sleep, there must be a correlation there. > Have a nice day and please continue working on these tools > I am just speaking up because I found code in Pier that was not compatible with Squeak, so I worry where this is all going. Keith

Feb. 12, 2009

[Pharo-project] I have a problem and I will redo the last update

by StÃ©phane Ducasse

sorry. stef

Feb. 12, 2009

[Pharo-project] 10233 drag and drop a file -> DNU MIMEType

by StÃ©phane Ducasse

Hi mike I integrated your changes but I still get a problem when I drag and drop a file. Can you check that you changes are really in? and let us know Tx Stef

Feb. 12, 2009

Re: [Pharo-project] Workspace API

by Keith Hodges

> time > time time > have you seen that adrian is working on trait sharing and that we are > waiting for that > since a couple of months or more. > > Stef > Will it load into 3.10? Keith

Feb. 12, 2009