|
osdir.com mailing list archive |
|
Subject: Re: Re: Five under Windows - msg#00002List: web.zope.z3base.fiveJeroen Janssen wrote: Martijn Faassen wrote: Perhaps you could try this out. If you could write up a document about how it all can be made to work on windows we'd be happy to check it into our repository! That sounds ok to me, I'll see what I can do. Sorry for the lack of progress here, but it's been a 'bit' busy at my work the past week(s). However I'm still planning on finishing it :) That's great to hear. I got busy myself so I understand. :) Regards, Martijn Thread at a glance:
Previous Message by Date: click to view message previewRe: Five under WindowsJeroen Janssen wrote: Martijn Faassen wrote: Perhaps you could try this out. If you could write up a document about how it all can be made to work on windows we'd be happy to check it into our repository! That sounds ok to me, I'll see what I can do. Sorry for the lack of progress here, but it's been a 'bit' busy at my work the past week(s). However I'm still planning on finishing it :) --- Jeroen Next Message by Date: click to view message previewRe: r5538 - z3/Five/branch/dreamcatcher-cmf-compat-branchSidnei, +def skinDirectory(_context, directory, module, for_=None, + layer='default', permission='zope.Public'): ... +class ISkinDirectoryDirective(Interface): + """Register each file in a skin directory as a resource + """ I know that it is (sadly) common practice in the CMF world to call skin layers simply 'skins', but Zope 3 requires a good understanding of the two separate terms, otherwise people won't understand what's going on and think that Zope 3 does it all different, but it doesn't. What you really mean here is a _skin layer_, so I would recommend calling this directive five:skinLayerDirectory or simply five:layerDirectory... Btw, the docstring of the directive schema is incorrect. Currently, all the handler does is register every page template file as a browser page... ;) Philipp Previous Message by Thread: click to view message previewRe: Five under WindowsJeroen Janssen wrote: Martijn Faassen wrote: Perhaps you could try this out. If you could write up a document about how it all can be made to work on windows we'd be happy to check it into our repository! That sounds ok to me, I'll see what I can do. Sorry for the lack of progress here, but it's been a 'bit' busy at my work the past week(s). However I'm still planning on finishing it :) --- Jeroen Next Message by Thread: click to view message previewRe: r5538 - z3/Five/branch/dreamcatcher-cmf-compat-branchSidnei, +def skinDirectory(_context, directory, module, for_=None, + layer='default', permission='zope.Public'): ... +class ISkinDirectoryDirective(Interface): + """Register each file in a skin directory as a resource + """ I know that it is (sadly) common practice in the CMF world to call skin layers simply 'skins', but Zope 3 requires a good understanding of the two separate terms, otherwise people won't understand what's going on and think that Zope 3 does it all different, but it doesn't. What you really mean here is a _skin layer_, so I would recommend calling this directive five:skinLayerDirectory or simply five:layerDirectory... Btw, the docstring of the directive schema is incorrect. Currently, all the handler does is register every page template file as a browser page... ;) Philipp Loading Comments...
|
|
