[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[curn-users] enhancement requests
- To: curn-users@xxxxxxxxxxx
- Subject: [curn-users] enhancement requests
- From: Mark Fletcher <dafletcha@xxxxxxxxx>
- Date: Sun, 8 Oct 2006 13:34:55 -0700 (PDT)
- Authentication-results: wildbean.clapper.org from=dafletcha@xxxxxxxxx; sender-id=neutral; spf=neutral
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=Sb6keJBBqF0D/DDn4hPl8FEZBxPsVLYVukpCvtMhXVBqqhyH5iMww5jcIp2JWudbQpnMZZ1Fv+ltKo6hSQ6DcXFrwuDM5CpCqOdYsWYgLAzITGoyjfULdpM63ZDqrsfC/mAv3JR39O6CwT+hqFoypv35gFiq2ICLTLoIKxVPwto= ;
- Sender: owner-curn-users@xxxxxxxxxxx
Hi Brian,
I'd like to request another enhancement for your next version. In the
same way you can override a channel title with TitleOverride, I'd like
it if I could override that channel's default URL with a parameter like
"URLOverride". I'm dealing with RSS feeds from Jira and its
channel.links all point to the main Jira page, rather than to the
actual report that they're based on.
For that matter, I could use an "EditChannelURL" param instead of or in
addition to "URLOverride". Jira's channel urls differ from their styled
html view in only a few parameters. It would probably be easy to derive
the channel url by applying a regExp to the feed url. Then again,
looking at your FreeMarker data model, I don't see the feed url exposed
anywhere. So...
That brings up one more request :-) If it's not already exposed, can
you provide FreeMarker access to a channel's rss feed url? In addition
to enabling regExp manipulation to derive a channel url, it would allow
me to add an "XML" button to each channel so that my readers could add
a feed to their own RSS readers.
Mark
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
---
*** Posted to the curn-users mailing list (curn-users@xxxxxxxxxxx).
Back to curn-users archive.