Folder-RSS generates an newsfeed containing changes within a folder. Use it to see what files are new in a particular folder by subscribing to the feed with an RSS reader like SharpReader:
Syntax: folder-rss.exe c:\temp > d:\temp\test.xml

-justice (May 09, 2007, 08:03 AM)

:up: :up: :up: :up: :up:                :-* :-* :-* :-* :-*
People talk of (including my own yappity yap) moving from desktop to web. The reverse, it now seems, is even more interesting.
I was going to sit down and complete some programming tasks. But, you've succeeded in disrupting my schedule  ;) ;)

File filters should work, put paths with spaces in quotes. Run it as a scheduled task once a day to generate a new feed. Defaults list the last 100 items that have been modified /are added within the last 14 days.
AHK source + compiled .EXE provided. Your suggestions and comments are much appreciated :) 

Feature-packed and open source! drool drool droooooool.....

Also the software is really beta stage (first public appearance), so there's bound to be bugs, but as it's not doing much harm so safe to use. RSS2.0 validated feeds.

How about "Patent-pending standards-compliant webdesk(TM) technology"?

This is a nice piece explaining what FOSS is, to the layman or the newbie:

http://www.freesoftwaremagazine.com/articles/beginners_guide_understanding_free_software


Do have a look.
PS: it could also make you hungry ;)

this is sort of bigger.

Now, FOSS is going to spread all over the place with Redhat and Sourceforge.net opening their FOSS exchanges.

A sharware author who is just starting out or is small (just one or two small programs) has two options:
1. Opensource the program, get people involved, get publicity and therefore make money.
2. Remain closed source, shareware, fight, invent and market the new features to keep up with the fiery pace of code perfection that FOSS is all about (many minds solving the problem, instead of one person)
3. Develop a loyal user base and keep them always interested.

The first two are already well-studied methods.

The third is what I'm talking of: Plugins

Write (or rewrite) your applications so that people can contribute with *minimum* effort.
Markup of any kind, preferably XML, seems to be the best bet.

If your users are typically non-technical, as in, "Do you have to actually learn a programming language to add a feature ?!?!" or "XML, yeah! I've heard it's hot, but I don't know when I'll get around to actually learning it", then maybe you should be using .ini files.

You then have to do some marketing
1. free licenses or discounts for the best plugins
2. let your user community earn from the plugins they make
3. Ask your users openly, to submit plugin ideas and feature requests
..........[your novel ideas here]
and so on.

I personally prefer FOSS, but it's quite obvious that the *dominant* Windows world has a ton of shareware programs, authors, professional organisations and so on. Naturally, they aren't going to make money if there is free software available to do just what their product is doing, but better.

As an afterthought, Donationcoder is probably an experiment in just this.

Ideally, FOSS should have run on donations and all would be well. But people will happily use your programs to make a huge difference in their computer productivity, but won't donate. That's the unfair part. But that's how it is.

Although my strong bias is towards a free, open culture and open source software, the hard fact is that people with money do not donate fairly. In fact I would go as far as to say that the richer you are, the lesser you donate, because in today's economic scenario, only those who are unfair become rich quickly.

Fair, straight good guys almost always just manage.

So, your best friend is the small user with a bigger heart. Notice him, pamper him. He will probably support you far more effectively than the rich user.

Just my opinions. YMMV.