> Just curious if someone can tell me where in Seaside I can look to get a
> list of all of the available
> "html" messages I can use when rendering with Seaside.. In looking at
> the online docs for Seaside,
> it seems more like a subset of whats available instead of having
> everything there..  Even better would
> be some good examples of each possible item and typical usage.  I've
> been poking around in the
> Seaside classes, but am not sure what I should be looking for exactly..
> Can someone point me in the right direction?
>
> This came about when I was looking for the proper way to generate the
> following HTML:
>
> <p style="font-size: x-large; text-align:center;"> ... </p>
>
> I think I should be doing something like :
>
> html paragraph with: [ ... ]
>
> but am unsure about how to set specific css styles for this sort of
> case, either using the new or old Canvas API
>
> Thanks!
>
> -- Rick
>
> _______________________________________________
> Seaside mailing list
> [hidden email]
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

> Julian Fitzell wrote:
>
>> For the old API, just browse the protocol of WAHtmlRenderer.
>>
>> For the Canvas API, you need to do a little work since the methods are
>> spread out across a bunch of classes.  But most of them are on
>> WAHtmlCanvas.  Then look at the rest of the canvas class hierarchy and
>> the several tag classes in the Seaside-Canvas and Seaside-Canvas-Tags
>> system categories.
>>
> Do I need to do anything if I want to use one over the other?  In my
> case I believe I'm using the default (whatever that is).. If it helps,
> I'm using Seaside 2.5b8..
>
> -- Rick
>
> _______________________________________________
> Seaside mailing list
> [hidden email]
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

> Julian Fitzell wrote:
> > For the old API, just browse the protocol of WAHtmlRenderer.
> >
> > For the Canvas API, you need to do a little work since the methods are
> > spread out across a bunch of classes.  But most of them are on
> > WAHtmlCanvas.  Then look at the rest of the canvas class hierarchy and
> > the several tag classes in the Seaside-Canvas and Seaside-Canvas-Tags
> > system categories.
> >
> Do I need to do anything if I want to use one over the other?  In my
> case I believe I'm using the default (whatever that is).. If it helps,
> I'm using Seaside 2.5b8..

> Whatever your component returns when sent #rendererClass will be used
> as the renderer for that component.
>
> WAPresenter (a superclass of WAComponent) implements it like this:
>
> rendererClass
>     ^ WAHtmlRenderer
>
> So your components will all use the old rendering API unless you
> reimplement that method to return WAHtmlCanvas instead.  If you want
> to do this, it's probably best to make a component subclass for your
> project and then subclass that for all your components.  This is good
> practice anyway as there always seems to be behaviour you want to
> share across all your components anyway.
>

> Julian Fitzell wrote:
>
>> Whatever your component returns when sent #rendererClass will be used
>> as the renderer for that component.
>>
>> WAPresenter (a superclass of WAComponent) implements it like this:
>>
>> rendererClass
>>     ^ WAHtmlRenderer
>>
>> So your components will all use the old rendering API unless you
>> reimplement that method to return WAHtmlCanvas instead.  If you want
>> to do this, it's probably best to make a component subclass for your
>> project and then subclass that for all your components.  This is good
>> practice anyway as there always seems to be behaviour you want to
>> share across all your components anyway.
>>
> Thanks Julian -- my next question is whether or not the WAHtmlCanvas is
> sufficiently stable at this point to use it (e.g. is the design going to
> change enough to break things as I proceed down my path and perhaps
> upgrade Seaside occasionally as I go).. If there is still working being
> done that may break things that use it, I'll probably continue using
> what I've got now (WAHtmlRenderer).. Thanks!
>
> -- Rick
>
>
> _______________________________________________
> Seaside mailing list
> [hidden email]
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

> Rick Flower wrote:
>
>> Julian Fitzell wrote:
>>
>>> Whatever your component returns when sent #rendererClass will be used
>>> as the renderer for that component.
>>>
>>> WAPresenter (a superclass of WAComponent) implements it like this:
>>>
>>> rendererClass
>>>     ^ WAHtmlRenderer
>
> Ok.. Problem solved.. If I change my MyWebApp>>rendererClass definition
> to look like the one below,
> the problem disappears and everything works..
>
> rendererClass
>    "Set to either WAHtmlRenderer for old Seaside rendering or
> WARenderCanvas for new style"
>    ^ WARenderCanvas
>
> -- Rick
>
> _______________________________________________
> Seaside mailing list
> [hidden email]
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside