How's this for cool? An SD slot camera...It's sold out until September, but this sure beats the sleeve cameras that have been out for pocket pc's in the past.
After about a month of working on it off and on, my PocketPC RSS aggregator actually is functional...I'm still deciding whether or not the client will just be ie on the PPC, or if I'll also make a CF client reader. (I probably will). It's fully coded in .NET, of course...
- User specified thread limit for updates
- Can run as a service in the background (updates on a user specified time increment)
- Creates an index page with anchors to specific stories, etc.
- Adds file to folder that is synchronized with ActiveSync (user specifies which device(s) to sync to, read from the registry)
- Reads opml files (from other aggregators)
Not Yet Implemented:
- User specified # of layers to crawl and archive.
- Support for that other protocol?
It's still not ready to release, though. I should post a pic up at some point.
Update: After quite some time without revisiting this project, I've been asked about it again (see my response to the first inquiry here ), unfortunately, not much progress has been made since this point, but I”m writing another post on future plans (link will go here very shortly).
In EPorter's post , he mentions the issue of RSS authentication, to get to personal information. Why shouldn't we be able to secure content via server tools (although I do think this should be extended into the RSS / XXXX specs)?
What about creating an email client that recreated your email as an rss feed? You could create a "rule" / "filter" on the subject line and/or your bank's email address. Then you'd just need to secure the rss feed on the server side so only you could get it. IP restriction for receiving the feed? Would it be really bad to use some sort of password encoded url (ie. http://logon:email@example.com/BankTransfers.aspx) for the RSS feed?
While trying to write my latest app, I've discovered some more about divergence between Java and .NET. I'm writing a multithreaded app, only to uncover that .NET parent threads don't “own” their child threads (!). So, what are other peoples' experiences with threading books for .NET? The only one I've come across so far is Alan Dennis' “.NET Multithreading” but that seems to have gotten mixed reviews over at amazon. Is his the authoritative source, or are there better?
As a relative newcomer into the blogging scene, I see the mammoth presences of the giants. They are those who get loads of visitors, whether by word of mouth, or through OEM (so to speak) inclusion via such programs as the wickedly fast SharpReader. I wonder just how to attract readers so to actually have an impact through writings. Today Dave Winer of Scripting News posted an essay about pointers (anchors).
I must admit that while I don't agree with some of the things he has to say, this point is perfectly on target. The article, titled “Pointers Are Cheap,” touches briefly on the issue of journalistic integrity, but the greater point is the fact that links in articles are 99% more likely to produce results that the end user is interested in. They are reading the article because it is of interest, therefore, the link may be of use to them as well (NB: made-up statistic).
I wonder if what I have to write here is important enough to the community to make an impact. Without flaming or trolling. I plan to announce a project I have been working on, that will eventually be made open-source on GotDotNet. Hopefully people can use it effectively or learn from it enough to make my blogging presence worthwhile.
I got accepted into the .Text project, and hopefully will be able to contribute to the code, although more likely, I will proof text that goes out; I'm picky like that. Congrats to Scott for getting to #4 on their list!
Has anyone noticed the “bug” in MS Query Analyzer? If ever you quit a long-running query, it'll spell “cancelled” two ways: both the correct way, and “canceled.”
As I wrote late last night, after some coffee-induced coding, the first release of SystemTrayApplication is now available at GotDotNet workspaces here. I like to think it has some purpose to it. It's the easiest way to get a system tray icon for your application. Just inherit from the SystemTrayApplication class, and build and run.
If you want to change the icon, embed a *.ico file in your project, and override like so in your form:
protectedoverride void CallIconSet()
I just got tired of writing separate System Tray winforms, even though the article at Code Project makes it pretty easy. So, I'm writing a generic SystemTrayApplication, which will hopefully be up here sometime tonight or tomorrow. Thanks to Scott for providing the blog space (after goading me for months to finally give in and use the application :) ) I must admit it makes me less of a hypocrite than to be an ASP.NET developer using Movable Type.
Update: Here's the application class.