Slow Resources rendering time in 2.5 with large numbers of items in a folder

Wed Apr 16 19:26:50 UTC 2008

Adding the Resources DG to the CC list and removing the "content"  
group (which is the group focused on support for authoring in sakai).

Jim

On Apr 16, 2008, at 3:11 PM, Knoop, Peter wrote:
> Hi,
>
> I wanted to bump this thread again as we are rapidly approaching the
> deadline (21 April) for fixes to be include in the 2.5.1 release from
> the 2.5.x maintenance branch:
>
> http://bugs.sakaiproject.org/jira/browse/SAK-13292
>
> No one has reported trying the new version of Dojo to determine if it
> addresses the performance problems, so at this point things are  
> leaning
> towards a quick fix that would eliminate the performance problem.  As
> noted previously this would also take us back to 2.4.x-style, non-Dojo
> menus and behaviors.
>
> Is there anyone who has time to test out if the newer version of Dojo
> will address the performance concerns in time for the 2.5.1 deadline?
> Otherwise, we can revert the menus and address the performance  
> concerns,
> and strive for a better fix in time for 2.5.2 in a couple months (and,
> of course, available in 2.5.x as soon as it is ready.)
>
> Are there strong opinions one way or the other on the issue of whether
> it is better to live with the performance problems and the Dojo menus,
> or better to fix the performance problems and revert the menus to the
> old style and behavior?  My sense at the moment is that the  
> majority is
> interested in fixing the performance problems.
>
> Thanks.
>
> -peter
>
>> -----Original Message-----
>> From: fluid-work-bounces at fluidproject.org [mailto:fluid-work-
>> bounces at fluidproject.org] On Behalf Of Clay Fenlason
>> Sent: Friday, March 28, 2008 2:58 PM
>> To: sakai-dev at collab.sakaiproject.org;
> content at collab.sakaiproject.org;
>> fluid-work at fluidproject.org
>> Subject: Re: Slow Resources rendering time in 2-5-x
>>
>> Those were the UX reasons for preferring the widgets introduced in
>> 2.5, yes.  The mouseover dropdowns have not been well received here,
>> and we wouldn't want to work toward a mere reversion to the 2.4 case
>> as a result.  We need to see the 2.4 nuisances addressed without
>> introducing a performance hit, and that should be achievable.
>>
>> ~Clay
>>
>> On Fri, Mar 28, 2008 at 2:28 PM, Knoop, Peter <knoop at umich.edu>  
>> wrote:
>>> So one option here is to switch back to the 2.4 style menus.  If we
>> did
>>>  so, what fixes or enhancements might we potentially loose?  It
>> sounds
>>>  like the accessibility issues have been addressed to a degree in
>> 2.4.x.
>>>  We would potentially be bringing back two undesired behaviors
>> (though
>>>  they might be fixable with a little work): whenever the mouse
> passes
>>>  over the menu in 2.4.x it pops up obscuring the content underneath,
>> and
>>>  the menu always pops-down even when you're at the bottom of the
> page
>> and
>>>  it will go off-screen.
>>>
>>>  Are there other behaviors or potential losses of functionality that
>>>  might concern folks, if we switched resources back to using the
>> 2.4.x
>>>  style menus?
>>>
>>>  Thanks.
>>>
>>>  -peter
>>>
>>>
>>>> -----Original Message-----
>>>> From: Jim Eng [mailto:jimeng at umich.edu]
>>>
>>>> Sent: Thursday, March 27, 2008 4:20 PM
>>>
>>>> To: ieb at tfd.co.uk
>>>
>>>> Cc: Clay Fenlason; sakai-dev at collab.sakaiproject.org;
>>>> content at collab.sakaiproject.org; fluid-work at fluidproject.org
>>>
>>>
>>>> Subject: Re: Slow Resources rendering time in 2-5-x
>>>>
>>>> We switched to dojo on recommendation from fluid because the dojo
>>>> menu buttons were thought to be more accessible than the
>> "homegrown"
>>>> menu buttons in 2.4.x that were based on static unnumbered list
>>>> elements and css.
>>>>
>>>> At this point, though, I think Gonzalo has improved (fixed,
>> maybe?)
>>>> the accessibility of the menu buttons in 2.4.x, and there are
>>>> problems with the dojo menu buttons in 2.5.x (including
>> accessibility
>>>> issues?).  Sakai 2.5.1 might be a good time to switch back to the
>>>> menu buttons used in 2.4.x.
>>>>
>>>> Ducking for cover, now.
>>>>
>>>> Jim
>>>>
>>>>
>>>>
>>>> On Mar 27, 2008, at 3:17 PM, Ian Boston wrote:
>>>>
>>>>> Here is a dumb question, why are we using dojo and dom
>> manipulation
>>>>> to build lots of menues, when perhapse pure css menus and
> static
>>>>> markup would work with all our target browsers ( inc ie6 AFAIK)
>> ?
>>>>>
>>>>> Or am I missing something about the behaviour of these menues
> or
>>>>> the set of target browsers.
>>>>>
>>>>> As I said, its probably a dumb question, please shout if it is.
>>>>>
>>>>> Ian
>>>>>
>>>>> Sent from my Pearl, sorry about the briefness and spelling!
>>>>>
>>>>> -----Original Message-----
>>>>> From: "Clay Fenlason" <clay.fenlason at et.gatech.edu>
>>>>>
>>>>> Date: Thu, 27 Mar 2008 14:09:56
>>>>> To:sakai-dev at collab.sakaiproject.org,
>>>>> content at collab.sakaiproject.org,       "fluid-
>>>>> work at fluidproject.org" <fluid-work at fluidproject.org>
>>>>> Subject: Re: Slow Resources rendering time in 2-5-x
>>>>>
>>>>>
>>>>> On Thu, Mar 27, 2008 at 1:00 PM, Stephen Marquard
>>>>> <stephen.marquard at uct.ac.za> wrote:
>>>>>> Hi all,
>>>>>>
>>>>>>  I haven't had any responses to this so am asking again.
>>>>>>
>>>>>>  Are the dojo/dijit buttons a dead-end or can they be
> improved?
>>>>>
>>>>> I don't know, but perhaps a JS maven on the Fluid lists might
>> have
>>>>> some suggestions.  Colin or Eli?  Client-side caching of some
>> sort?
>>>>>
>>>>>>  Are other sites going into production with 2-5-x concerned
>> about
>>>>>> rendering time for Resources with large sets of files, or do
>> most
>>>>>> sites only put a few things in each Resources folder?
>>>>>
>>>>> We're concerned.
>>>>>
>>>>>>  Is anyone actively working on or supporting the current (2.5)
>>>>>> Resources code, or is everyone on other projects or working on
>>>>>> complete replacements?
>>>>>
>>>>> The Resources code is being supported in maintenance mode, yes,
>> but
>>>>> it's fair to say that new development energy is oriented more
>> toward
>>>>> replacement tools and widgets.  I think we'd be ready to
>> contribute
>>>> to
>>>>> working out a solution for this particular problem.
>>>>>
>>>>> ~Clay
>>>>> _______________________________________________
>>>>> fluid-work mailing list
>>>>> fluid-work at fluidproject.org
>>>>> http://fluidproject.org/mailman/listinfo/fluid-work
>>>>>
>>>>> ----------------------
>>>>> This automatic notification message was sent by Sakai Collab
>>>>> (https://collab.sakaiproject.org/portal) from the DG:
>> Development
>>>>> (a.k.a. sakai-dev) site.
>>>>> You can modify how you receive notifications at My Workspace >
>>>>> Preferences.
>>>>>
>>>>>
>>>>>
>>>>
>>>> ----------------------
>>>> This automatic notification message was sent by Sakai Collab
>>>> (https://collab.sakaiproject.org/portal) from the DG: Content &
>> Author
>>>
>>>
>>>> site.
>>>> You can modify how you receive notifications at My Workspace >
>>>> Preferences.
>>>
>>>
>>>
>>
>>
>>
>> --
>> Clay Fenlason
>> Director, Educational Technology
>> Georgia Institute of Technology
>> (404) 385-6644
>> _______________________________________________
>> fluid-work mailing list
>> fluid-work at fluidproject.org
>> http://fluidproject.org/mailman/listinfo/fluid-work
>
> ----------------------
> This automatic notification message was sent by Sakai Collab  
> (https://collab.sakaiproject.org/portal) from the DG: Content &  
> Author site.
> You can modify how you receive notifications at My Workspace >  
> Preferences.
>
>
>