Hello Simon, thanks for the informative answer. This is a
good start and I will dig into the TitlePermalinkProvider
and use trial and error. So, expect more questions if you
don't mind. Thanks! David.
Simon Brown wrote ..
> Just catching up on some threads from the mailing list
...
>
> Basically, each blog entry has a "permalink"
URL that readers can use
> to access that blog entry. Ideally, this should never
change (hence
> "permanent link") and there is no standard
for permalinks. Given the
> dynamic nature of Pebble (i.e. it's a webapp and not
static HTML pages
> on a web server), there are a number of ways in which
permalinks can
> be generated, but the concept is simple : Pebble
associates a URL with
> a particular blog entry.
>
> Given that different people want different permalinks
(e.g. some
> people like to use numbers and IDs, others to use the
blog entry
> title, etc), Pebble has a plugin called a
PermalinkProvider, which
> lets you switch in and out the strategy for generating
permalinks. I
> see that you are using the TitlePermalinkProvider and
this generates
> permalinks based upon the date and title of the blog
entry. You can
> see some more examples of PermalinkProviders in the
online help.
>
> Does that answer your question?
>
> Cheers
> Simon
>
> On Sat, Mar 8, 2008 at 9:58 PM, David Brown
<david davidwbrown.name> wrote:
> > Hello, Simon and all the Pebble gurus and users. I
have a simple and singular
> question about: Permalinks. I have read the Pebble help
about Permalinks and I
> have gone unfortnately to Wikepedia and read some
content among other things found
> randomly on Google. Notwithstanding, after all of the
events covered in the previous
> sentence I do not know how Pebble generates a
PermaLink. I do understand what my
> Pebble instance uses as defaults for PermaLinks among
the other Pebble configurables
> (follows). Maybe, there are other Pebblers out there
that would appreciate a short
> treatise on Permalinks as they relate to Pebble. I
understand that Permalinks do
> not enjoy any type of standardization. If I have missed
something (likely) in the
> Pebble doco please advise, David.
> >
> > OS: Debian 3.1
> > Pebble: 2.2.x
> > Theme: user-default
> > Permalink provider:
net.sourceforge.pebble.permalink.TitlePermalinkProvider
> > Blog listener:
net.sourceforge.pebble.event.blog.CacheListener
> >
> > (Maybe there should be a comprehensive Pebble
configurables dump page with all
> administratively or default configurable properties).
> >
> >
------------------------------------------------------------
-------------
> > This SF.net email is sponsored by: Microsoft
> > Defy all challenges. Microsoft(R) Visual Studio
2008.
> > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
a>
> > _______________________________________________
> > Pebble-user mailing list
> > Pebble-user lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/pebble-user
> >
>
>
------------------------------------------------------------
-------------
> This SF.net email is sponsored by the 2008 JavaOne(SM)
Conference
> Don't miss this year's exciting event. There's still
time to save $100.
> Use priority code J8TL2D2.
> http://ad.doubleclick.net/clk;1987
57673;13503038;p?http://java.sun.com/javaone
> _______________________________________________
> Pebble-user mailing list
> Pebble-user lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/pebble-user
------------------------------------------------------------
-------------
This SF.net email is sponsored by the 2008 JavaOne(SM)
Conference
Don't miss this year's exciting event. There's still time to
save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;1987
57673;13503038;p?http://java.sun.com/javaone
_______________________________________________
Pebble-user mailing list
Pebble-user lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/pebble-user
|