On Feb 28, 2006, at 6:52 PM, Giuliano Gavazzi wrote:
I see now that there is a General Web UI item in the TODO. Let me add
a plea: please do not use php for the future UI!
Don't worry, that won't happen. What might/should eventually happen
is the adoption of a decent Python templating
if not mlist.digestable or not mlist.nondigestable:
replacements['mm-digest-radio-button'] =
replacements['mm-undigest-radio-button'] =
replacements['mm-digest-question-start'] = '!-- '
replacements['mm-digest-question-end'] = ' --'
else:
I vote for Zope Page Templates.
http://www.owlfish.com/software/simpleTAL/
-jag
On Thu, 2006-03-02 at 09:23 -0500, Barry Warsaw wrote:
On Feb 28, 2006, at 6:52 PM, Giuliano Gavazzi wrote:
I see now that there is a General Web UI item in the TODO. Let me add
a plea: please do not use php
On Thu, 2006-03-02 at 11:57 -0500, Joshua Ginsberg wrote:
I vote for Zope Page Templates.
http://www.owlfish.com/software/simpleTAL/
I actually spent a lot of time when prototyping MM3 and used TAL (the
one from Zope3) and found it excruciating to use, especially when i18n
was added. It's been
Sorry, I mixed up the options with list subscription page, the list
subscription page is fine, as it uses mm-digest-question-start/end to
comment out the digest section and they are parsed correctly by
listinfo (apart from a possible extra 'not'), but in the options page
the digest section
On 2 Mar 2006, at 18:08, Mark Sapiro wrote:
there is, I think, a bug. Shouldn't it be:
if not mlist.digestable or mlist.nondigestable:
No. The intent is to not offer the digest radio buttons if there is no
choice, i.e. if you can't choose digest or you can't choose nondigest
because
BAW == Barry Warsaw [EMAIL PROTECTED] writes:
BAW I really /wanted/ to use TAL but it was way too unwieldy to
BAW develop.
+1 Unfortunately, TAL doesn't seem to scale _down_ to typical
volunteer-staffed open source.
--
School of Systems and Information Engineering
