Well, let's see.
I use two different handlers because I think there are two different
events that manipulate the breadcrumb path.
One 'event' is when the application flows from one page to another. This
other page must have the opportunity to create its 'crumb' information and
have it stored in
One 'event' is when the application flows from one page to another.
...
The other event is when a user clicks on one of the individual crumbs on
the breadcrumb path,
Ah... I think I understand. I'm pretty sure then that the events you
are using don't work they way you think. Have you put
Really appreciate the feedback! Although the approach I currently use
works, yours looks far cleaner and better. I'll have a go at it tomorrow
and let you know how this works out.
Again - really appreciate it.
-J.
One 'event' is when the application flows from one page to another.
...
The
Hi,
Need some advice. In T4 I had a breadcrumb component that got its
information from a breadcrumb model structure. Each page that needed to go
onto the crumb path would implement some base page class. This page class
implemented PageRenderListener and IExternalPage. The former to add info
to
I used T4 for a short period a long time ago, so I'm not understanding
the parallels that you are making. Can you describe the workflow that
you are shooting for? I'm not clear why you'd remove the breadcrumb in
the activate event and the add it again the beginrender event.
Josh
On Wed, Apr 23,
I used T4 for a short period a long time ago, so I'm not understanding
the parallels that you are making. Can you describe the workflow that
you are shooting for? I'm not clear why you'd remove the breadcrumb in
the activate event and the add it again the beginrender event.
beginRender will
Ah, by workflow I meant to ask when you expected the events to get
fired, which you answered for the onactivate handler.
So, why not do this all in one event handler, perhaps setupRender?
On Wed, Apr 23, 2008 at 11:44 AM, Jan Vissers [EMAIL PROTECTED] wrote:
I used T4 for a short period a
Hi,
I'm not sure if I understand...
Do you mean to say that manipulating the breadcrumb path (adding or
removing crumbs) should/could all go into one event handler?
-J.
Ah, by workflow I meant to ask when you expected the events to get
fired, which you answered for the onactivate handler.
I'm not sure if I understand...
Do you mean to say that manipulating the breadcrumb path (adding or
removing crumbs) should/could all go into one event handler?
Sure, couldn't they? I'm not sure why they are split up into the two
different event handlers. Except in the case of action links and
