- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Bug PackageInfo >> classes return also Traits

by Lukas Renggli

> Hi folks. I've just discovered that PackageInfo >> classesÂ return a > collection of classes AND traits. This is incorrect. Why is this wrong? Collections are mostly polymorphic to traits. > Solutions are: > > 1) Rename #classes to #classesAndTraits > 2) Modify #classes so that it ONLY answer classes > > I would like to fix it but I am not sure the consequences of such change. > Maybe Monticello doesn't take into account Traits anymore hahha Yes, all users of PackageInfo will break. Lukas -- Lukas Renggli www.lukas-renggli.ch

May 10, 2010

[Pharo-project] Bug PackageInfo >> classes return also Traits

by Mariano Martinez Peck

Hi folks. I've just discovered that PackageInfo >> classes return a collection of classes AND traits. This is incorrect. Solutions are: 1) Rename #classes to #classesAndTraits 2) Modify #classes so that it ONLY answer classes I would like to fix it but I am not sure the consequences of such change. Maybe Monticello doesn't take into account Traits anymore hahha Thanks for any help you can give. Mariano

May 10, 2010

Re: [Pharo-project] add return its argument

by Norbert Hartl

I don't have time to scan the mailing list in detail. Was there any discussion that led to this change? Any pointers appreciated. I always thought the comfort of being able to chain selectors like add: outweighs the uniformity. Norbert On 08.05.2010, at 17:31, stephane ducasse wrote: > if somebody wants to check that the fixes I made are ok > and that at:put: and add: return their arguments > > > <addReturnValue.1.cs> > > Stef_______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

May 10, 2010

Re: [Pharo-project] Pharo and Ubuntu

by laurent laffont

Hi Torsten, I know there's a package team for Squeak. http://alioth.debian.org/projects/pkg-squeak/ <http://alioth.debian.org/projects/pkg-squeak/>and that last squeakvm has entered debian testing http://lists.alioth.debian.org/pipermail/pkg-squeak-devel/2010-April/000077… As Ubuntu is based on debian testing/unstable, I suppose squeakvm will enter in next Ubuntu release. You may ask on the packagers mailing list: http://lists.alioth.debian.org/mailman/listinfo/pkg-squeak-devel Cheers, Laurent Laffont On Sun, May 9, 2010 at 10:57 PM, Torsten Bergmann <astares(a)gmx.de> wrote: > Hi there, > > just installed Ubuntu 10.04. In the Software Center > I was able to find and install Squeak. > For Pharo I had to use the one click ZIP. > > But what has to be done so that Pharo is listed in the > Ubuntu Software center too and is installed with a few > clicks so it integrates well (icon, correct image, ...) > > Thx > T. > > -- > GRATIS fÃ¼r alle GMX-Mitglieder: Die maxdome Movie-FLAT! > Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01 > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

May 10, 2010

[Pharo-project] Fwd: [Vm-dev] Re: Freetype plugin archive

by StÃ©phane Ducasse

> From: "David T. Lewis" <lewis(a)mail.msen.com> > Date: May 9, 2010 7:26:22 PM GMT+02:00 > To: vm-dev(a)lists.squeakfoundation.org, Pharo-project(a)lists.gforge.inria.fr > Cc: m.rueger(a)acm.org > Subject: [Vm-dev] Re: Freetype plugin archive > Reply-To: Squeak Virtual Machine Development Discussion <vm-dev(a)lists.squeakfoundation.org> > > > On Sun, May 02, 2010 at 08:55:33AM -0700, Michael Rueger wrote: >> On 5/1/10 11:31 AM, Bert Freudenberg wrote: >>> On 01.05.2010, at 18:31, David T. Lewis wrote: >> >>>> Do you know if the rest of the stuff in http://source.impara.de/freetype/ >>>> still has value (or has it been superceded by Freetype Plus)? >> >> I would think so, that's why there wasn't any further development on the >> freetype plugin. >> The current repositories are of somewhat historical value for e.g. the >> Sophie builds. > > I have opened a new SqueakSource project for the Freetype plugin (FT2Plugin). > > MCHttpRepository > location: 'http://www.squeaksource.com/FreetypePlugin' > user: '' > password: '' > > This contains copies of all the Freetype-Plugin entries from the archival > repository at http://source.impara.de/freetype, as well as one additional > update from Mantis 7521. > > Project administrators are Andy Tween, Bert Freudenberg and me. Developers > are everyone whose author initials appear in the original archive. > > VMMaker class>>updateFromServer should now load FT2Plugin from the new > FreetypePlugin repository. A similar update will be needed for > ConfigurationOfVMMaker for Pharo. > > For now the original package name Freetype-Plugin has been retained, > although I note that this conflicts with the current packaging of Freetype > in SqS/Freetype Plus, so a change to the package name may be in order. > > FT2Plugin contains dependencies on Freetype. This is the reason that > I moved it to a separate SqueakSource project rather than include it > in the SqS/VMMaker repository. > > Dave >

May 10, 2010

[Pharo-project] [update 1.1] #11347

by StÃ©phane Ducasse

11347 ----- - better Categorizer class comment. - Issue 2400: Support passwords/usernames urls with dangerous - Some WeakSet tests expected to fail. - Issue 1920: Better PureBehaviorTests - Issue 1934: some tests for WeakRegistry

May 10, 2010

Re: [Pharo-project] [Pharo-users] I'm new

by StÃ©phane Ducasse

> > http://book.pharo-project.com

May 10, 2010

Re: [Pharo-project] Pharo and Ubuntu

by StÃ©phane Ducasse

I do not know the process to get pharo included. If somebody does then we get a chance. On May 9, 2010, at 10:57 PM, Torsten Bergmann wrote: > Hi there, > > just installed Ubuntu 10.04. In the Software Center > I was able to find and install Squeak. > For Pharo I had to use the one click ZIP. > > But what has to be done so that Pharo is listed in the > Ubuntu Software center too and is installed with a few > clicks so it integrates well (icon, correct image, ...) > > Thx > T. > > -- > GRATIS fÃ¼r alle GMX-Mitglieder: Die maxdome Movie-FLAT! > Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01 > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

May 10, 2010

Re: [Pharo-project] Metacello questions

by Mariano Martinez Peck

My advice is not to specify versions in a project reference. If you have a baseline and in such baseline you reference a project, for example: "this piece of code is inside a baselind" project: 'UI Support' with: [ "One or more of the following attributes may be defined or changed" spec "Name of config class (i.e., ConfigurationOfXXX)" className: 'ConfigurationOfUI'; "Version of project to be loaded. if theversionString is not specified, then the latest version of the project is used." versionString: '1.0'; Then, DO NOT PUT versionString: there. So: "this piece of code is inside a baselind" project: 'UI Support' with: [ "One or more of the following attributes may be defined or changed" spec "Name of config class (i.e., ConfigurationOfXXX)" className: 'ConfigurationOfUI'; "Version of project to be loaded. if theversionString is not specified, then the latest version of the project is used." file: 'XXX'. And in a version method that has THAT basline, you write: spec project: 'UISupport' with: '1.0'. In summary, don't put version information in baselines, only in version methods. That's just my advice. Cheers Mariano On Thu, May 6, 2010 at 10:13 PM, Torsten Bergmann <astares(a)gmx.de> wrote: > >Does that mean the documentation is just wrong then? > > I would see/interpret it like this: With the baseline you describe a set of > packages (structure/dependencies) that form your app/project (MyApp). Beside > the usual loading of a version: > > (ConfigurationOfMyApp project version: '1.0') load > > it is possible to load also a baseline - this would load all the latest > Monticello package versions of any package described in this baseline: > > (ConfigurationOfMyApp project version: '1.0-baseline') load > > Note that in the baseline you dont say anything about the Monticello > package > version to use/load. > > In a baseline you can also define a dependency on another project (that > provides a config too, for instance ConfigurationOfMyFoo). > > Now you have two options: > > a) dont say anything about the version of "ConfigurationOfMyFoo" in the > baseline > => this should load the latest version of Foo's Metacello > configuration then, > so you get the latest version of "Foo" when loading the baseline > of MyApp > > b) you note/give a default version for "ConfigurationOfMyFoo" in the > baseline > => then this specific version of "Foo" is loaded when you load the > baseline for MyApp. > I think you can override the version specified in the baseline in > a #versionXXX of MyApp if required > > Loading baselines is usefull if you work in a team. If you work on the > same baseline you can just load it to be up to date with the latest > commits of the other team members. > > If your dependencies, load order, set of packages/pre-projects change then > you typically create a new baseline. > > But it is more often the case that you just create new versions based on > a baseline. In a versionXXX you pin/mark the Metacello version of all > packages/projects version that fit/work together to form this version. > > Maybe Dale is able to correct me if I'm wrong. > > Thanks > Torsten > > > > -- > GRATIS fÃ¼r alle GMX-Mitglieder: Die maxdome Movie-FLAT! > Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01 > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

May 9, 2010

Re: [Pharo-project] [Pharo-users] I'm new

by Mariano Martinez Peck

On Sun, May 9, 2010 at 10:52 PM, Deathiop.dev <deathiop.dev(a)gmail.com>wrote: > Hello everybody, > > I'm a recent Pharo user and I think it's pretty good. > Hi and welcome! > So I really want to help. I went on the bug tracker but it seems difficult > for me to resolve this kind of issues for the moment. > > I don't know how did you checks the issues, but just in case, you can try with this link: http://code.google.com/p/pharo/issues/list?can=2&q=&sort=difficulty&colspec… If you look on the top, you will see all the issues that are tagged as easy. Of course, for a new comer, that "easy" may even be difficut, so don't worry ;) But you can help with a lot of things, not only fixing bugs. The first thing I would advice you, is that if you want to collaborate in Pharo development, you should register in "Pharo Development" < pharo-project(a)lists.gforge.inria.fr>. This mailing list is mostly for people that just want to use Pharo. In such mailing list, you will see and keep track of all the progress, problems, etc. One of the things to do is to test for example when someone commits a change or a fix and ask for testing/feedback. Just someone to say "it works here" or "it didn't work for me" are perfect. The same when someone creates an issue. Just saying "I could reproduce" is good. Then, you can help us and make a better documentation: the website, the FAQ, Pharo By Exmple (http://pharobyexample.org/) and the last pharo book: http://book.seaside.st/ You may want to read, review, give feedback, etc. Another cool way of learning is writing unit tests. You can collaborate writing unit tests and committing them. That's all I have in mind. I hope you join! Cheers Mariano > This brings me to a really simple question: How can I help ? > > Regard, > Deathiop. > _______________________________________________ > Pharo-users mailing list > Pharo-users(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users > >

May 9, 2010