Node or AA based Class Support

Is there anyway we could do classes ether as AA out put or as Node output. I say this because internally we avoid AA's as much as possible.

this is a good suggestion - so something like NodeClass? whereby

• automatcially creates a className.xml,
• imports the declaring brs file into className.xml
• the public methods become <function> interface entries in className.xml
• public fields become <field> entries on className.xml

There's a lot in this idea - I think you should raise it as a separate issue - as it's a hugely useful; but also huge feature; but (imho) way beyond the scope of pobo (i.e. aa) classes

The above was a response from @georgejecook

Originally posted by @chrisdp in https://github.com/TwitchBronBron/brighterscript/issues/1#issuecomment-499995224

No files, tests, or entry points are named in the issue. First clarify whether the goal is AA-based classes, Node output, or the proposed NodeClass design, then define the expected className.xml generation, imports, public method interfaces, and public field entries. Done means the selected class support is implemented with clear behavior and coverage.