On 04/03/2012 07:23 PM, Andy Fitzsimon wrote:

On 04/04/2012, at 12:41 AM, Hugh O. Brock wrote:

I firmly believe non-JS support should continue to be a hard
requirement for us, both for US Govt. accessibility requirements and
because it's good coding practice.

Having said that I am also absolutely certain that we will not have
scope for that level of change to the Katello UI over the next year,
given the rest of the issues on the agenda. So I think we'll have to
live with the difference until then (which is really more or less OK,
given that we don't really know what shape the combined app will take
over time).

Take care,
--H


+1 to this.

 let's not go backwards with out decision making.    
we need to be ready for both states of user activity and hopefully katello can catch up later down the track.

Agreed, we can accomplish this via graceful degradition [1] or progressive enhancement [2]. (correct me if I'm wrong but I believe we are currently doing the later, which is more preferable).

In any case, as far as $topic, are there any screenshots or similar available of what the currently Katello interface looks like? Also what is the scope of this feature? Will there be links to both applications in the shared templates? What will happen if the user only has one of the applications installed? (eg Aeolus without Katello or Katello w/out Aeolus)

  -Mo

[1] http://en.wikipedia.org/wiki/Unobtrusive_JavaScript#Degrading_gracefully
[2] http://en.wikipedia.org/wiki/Progressive_enhancement