> - hello-world.xml > ...The sample <tt>HelloJava</tt> > application also defines a convenience <tt>main()</tt> > method that delegates to > <tt>DesktopApplicationContext.main()</tt>, allowing it to > be bundled in an executable > JARs and more easily launched from within an IDE. Defining > such a convenience method > is common practice in Pivot development. > </p> > But in the HelloJava sample (inside the page, and in the .java source) > the main method has been removed some time ago if I remember well ...
I removed the reference to the convenience main() method, since this approach is no longer used as pervasively as it used to be. > - 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. > And, in this section: > <p> > Most Pivot applications will be constructed this way, > declaring the structure of the > UI in BXML rather than creating it programmatically in > code. However, event handlers, > which allow an application to respond to user input, are > always defined in code (either > Java or a compatible JVM scripting language). For example, > the following BXML produces > output very similar to the previous two versions, using a > combination of BXML and > JavaScript: > </p> > I think it will be more clear (again, to newbies) that the following > part is related to something like an "All BXML" solution, for example > splitting the previous paragraph, and add a little spacing and a title > before the last section ... I hope to be clear, if not tell me :-) . I think this would be an artificial distinction. Compiled and script code can be freely intermingled in any application (and commonly will be). So I think it is best to leave it as is. > - stock-tracker.ui.xml > <h3>The Bindable Interface</h3> > Here there isn't a sample (BXML side, but aligned with the Java code > shown) of how to define elements inside BXML to be binded by code. > And I'd add a little more space just before the last part on > initialize() ... to better shown that's another section here. Done. > including JavaScript, Groovy, adnd Clojure, among others. > Any attribute value preceded by > a type error ... > initialization paramters for class instances declared as > elements. Script code can > a type error ... Fixed - thanks. > - stock-tracker.ui.xml > References to "@" symbols are still valid ? Yes - that's how we convert attribute values to URLs that are relative to the current document. > - 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. > 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? At this point, that probably isn't necessary, since most of the tutorials have been updated to use ScriptApplication as a launcher. G
