[Seaside] Brush or Component?

Sebastian Sastre ssastre at seaswork.com
Mon Jan 28 15:37:26 UTC 2008

Hi Esteban,

	to know if it's possible to make a full component you should know
how much you can control of it (will have you access to it's sources? Only
an api?). I would think in evaluating the convenience of it "wrappeability"
before anything.

	About your second question, aren't you using css/javascript external
files? Are you really planning to serve css with comanche/swazoo instead
apache, etc?

	I think in a component, problbly wrapped by a div, that just has the
css classes it needs and are defined in detail in the css file.


Sebastian Sastre

> -----Mensaje original-----
> De: seaside-bounces at lists.squeakfoundation.org 
> [mailto:seaside-bounces at lists.squeakfoundation.org] En nombre 
> de Esteban A. Maringolo
> Enviado el: Lunes, 28 de Enero de 2008 11:41
> Para: Seaside - general discussion
> Asunto: [Seaside] Brush or Component?
> Hi,
> I'm planning to wrap a date picker
> (http://www.dynarch.com/projects/calendar/), what is the best 
> approach I should take?
> Use it as a brush, make it a full featured component, or use both?
> Is it possible to automatically reference the required css/js 
> when this wrapper is used, or must be defined explicitly in 
> the containing component?
> Best regards,
> --
> Esteban A. Maringolo
> eMaringolo at gmail.com
> _______________________________________________
> seaside mailing list
> seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

More information about the seaside mailing list