>Can hardly wait until it will be available Arnon
don't set your hopes to high, it is just the approach i use,
I believe it is ok, but that doesn't mean any of you will like it
> by in the meantime, let me argue a bit with you.
ok, i'll see what i can do :)
>It is not that there are problems with OO design and analysis here, in fact there is a major cath 22!. Either you build your systems OO or you do not.
I disagree to this, I use OO in all my program and I use OO to some extent in my design
> The benefits come from the incremental construction of a "framework" in function of which you can apply OOA and OOD, or am I missing something?
using OOAD as the base for OOP is desirable,because that way the transition
from design to code is more smooth and thus faster.
a "framework" to me is a set of tools that will help build my next project
without re-inventing the wheel all-over again
using OOP I can create a set of blackboxes that perform
specific task which i can use and re-use all over my apps
for example part of my framework is a component the manages objects
there is one component used for searching in tables, etc.
> so you still have to save your 'objects' in a RDBMS, which is to date he most performant way of saving and retrieve large amounts of data.
VFP is not a OODBMS it is a RDBMS, I don't think that going throu
the trouble of making OO wrappers for table is worth it
so I guess we agree on this one
Previous
Reply
View the map of this thread
View the map of this thread starting from this message only
View all messages of this thread
View all messages of this thread starting from this message only