As the previous thread became a bit overloaded, I start a new one.
First I sum up where I am, a bit of the discussion with Malte, and I would like your comments on some points.
You can checkout the last version from the cvs (the version is reviewed by Andrew and Malte).
So 2 goals to be achieved with these changes :
-> the look and feel : should be more beautiful than ever (and no doubt it is already, except with IE), and should be super easy to change, for graphists to be able to adapt it for their own need, for the needs of their institution, etc)
-> the navigation process : is now very confusing. Users get lost between their own space and the communities's, they don't understand the difference between the control-panel and the control-panel.
What I've done for now :
-> use my own DefaultMaster : this is to remove all the old and unused css from the html header, and to adapt the html tags to the new css.
-> localized using catalog files not to rely on the next version of openacs. This is to be changed, as the next version of dotlrn will use OACS 5.2.
-> Added static tabs : this is part of the navigation process. These tabs should offer a kind of "reference" for users to navigate through the site. Done with parameter from the info file, so it will offer a way to create new tabs in the future, via an administration console (probably part of the control panel)
Now, apart from what we discussed and agreed with Malte, I would like opinion and ideas from everyone regarding some points :
-> The "you_are_here" : Malte thinks it is not obvious, I thought we could add a text above the tabs. Now it is, I would like what other thinks of that ? Is it still confusing where you are ? Is better in one way or the other ?
-> Breadcrumps : 1 line, 2 lines, 3 lines ? How would you organize it ? I'm removing the links "your account" and "logout" as they are already part (or will be) of the tabs navigation process. Anyway, this can be easily changed with modifying the css (so it is not a priority, even if we should agree on the final solution before next stable release)
Waiting for your comments, I'm going back to the code ![]()
Jeremy
Request notifications