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

Re: [Pharo-project] [Metacello] Re: [BetaTesting] [ANN] Pharo-1.1-11367-Beta1dev10.05.1

by Dale Henrichs

Mariano, I'm not sure I am following ... What Help package are you referring to? Dale ________________________________________ From: metacello(a)googlegroups.com [metacello(a)googlegroups.com] On Behalf Of Mariano Martinez Peck [marianopeck(a)gmail.com] Sent: Friday, May 21, 2010 1:36 AM To: Pharo Development; metacello(a)googlegroups.com Subject: [Metacello] Re: [Pharo-project] [BetaTesting] [ANN] Pharo-1.1-11367-Beta1dev10.05.1 On Fri, May 21, 2010 at 8:29 AM, Torsten Bergmann <astares(a)gmx.de<mailto:astares@gmx.de>> wrote: >Thanks Torsten. I wasn't aware of such package. So..for next release I will >add a project reference from ConfigurationOfPharo to >ConfigurationOfHelpSystem >It is not clear for me where Help packages should be hosted. For >example, ScriptManager host its own Help package in its own repository. >But Metacello is in the HelpSystem repository. The book for Metacello was just a demo - typically I would expect them to be in the same repo as the code. I dont want a "docu only" repo - if it is close to the code it will be easier to know and maintain it. 100% agree. Dale, do you think it is worth to take the Help package from HelpSystem repository and put it in Metacello repo ?

May 21, 2010

Re: [Pharo-project] Cross-fork Metacello configurations

by Miguel Enrique CobÃ¡ Martinez

El vie, 21-05-2010 a las 09:13 -0700, Sean P. DeNigris escribiÃ³: > I created a Squeak/Pharo SSpec, which puts the fork-specific world menu code > into a Platform package. > > As I work on the config, I came up against Pharo using Object as a subclass, > but the Squeak Inbox requiring (because of the browser tool) > MetacelloConfiguration. > > What would be the best/easiest way to deal with this? > > If the configs have to be forked, then Metacello really loses value (i.e. > #squeak and #pharo). And, I do a lot of work in both forks, so it would be > a shame to pick one to upload to and not share work that has already been > done with half the users. That was one of the problems of the Configuration Package proposed by Andreas. Promotes copy&paste of configurations (bad bad) and in the long term forks and completely rework to create configurations for Squeak and a different (although similar) for Pharo. As you say, it doesn't matter that Metacello is capable of installing cross-platform packages. With independently created configurations for the same packages, is has been stole of its usefulness and is discouraging Pharo users that have developed ConfigurationOfXXX that worked both in Squeak and Pharo in the past. > > Thanks. > Sean > -- Miguel CobÃ¡ http://miguel.leugim.com.mx

May 21, 2010

[Pharo-project] [update 1.1] #11368

by StÃ©phane Ducasse

11368 ----- - Issue 737: part of -> WeakArray>>isFinalizationSupported cleaning. Thanks henrik - Issue 516: file exists enh. Thanks henrik - Issue 2447: menu item not showing up. Thanks alain - Issue 1709: Enhanced TextDiffBuilder from squeak trunk. Thanks henrik This is cool to have you around :) I mean really cool. Stef

May 21, 2010

[Pharo-project] Cross-fork Metacello configurations

by Sean P. DeNigris

I created a Squeak/Pharo SSpec, which puts the fork-specific world menu code into a Platform package. As I work on the config, I came up against Pharo using Object as a subclass, but the Squeak Inbox requiring (because of the browser tool) MetacelloConfiguration. What would be the best/easiest way to deal with this? If the configs have to be forked, then Metacello really loses value (i.e. #squeak and #pharo). And, I do a lot of work in both forks, so it would be a shame to pick one to upload to and not share work that has already been done with half the users. Thanks. Sean -- View this message in context: http://forum.world.st/Cross-fork-Metacello-configurations-tp2226383p2226383… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

May 21, 2010

Re: [Pharo-project] Where should I put ConfigurationOfGLMorphic

by Henrik Johansen

Don't put it in the same package? Doesn't really make sense to have the configuration for how to load a package be part of the package itself... (though, it does make sense to keep them in the same repository) Cheers, Henry Den 21. mai 2010 kl. 17.52 skrev Javier PimÃ¡s <elpochodelagente(a)gmail.co m>: > Wow, this is brilliant! it it'd have been of great help yesterday ;) > I gave it a quick look an there's one thing I still don't > know how to do. I need to put ConfigurationOfGLMorphic inside > GLMorphic package, but as it isn't in any GLMorphic-* category it > isn't automatically detected by monticello. I don't see any button > to add a class or category to the package. What should I do? > > thanks, > javier. > > 2010/5/21 Mariano Martinez Peck <marianopeck(a)gmail.com> > > > 2010/5/21 Javier PimÃ¡s <elpochodelagente(a)gmail.com> > Hi, I made a very basic ConfigurationOfGLMorphic that manages it's > dependency on FFI. Where should I upload this configuration now? > > > Hi Javier. Here I attach a first not-yet-draft chapter of Metacello. > There you will find the answer ;) (feedback is welcome!!!) > > But in sumary, you should commit to the repository of the same > project. In your case, as Igor said, to GLMorphic repository. > There you can commit your development changes to the configuration. > Once you have a released version, you just copy it to > MetacelloConfiguration repository. > > Cheers > > Mariano > > > > Regards, > Javier. > > -- > Javier PimÃ¡s > Ciudad de Buenos Aires > > _______________________________________________ > 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 > > > > -- > Javier PimÃ¡s > Ciudad de Buenos Aires > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

May 21, 2010

Re: [Pharo-project] Where should I put ConfigurationOfGLMorphic

by Javier PimÃ¡s

Wow, this is brilliant! it it'd have been of great help yesterday ;) I gave it a quick look an there's one thing I still don't know how to do. I need to put ConfigurationOfGLMorphic inside GLMorphic package, but as it isn't in any GLMorphic-* category it isn't automatically detected by monticello. I don't see any button to add a class or category to the package. What should I do? thanks, javier. 2010/5/21 Mariano Martinez Peck <marianopeck(a)gmail.com> > > > 2010/5/21 Javier PimÃ¡s <elpochodelagente(a)gmail.com> > >> Hi, I made a very basic ConfigurationOfGLMorphic that manages it's >> dependency on FFI. Where should I upload this configuration now? >> >> > Hi Javier. Here I attach a first not-yet-draft chapter of Metacello. There > you will find the answer ;) (feedback is welcome!!!) > > But in sumary, you should commit to the repository of the same project. In > your case, as Igor said, to GLMorphic repository. > There you can commit your development changes to the configuration. Once > you have a released version, you just copy it to MetacelloConfiguration > repository. > > Cheers > > Mariano > > > > >> Regards, >> Javier. >> >> -- >> Javier PimÃ¡s >> Ciudad de Buenos Aires >> >> _______________________________________________ >> 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 > -- Javier PimÃ¡s Ciudad de Buenos Aires

May 21, 2010

Re: [Pharo-project] UI Builder

by StÃ©phane Ducasse

no idea. Indeed this was a bad idea to remove it. Stef On May 21, 2010, at 5:29 PM, Torsten Bergmann wrote: > What is the state of the UI builder? When can we expect a > version that is compatible with Pharo 1.1.? > > Unfortunately the SqS project was removed ... so > no one can follow progress... > > 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 21, 2010

[Pharo-project] UI Builder

by Torsten Bergmann

What is the state of the UI builder? When can we expect a version that is compatible with Pharo 1.1.? Unfortunately the SqS project was removed ... so no one can follow progress... Thx T. -- GRATIS fÃ¼r alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01

May 21, 2010

Re: [Pharo-project] Fwd: Re: Decoding bug with XMLParser ?

by Alexandre Bergel

> While in Pharo it's: > (Unicode value: 8230) codePoint. "===> 1069555750" > (Character value: 1069555750) charCode. "===> 8230" > (Character value: 1069555750) leadingChar. "===> 255" Thanks for you all for your explanation. Therefore, the following test goes green: -=-=-=-=-=-=-=-=-= exampleEncodedXML ^'<?xml version="1.0" encoding="UTF-8"?> <test-data>…</test-data> ' testDecodingCharacters | xmlDocument element | xmlDocument := XMLDOMParser parseDocumentFrom: self exampleEncodedXML readStream. element := xmlDocument firstTagNamed: #'test-data'. self assert: element contentString first charCode = 8230. self assert: element contentString first leadingChar = 255. self assert: element contentString first codePoint = 1069555750 -=-=-=-=-=-=-=-=-= What we first thought as a bug, is plain expected behavior. Fixed in XML-Parser-Alexandre_Bergel.76 Cheers, Alexandre

May 21, 2010

Re: [Pharo-project] [squeak-dev] Excluding an autogenerated methods from MC package. How?

by Lukas Renggli

I would put them into an extension category of a non-existing package like *generated. Lukas On 21 May 2010 14:49, Igor Stasenko <siguctua(a)gmail.com> wrote: > Hello all, > > say, i have some methods having automatically generated sources, and i > want them to be > not included into a package, since they are generated/refreshed > anyways once package loaded. > Is there a way to tell MC > 1. to exclude such methods, when writing a package > 2. to ignore any changes to these methods and don't mark a package as dirty > ? > > -- > Best regards, > Igor Stasenko AKA sig. > > -- Lukas Renggli www.lukas-renggli.ch

May 21, 2010