mason_advocacy

This is part of The Pile, a partial archive of some open source mailing lists and newsgroups.



mozilla-webtools@mozilla.org

Subject: Re: Bugzilla UI Abstraction strategy?
From: adam@thelonious.new.ox.ac.uk (Adam Spiers)
Date: 2 Oct 2000 15:59:59 +0100

ObDeLurk: Several of you have probably already seen my name floating
  around on mozilla.org bugzilla/bonsai bugs.  I finally discovered
  this newsgroup and #mozwebtools a few days ago (thanks Tara ;-).
  I've no idea why it took me so long, but you can all expect to see a
  fair bit of me from now on; I'm responsible for maintaining the
  bugzilla installation within our company, and as a keen Perl/MySQL
  hacker I have a strong interest in improving bugzilla/bonsai. ]

In article <39B997A1.12F63D18@bluemartini.com>,
Chris Yeh  <cyeh@bluemartini.com> wrote:
> One of the holy grails/blue sky/long standing wish list items for
> Bugzilla has been to modularize the form UI from the Perl and SQL. I've
> heard a variety of different approaches for this.

[snip]

> Given these principles, what strategy and software should we use? The
> following appserver/content tools have been mentioned to me as possible
> candidates for use with Bugzilla:
> 
> * Zope: http://www.zope.org
> 
> * Enhydra: http://www.enhydra.org
> 
> * Mason: http://www.masonhq.com
> 
> Does anyone have any real world experience with these? Are they
> difficult to implement? What's the learning curve like?

I have real-world experience with Mason; in fact I've just finished a
medium size project using it.  I enjoyed using it so much that I'll
have to contain my enthusiasm to this paragraph to avoid boring you
all ;-)  The learning curve is tiny.  If you know Perl, and you know
HTML, you only need to know a few facts about components (which are
basically HTML chunks with embedded Perl), and a few tricks about how
to get it working with Apache/mod_perl, and you're away.  It satisfies
all the requirements you laid out above, AFAICS, and has lots of other
nice features.  The components concept would suit us very well, as we
already build up pages from common bits (headers, footers, etc.)

I know nothing about Zope or Enhydra.  With regards to XML, I think it
would be great if we could offer import/export via it, but I don't
really see how else it can serve us.

Adam

===


the rest of The Pile (a partial mailing list archive)

doom@kzsu.stanford.edu