I'm delighted with the web centric approach to the next gen architecture. (Although a bit skeptical about Silverlight). In the "what's in it for me" vein I'd like to pose the following question:
Is it possible to develop the UI in such a fashion that modules, parts of the UI, could be used in our public websites? The most obvious example would be the patron's address/contact information.
I think all of us struggle with our development efforts and I am also concerned with Silverlight. While I understand the push to use something that is simple and straight forward (Microsoft Centric Approach), is it the best for longevity and compatibility. While MS currently supports Silverlight on various browsers that could change.
Using HTML 5.0, CSS, or a Javascript / Ajax option opens the entire community into an App store kind of approach. If Center Theatre Group develops this really cool widget and module, we could easily share it with the entire Tessitura community, and because it is using standards, more browsers and applications should be available.
Thoughts?
Dave
Perhaps we should start a Siverlight discussion. I'm glad I'm not the only skeptic.
Microsoft has a HORRIBLE track record regarding web compatibility. There are people very high in Microsoft who want to use the browser as a sales tools for their OS. Silverlight looks to be another example of this.
That being said, I do acknowledge the need for some kind of thin client development environment. The next gen cannot be done all in javascript. And there's not really much in the way of choice, Flash is not right, it may be that Silverlight is the only workable solution.
Dave: My thoughts exectly.
Mark: You said: "The next gen cannot be done all in javascript." I don't see why not. We're just talking about a client interface here. What is there, in the way of displaying/submitting/interacting with data, that couldn't be done with HTML and JavaScript?
-Morgan
Hi Morgan, I'm doubtful about doing a robust DB client in all AJAX mainly because of the need for strong type and syntax enforcement at the UI layer.
It can be done, but it requires a lot of custom development, rather than dropping a control on a form.