On 24-Aug-06, at 7:48 PM, Norman Palardy wrote:
On Aug 24, 2006, at 5:28 PM, Alexander Cohen wrote:
Im not sure i understand what a "first class Class" is.
In any case, the idea is that i want to have a class somewhat like
Cocoas' NSDocumentController. It manages several instances of
NSDocument. People using these classes only need to implement
their own subclass of NSDocument and put its name in a text file
that is read in at app start. This way, the NSDocumentController
knows what subclass of NSDocument to instantiate. Now, you could
subclass NSDocumentController and it could have a factory function
for creating instances of your subclass of NSDocument, but thats
overkill.
Im sure RS has an internal function to instantiate classes by name,
please make it external so us developers can use it.
Since the "user" has to do all this in RB source code anyways why
not just make sub classes of NSDocument in code ?
The compiled code needs to know about all subclasses when it's
compiled.
Unless you're supplying a way to load a class in at run time it
seems that's the way to do this.
Because we are a large group of developers and we dont need them to be
reimplementing the wheel evertime theres a new app to write. It
actually keeps the focus on the problem which is what im looking for.
Its a real time saver.
AC
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
