Just to say it'd be real useful if the compilerDoc showed all know subclasses of the class in question.
I keep finding myself scrutinising the fwt class list looking for classes ending with xxxPane!
brianSun 4 Mar 2012
That would be nice, although it always gets into the problem of dependencies and how far you look (in your own pod, in every pod installed, etc)
SlimerDudeSun 4 Mar 2012
I think it's not unreasonable to keep it to your own pod. That way the docs don't change depending on what you had installed at the time!
KevinKelleySun 4 Mar 2012
+1
At the IDE level there should be an ability to see a whole hierarchy based on build.fan dependency declaration. For standard fandoc, in-pod-only would be right.
Fantom tends away from deep hierarchies; but fwt and compiler are two places where there is a deep natural inheritance, and where this would be a help.
SlimerDude Sun 4 Mar 2012
Just to say it'd be real useful if the compilerDoc showed all know subclasses of the class in question.
I keep finding myself scrutinising the fwt class list looking for classes ending with
xxxPane!brian Sun 4 Mar 2012
That would be nice, although it always gets into the problem of dependencies and how far you look (in your own pod, in every pod installed, etc)
SlimerDude Sun 4 Mar 2012
I think it's not unreasonable to keep it to your own pod. That way the docs don't change depending on what you had installed at the time!
KevinKelley Sun 4 Mar 2012
+1
At the IDE level there should be an ability to see a whole hierarchy based on build.fan dependency declaration. For standard fandoc, in-pod-only would be right.
Fantom tends away from deep hierarchies; but
fwtandcompilerare two places where there is a deep natural inheritance, and where this would be a help.