Determining which libs are core

[BillHodges]

I'm trying to build a "Universal" application. I'm assuming the best way to determine which classes are in the core library and hence shared, is by looking for it's existence in the packages/core/src directory of the distribution. Is this correct?

In the future would it be possible to get this information from the documentation?

Thanks

[mitchellsimoens]

The documentation is still using the old jsduck that isn't being maintained anymore and has no knowledge of what a core is and what a toolkit is. We are working on new documentation but currently it's more manual source reading or trial and error.

[wemerson.januario]

The documentation is still using the old jsduck that isn't being maintained anymore and has no knowledge of what a core is and what a toolkit is. We are working on new documentation but currently it's more manual source reading or trial and error.

Will Ext 6 come with new documentation system instead js duck?

[mitchellsimoens]

Will Ext 6 come with new documentation system instead js duck?

mmm, if it's done

[worthlutz]

mmm, if it's done

And if it's not done? No documentation?

[mitchellsimoens]

Of course not, will just use the JSDuck like we have been

[worthlutz]

Of course not, will just use the JSDuck like we have been

Thanks Mitchell.

My comment was a JOKE!

Sometimes it seems that a little levity is needed around here.

[mitchellsimoens]

Thanks Mitchell.

My comment was a JOKE!

Sometimes it seems that a little levity is needed around here.

Appreciate it too! Guess I am too used to being beat up all the time.

[franklt69]

Which was the reason to discontinue jsduck?


Regards
Frank

[mitchellsimoens]

Major reason for me is its built with ruby and doesn't actually belong to anyone internal. Cmd is a great platform to host something in this arena so there wouldn't be any dependency to install.