I'm moving from the LGPL version into the Pro edition for any future projects I might do, and I'm having a hard time wrapping my head around some of the concepts of the Pro edition in practice. I've gone through a large lot of documentation from the quick start guide and samples, but maybe I'm just not there yet...
In the LGPL projects I worked solely with GwtRpcDataSource. This simply let me work with something that I was already familiar with. Granted the CRUD process was tedious to implement (backed by Hibernate, no DTOs though - was using Gilead), but I had complete control and understanding of what happened from GUI to DB.
1) Event fires on GUI.
2) The widget fires its DS' execute method. I would inject any extra criteria into the DSRequest as needed.
3) The DS makes a GWT-RPC call with the appropriate parameters based on the DSRequest criteria.
4) On the GWT-RPC callback, the returned POJOs are converted to ListGridRecords (usually) for the widgets to display.
This worked particularly well for me for situations where for example, a SelectItem gave suggestions as the user typed (by interrogating the DB, which has a _large_ dataset, and returning the results for the SelectItem to show on the fly)
How might this fit in with the Pro edition's workflow of having a DS generated from scratch, and GUI created with Visual Builder instead of with code?
In the LGPL projects I worked solely with GwtRpcDataSource. This simply let me work with something that I was already familiar with. Granted the CRUD process was tedious to implement (backed by Hibernate, no DTOs though - was using Gilead), but I had complete control and understanding of what happened from GUI to DB.
1) Event fires on GUI.
2) The widget fires its DS' execute method. I would inject any extra criteria into the DSRequest as needed.
3) The DS makes a GWT-RPC call with the appropriate parameters based on the DSRequest criteria.
4) On the GWT-RPC callback, the returned POJOs are converted to ListGridRecords (usually) for the widgets to display.
This worked particularly well for me for situations where for example, a SelectItem gave suggestions as the user typed (by interrogating the DB, which has a _large_ dataset, and returning the results for the SelectItem to show on the fly)
How might this fit in with the Pro edition's workflow of having a DS generated from scratch, and GUI created with Visual Builder instead of with code?
Comment