pier and seaside 3.0

[Nick Ager]

To answer myself the magic incantation I've arrived at for registration is:

PRPierFrame registerAsApplication: 'pier' kernel: (PRKernel new root:
(PRPage new title: 'test'; contents: 'Pier on Seaside 3.0'))

Still trying to understand how to register PRPierFrame class>>exampleBasic
and exampleDocumentation. I'll see if I get anywhere this afternoon...

Nick

2010/1/5 Nick Ager <nick.ager at gmail.com>

> Hi Jan,
>
> Thanks that was exactly what I was after.
>
> Pier and Magritte loaded with a few errors (see later), then I registered
> Pier with:
>     PRPierFrame registerAsApplication: 'pier' kernel: PRKernel new
>
> When I then go to browse localhost:8080/pier I receive the error:
>    MNU: receiver of viewCommandClass is nil
>
> Digging into the call-stack originating at PRPierFrame>>initialRequest the
> structure passed to PRContext>>kernel:structure: is nil which originates
> from a call to PRKernel>>root returning nil. Any thoughts anyone?
>
> BTW the load errors:
> "FileList2 is Undeclared", in MAFileMorph - doesn't seem too concerning as
> I'm only interested in the seaside bindings.
> I ignored the error: "Pier-Core depends on PRPackage class>>pierTestsModel"
> PRCommandTest>>testDate(WAPlatform is undefined)
> PRCommandTest>>testTimestamp (WAPlatform is Undeclared)
> PRPersistencyTest>>testMutexForked(WAPlatform is undefined)
> PRSegmentPersistency>>cleanupSeaside (WAEntryPoint is Undeclared)
>
> Should I be concerned by any of these load errors?
>
> Nick
>
> 2010/1/4 Jan van de Sandt <jvdsandt at gmail.com>
>
>  Hello Nick,
>>
>> I use the following "Gofer code" to load Magritte and Pier into a Seaside
>> 3 image. Magritte is a prerequisite for Pier:
>>
>> "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';
>> 	package: 'Pier-Tests-Model';
>> 	package: 'Pier-Seaside';
>> 	package: 'Pier-Pharo-Seaside';
>>
>>
>>
>>
>> 	package: 'Pier-Security';
>> 	package: 'Pier-Pharo-Persistency';
>> 	package: 'Pier-Tests-Security';
>> 	load.
>>
>>
>> Jan
>>
>>
>>
>> On Mon, Jan 4, 2010 at 5:27 PM, Nick Ager <nick.ager at gmail.com> wrote:
>>
>>> Happy New Year to the list.
>>> I've been developing a site using vanilla seaside 3.0a5, and have belated
>>> released that there's much functionality in base Pier and the add-ons which
>>> would save me significant time. From what I can gather from a brief search
>>> of the list there is an early port to 3.0, though I've struggled to load it
>>> into my image. Is there a load script I can use for 3.0? Is it really
>>> sensible to try an early 3.0 port when I'm still struggling to get to grips
>>> with the basic concepts - would I be better off using 2.8 and revert my
>>> jQuery code to prototype/scriptaculous?
>>> Thanks Nick
>>>
>>> _______________________________________________
>>> Magritte, Pier and Related Tools ...
>>> https://www.iam.unibe.ch/mailman/listinfo/smallwiki
>>>
>>
>>
>>
>> _______________________________________________
>> Magritte, Pier and Related Tools ...
>> https://www.iam.unibe.ch/mailman/listinfo/smallwiki
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.iam.unibe.ch/pipermail/smallwiki/attachments/20100105/4f2cf38c/attachment.html>