[Snippet] FeedX

Quote from: kylej at Mar 06, 2007, 12:18 PM

jesse,
just add &orderby=starttime&sortorder=a to your google calendar feed url. you can find all of the params here:

http://code.google.com/apis/calendar/reference.html#Parameters

Yeah, I knew of those parameters, I was just using the unsorted Google feed to test out the new sortElements parameter to see if I could get it to work like I expected it to

And does it work jesster?

Brian,

I think I am mixing up some of the terminology. If I enter into the description field for an event in the Google Calendar:



The raw XML feed contains:



FeedX parses that code into Google

While SimplePie and Firefox parses that code back to the way it was originally inputed:



I guess I just figured if SimplePie and FireFox do it, they must have good reason for it, and it should be a parameter, as I prefer the way FeedX parses it into the clickable link.

No I changed my cacheTime to `1` and when I change it from DESC to ASC, nothing changes. You mind trying to sort it on the starttime? You can use my test feed address if you want.

http://www.google.com/calendar/feeds/iblewyouup%40gmail.com/public/full/?singleevents=true

Oops, I wasn’t taking into account attribute values when sorting.

I’ve added a new param called &convEntities, the default is 1 which converts entities to characters, 0 will convert the characters back into entities:

Sort + entities=`0` example: http://brianstanback.com/feedx.html

I’ve updated the version, snippet, and download in the first post.

Also, cacheTime=`1` is not necessary for sorting as long as cacheType is not set to 1.

Ahh, thanks for the tip about cacheTime. I will give the updated snippet a whirl tomorrow.

I’ve updated the code in the first post to version 0.1.0 (when upgrading, please update the actual snippet and all files from zip archive). The most notable change in this version is the new debug console which I adapted from Ditto 2. Let me know if the debug view is helpful/clear enough.

2007/03/09 - 0.1.0
------------------
UPDATED: Changed directory structure for assets/snippets/feedx directory
UPDATED: &tplBuilder now called &debug, integrated adaptation of Ditto2 debug system
ADDED: Language file for debug and system errors
UPDATED: Changed &tplPreset parameter to &preset
UPDATED: Improved error reporting, writing to the system event log during non-fatal errors

http://brianstanback.com/feedx.html

I finally had some time to play with FeedX, and I am very impressed! Once I figured out how to chain my chunks (LoL) and get my params inline, it was working flawlessly! Through CSS I can manipulate the feed output almost any way I need to, and the templating at each level of the feed made it that much easier to get the look & feel I was after.

The fact that it comes with Caching to boot is just a huge perk. Thank you for such a dynamic and invaluable add to the arsenal

PS
The Debug console (from Ditto) is SUPER handy for viewing real-time placeholder options via Template Builder. I like how it breaks down the Feed, too, showing the guts in an easy to reference manner. This is just great.

Wow, the new debug is wonderful, really helpful to me

A small thing: When I used either &usePhx=’1’ OR &usePhx=’0’ my Phx strips broke. It worked again when I removed usePhx alltogether from the call. You might have a bug there.

Now here’s what on my wishlist: an optional arbitrary string parameter I can give to the FeedX call, something like this:



I then want this string returned as a placeholder, maybe not in the ’outer’ template but at least in channel and item. I will use this to control display and output. For my specific purpose, the string will be the ID of the DIV where I want the content of the different items shown. I use javascripts and getElementById, and there is no other way I know of that can make a custom DIV ID known inside the different ITEM templates on a per-feed basis.

Say, is there another, well-known MODx way to do something like this?

I might be able to hack this myself, but then I’d be forced to hack it each time you update FeedX, so I’ll first request it to become part of FeedX. I would think that others could find use of a paramter like this too.

A small thing: When I used either &usePhx=’1’ OR &usePhx=’0’ my Phx strips broke. It worked again when I removed usePhx alltogether from the call. You might have a bug there.

Never use single-quotes around parameters (’) ... always use back-ticks: ` (on US Keyboards, frequently the key to the left of the 1-key on the top row).