[Building Sakai] [sakai2-tcc] Assignments 2

[Steve Swinsburg]

Having multiple UI frameworks doesn't matter so much, it's when they are unsupported and outdated that it becomes an issue.

It does make maintenance a hassle but if the version is supported it's not so bad. 

I don't think you could settle on one UI tech in this sort of community anyway though, since there are other frameworks  that will be better and people like to dev in what they know, and since they can. If this was commercial it would be a different story and everyone would be using Wicket. 

Portlets in uPortal are the same, they could be written in just about anything.  

Cheers
A


Gesendent von meinem iPhone

On 08/03/2013, at 0:47, "Mark J. Norton" <markjnorton at earthlink.net> wrote:

> >  I also agree with Matt that RSF could be considered an issue: nobody outside of Sakai uses it.
> 
> The fact that Sakai uses 6 or 8  different UI frameworks is an issue, some of which are out of date and unsupported.  The fact that RSF was a custom framework was discussed at the time we started using it.  It resolved some serious problems in JSF and was in use before JSF2 came out.  If the Sakai community plans to fix the UI framework problem, it goes much deeper than RSF.
> 
> - Mark Norton
> 
> 
> On 3/7/2013 5:01 AM, Adrian Fish wrote:
>> I'm in agreement with Chuck in that the effort should be expended to mutate the current code rather than embrace yet more uncertainty. The XML stuff is a pain in the derriere and needs pulling out into proper relationships, but it can be done. The statefulness can be sorted.
>> 
>> The Profile2 precedent that Megan offered is a little bit off the mark. Functionally, A2 does not offer enough above A1 to justify it being a replacement. Profile2 in functionally vastly superior to the Profile tool and was a no brainer replacement; you can't compare the Profile and Assignments1 scenarios.
>> 
>> I also agree with Matt that RSF could be considered an issue: nobody outside of Sakai uses it.
>> 
>> Cheers,
>> Adrian.
>> 
>> 
>> _______________________________________________
>> sakai-dev mailing list
>> sakai-dev at collab.sakaiproject.org
>> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
>> 
>> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"
> 
> _______________________________________________
> sakai-dev mailing list
> sakai-dev at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-dev
> 
> TO UNSUBSCRIBE: send email to sakai-dev-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20130308/da0edd93/attachment.html