Modularity in the UI - Web Widgets?

Thanks for the comment, Mark. 

We have had this discussion about the possible reuse of parts of the internal UI and I would say at this point it's a "would be nice to have" kind of thing.  Our goal at the moment is to design these things this way, but we also don't want to be constrained by HAVING to do it that way.  So we're going to see how things sort out in the design as we see how easy/difficult (expensive/not expensive) that becomes.

Thanks Chuck, I suspected that would be the answer. But I'm glad it's in the discussion. There may be a middle ground, sharing source, separate compiles ect. 

Certainly, this would need to be a bi-product of the development process and not a requirement.

Hello, all,

I just wanted to add that I, too am happy to hear about the web-based interface for the next gen project. However, I'm more that just a bit skeptical about Silverlight. Silverlight is pretty much DOA in my opinion (as a web developer). I'd love to see Tessitura embrace upcoming standards like HTML 5 and CSS 3. At the very least, I would heavily favor JavaScript (AJAX) over Silverlight.

The same also goes for the back-end business logic. At the conference, there was talk about using Ruby or Java to create the data services "modules" -- which would be great! But, I do understand the desire to leverage Tessitura's current .NET knowledge.

   -Morgan

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

I agree that NextGen should consider javascript/ajax approach.  I am also concerned about the Silverlight approach, and future browser compatibility issues.  Javascript libraries like jquery and jqueryUI are easy to use, fast, and highly functional.

I also encourage the development team to consider Ruby or Java for back-end programming.

the Tessitura App Store - TAPPS

Perfect name Dave, it encapsulates the whole concept. 

Dave,

on the contrary, the comments truly are helpful and welcome, and keep them coming.   I just wanted to point out how challenging a decision this will ultimately be, and that the team is giving it a great deal of careful consideration.  

I think I can safely say that you can count on the creation of some sort of mechanism for sharing custom widgets and other member-created components, just as Tessitura Network already provides a forum for sharing user-developed reports and utilities.

Alan

Hi All,

Good day.

I think Silverlight is interesting topic.

I don't think Silverlight try to replace Ajax or CSS at all, the target is Flash.

Is Microsoft Silverlight a Flash Killer?

So the point is: Do you think we should replace Flash with Silverlight in the NG Tessitura?

have fun

Ben

I'm just curious if there have been any decisions on the Silverlight vs. other options front. Alan? :)

No decisions yet.  We're actually working on a dual track approach in development right now, finishing 3 or 4 stories that have UI components in both extJS (a Javascript library) and Silverlight.  So far both have their ups and downs.  Silverlight make solving cross domain issues, much easier and has lots of visual and customization potential.  extJS makes TDD (Test Driven Development) easier, is more open but requires a bit more work on the security and is a slightly higher hurdle on the customization side.  Like most choices, there probably is not going to be an obvious answer but we're committed to learning as much as we can.  Then making a decision by the end of Iteration 4, in 3 more weeks.  And finally, of course, EMBRACING the decision.

Further thoughts here are always welcome!