🚀 go-pugleaf

Sven Goetgeluck wrote:

>>2) When the component extends an abstract class. The solution is to
>>   declare a "proxy" concrete class for the designer.
> 
> 
> so i cannot do it the way i do it extends from jdialog ,
> in jb 3 is worked perfect

JBuilder 3 was based on a hybrid of Java and Delphi.
I don't know whether the Designer was a Delphi
component, but to make comparisons between the
two products isn't very meaningful.

> what is ment by a "declare proxy concrete class"

The release_notes.html file, which I mentioned earlier,
explain this.  Please do read this file.  It's found
in the root directory of your JBuilder installation:
e.g.,

   d:/JBuilderX/release_notes.html

Click on the link to "Designer" in the Table
of Contents.

I still think that you should consider
aggregation instead of inheritance here.
I consider a dialog as a functional shell into
which one aggregates viewable components.
Maybe that's too limiting, but that's how
I look at it.  And so far, that view has
served me well: it tends to make the viewable
components I write re-usable in more than just
a single dialog class hierarchy, and avoids
the red bean problem entirely.


-- 


Paul Furbacher (TeamB)

   Save time, search the archives:
        http://www.borland.com/newsgroups/ngsearch.html

   Is it in Joi Ellis's Faq-O-Matic?
        http://www.visi.com/~gyles19/fom-serve/cache/1.html

   Finally, please send responses to the newsgroup only.
   That means, do not send email directly to me.
   Thank you.