Sam Tregar wrote:
DBIx::Recordset for object wrapping of SQL queries for
managability. ]
I thought this was just another OO DB wrapper, but I don't remember
looking too closely.
No, I would say that DBIx::Recordset is a procedural API for driving a
database. The usage therefore
John Day wrote:
HTML::Template is a good candidate for the view (but not the only candidate!). [ print statements and here-documents are *NOT* good candidates. ]
Agreed, H::T has its shortcomings. The steep learning curve of TT is one of H::T's best points! Of course after I have read the
Richard Dice wrote:
My experience with SQL DBI is that it quickly becomes unwieldly. I
guess my question is, what kind of SQL/DBI helper techniques are you
using to reign in the unwieldly-ness?
There are a number of CPAN modules that typify each technique. [ E.g.
SQL::Snippet for
John Day wrote:
H - titles can have a huge impact on how writers think. Jesse has been very careful to keep the vision for CGI::A clear, let it not be cluttered with application or even author specific code, but keep it clean, clear and a wonderful foundation on which anybody can build.
Mark Stosberg wrote:
What we /need/ is more open source applications so we can see more
examples of how we all code, and learn from the best and worst of that.
I have a 13k .tar.gz file that contains a CGI::Application that is up
and running and useable 24 hrs/day.
It is a site which keeps
Hi,
I just stumbled upon Class::WeakSingleton, and I have the feeling that
it could help a lot in keeping certain global objects available without
having a multiple instances.
Some of the objects I'm thinking about are used in a lot of places, but
there really should be only one instance for
On 2004-01-28, Stephen Howard [EMAIL PROTECTED] wrote:
Now why I like TT is that i don't really have to do any 'display prep'
of the items to be returned to the user.
I appreciate this. I've wrestled with this some using H::T.
Data::Grouper and careful use of DBI help this some, but I could
At 11:02 AM 1/29/2004 -0500, Terrence Brannon wrote:
John Day wrote:
H - titles can have a huge impact on how writers think. Jesse has been very
careful to keep the vision for CGI::A clear, let it not be cluttered with
application or even author specific code, but keep it clean, clear and
At 10:45 AM 1/29/2004 -0500, Terrence Brannon wrote:
Richard Dice wrote:
My experience with SQL DBI is that it quickly becomes unwieldly. I guess my
question is, what kind of SQL/DBI helper techniques are you using to reign in the
unwieldly-ness?
There are a number of CPAN modules that
On 2004-01-28, Cees Hek [EMAIL PROTECTED] wrote:
One other handy feature that I use is the WRAPPER plugin. It allows you
to simplify the header footer includes that is quite common in
templates.
This does seem handy. I handle this with H::T by using DreamWeaver
templates, although I
On Thu, Jan 29, 2004 at 06:43:48PM +, Mark Stosberg wrote:
Header.tmpl:
title[% Title %]/title
!--Top navigation stuff here --
[% USE Family(PageID) %]
[% FOREACH Relative = Family.Left_Rail %]
[% IF Relative.Type == 'Parent' %]
!-- Output a parent type breadcrumb --
[%
well, to be fair to TT, i think it's a little easier to read it this
way, as opposed to the original example
title[% Title %]/title
[% USE Family(PageID) %]
!--Top navigation stuff here --
[%
FOREACH Relative = Family.Left_Rail;
SWITCH Relative.Type;
CASE 'Parent' %]Parent Type
William McKee wrote:
This could be pulled into another template with the following line:
xi:include href=header.tmpl /
I want to make a fundamental points about website design here...
componentizing a website's view via a templating language is very
different from what experts in
On Thu, Jan 29, 2004 at 06:00:58PM -0500, Terrence Brannon wrote:
I want to make a fundamental points about website design here...
componentizing a website's view via a templating language is very
different from what experts in Macromedia Dreamweaver or Frontpage are
used to having done.
14 matches
Mail list logo
