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

Re: [Pharo-project] Can't install Pier on Pharo

by CÃ©drick BÃ©ler

I think I have a problem with MIMEType too since I ve upgraded pharo 10231 (there was change on the network package) MNU at least on: MIMEDocument class>>contentTypeHtml and if I put back this method, I get an (seaside) internal error because of MNU: MIMEType>>indexOf: Don't know if fixed with recent version of seaside 2.9, but seaside 2.9 alpha and probably 2.8 don't load anymore. CÃ©drick ps: a not nice work around is to file-in the old MIMEType Class (joined) - don't know how to fix that cleanly... 2009/2/10 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > Not that I know. > I will let mike answer :) > Stef > > On Feb 10, 2009, at 4:32 PM, Damien Cassou wrote: > > > On Tue, Feb 10, 2009 at 3:55 PM, StÃ©phane Ducasse > > <stephane.ducasse(a)inria.fr> wrote: > >> MIMEDocument class>>resetMIMEdatabase seems the faulty one > > > > Yes. Did someone removed that method? > > > > -- > > 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 > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- CÃ©drick

Feb. 13, 2009

Re: [Pharo-project] Distributed versioning ... MonticelloHub?

by StÃ©phane Ducasse

> Of course SqueakSource isn't as inviting as github, In two minutes you have an account and project you can share. Now geert when you publish with MC you always get a copy of the package on your disc so what I do is to always develop in the same folder so that all the packages goes into my package cache which I never empty this way I have a copy of what I'm doing on my disc. Now it should be simple to automatically publish the local folder to the net in case you were only locally working. > it has a vastly smaller > community and mindshare than git and that's not going to change any > time > soon. Though we Smalltalk'ers keep hoping, Smalltalk still hasn't > taken > over the world and probably never will.

Feb. 13, 2009

Re: [Pharo-project] Pharo Smalltalk now also on Nabble

by StÃ©phane Ducasse

On Feb 13, 2009, at 9:51 AM, Adrian Lienhard wrote: > hehe, I was just adding it right now ;) hehe :) So I press the button just in front of your finger :) Stef > > > Adrian > > On Feb 13, 2009, at 09:46 , StÃ©phane Ducasse wrote: > >> someone already did it :) >> Thanks I published the new page. >> >> On Feb 13, 2009, at 12:19 AM, Geert wrote: >> >>> >>> Maybe Nabble should be added on the " http://pharo-project.org/community >>> pharo-project.org/community " page as an alternative interface which >>> allows >>> users to browse and search archived emails in an online forum and >>> where >>> members can post and reply to the mailing list? >>> >>> >>> Thanks >>> ! >>> Stef >>> >>> -- >>> View this message in context: http://n2.nabble.com/Pharo-Smalltalk-now-also-on-Nabble-tp2311636p2318555.h… >>> Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >>> >>> >>> _______________________________________________ >>> 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 > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Feb. 13, 2009

Re: [Pharo-project] Distributed versioning ... MonticelloHub?

by StÃ©phane Ducasse

> As for Pharo and whether Squeak code from those places will work on > Pharo, > for now, yes, most of it does; however, as Pharo continues to grow and > differentiate itself from Squeak, eventually it'll have to be > considered a > separate platform that is no longer Squeak compatible. That is > rather the > point, it just so happens the fork is recent enough that it's still > basically Squeak 3.9 but that won't last forever. Pharo is not > Squeak, so > it'll be interesting to see how much of the community it captures > and it all > unfolds. We will see but our goal is not to captures people :) Our goal is to open a free space for good, clean and robust software. I would love to see all kind of software running on top of pharo - education - web - new languages the real problem with squeak was that we got stuck in death kiss with the past. I like experiment made by people but experiment should be either cleaned, used, maintained... or belong to the past. > Me, I'm just a working programmer and this is all just my opinion, but > that's how it all looks to me. Squeak paid my bills, Pharo is > replacing it. > Good riddance to the silly mouse, name, and look, and hello to a > serious > business oriented open source Smalltalk that I'm not embarrassed to > mention > to clients. Yes the look, the look and the look. :) Money is not evil and I have been thinking that it would be great if we could build a community of companies that could offer Pharo enhancements (kind of support but in a bounty way). For now we should get 1.0 out of the door but after that this would be the time to think about that. Stef

Feb. 13, 2009

Re: [Pharo-project] Pharo Smalltalk now also on Nabble

by Adrian Lienhard

hehe, I was just adding it right now ;) Adrian On Feb 13, 2009, at 09:46 , StÃ©phane Ducasse wrote: > someone already did it :) > Thanks I published the new page. > > On Feb 13, 2009, at 12:19 AM, Geert wrote: > >> >> Maybe Nabble should be added on the " http://pharo-project.org/community >> pharo-project.org/community " page as an alternative interface which >> allows >> users to browse and search archived emails in an online forum and >> where >> members can post and reply to the mailing list? >> >> >> Thanks >> ! >> Stef >> >> -- >> View this message in context: http://n2.nabble.com/Pharo-Smalltalk-now-also-on-Nabble-tp2311636p2318555.h… >> Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >> >> >> _______________________________________________ >> 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. 13, 2009

Re: [Pharo-project] Pharo Smalltalk now also on Nabble

by StÃ©phane Ducasse

someone already did it :) Thanks I published the new page. On Feb 13, 2009, at 12:19 AM, Geert wrote: > > Maybe Nabble should be added on the " http://pharo-project.org/community > pharo-project.org/community " page as an alternative interface which > allows > users to browse and search archived emails in an online forum and > where > members can post and reply to the mailing list? > > > Thanks > ! > Stef > > -- > View this message in context: http://n2.nabble.com/Pharo-Smalltalk-now-also-on-Nabble-tp2311636p2318555.h… > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Feb. 13, 2009

Re: [Pharo-project] Loading Curl Pb

by danil osipchuk

The squeaksource project was intented for developers mostly rather than for end user. The interface class is coupled with the vm-plugin code there, so it does depend on vmmaker. It seemed reasonable for me, because you don't get the plugin binary from squeaksource anyway - you need to build it (and load vmmaker) or to get it from somewhere else ( for instance following the instructions from http://wiki.squeak.org/squeak/5865 ). However I recall several ocasions when I promised to make a new version of it and I even started thinking about wrapping it into installer similar to FreeType plugin, but got distracted. I will try to update the code to recent version and to make a user friendly installer on this weekend. It would help a lot, if there is anybody who has vm-builder setup on windows ready to compile the updated version. I have windows only at work, and I have no time to work on it here, so making both linux and windows version is a bit to much for me at the moment. regards, Danil 2009/2/12 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > 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 >> > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Feb. 13, 2009

Re: [Pharo-project] Distributed versioning ... MonticelloHub?

by Ramon Leon

> As you can see I am still finding my feet here :) Amazing > though, that > during my research I didn't come across > http://squeaksource.com > squeaksource.com myself. I actually had come across > SqueakSource some time > ago when I started to look at Squeak. > > So, am I correct in assuming that SqueakSource was intended to replace > SqueakMap and Package Universe then? Since Pharo is a fork of Squeak, > wouldn't it need some sort of Pharo specific repositories or would all > SqueakSource repositories continue to work on Pharo? The > whole SqueakMap, > Package Universe, SqueakSource and Monticello is very confusing. > SqueakSource doesn't really look as inviting as Github either > ... I did see > there is a SqueakSource 2 project though. It is all rather confusing but all these things seem to have different goals. From what I gather it's something like this... - SqueakMap: Meant as a distribution point for sharing published code in any format for any version of Squeak. The downside is it doesn't handle dependencies and is for sharing releasable versions, it's not a source code repository meant for development like squeaksource. The expectation is that if you see something in SqueakMap, it might work, it might not, it might with a bit of hacking and careful manual checking of possible dependencies. Was around before Monticello when people were still slinging sars and change sets for sharing code. SqueakMap is not meant to be a package manager, just a global single place to find all things squeak. - Package Universe: Seems to have been intended to be a version specific repository of packages and dependencies that are known to work in that particular version of Squeak. The expectation is that if you see something in Universe, it should work and will install any necessary dependencies. While this isn't always the case, most stuff seems to work pretty well. Admittedly, there's some overlap with SqueakMap here but it's really meant to be more like a package manager for your squeak image. It's comparable to apt-get or aptitude in Debian. - Monticello: Distributed version control and now the main format most squeakers share code in. Packages can be shared via package universe, squeakmap, and squeaksource. - SqueakSource: A public repository for the community to open and host Monticello projects. Of course, anyone can host their own such repositories as well and some do, but many big projects are on SqueakSource. Through here you be find the latest development versions, commit by commit, whether it's been released or not and can join and contribute code to these projects. You might have installed your software from squeakmap or package universe initially, but it's here you'll keep much of it up to date with the latest versions or find the latest bug fixes. Of course SqueakSource isn't as inviting as github, it has a vastly smaller community and mindshare than git and that's not going to change any time soon. Though we Smalltalk'ers keep hoping, Smalltalk still hasn't taken over the world and probably never will. As for Pharo and whether Squeak code from those places will work on Pharo, for now, yes, most of it does; however, as Pharo continues to grow and differentiate itself from Squeak, eventually it'll have to be considered a separate platform that is no longer Squeak compatible. That is rather the point, it just so happens the fork is recent enough that it's still basically Squeak 3.9 but that won't last forever. Pharo is not Squeak, so it'll be interesting to see how much of the community it captures and it all unfolds. Me, I'm just a working programmer and this is all just my opinion, but that's how it all looks to me. Squeak paid my bills, Pharo is replacing it. Good riddance to the silly mouse, name, and look, and hello to a serious business oriented open source Smalltalk that I'm not embarrassed to mention to clients. Ramon Leon http://onsmalltalk.com

Feb. 13, 2009

Re: [Pharo-project] Distributed versioning ... MonticelloHub?

by Keith Hodges

Geert wrote: > Ramon Leon wrote: > >> You named everything but the thing you're looking for. We have >> squeaksource.com, which is kind of like github, a place to share >> Monticello >> packages. >> >> Ramon Leon >> http://onsmalltalk.com >> >> > > As you can see I am still finding my feet here :) Amazing though, that > during during my research I didn't come across http://squeaksource.com > squeaksource.com myself. I actually had come across SqueakSource some time > ago when I started to look at Squeak. > > So, am I correct in assuming that SqueakSource was intended to replace > SqueakMap and Package Universe then? Since Pharo is a fork of Squeak, > Squeaksource is the place to manage the source that makes up a project. You can also set up your own repositories (with ftp for example), much like other scm tools. SqueakMap/Universes/ and Sake/Packages are places to publish the end results of projects, for others to load. SqueakMap - is intended to be the directory of all packages, but it doesn't support dependencies. Universes - has packages with dependencies targeted for a specific version of squeak. Sake/Packages - has package definitions browseable in a standard class browser - supports dependencies - supports unloading - load current published / or latest beta code it can find hope this helps clarify our murky world Keith

Feb. 13, 2009

Re: [Pharo-project] Distributed versioning ... MonticelloHub?

by Geert

Ramon Leon wrote: > > You named everything but the thing you're looking for. We have > squeaksource.com, which is kind of like github, a place to share > Monticello > packages. > > Ramon Leon > http://onsmalltalk.com > As you can see I am still finding my feet here :) Amazing though, that during during my research I didn't come across http://squeaksource.com squeaksource.com myself. I actually had come across SqueakSource some time ago when I started to look at Squeak. So, am I correct in assuming that SqueakSource was intended to replace SqueakMap and Package Universe then? Since Pharo is a fork of Squeak, wouldn't it need some sort of Pharo specific repositories or would all SqueakSource repositories continue to work on Pharo? The whole SqueakMap, Package Universe, SqueakSource and Monticello is very confusing. SqueakSource doesn't really look as inviting as Github either ... I did see there is a SqueakSource 2 project though. -- View this message in context: http://n2.nabble.com/Distributed-versioning-...-MonticelloHub--tp2319149p23… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Feb. 13, 2009