This was good to hear, as I have been having a pretty rough time building images from
scratch recently.
I have made some changes to WAAdmin to stop bogus errors arising in >>register: at:
than often relate to register:asApplicationAt: becuase I have a whole set of classes for
which I run class-side >>initialization
as a final step before
WAAdmin clearAll.
WAEnvironment initialize.
WAEnvironment reloadApplications.
WAKom startOn: 18080.
There are also many places where OmniBrowser is broken or where classes in O2 have
instances being sent messages by OB - I have not even bothered debuggin those as they do
not generally impede finding what is needed to get a base image (Squeak 3.10) or Pharo
RC-1 (pharo1.0-10502-rc1web09.12.2) to run Seaside 3.0 on Win XP SP3
None of the web app examples would run in my last build (Jan 7) - most impacted by changes
that seemed intended for Pier ...
For my non-HTML web markup I was concerned to see htmlEncoder move up a level to the tag
parent of WAHtmlDocument and concerned by the state of path methods in WAUrl ( I get there
due to walkbacks occurring in a few places )
I have not yet had a script that worked from top to bottom: the last problem was with the
script calling an install.st to fileIn so I now pull in Installer on my own first BUT that
will not run error-free until I pull in Grease ...
Here is my last list of classes where I comment out the class-side initialize until I have
all nec loaded, then uncomment all of those and let fire
WAVersionUploader initialize.
WAWalkbackErrorHandler initialize.
WADevelopmentConfiguration initialize.
WAWalkbackErrorHandler initialize.
WADispatcherBrowser initialize.
WAStatus initialize.
WAVNCController initialize.
SUAllTests initialize.
SULightboxTest initialize.
WAAllTests initialize.
WABrowser initialize.
WACounter initialize.
WAExampleBrowser initialize.
WAMultiCounter initialize.
WARenderCanvas initialize.
Here is my make-shift get-the-classes to fileIn variant for WAAdmin
| path dispatcher |
path := aString subStrings: '/'.
dispatcher := path allButLast
inject: aDispatcher
into: [ :result :each |
result handlers notNil
ifTrue: [
result handlers
at: each
ifAbsent: [ result register: WADispatcher new at: each ] ]
ifFalse: [ result register: WADispatcher new at: each]
].
^dispatcher register: aRequestHandlerClass new at: path last
--- On Sat, 1/9/10, Lukas Renggli <renggli(a)gmail.com> wrote:
From: Lukas Renggli <renggli(a)gmail.com>
Subject: Re: 3.0 merge status
To: "Magritte, Pier and Related Tools ..." <smallwiki(a)iam.unibe.ch>
Date: Saturday, January 9, 2010, 9:32 AM
Thank you for these scripts. I use
them to load the new code into
Seaside 3.0 images, see
<http://hudson.lukas-renggli.ch/job/Seaside%203.0/>.
This job builds a Seaside 3.0, saves it; loads Magritte 2
into that
image, saves it; and finally loads Pier 2 and saves it. It
also runs
the tests and generates a report. I haven't yet tried the
actual
images, but this should make it easier to see what works
and what is
broken.
Lukas
2010/1/8 Nick Ager <nick.ager(a)gmail.com>om>:
I reviewed all my merges and discovered I'd
lost
changes in:
PRPierFrame>>initialRequest
PRViewCommand>>initialRequest
MAOneToManyComponent>>add
With the corrections in place, Pier appears to working
once again. There are
a couple of anomalies - the Pier logo doesn't
appear
on the home screen and
I received one walkback while clicking around.
I'll
investigate these
problems later. I've also yet to look at any
add-ons
including the
Pier-Blog.
I've loaded the code into a fresh seaside3.0a5 image
(with updated Gofer)
and the code loads cleanly.
For reference the load script I used was:
"Load Magritte for Seaside 3"
Gofer new
renggli: 'magritte2';
package: 'Magritte-Model';
package: 'Magritte-Pharo-Model';
package: 'Magritte-Tests-Model';
package: 'Magritte-Tests-Pharo-Model';
package: 'Magritte-Seaside';
package: 'Magritte-Pharo-Seaside';
package: 'Magritte-Morph';
load.
"Load Pier for Seaside 3"
Gofer new
renggli: 'pier2';
package: 'Pier-Core';
package: 'Pier-Pharo-Core';
package: 'Pier-Model';
package: 'Pier-Pharo-Model';
package: 'Pier-Tests-Model';
package: 'Pier-Seaside';
package: 'Pier-Pharo-Seaside';
package: 'Pier-Security';
package: 'Pier-Pharo-Persistency';
package: 'Pier-Tests-Security';
load.
PRPierFrame registerAsApplication: 'pier' kernel:
(PRKernel new root:
(PRPage new title: 'test'; contents:
'Pier on Seaside
3.0'))
_______________________________________________
Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki
--
Lukas Renggli
http://www.lukas-renggli.ch
_______________________________________________
Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki