[Seaside] Front-End developer coordination

Norbert Hartl norbert at hartl.name
Sat May 25 07:04:59 UTC 2019



> Am 24.05.2019 um 21:09 schrieb BrunoBB <smalltalk at adinet.com.uy>:
> 
> Hi,
> 
> We are doing a project with Seaside and there is a Front-end developer
> mostly for CSS creation.
> 
> How do you approach this problem (coordination between Seaside developer and
> frontend developer) ?
> 
> I mean in Seaside the HTML code is generated but it has to do some
> references to the CSS created by the frontend developer.
> 
> One approach can be:
> 1) Add css class names (the css does no exist yet) in Seaside code (html div
> class: 'to-be-developed-by-frontend-dev').
> 2) The frontend create the CSS file for classes in 1).
> 
> Very simple but i wonder how do you solved this problem ?
> 
You are using component like things in the backend and frontend. In the normal case seaside component will render something like a div defining the space for this component. So give it a class attribute containing information about the component like navigationBar or orderForm. This can be used in CSS to style according to the backend component. See it as an interface. The backend defines functional name hierarchy that the frontend can take to implement a view on it. Nowadays I would have a look into W3C components to save you from trouble with relative CSS. W3C components build isolated views of components.

Norbert
> regards,
> bruno
> 
> 
> 
> 
> 
> --
> Sent from: http://forum.world.st/Seaside-General-f86180.html
> _______________________________________________
> seaside mailing list
> seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside



More information about the seaside mailing list