It’s wrong to say the general public has access to your thoughts. They only have access to the you you wish to portrait. The only problem I see with it is that most new users won’t think of it that way until too late.

Twitter (or the other twitter like social applications) should not be viewed like IM, Phone calls or email. They are broadcasts that you care or don’t care get read.

As far as big brother is concerned, just like email, IM, etc. You need to edit yourself and think about what you are putting out there.

Now that I know you are turning off your IM and email, I’ll make sure I call you when I need an answer from you.

My suggestion would be to gather as many e-mails as possible and start a Google or Yahoo group and invite them. Add e-mail address to the information collected on RSVPs and invite them. Most people by now can write and read e-mail and are much more comfortable doing so that editing a wiki.

Hope this helps,
Carl

Peas.

It’s actually not too difficult to create something like that from scratch (if you have some good developers and the time to spend). I’ve learned alot from working with Draagon that if I were to do it again, I’d definitely make some different decisions (most notably create a better abstraction layer for UI framework integration so I could better incorporate things like Spring MVC, AJAX or JSF without having such a hard dependency on struts).
Sadly, I don’t have a ton of time or developers, but I agree this shouldn’t be to hard to build.

The presentation tier has a notion of metadata aware views which can render collections of metadata using whatever underlying presentation framework we’d like. Right now, we have special views for struts/ajax/jsf, etc. I’d like to setup another layer of abstraction which allows us to set the UI framework globally rather than our current system which requires the developer to be aware of which UI framework is in use.

This sounds interesting, and I’d obviously like it to be driven by metadata, as I’d like it to be very configurable, and to handle most display situations.

I’ll keep you posted as I continue to ponder and develop the system.

What I’m not clear on is whether we’re talking about data filtering, as in who can see what rows in a table, or data element filtering, who can see which columns in a table or fields on a screen.

So, take your typical webapp. There’s some table and a series of screens that let you do the CRUD operations. Typically the update operation draws a screen wih all the data for the record and the primary key, usually hidden. Then when submit occurs, all the fields are written back to the database WHERE the primary key matches. It usually requires that you carry all the fields down to the page and back. Unless you target your update directly at the columns that the user modified. That’s a bit of work. I suppose you could try and keep track of the unseen data in a session state.

What I’d really like is to have data elements that are from an OR tool that I could merge with a set of metadata that a web framework would understand how to present. You could then have the metadata calculated based on user role. Although there’s still the issue of where the data flows. Probably a lot to ask.