Great ideas Mark!  Does this mean I now owe you ca$h?  I didn't consider the
permutation where you would discuss improvements without actually requesting
them!  You are a thinking man aren't you?  I'll work the RESTful style of
request METHOD into the configuration after studying that plugin first.


Thanks,
Scott

On 10/14/07, Mark McLaren <[EMAIL PROTECTED]> wrote:
>
> I have been thinking a little more about the BreadCrumbInterceptor.  It
> may be a blunt instrument but I was thinking it would be a fair
> assumption to only include actions invoked via the GET method in the
> bookmarks trail.  This could be achieved in the interceptor with code a
> bit like:
>
> ActionContext context = invocation.getInvocationContext ();
> HttpServletRequest request =
> (HttpServletRequest)context.get(HTTP_REQUEST);
> if ("GET".equals(request.getMethod()){
>     // Do the magic stuff
> }
>
> I also thought that breadcrumbs of this nature would be really useful in
> an application that stores the most recent searches (imagine a S2 app
> using Lucene).  In this scenario it would be good to additionally
> include the querystring in the breadcrumb URL.
>
> The only problem with these suggestions is that it makes it a far less
> simple example (and I don't plan on paying for my feature requests - do
> I qualify for the 3 for $250 yet?).
>
> Mark
>
>
> Adam Hardy wrote:
> > The motive website article is almost comprehensive, but they miss 2
> > points about breadcrumb history menu:
> >
> > firstly it's not redundant just because of the browser's history
> > functionality - when you go back in the browser and then choose a new
> > link, you lose your ability to go forward in the browser history
> > again. A breadcrumb menu keeps your history even if you retrace your
> > steps.
> >
> > secondly for that reason, there is no need to try to work out whether
> > a page is in the history already or not. Just let it appear twice or 3
> > times or however many times.
> >
> > But their point that breadcrumb history menus only having use in
> > certain situations is very true. I always wish that javadocs had it
> > built in.
> >
> > Mark McLaren on 14/10/07 16:05, wrote:
> >> Good stuff.  Here is some feedback for you, free of charge. :)
> >>
> >> There is a slight issue with www.strutsschool.com (demo site for the
> >> breadcrumb plugin?).  I think flipCoin should probably appear in your
> >> excludeMethods as accessing flipCoin through the breadcrumb link
> >> throws an exception.  (the flipCoin breadcrumb is created by clicking
> >> on submit on the samples.action page).
> >>
> >> Also, I think you need to make it clear that this provides
> >> "breadcrumb navigation as transcript/history" rather than the
> >> "Homeward Path" style of breadcrumbs that is more prevalent.
> >> (Breadcrumbs is a most ambiguous term!).
> >>
> >> <http://www.motive.co.nz/glossary/breadcrumb.php>
> >> <http://developer.yahoo.com/ypatterns/pattern.php?pattern=breadcrumbs>
> >>
> >> My personal preference would be to display breadcrumbs in an
> >> unordered list with appropriate CSS styling. e.g.:
> >>
> >> <http://www.alistapart.com/articles/taminglists/>
> >>
> >> I was also thinking that a homeward path breadcrumb navigation
> >> implementation would be a good demonstrator for the S2 XSLTResult type.
> >>
> >> HTH
> >>
> >> Mark
> >>
> >> [EMAIL PROTECTED] wrote:
> >>> Greetings --
> >>>
> >>> I finished the S2 breadcrumb plug-in and you are welcome to it and the
> >>> source code at www.strutsschool.com.  I plan to cover the plug-in
> >>> process in
> >>> a chapter of the Struts 2 in Action
> >>> <http://www.manning.com/dbrown/>  book
> >>> which is soon to be released.  Until then, a few folks have asked if
> >>> they
> >>> could get it sooner.  Once you download the plug-in, be sure to see
> the
> >>> README.txt file contained inside the jar.  This explains how to add
> and
> >>> configure the plug-in to your liking and sample HTML code for
> >>> displaying the
> >>> crumbs on your site.
> >>>
> >>> Please let me know of any issues that you encounter and I will accept
> >>> feature requests at $100.00 each or three for $250.00! :)
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


-- 
Scott
[EMAIL PROTECTED]

Reply via email to