>>> - hello-world.xml >> ... >> I removed the reference to the convenience main() method, since this > approach is no longer used as pervasively as it used to be. > Ok, so probably also in the doc the references to main() should be removed > too (or changing a little the paragraph to explaining that in code those > part has been removed because ...), right ?
I'm pretty sure I have removed most of these references - are you still seeing some? >>> - hello-bxml >>> Is there a way to write in page a title when bxml files are shown (for >>> example for hello.bxml and hello_javascript.bxml) ? >> >> In these cases, I think that the name of the file isn't all that relevant - > the content of the example is what is important. > Yes, but could be useful to simplify users that want to read a tutorial and > make experiments with code in the same time, so reading the file name of > bxml files could be useful to know what to open directly in the IDE, all > here ... It is possible - I believe the source XML contains the name of the file. We'd just need to update the XSLT to add it to the HTML output. Feel free to look into this if you are interested. >>> - stock-tracker.events.xml >>> The isn't a sample to explain how to link Actions from inside BXML files. >> >> That's OK - it is covered in another tutorial. > Ok, but what do you think to put a line of text there to say something like > "this is covered in the ... Tutorial" (even without an hyperlink, but just > as an info). I really don't think it is that big a deal, but feel free to add this if you like. >>> And a last question, not related to documentation: >>> in many samples I've seen that if we'd have an abstract class >>> (implementing Application, and with a default implementation of all >>> their methods) containing some common stuff (like a bindable Window, >>> and some commonly-used global variables like BXMLSerializer, >>> JSONSerializer, Resources, Locale, etc ...) maybe we could simplify >>> some tutorials and demos ... what do you think ? Or maybe if not for >>> Pivot itself, for one it its extensions ? >> >> Are you suggesting that we create a common default implementation of the > Application interface that we can use throughout the tutorial? > Yes, and maybe not only in tutorials ... I have considered this at various times, but there just doesn't seem to be that much commonality across our various demo and tutorial applications.
