On Tue, 25 Jul 2006, Bisma Jayadi wrote:
Hi all...
Currently I'm planning to develop an application for database modeling, in my
spare time. I plan it'd be similar to FabForce's DBDesigner 4
(http://www.fabforce.net/dbdesigner), though it has nothing to do with the
FabForce's. Yes, I'll reinvent the wheel, but I have good reasons for it.
Current development status is I've finish the class for table model which is
derived from TCustomListBox with custom paint method. And now I'm starting to
develop the relation model. The first idea came to my mind was create a new
class contains 3 TBevel(s) which are combined to build a relation model.
After few hours of coding, I found this idea is too complicated (I've to
synchronize 3 objects) so I plan to solve it another way.
Here I need some suggestions... which is the best component I should derive
from to make the relation model? I've been thinking about TPaintBox but I
think it too big and too complex for just a relation model component. I want
it able to paint fast and requires less memory.
Why don't you use a single paintbox to draw all your data on ?
Creating a separate GUI object for each object in your database is a very bad
idea;
I worked with such programs, and at 250 tables in the model, such programs
become
incredibly slow. A redraw takes forever.
Better take a single paintbox or tcustompanel and draw everything on that.
Michael.
_________________________________________________________________
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject
archives at http://www.lazarus.freepascal.org/mailarchives
