-
-
I've tried for years to go digital - PDA's from the Palm to CE just didn't do it for me. The problem is that they weren't input devices (even though it was possible with extra keyboards and fairly good hand writing recognition)...but I just couldn't do it. Had to force myself to use these devices - not natural at all to work on a 3 X 4 inch surface...that would be good for the detectives on Law and Order though...
But tablets - well, that's a different story. Its all natural. I want to use it (not because its cool) because its natural to use. My 4 year old is already a master at using it...as he should be since this thing will change the way he'll learn in the future.
I'm a bit dissapointed in Beta 2 of One Note as it applies to the tablet. It "don't" work well. Every stroke makes a different "area" in One Note - not good. I hope the next release is better for the tablet.
I haven't opened my trusted note books in two weeks now.
Here's the issue though - I was begging for the Toshiba - but for some reason, the person who orders these things for me hates to get me what I want (its an ego thing I think) and got me the Compaq/HP - and got himself the Toshiba. I like the Compaq's ability to seperate the tablet from the keyboard as well as the glass screen. A bit more durable I think even though it has a smaller screen.
And, of course, I have .NET installed on it ;-)
Anyone create any Tablet specific apps yet? Where's a good place to start.
-
-
The problem: Complex object hierarchy, many complex business rules
The bigger problem: Rules change all the time, and they are different depending on how/where the app is run.
A bigger problem: There exist multiple levels of rules - that may or may not conflict.
So, how would we do this - well, there are many possibilities - some of which I know have already been implemented. But, from what I have seen, I think I have a better way.
On that note, I think I'm going to create a complete Business Rules Application Block that would allow you to segment your business rules from the rest of your application. It will also allow you to data drive when and how they fire and what happens rule exceptions occur. Of course, it needs to be service oriented and scaleable - ready for the enterprise – good for web or larger smart client applications. I need to make sure that we can consume virtually any object hierarchy - probably through some abstraction of the object and XML. Plug this baby in, create some rules - and away you go. Couple this with a Visual Studio.NET Add-In that would help facilitate the creation and maintenance of the rules – and you have a kick ass utility.
This is a problem I’m solving in another area of my life… but the way I see it, this is a big problem and I think there needs to be a big, generic, and re-usable solution – which may not be the end result of how I’m trying to solve the same problem in my day job.
Now, where should I start – well, a model of course… away I go…I’m inspired…check back with me in a couple of weeks…I may have something.
(Lately, I’ve had a crap load of “block” ideas…)