I generally follow this approach for long lists and reports, but the tree
tag is a bit more tricky because you only have a simple "data" object
without the context that a real object provides. A real object makes it a
lot simpler if you recursively draw a hierarchy - doing it with simple
"data" o
At 05:26 PM 4/24/01 +0200, Roch'e Compaan wrote:
>How do you bind a SQL Result with multiple records with multiple instances
>of the class? Can you do this in Skinscript? Or do you mean I should return
>the sql result directly?
Just return the result directly. If the data is all from SQL, that'
How do you bind a SQL Result with multiple records with multiple instances
of the class? Can you do this in Skinscript? Or do you mean I should return
the sql result directly?
Roché
> Why don't you just have the rack's getChildrenFor() method return
> instances
> of the correct class, with all
At 03:01 PM 4/24/01 +0200, Roch'e Compaan wrote:
>Building the tree leads to a whole bunch of queries to the database that
>really slows thing down ie. besides the queries that retrieve children,
>select queries to retrieve individual instances is called by getItem through
>SkinScript for each ite
Hi Everybody
We are porting a desktop application to Zope using Interbase and ZPatterns.
In this application objects like Vintage, Farm, Vineyard, Block and Panel
form a hierarchy and are displayed with the Zope tree widget. To build the
hierarchy we use a method called getChildrenFor() on each
