Read through HelloWorld and Calculator examples, what’s next?
We are definitely preparing to give out more examples. In mean-time, you can read through the examples available in millstone.org. Just change org.millstone.base → com.itmill.toolkit.
We will deploy few samples more within couple days. Package contains demo for using QueryContainer (Table, Tree or Select), Modal window and Tree sample.
When are these coming?
Testing version of 4.0.1 is accessible from
http://toolkit.itmill.com/testing
, please have a look. It contains 14 new demos and source code for all the demos, including feature browser.
Testing version of 4.0.1 is accessible from
http://toolkit.itmill.com/testing
, please have a look. It contains 14 new demos and source code for all the demos, including feature browser.
Thanks for the examples!
Many things got clear reading those small samples.
If it is possible it is nice to see some bigger examples of ‘real’ applications. Also I would like to see what strategies there is to do ‘page’ transitions.
-John
In many cases there is no need for ‘page’ -concept in application. But sometimes it is surely needed. In those cases many applications create a View -interface and somekind of Navigator class that controls View transitions.
For example, if you are implementing a CRM -software, you probably want to have customer, contact and meeting in your data-model. Say, you
implement those with data-classes Customer, Contact and Meeting. To show and edit those data classes in UI, you might want to implement UI-components CustomerView, ContactView and MeetingView. A simple way of implementing such classes is to extend CustomComponent. In order to navigate between those (link to each other for example) it is wise to create a View -interface that is implemented by all view-classes. You could include methods like getViewTitle() in the View interface. To navigate between Views, you can implement Navigator class that listens to requests for changing between view and opens corresponding Views in to UI to correct place. Navigator can also query from views (through View-interface) if is possible to navigate away from current View (if user has saved the changes). An you can implement linking from outside web-pages by interpreting get-parameters or uri-parts (parameter handler or uri handler) in Navigator. Also it is typical to maintain history of past views in Navigator to access recent data-items easily.
Of course there are many other patterns for implementing the page concept, but this one has been proven in many production applications.