[imc-cms] [Imc-drupal-dev] IMC CMS - next meeting Saturday 30th September 1400 UTC - https://chat.indymedia.org/ - channel #cms
john duda
john at manifestor.org
Wed Sep 27 09:14:53 PDT 2006
On Wed, Sep 27, 2006 at 06:55:38PM +0300, qwerty wrote:
> On Wednesday 27 September 2006 05:49, Dave Fregon wrote:
> > Basically it comes down to the fact that there just isn't enough Plone
> > folk out there in Indymedia land, the learning curve can be quite a jump
> > for php coders, not familiar with the total change of 'concepts'.
> >
I have to second this...my first foray into Plone development was
really scary. Coming from a relational database web programming
mindset, it was really amazing how difficult it was to do simple
things like get a list of a certain type of object and do something
with that data. Not that it was all that verbose in the end, but
whereas listing rows/objects would be the "hello world" in any
mysql+php tutorial, i seem to recall having to wade through a lot of
not so well thought out documentation on writing products that was
pretty sparse, and less than easy to dive into. And then just sort of
guessing at the right way to do things. Because of things like
acquistion, it was really hard to find out where in the code something
happened, so trying to look at source code to figure out how something
worked often proved difficult as well.
At the time, Archetypes was also really new, and I remember being
really excited by it(it's a great idea!), but really frustrated by the
implementation, specifically with incompatibilities between various
distributions/versions of different products. On this point, if we do
wind up going with something that gets turned into the indy-cms by the
addition of lots of plugins, it might make sense to maintain a
repository of tested compatible versions of the full suite.
and then there was catalog corruption....
-john
--
this is where my public key can be found:
gpg --keyserver pgp.mit.edu --recv-keys 03817826
Key fingerprint = 6C11 8D70 2ADE EFA9 498D 72CB 77EA 391A 0381 7826
More information about the imc-cms
mailing list