Dear Casey,I'm the OpenSyllabus folk from whom you accidentally deleted the comment...So, I would like to get in my two cents worth on this issue. In so doing, I would like to make some complimentary comments with respect to what you have done, the GWT program, not the deletion. ;-) At first sight, your StringReverser example seems not too far from our own HelloGWT Sakai's tool (Random Number Generator) using RPC communication.As I have written in my best post ever done in English, but tragically lost forever in the cyberspace ;-), last September, the OpenSyllabus team stopped its effort on the HelloGWT just waiting for "popular demand". The HelloGWT code was done but we still had to write the tutorial. Maybe we were too much ambitious at that time and we should have published the code « as is ». So the need is there now! Furthermore, the timing is right since we are planning our next Sprint development step.Meantime, you could visit the OpenSyllabus Web site, and give a look at our integration strategy based on previous work by Luis Filipe Lobo and George Georgovassilis. From our side we will put links to your blog.I will keep you in touch with the tutorial.No grudge held for the deleted comment. It is also happening to me. But this time, I will make a copy...Greetings from Montréal, in minus 25 degree CelsiusClaude Coulombefor the OpenSyllabus Team
Hi Claude,Thanks for coming back!The StringReverser itself came from another fine site; I just used it to reduce the chance that my inexperience ( to say the least ) with GWT wasn't a factor.As it is already nicely packaged and 'ready to go' I just re-arranged it into Aaron's App creator layout and did some wiring.What my experiment does not address is the developer's workflow. I think this will be a bit of a stumbling block and is why previous pioneers split up their projects.My next steps will be to steal Luis's build.xml and Eclipse project packaging scheme to at least allow the merged app to build in Eclipse. I want to reach a state where my Sakai side logic is all in a webservice and I can hack on the UI using some kind of Hosted Mode to the webservice. Yes I am waving hands. :)
Greetings Casey,You have got me again....I would like to share our proposed development cycle with GWT and Sakai to your sagacity.In a nutshell, let me summarize our findings in view of the development workflow :* Use case A - client update only, in "Hosted Mode"* Use case B - backend update only, involving Sakai Application Compilation and deployment with maven (separately or using the eclipse Maven plugin)* Use case C - full compilation when for example you change the communication interfaceTo save time, use "Hosted Mode" as much as possible for client code developments, because,it is faster than a GWT compilation.I hope this could make a contribution to your reflection on GWT development with Sakai.Greetings from Montréal, in minus 30 degree CelsiusClaude Coulombefor the OpenSyllabus Team
Oh Claude of the frozen north,Yes, I sometimes have occasion to lament having left Rochester NY a few years ago to languish here, skiing in warm sunlight and giant mountains.but I know your city is beautiful!* brrrr *I'm looking forward to checking out your workflow document.In some ways the workflow I'm thinking about isn't much different from those where you have to punch out client side code for WSDL stuff.
Post a Comment