May 2010 - Pharo-dev - lists.pharo.org

[Pharo-project] Set and get values from the VM AND the image
by Mariano Martinez Peck May 10, 2010

May 10, 2010

Hi folks. I need to intercept all messages. For such purpose, I modified Interpreter >> normalSend like this: normalSend "Send a message, starting lookup with the receiver's class." "Assume: messageSelector and argumentCount have been set, and that the receiver and arguments have been pushed onto the stack," "Note: This method is inlined into the interpreter dispatch loop." | rcvr | self inline: true. self sharedCodeNamed: 'normalSend' inCase: 131. rcvr := self internalStackValue: argumentCount. (self isIntegerObject: rcvr) ifFalse: [ self doSomething: rcvr. ]. lkupClass := self fetchClassOf: rcvr. receiverClass := lkupClass. self commonSend. But now, from the IMAGE side I would like to enable or disable such intercept. It would be great if from the Image side I can set a value to a boolean and read such value and ask, from the VM side. Do you know if I can do this? Should I use specialObjectArray ? If true, can you give me a hint of how to do it ? Thank you very much. Mariano

1 0

[Pharo-project] idea for a mini browser to trait
by Tristan Bourgois May 10, 2010

May 10, 2010

I'm working on trait and when there conflicts we can see the problematic methods. But if you want to see what there are into the methods where there are the problem you have to do it manually. So why not create a mini browser to: 1)see the code of the methods 2)choose the method to keep (so remove the other method) Like that you can rapidly see what method to keep or simply see the methods and could reuse the code for an overridden method. I think that's a good idea! Tristan Bourgois. -- View this message in context: http://forum.world.st/idea-for-a-mini-browser-to-trait-tp2165466p2165466.ht… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

2 1

[Pharo-project] Bug PackageInfo >> classes return also Traits
by Mariano Martinez Peck May 10, 2010

May 10, 2010

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

4 6

[Pharo-project] [update 1.1] #11348
by StÃ©phane Ducasse May 10, 2010

May 10, 2010

11348 ----- - Issue 2401: reduce: or fold: - made change events of MCPackageManager and MCRepositoryGroup a bit more useful Stef

1 0

[Pharo-project] add return its argument
by stephane ducasse May 10, 2010

May 10, 2010

if somebody wants to check that the fixes I made are ok and that at:put: and add: return their arguments Stef

4 4

[Pharo-project] Pharo and Ubuntu
by Torsten Bergmann May 10, 2010

May 10, 2010

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

3 2

[Pharo-project] Fwd: [Vm-dev] Re: Freetype plugin archive
by StÃ©phane Ducasse May 10, 2010

May 10, 2010

> 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 >

1 0

May 10, 2010

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

1 0

Re: [Pharo-project] [Pharo-users] I'm new
by Mariano Martinez Peck May 10, 2010

May 10, 2010

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 > >

2 1

[Pharo-project] Metacello questions
by Torsten Bergmann May 9, 2010

May 9, 2010

>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

2 1