Hi Stephen, Stephen Colebourne wrote on Wednesday, March 15, 2006 1:12 AM:
> Progress to remove commons-build seems to be moving along > nicley. So far > at least [lang], [io], [primitives], [collections], [codec], [logging] > and [betwixt] are done, plus [pool] unpublished. > > > I believe that I may have an even sneakier way to handle the > shared menu > part however. This is a medium term idea... > > We could write a piece of javascript that adds the menu items to the > page dynamically after the page is loaded. The script could be hosted > online and referenced by http. Thus one change to the > javascript would > affect all websites without regenerating them (as the CSS > will do now). > > Unfortunately, I don't have the time to investigate or play with this > right now, but if anyone else wants to feel free! Don't forget, that some user's are surfing without JavaScript. This is even more true in corporate environments. E.g. in my company there's a filter installed in the firewall (SurfinGate from FinJan), that strips off "suspicious" JavaScript. > In the meantime, I suggest continuing with the current > process to remove > commons-build as that seems to be working fine so far. - Jörg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
