Aaaah...I understand. Let me think on that one for a little while. I don't see a solution right now.
/Joakim On Wed, Aug 10, 2011 at 8:56 AM, Dominik Hurnaus <dominik.hurn...@gmail.com> wrote: > Hello Joakim > > I am also working on Gerolds project. The difference is that we do not only > need a static string (or message key) for a single page, but dynamic text > depending on what entity is shown on the page. > > Consider the page BusinessPartnerDetail. Your breadcrumb-implementation > would show "businesspartner.page.title" for each business partner I opened. > What we need is different, we need to have "Businesspartner Hans Huber", > "Businesspartner Joakim Olsson", ... (what Gerold described as 'summary') > > Unfortunately we don't see a way to get this data, since the Dispatcher is > called before the page is initialzed (before the onActivate methods are > called), and therefore we cannot access this information. > > Any idea on how to achieve that? > > Best regards, > > Dominik > > 2011/8/10 Joakim Olsson <joa...@unbound.se> > >> Hi, >> >> I don't really see the difference between my module >> tapestry-breadcrumbs and what you are looking for. What is missing >> from tapestry-breadcrumbs for you to use it? Maybe it can be added? >> >> Regards, >> Joakim >> >> >> On Wed, Aug 10, 2011 at 8:04 AM, Gerold Glaser <gerold.gla...@gmail.com> >> wrote: >> > Dear Listeners! >> > >> > In our application we want to track the pages a user has visited and >> provide >> > a "last visited object" widget in the application for faster access. >> > >> > Our idea was to provide an Annotation @LastVisitedPage on the page to >> mark >> > the pages that should be included in the history (like it is done in the >> > breadcrumb project of https://github.com/argoyle/tapestry-breadcrumbs/). >> > >> > The text shown in the last visited object should be rendered by the page >> due >> > to performance and translation purposes. The track should be written >> after >> > the page is rendererd. >> > >> > @LastVisitedPage(summary="prop:summary", context="prop:context") >> > public class PageA >> > { >> > private Bean bean; >> > >> > @Inject >> > private Messages messages; >> > @Inject >> > private Repository repository; >> > >> > void onActivate(Long id) >> > { >> > this.bean = repository.loadBean(id); >> > } >> > public String getSummary() >> > { >> > return messages.get("translationfor.this.page") + " " + >> bean.getSummary(); >> > } >> > >> > public Long getContext() >> > { >> > return bean.getId(); >> > } >> > } >> > >> > Is the following solution possible and could you provide an example for >> > processing the properties? >> > I don't know how to access the props from the Annotation in the >> Dispatcher. >> > >> > Best regards, >> > Gerold >> > >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org >> For additional commands, e-mail: users-h...@tapestry.apache.org >> >> > > > -- > > Freundliche Grüße / Best regards, > > Dominik Hurnaus > > *C *a t a l y s t s > Software Engineer > > Mobil: +43 (650) 723 6 723 > dominik.hurn...@catalysts.cc > www.catalysts.cc > Ottensheimer Straße 27, A-4040 Linz > > *task**mind** ** > ... Aufgaben im Team erledigen** > www.taskmind.net* <http://www.taskmind.net/> > > Catalysts GmbH, Firmensitz: 4232 Hagenberg, Firmenbuchnummer: FN 292140v > beim Landesgericht Linz > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
