On 3/14/11 8:09 PM, Dylan Jay wrote:
I think this whole thread raises a big documentation issue.
How is it that this question can still be asked? Where can we inject
documentation so there's no question that serious develop show be done
in the filesystem?
I know in the early days many developer friends being put off by
Plone/Zope being about unsource controlled, TTW code and I thought we'd
shaken that image :(
Although it kind of pains me to say this, I don't think we will be truly
rid of the problem (confusing TTW w/file system best practices) until we
have completely rid Plone of Zope2 (the "good" news is it will probably
happen within a few years; when I think it'll be at least reasonable to
expect moving Plone to the ZTK is possible).
And it's not just "documentation" that is the problem. Old vs. new
permeates any "modern" Zope2 application including Plone. All we can
really do (IMHO) until all the work (moving old to new) is done *is* to
document the status quo (e.g.
http://collective-docs.plone.org/tutorials/old-style-vs-new-style/index.html)
Alex
---
Dylan Jay
Technical Solutions Manager
PretaWeb: reducing duplication in the government web.
P: +612 80819071 | M: +61421477460 | twitter.com/djay75 |
linkedin.com/in/djay75
On 14/03/2011, at 10:06 PM, Maurits van Rees wrote:
Op 13-03-11 21:02, raharley schreef:
Thanks for your replies. I will check those out. Am I correct in what
I said
about the ZMI, that it should be avoided for Plone development in
favour of
the filesystem? Or is the filesystem advantage negated if no source code
versioning system is required?
Development of new features should indeed NOT be done in the ZMI.
Development should be done on the file system. A versioning system for
your source code is highly recommended, but not required.
When your source code is on a file system:
- you can easily share your code with others
- you can use version control
- you can see which code you actually made, instead of guessing that
it was just a few templates in the portal skins custom map and
forgetting some scripts you added in the root, or changes you made in
the portal_css
- you can test a new version of the code on your development machine
without needing a copy of the (possibly big) Data.fs
For more documentation resources I would say browse through
http://plone.org/documentation and see which documentation fits your
needs best.
Cheers,
--
Maurits van Rees
Web App Programmer at Zest Software: http://zestsoftware.nl
Personal website: http://maurits.vanrees.org/
_______________________________________________
Product-Developers mailing list
[email protected]
https://lists.plone.org/mailman/listinfo/product-developers
--
Alex Clark ยท http://aclark.net/help-me-help-plone
_______________________________________________
Product-Developers mailing list
[email protected]
https://lists.plone.org/mailman/listinfo/product-developers
