Ploneã«å¤–部モジュールインストール
Originally from del.icio.us/tag/plone by
Ploneã«å¤–部モジュールインストール
Originally from del.icio.us/tag/plone by kmatsumur
PythonScript ã§æ¨™æº–以外ã®ãƒ¢ã‚¸ãƒ¥ãƒ¼ãƒ«ã‚’使ㆠ— takanory.net
Originally from del.icio.us/tag/plone by kmatsumur
In response to optilude saying “Plone 3 Rocks Hard” I feel compelled to add that developing with Plone 3.0 is (at least) just as enjoyable. Witsch and I have migrated a client project based on Plone 2.1 to 3.0 (trunk) ca. eight weeks ago and have been working with the Plone 3.0 API on a daily basis ever since. And while we did pay some penalty by aiming at a moving target that penalty has well paid off by the niceties we’ve been enjoying since.
From a developer point of view that change is perhaps not as dramatic as for an end user, as things like the Zope 3 component architecture (via Five), Generic Setup, membrane etc have been available already since 2.1. It’s more the fact that Plone itself uses these technologies now to a much larger degree, i.e. their benefits are no longer limited to your own code. Just take a look at the plone.* namespace for instance, that now makes up the core of what is Plone 3 (as opposed to just CMFPlone which otherwise would undoubtedly have become dangerously bloated and monolithic).
By using Zope 3 components Plone is becoming a very rich development framework where you as a developer can ‘mix and match’ and chose from a wide array of components and adapt them for your needs without having to bother with (much) of the (Zope 2) baggage that comes with using a full-grown CMS. (instead of using some lighter weight framework such as Django, Turbogears or Ruby on Rails).
On a gut level it comes down to this for me: both the code that I am writing as well as the pages that are generated from it have become lighter, more readable and more elegant. I make less compromises in my daily work and the satisfaction that I get from it has risen drastically during the past six weeks. I’d ten times rather risk being labelled as a fanboy than shutting up about how cool Zope 3 and Plone 3.0 are. And now back to work (yay!)…
Tom Lazar: Developing with Plone 3 Rocks Hard
Originally from Planet Plone by Tom Lazar
Dear Plonewars.com May 14th, 2007 Your website is pointless. It has a stupid name. It looks lame. It…
Your website is pointless. It has a stupid name. It looks lame. It contains no useful information whatsoever. Your trackback spam is annoying. Please, just cease to exist. Or at least cease to latch yourself onto every last blog entry I post.
5…4…3…2…1…
Martin Aspeli: Dear Plonewars.com
Originally from Planet Plone by optilude
Originally from del.icio.us/tag/plone by duke_iizu
Nabble – Plone – Cono Sur forum & mailing list archive
Originally from del.icio.us/tag/plone by koliko
Originally from del.icio.us/tag/plone by koliko
A webcast comparing web application frameworks (Java J2EE, Ruby on Rails, Zope/Plone, TurboGears, Django) to see what works best.
Better Web App Development — Sean Kelly
Originally from del.icio.us/tag/plone by gerd.storm
Okay, so I’m a bit biased (I wrote a bunch of it), but I had the chance to actually use Plone 3 in anger today. And it rocks. It rocks hard. It’s just more fun to use, it feels slick, it feels fancy. Y’all don’t know what you’re missing.
Go try the beta and see what I mean. ![]()
Martin Aspeli: Plone 3 Rocks Hard
Originally from Planet Plone by optilude