Clarion Folk

This one is so simple to understand. But would get reasonably complicated to implement.

The system (web or desktop, probably both) would take in any kind of file (doc, image, blah blah).

It would then Output to ANYTHING.

What’s the purpose of this? Let’s say you had a bunch of images, but need them in a document. How hard is it to just plonk a bunch of images into Word? Not very. But this is what it would do.

The logic would take the files you give it, examine them, and see if the output file could be a container for those files. If not, then it has some nice practical rules for dealing with things.

Let’s say you give it a Doc, and Excel sheet, and a WMV file. You feed them in. You _can_ tell it what you want back. OR you let it do it’s business.  Which is to give you back a single file with the inputted files in sequence (or however they would be moulded together, based on contextual default rules, or indeed rules of the Users making).

So the DOC and XLS and WMV files would be joined in beautiful unison into ..

Well, how would you do it?

[Read more →]

Stats. Reports. Most people deal with stats in their daily lives. Even folk who never go near a computer.

This system would take in feeds (you could kick off with just XML), and intelligently work out patterns based on the input.

There would be four parts, that I can see.

1. The Parsing of the Feeds (the different types of file structures)
2. The Rules Interface
3. The Interpretation of the Rules / Calculation of Results / Pattern Recognition
4. The Reporting of Results (Bling Graphs and wotnot)

There are so many sub-systems you could build around this. Contextually refined for various tasks. But this one would be generic. Meant for the masses.

[Read more →]

Here’s an idea.

1. A web server where people log in with their social media details (like Twitter, or Facebook, or ..).
2. The server doesn’t store the password, but it stores the Service (eg. Twitter) and the Username.
3. The server pulls in the contacts from the Service, through the available API, if there is one.
4. The Contacts then can be modified, exported, used etc. Other details can be added.
5. To make it actually worthwhile, the server needs to go a few more steps. Using the Users details, try and find their other “presences”. Their existence in other Social Media services.

It’s nothing more than a db of Contacts with relevant contextual information. That, and the logic to _find_ the relevant contextual information : ).

[Read more →]

Here’s an idea.

1. A little system tray program that retrieves contextual information. There could be many different paper boys, or chuck all functionality into one.
2. Used for tracking Real Estate Properties, both Rental and Sales.
3. Used for tracking Blogs, real-time alerts when someone updates their blog.

Notes:

Couldn’t possibly be any good trying to mash together everything. Needs clarity.

The Real Estate one is good. People can use this little satellite app to store and search for the Property types they are looking for.

The app will store all results, in some way.

[Read more →]