[prev in list] [next in list] [prev in thread] [next in thread] 

List:       barracuda
Subject:    Barracuda: Component progress
From:       Barracuda () enhydra ! org (=?iso-8859-1?Q?Timo_Sillanp=E4=E4?=)
Date:       2001-01-24 10:10:32
[Download RAW message or body]

Hi Christian,

and thanks for your answer.

>This was a great question...does my answer help at all?

Yes, it does, a bit. My question is now: can you reuse XMLC page objects?

It appears to me that pages are permanently attached to component
hierarchies. Therefore, to reuse a component hierarchy, you must also reuse
the XMLC page object. I did not know that this is possible, since I thought
that ID attributes are thrown away when the page is used. For example, when
you are filling a table, you would do as follows:

1. Extract template row from the table by ID.
2. Remove the template row from the table.
3. Remove the ID attribute, since IDs must be unique in the page.
4. Clone the row as many times as needed and fill in the data.

At least this is what I read in some Enhydra tutorial/example (I haven't
done any real Enhydra programming though).

Of course this is not a problem if the page doesn't change once it has been
rendered. But often this is not the case, since data changes.

Obviously there's still something that I don't understand. Can you clarify?

Timo

-----------------------------------------------------------------------------
To unsubscribe from this mailing list, send email to majordomo@enhydra.org
with the text "unsubscribe barracuda" in the body of the email.
If you have other questions regarding this mailing list, send email to
the list admin at owner-barracuda@enhydra.org.

[prev in list] [next in list] [prev in thread] [next in thread]