+10 on that idea :)
________________________________________ From: [email protected] [[email protected]] on behalf of Dale Henrichs [[email protected]] Sent: Thursday, February 23, 2012 4:30 AM To: [email protected] Subject: Re: [Pharo-project] 1.4 and forward (was Netstyle experience) Bill, I hear and appreciate your feedback about Metacello ... when one has a ConfigurationOf class for specifications there are temptations to leverage the fact that it is a class, we can end up with a proliferation of class-side short cut methods that do all sorts of interesting things. I'm hoping that the Metacello scripting API (which I am currently working on) will provide a more uniform way to load projects and reduce the demand for class-side shortcuts on the ConfigurationOf class ... Dale ----- Original Message ----- | From: "Wilhelm K Schwab" <[email protected]> | To: [email protected] | Sent: Wednesday, February 22, 2012 11:49:43 PM | Subject: Re: [Pharo-project] 1.4 and forward (was Netstyle experience) | | Stef, | | Feedback, not whining (as some might claim): this snippet illustrates | my frustration with Metacello. Note that ConfigurationOfXMLSupport | (at least in the past) requires #loadDefault vs. #load. It would be | *really* nice to have ONE incantation that always gets latest stable | releases. | | I'm trying to load a LOT of stuff, so having a stable infrastructure | would be helpful. Just saying... It might be too idealistic, but | the current situation has me capturing things that *appear* correct | and might not be (or quickly turn obsolete). Ultimately, we | probably need real packages. | | Thanks for Pharo! | | Bill | | | | | ________________________________________ | From: [email protected] | [[email protected]] on behalf of | Schwab,Wilhelm K [[email protected]] | Sent: Thursday, February 23, 2012 2:41 AM | To: [email protected] | Subject: Re: [Pharo-project] 1.4 and forward (was Netstyle | experience) | | Stef, | | From my "throw-away" 1.4 image: | | Gofer new | squeaksource: 'XMLSupport'; | package: 'ConfigurationOfXMLSupport'; | load. | (Smalltalk at: #ConfigurationOfXMLSupport) perform: | #loadDefault. | | | #( 'SIXX-Core' 'SIXX-Examples' 'SIXX-InOut-Common' | 'SIXX-InOut-Squeak' 'SIXX-ParserAdapter' | 'SIXX-Squeak' 'SIXX-Test' | ) do:[ :each | | self loadLatestPackage:each fromSqueaksource:'SIXX'. | ]. | | The above appears to have worked, and I *almost* wiped it out with a | new attempt... Pays to look sometimes. | | Bill | | ________________________________________ | From: [email protected] | [[email protected]] on behalf of | Schwab,Wilhelm K [[email protected]] | Sent: Thursday, February 23, 2012 2:27 AM | To: [email protected] | Subject: Re: [Pharo-project] 1.4 and forward (was Netstyle | experience) | | Stef, | | Reading this is encouraging. I have not forgotten about 1.4, I have | simply been heavily distracted. SIXX is a concern, as I built a lot | on top of it and (I *think*) need to get it loaded in order to | evaluate Fuel vs. it. XML parsers are a big part of life for SIXX. | Regardless of any change I might make, SIXX should be in the image | to load "legacy" data (from last month<g>). | | I will try again soon. | | Bill | | | ________________________________________ | From: [email protected] | [[email protected]] on behalf of Stéphane | Ducasse [[email protected]] | Sent: Wednesday, February 22, 2012 3:50 PM | To: [email protected] | Subject: Re: [Pharo-project] Netstyle experience (was Do not feed the | trolls) | | On Feb 22, 2012, at 1:58 PM, Norbert Hartl wrote: | | > | > Am 22.02.2012 um 13:28 schrieb Germán Arduino: | > | >> Example: xmlrpc died before to born, worked only in 1.1.1, now I | >> must find time to update it to zinc and 1.3 but with the fear | >> that again will not work in 1.4. | > | > What are your building blocks except http and xml? If you were | > working on 1.1.1 then xml parser moved quite a bit and zinc | > appeared on the scene. The changes to adopt xml parser should be | > minimal. Zinc provides a facade that mimicks backward | > compatibility. So you could have an easy start. But to be honest | > the situation is soooo much better with having zinc that you might | > save some time in development if you use zinc straight away. | > And about 1.4: Yes, it moves a lot but zinc and xml do not. Xml is | > stable since months and the change rate in zinc is also dropping. | > So you might expect them to be available until...let's say...3 | > months from now. :) Ok, just kidding, I think the will stay | > similar for quite some time. | | Exactly. | Doru got **all** the moose tools in 1.4 and some of them like glamour | rely a lot on UI changes. | I doubt that xmlrpc got any impacted on Morphic change. We do not | change XML (but the XML maintainers did) | and Zinc is just much much much better than the old system so it | should be not difficult to adapt especially if you ask. | | Stef | | | |
