Ilya A. Volynets-Evenbakh wrote:
User may have bunch of courses, are you going to open a new session for each course? What if user just created new subtopic or test and wants to assign it to couple of his courses? Why would we have a course Repository anyway? Is user going to login each time for each course? Keeping bunch of ids in environment not a very pretty idea, are you going to keep all hierarchy in environment too? What if you want to display the whole tree, for breadcrumbs, for example? Run additional query on View object page? All queries(ideally) should be run and displayed on "Repository_View" template. Consistency is a huge factor when you deal with complicated UIs.Sergey wrote:Anatoly Volynets wrote:Easy: nothing tragic happens (: Repository is the storage where authors shop for suitable UMOs. That's it! Author's workbench is his course, period. If he finds something in the Repository he, most probably edits it, puts it in his course and feels happy.The question is how does he put it in his course(what if he wants to add problem to the test that belongs to this TLT(course)?). How do we know to what course to put an object which user just foundusing repository search?User can only work on one course at a time. This means you keep current course/topic/etc. being edited in user's session.
Please make it clear if I have to stop doing my design and switch to having "one course per session" design. I don't want to waste my or company time. Thanks.What I'm currently trying to do is to somehow emulate user's experience with folders. Of course it won't be that pretty, but I'll try.We just need rough page-flow emulation with this. Of course it'll be prettier and easier in many ways with code.
Authoright © Total Knowledge: 2001-2008