Answering the last question/observation first, there’s a gap between saying “that wouldn’t be hard to do,” and the actual time and effort one can afford it. In other much longer words, some things are easy to incorporate in a project, but must be evaluated against many factors: one is the problem all of us face of a mere 24 hours in a day, of which little seems to be available for the things *we* want to do; one is the skillset of the developer; one–though it feels more like forty–is what’s already on the list of todos or planned features. And there’s always the chance you want a program to do something that conflicts with other goals. So keep all that in mind when the phrase “that wouldn’t be hard to do” comes up, even when it comes from someone assumed to know what they’re talking about (just try not to assume it too often).
On to your wish list.
– It should remember the “tracking only” state (extracted from your email message)
Will occur in R1 (Release or final version 1), set through a cookie. I originally thought of saving this as an option, but want it to be user-aware.
– Sortable columns
Something I looked at early on, and I do plan to add it–mainly because I want it. But I stuck it on the backburner until I gain a better understanding of SQL JOINs. Ironically, another project I was asked (i.e. paid) to code, but which had nothing to do with SQL, gave me some insights in the way to play here. Consider sortable columns slotted for R1.1. But first, gotta finish up R1…
– truncation of referrer, so it doesnt overrun the UI
This should occur. The plugin passes its own css, in which several table columns are set to overflow: hidden;… took a look and it’s probably a browser (IE) issue caused by setting columns to an auto width. I’ll see if I can fix without forcing a set width (which I’d like to avoid so the columns contract/expand with the browser window).
– Filtering/searching based on filename, date, etc
Would have to wait for R1.1 or possibly R1.2. But a good idea, considering how easily one can end up with hundreds of files to track and thousands of downloads per file.
– a function to allow inclusion of download data in the WP templates.
This has come up in emails and blog comments, and I’m dumbfounded over how such a feature never occured to me. It affected one of those spontaneous “of COURSE it should do that!” moments. So even though I put the plugin’s development in ‘fixes and final features’ mode, a template function (uh, tag) for this will find its way into R1.
