From: sourceforge - T. i. <no...@so...> - 2010-06-02 10:12:48
|
#11420: MinGW: project "Files" view exhibits inconsistent behaviour --------------------------+------------------------------------------------- Reporter: keithmarshall | Status: new Keywords: | Private: 0 --------------------------+------------------------------------------------- The latest incarnation of the FRS "{{{all files}}}" view has created some serious problems for the MinGW Project, itemised in increasing order of severity from 1..4 below. I appreciate that you are trying to generate an improved user experience. First, you gave us a FRS with an extended hierarchical organization. This was a welcome enhancement, apart from the mind numbingly slow rendition of the accompanying "{{{View all files}}}" page. Now, you appear to be attempting to address this issue, and the current rendition does seem to be vastly improved in this respect. However, it is not without problems, some serious for this project: 1. Marshaling only the top level directories into the initial view does seem to provide a welcome speed boost, but do you really then need to invoke an entirely new page to expand a subdirectory view? Why not expand in place, within this initial page, as seems to be the intent within the subsequent subdirectory pages? This however, is mostly a cosmetic issue, and is the least of the problems. 2. For the MinGW Project, on selecting one of the directory links from the initial view, the behaviour on the subsequent subdirectory pages is inconsistent; for some such pages, the hierarchy is shown much as it was in the earlier (slow) rendition, but showing only a subset of the project's entire FRS hierarchy, and orders of magnitude faster than previous performance. For subdirectories which do behave this way, subject to the critique of (1), this isn't a problem. 3. For certain subdirectories, the behaviour described in (2) is NOT observed. For example, in the cases of our "{{{MinGW}}}" and "{{{MSYS}}}" directories, (our two PRINCIPAL top-level subdirectories), the hierarchical organization is NOT correctly depicted in the subdirectory view; all entries at the next level are depicted at the same level as the parent, as if they were its siblings rather than its children, and there are no "arrow" icons offering the ability to expand the subtree. In the cases of SOME of these degenerate subdirectory references, clicking through the link invokes a THIRD new page display, where the behaviour does seem to result in the appropriate hierarchical rendition. However... 4. In the particular case of the "{{{MinGW/BaseSystem}}}" hierarchy, (and there may be others, as yet undiscovered), clicking through the "{{{BaseSystem}}}" link invokes a third degenerate display, in this case showing ONLY the "{{{MinGW}}}" top-level directory and the one "{{{BaseSystem}}}" child, again depicting them as if they have a sibling relationship rather than a parent-child relationship, and there then seems to be no way to expose the underlying "{{{BaseSystem}}}" hierarchy, (which remains clearly visible in the "{{{Project Admin/File Manager}}}" view). This is a VERY SERIOUS PROBLEM for the MinGW project. -- Ticket URL: <http://sourceforge.net/apps/trac/sourceforge/ticket/11420> sourceforge <http://sourceforge.net/projects/sourceforge/> SF-project sourceforge |