[Building Sakai] Portal NEO Prefix

[Steve Swinsburg]

Putting aside the 'tools are wrong argument' (which I agree with, see
below.) I still don't see a need for the automatic prefixing of skins in
the the portal code.

It seems this code is catering for the sites that may have properties for
their own skins defined, which can easily be taken care of at either
upgrade time or at any time afterwards, with a line of SQL to upgrade them.

Re tools: Note that the Wicket way of rendering CSS has been around since
2.5 and worked since then. I'm not saying its the right way, and I'll look
at changing tools so its done via that request attribute, but its worked
for a long time. I am sure that its not only Wicket tools that manually
include the skin css though. Also the requirement to inline the body onload
will probably conflict with tools that use a jQuery document ready.

cheers,
Steve



On Mon, Mar 18, 2013 at 5:25 AM, David Adams <da1 at vt.edu> wrote:

> > These Archetypes were built when folks were not looking too closely -
> > we had no chief architect
>
> Do we have a chief architect now?
> _______________________________________________
> sakai-dev mailing list
> sakai-dev at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>
> TO UNSUBSCRIBE: send email to
> sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of
> "unsubscribe"
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20130318/18386e39/attachment.html