Re: can /skins/product_public be removed?

Reinout van Rees wrote:
> 
> Hi all,
> 
> Archgenxml generates both a /skins/productname/ and a
> /skins/productname_public/ directory.
> 
> * I've never used the public directory myself.
> * It looks like a relic from old times.
> * None of the newer products seem to use it.
> 
> => OK to strip that out of current archgenxml?
> 

+1 - it's very silly. It makes sense in a few cases, because the _public bit
puts itself in a different part of the skin layer (IIRC it's meant for cases
where your product overrides existing page templates - but you really ought
to be using a separate product for that anyway). Maybe have it in as an
option (or it's easy enough to add it back yourself anyway)

While you're at it, can you make sure AGX doesn't do

from Products.CMFPlone.PloneUtilities import ToolInit

since PloneUtilities spits a deprecation warning. I think it's in
CMFPlone.utils now.

Martin
--
View this message in context: http://www.nabble.com/can-skins-product_public-be-removed--t1555355.html#a4225269
Sent from the Archetypes - devel forum at Nabble.com.



-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642