Mattias Gaertner wrote:
> Al Boldi <[EMAIL PROTECTED]> wrote:
> > > > > Can you be more specific? What is ChildClass?
> > > > > I would expect a function to scan the classes of the project or
> > > > > a package. For example:
> > > > > function ScanProjectClasses(AProject: TLazProject):
> > > > > TSomeTreeStructure; function ScanPackageClasses(const
> > > > > APackageFilename: string): TSomeTreeStructure;
> > > >
> > > > Wow! That's even better.
> > > >
> > > > Maybe even add: function ScanSourceEditorClasses:
> > > > TSomeTreeStructure;
> > > >
> > > > which would scan all open source editor tabs down to TObject.
> > >
> > > What do yo mean with 'scan' down?
> >
> > i.e: TComponent -> TPersistent -> TObject
> >
> > > What information do you need? For example?
> >
> > For now, only the Class name. Later we may extend this.
>
> Functions to retrieve the ancestor list already exist.
> I thought (hoped), you want to create a class diagram, showing
> visually all classes of a certain scope (e.g. project, package) and
> their relationships. Not only the ancestors, but the interfaces and
> properties too. I hoped a start for an UML tool.
Great! But keep in mind that things do start small.
First, where are the functions that retrieve an ancestor list?
> > > > > > The result could then easily be put into a treeview, for
> > > > > > display and further functionality.
> > >
> > > How should this treeview work?
> >
> > Maybe use TTreeView and assign the scanned classes to TTreeView.Items.
> >
> > Do you have different idea?
>
> Mattias
Thanks!
--
Al
_________________________________________________________________
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject
archives at http://www.lazarus.freepascal.org/mailarchives
