Convention is very helpful. I think there is a lot of convention in Plone code. For example the approach to skinning:
* using dtml and dtml variables in the css * having a "skins" folder as a directory view * skin layers etc... * Generic setup profiles and the different xml files for registering items Perhaps the convention is sometimes understated. When I need to, I can spend the time and "decipher" these patterns, they are generally pretty logical. Unfortunately, for someone just getting started it can be overwhelming. On Tue, Jun 3, 2008 at 10:28 AM, Dylan Jay <[EMAIL PROTECTED]> wrote: > André Brown wrote: > >> My problem with Plone/Zope dev is that I really don't know where to start. >> I need some way to wrap my head around the framework so that I won't have >> to guess and hack to get something working. >> >> There also seems to be no standardization. There are a dozen ways to do >> something and it gets confusing. >> > > I think this is a good summary of most things that got said in this thread. > > It does seem that some good elemental documentation could help reduce the > "hurt" of wrapping your head around the framework. > > I'm not sure how to solve the standardization problem however. The change > is so fast that people are inventing new ways to do things before even being > aware of all the alternatives I feel. and just the framework itself has many > options for things like how to define an adaptor for instance. Coding > standards seem out of the question for a volunteer community. how do we > create standards in such a community? > > > > > _______________________________________________ > Product-Developers mailing list > [email protected] > http://lists.plone.org/mailman/listinfo/product-developers >
_______________________________________________ Product-Developers mailing list [email protected] http://lists.plone.org/mailman/listinfo/product-developers
