Modularity in the UI - Web Widgets?

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.

 

Parents
  • 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.

     

  • You can all see that this will not be an easy choice.   There is no perfect solution, and we are also attempting to anticipate not only technology but business needs many years into the future.    This is why the Development Team and Board Steering Committee have spent a lot of time and resources examining the merits of various choices.   The examination is being done from many perspectives: stability and compatability, ability to provide the functionality required to meet our current and future business requirements, longevity and vendor/community support and adoption, fit with the agile, test-driven development model, migration and conversion, training of development and support staff, training of Member administrators and end-users, and other considerations.

    The choice of Silverlight is by no means final, nor is it necessarily exclusive of also using other options side-by-side.   We have people with a great deal of expertise doing the technology spikes to help us arrive at the best possible choice, and that is a big part of the work being done now in the early stages of Release 1.   This input is excellent and appreciated, and I will also be interested to see the recommendations that come from the team as they do this work.

    Alan

  • Alan,

     

    I hope you didn’t see my comments and I suspect anyone else’s as something was bad or wrong.  I think we are all talking generalities and we are all out there guessing a bit.  I, like Mark, agree that it is exciting that Tessitura is taking this on in such a way to really discover what is best for the community.  I think Silverlight isn’t a bad choice, just something to be mindful of.

     

    I would love for you to put forth to the committee the idea of the Tessitura App Store (for lack of a better name).  It would be great that all of us can share and use each other code where it makes sense.  It also builds upon the idea that Chuck talked about yesterday of having a high degree of customization.  If we have this concept in mind while developing I think we could see a huge advantage over time.

     

    Just my two cents.

     

    Dave

     

    From: Tessitura Next Generation Forum [mailto:forums-nextgeneration@tessituranetwork.com] On Behalf Of Alan Levine
    Sent: Thursday, January 14, 2010 11:46 AM
    To: Dave Alton
    Subject: Re: [Tessitura Next Generation Forum] Modularity in the UI - Web Widgets?

     

    You can all see that this will not be an easy choice.   There is no perfect solution, and we are also attempting to anticipate not only technology but business needs many years into the future.    This is why the Development Team and Board Steering Committee have spent a lot of time and resources examining the merits of various choices.   The examination is being done from many perspectives: stability and compatability, ability to provide the functionality required to meet our current and future business requirements, longevity and vendor/community support and adoption, fit with the agile, test-driven development model, migration and conversion, training of development and support staff, training of Member administrators and end-users, and other considerations.

    The choice of Silverlight is by no means final, nor is it necessarily exclusive of also using other options side-by-side.   We have people with a great deal of expertise doing the technology spikes to help us arrive at the best possible choice, and that is a big part of the work being done now in the early stages of Release 1.   This input is excellent and appreciated, and I will also be interested to see the recommendations that come from the team as they do this work.

    Alan

    From: Morgan L'Argent <bounce-morganlargent2717@tessituranetwork.com>
    Sent: 1/14/2010 1:27:32 PM

    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

     




    You were sent this message automatically by www.tessituranetwork.com because you subscribed to the Tessitura Next Generation forum email notifications. You may reply to this message or visit the site to reply to the post above. If replying via email, please consider deleting the previous message text before sending to help with readability on the site. Thank you!

  • the Tessitura App Store - TAPPS

    Perfect name Dave, it encapsulates the whole concept. 

Reply Children
No Data