Logic ideas - 5 levels.

[Derek Atkins]

Quoting Neil Williams <linux at codehelp.co.uk>:

> A bit like QSF and qof_book_merge and indeed cashutil itself. To keep things
> small and simple(r) I copy current sources into a new tree for testing. It's
> much like creating a branch. I work with only the files I need for the
> current critical area, making development faster.
>
>> I'd like
>> to see an existing dialog of moderate complexity in terms of these
>> rules.
>
> Nothing yet, I've got other things to solve first. I'll post when I've got
> some real code.

I still don't understand how this helps with User Input problem...  You don't
want to have to build a "test object" and then test it..  I want to be able to
test the inputs before I translate them into an object and use all the object
setters.  I just don't see how this logic train solves the problem.

It sounds like I need to modify the object, test the modification, and if
there's a failure back out the modifications...  It also means I can't do
real-time testing (e.g. enable the OK button) on user inputs because I'm
contantly having to create test objects...

Short of creating a UI-Widget-Independent input layer, which is...  
painful.. I
just don't see how to solve this problem in a UI-independent way, and 
your five
levels still don't help with this problem.

-derek

-- 
       Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
       Member, MIT Student Information Processing Board  (SIPB)
       URL: http://web.mit.edu/warlord/    PP-ASEL-IA     N1NWH
       warlord at MIT.EDU                        PGP key available