Stef, New to migrate (below). It works!!! One "bad" thing is the hard-coded version, but it did indeed work as advertised. Thanks!!!! I clearly need to use the mirror in my gofer calls - that probably explains a lot of trouble I've had (hindsight is a wonderful thing). Sleep calls. Bill loadCitezen "1-10 - load Citezen if not installed. 4-10 - this appears to load Seaside too. 6-10 - will no longer load Seaside. 2-12 - force same." Smalltalk at:#CZAuthor ifPresent:[ :aClass | ^self. ]. Gofer new url:'http://ss3.gemstone.com/ss/citezen/'; package:'ConfigurationOfCitezen'; load. ( (Smalltalk at:#ConfigurationOfCitezen ) project version:'0.8') load: { 'NoWeb'}. " Migrate default loadCitezen. Migrate default loadOSProcess. Migrate default loadSeaside. " ________________________________________ From: pharo-project-bounces@lists.gforge.inria.fr [pharo-project-bounces@lists.gforge.inria.fr] on behalf of Schwab,Wilhelm K [bschwab@anest.ufl.edu] Sent: Thursday, February 23, 2012 3:10 PM To: Pharo-project@lists.gforge.inria.fr Subject: Re: [Pharo-project] 1.4 and forward (was Netstyle experience) Stef, I can't do it this minute, but I WILL try it - what else can a member the community do? :) I'm optimistic. THANKS!!! Bill ________________________________________ From: pharo-project-bounces@lists.gforge.inria.fr [pharo-project-bounces@lists.gforge.inria.fr] on behalf of Stéphane Ducasse [stephane.ducasse@inria.fr] Sent: Thursday, February 23, 2012 3:02 PM To: Pharo-project@lists.gforge.inria.fr Subject: Re: [Pharo-project] 1.4 and forward (was Netstyle experience) ok here is what I did I took the latest nautilus green version but it will work with the latest pharo Then I took the configurationOfCitezen from MCHttpRepository location: 'http://ss3.gemstone.com/ss/citezen/' user: '' password: '' and I did (ConfigurationOfCitezen project version: '0.8') load: { 'NoWeb'}. and it works. Can you give a try? Stef
Stef,
I will gladly try, though I thought I was using the up-to-date config. Is there maybe a stale copy in the citezen folder? *THAT* might have fooled me and caused the glitch. Thanks for the prod. I'll try again soon.
Bill
________________________________________ From: pharo-project-bounces@lists.gforge.inria.fr [pharo-project-bounces@lists.gforge.inria.fr] on behalf of Stéphane Ducasse [stephane.ducasse@inria.fr] Sent: Thursday, February 23, 2012 11:54 AM To: Pharo-project@lists.gforge.inria.fr Subject: Re: [Pharo-project] 1.4 and forward (was Netstyle experience)
On Feb 23, 2012, at 10:00 AM, Schwab,Wilhelm K wrote:
Stef,
This:
Gofer new squeaksource:'MetacelloRepository'; package:'ConfigurationOfCitezen'; load. ( (Smalltalk at:#ConfigurationOfCitezen ) project version: #stable) load: { 'NoWeb'}.
is loading Seaside. Did I do something wrong?
does not seem so this is really strange because I'm hacking in and on top of citizen in this moment and I did get problem.
Further, I've hit dependency warning (e.g. a 45 minute?? build stops dead in its tracks). Complaints so far over Transcript streams and Text Morph something or other. It finally bound up over preferences (missing message - detail later). I tried a separate load of Seaside, but it's complaining about preferences out of the gate.
For the "you're just complaining" crowd, I'm simply reporting what is happening. I would very much like to see Jenkins build a 1.4 and then a 1.4+Seaside.
Ok I will give a try because we migrated citizen to ss30 but we did not republished the configuration in MetacelloRepository. can you give a try?
Bill
________________________________________ From: pharo-project-bounces@lists.gforge.inria.fr [pharo-project-bounces@lists.gforge.inria.fr] on behalf of Schwab,Wilhelm K [bschwab@anest.ufl.edu] Sent: Thursday, February 23, 2012 3:21 AM To: Pharo-project@lists.gforge.inria.fr Subject: Re: [Pharo-project] 1.4 and forward (was Netstyle experience)
Norbert,
Thanks for the suggestion, but I really need to get things loaded so I can load an even bigger pile of code that I have written. There is also the question of how to capture all of the legacy data; it's not as easy as one might think, as some things are "in the wild."
I've really used this system, and could simply hang at 1.1.1 for a long time - I'm trying to do better than that.
Bill
________________________________________ From: pharo-project-bounces@lists.gforge.inria.fr [pharo-project-bounces@lists.gforge.inria.fr] on behalf of Norbert Hartl [norbert@hartl.name] Sent: Thursday, February 23, 2012 3:07 AM To: Pharo-project@lists.gforge.inria.fr Cc: Pharo-project@lists.gforge.inria.fr Subject: Re: [Pharo-project] 1.4 and forward (was Netstyle experience)
Am 23.02.2012 um 08:27 schrieb "Schwab,Wilhelm K" <bschwab@anest.ufl.edu>:
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>).
Bill,
is your real test to use sixx on 1.4? If you just want to test 1.4 then export your data with fuel from an 1.3 image and back into a 1.4 one. This should be pretty easy.
Norbert
________________________________________ From: pharo-project-bounces@lists.gforge.inria.fr [pharo-project-bounces@lists.gforge.inria.fr] on behalf of Stéphane Ducasse [stephane.ducasse@inria.fr] Sent: Wednesday, February 22, 2012 3:50 PM To: Pharo-project@lists.gforge.inria.fr 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