Re: [Zope-dev] ZTK TTW Content Types Project Wiki
So I am starting a project to build content types through the web using the ZTK.
Here is the url.
http://specialtyjobmarkets.com/Wikis/LozinskiClasses/FrontPage
Hi Christopher, I understand where you are. Four years ago, I made the transition from Zope2 to Zope3. It was about 12 months before the new technologies felt comfortable. In particular, my biggest irritation was Zope3 heads who had never used ZClasses and TTW development bad mouthing it. Recently, I have gravitated to Plone. There are a number of tools in Plone that demonstrate an interest in RAD in general and TTW as a RAD mechanism where appropriate. PloneFormGen has been improved recently. It is great for creating forms for creating content objects. ArchGenXML can generate the structure of complex applications. If you do it right, you can end up just writing the Python Code and File system is better in my opinion for that due to the debugger. However, it is tricky to get setup with argo uml in the first place. Plomino.net has a wonderful product that is very like python TTW development. It is not consistent with the Zope idioms, but it doesn't need to be because Plone users don't know them. It is very fast to develop and has good forms. I urge you to try it out. Don't be too harsh on Grok/Dexterity. Dexterity has worked out how not to repeat the definitions in interfaces, forms and content objects. It also produces an application with suprisingly little redundant code. I urge you to try it out. The benefits are of course quick turn around, version control, testability and the debugger. I made some edits on your wiki. Good Luck in your project Kevin
Thank you for the recent feedback. It is nice to know that people care. I have added a section reviewing the competing technologies, and why they are not right for my needs. I have laid out the technical proposal, a bit high level, I need to make it more specific. For example I need to add what is the interface that is needed by Factory objects. The great thing about ZTK is that somewhere that is documented.
I have added a section on my software philosophies. I am sure that it will drive some people nuts, but others will agree with it. Allow me to have my point of view. I also respect your point of view.
I do get a bunch of people who say I am nuts. So positive feedback would be most appreciated.
And of courses it is an anonymous wiki. I am using the ZWiki software. You are invited to add your comments. I have no idea what you will say, but I am sure it is useful.
Regards Chris _______________________________________________ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Don't be too harsh on Grok/Dexterity. Dexterity has worked out how not to repeat the definitions in interfaces, forms and content objects. It also produces an application with suprisingly little redundant code. I urge you to try it out. The benefits are of course quick turn around, version control, testability and the debugger.
Also note that (the Plone integration for) Dexterity allows you to create
types entirely through-the-web. This can then be meaningfully transitioned to filesystem development without forcing you to start from scratch. The big, big problem with any kind of TTW development is that it usually breaks down badly when you move your code to a production server and then need to continue development in a separate environment. Code and configuration stored in a database is difficult to deploy and merge when the same database holds live data and content. The same problem exists where more than one developer needs to collaborate. Without source files and source control, it's impossible to give each developer their own sandbox. Martin
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Martin Aspeli wrote:
Don't be too harsh on Grok/Dexterity. Dexterity has worked out how not to repeat the definitions in interfaces, forms and content objects. It also produces an application with suprisingly little redundant code. I urge you to try it out. The benefits are of course quick turn around, version control, testability and the debugger.
Also note that (the Plone integration for) Dexterity allows you to create types entirely through-the-web. This can then be meaningfully transitioned to filesystem development without forcing you to start from scratch.
The big, big problem with any kind of TTW development is that it usually breaks down badly when you move your code to a production server and then need to continue development in a separate environment. Code and configuration stored in a database is difficult to deploy and merge when the same database holds live data and content. The same problem exists where more than one developer needs to collaborate. Without source files and source control, it's impossible to give each developer their own sandbox.
We have this discussion in slighty various forms with Christopher every other year...I think it does not help much repeating the same arguments each year again...kind of hopeless if you ask me *shrug* - -aj -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQGUBAEBAgAGBQJMh26XAAoJEADcfz7u4AZjXvsLwJlCEmfSiTyi9rBxztfUv2dK qClILApNqVZSMAYDYgulTqrVpmujrGeMphCfbKJp/p8AOXogh+1e2T5LJCV+rhm1 NMGfVKxNgp2M28MOWKuYICrTgaQXOzjas/tN/1Lv2nxt1q/SPs1kjue6rcdMbi7i fOfk/oTTVU5WFTHdZCHlVJdydTMNxbtFuf/wZ2wzFxNz5Rkqxj9YdZB7eBoYlONx Q1htycNDAgejQJ0uvvljnw8K3J1iixEpQI9OShmH4nstxQMj09DPRb2PKIaqRXGf WZiiCSIgteWPMWnh8slYYaEXtJDS3zTKQX45o7xYWRPd5pdHpbTyhHuVNhpn+gpV kbjOaLGBzYv9o1Modwgtb6uH1ysX2cjZEQqESjt/NL8Kzjk+CCeAHtcxlyD0Sqa2 nD7cZg+OivYgoOKIECuVleDpAY+XQwFp4fTLAovziZRbAEsSyhN2qvetGIPG8QcM dqock3W78YE98ZuTqOyNekzWO573GZc= =iKmj -----END PGP SIGNATURE-----
participants (3)
-
Andreas Jung -
Kevin Gill -
Martin Aspeli