Mon, 06 Oct 2008 17:52:02 -0400 http://bugs.horde.org/ticket/5749 A restructured view system with tabs for nag This is an attempt to restructure the view code in nag so that it supports the "Tab view" used in Turba and Kronolith. This is only a first draft and one thing not working is the JavaScript feature of switching the tabs. I did not understand yet how this works :) Anyhow I wanted to submit this early in order to see if it goes into the right direction. I'm happy if you point out my mistakes since this is my first attempt at getting deeper into the UI aspects of Horde. Thanks! Thu, 27 Sep 2007 04:06:13 -0400 http://bugs.horde.org/ticket/5749#t37117 Probably not necessary but this updates the patch to the recent CVS changes. Thu, 27 Sep 2007 11:44:13 -0400 http://bugs.horde.org/ticket/5749#t37132 Added missing loadChildren() call when viewing a task. Fri, 28 Sep 2007 11:33:54 -0400 http://bugs.horde.org/ticket/5749#t37153 Is there a specific reason you think that this is better? The tabs in Krono/Turba were kind of a compromise to spiff things up a bit to work with DIMP because there wasn't time to make the editing truly inline. If we're going to spend time on this in Nag, I'd rather do that. Fri, 28 Sep 2007 23:28:27 -0400 http://bugs.horde.org/ticket/5749#t37202 > Is there a specific reason you think that this is better? I had the impression that the code structure in Konolith/Turba was an example of how the newer apps should be constructed. I guess I might have been mistaken there :) In any case the main reason for restructuring was that I locally patched nag for recurrence support in the Kolab driver. For task recurrence I think you need a dedicated "CompleteTask" view which would also allow to have more options on tasks with subtasks (e.g. "Complete task including all subtasks"). In addition I also wanted to add the quick deletion link so I needed another deletion confirmation page. Adding two views that currently don't exist was the reason for restructuring and looking at the UI parts of Horde. > The tabs in > Krono/Turba were kind of a compromise to spiff things up a bit to > work with DIMP because there wasn't time to make the editing truly > inline. If we're going to spend time on this in Nag, I'd rather do > that. Care to explaine "editing truly inline"? :) Maybe you can point out if there is another app in Horde currently doing it in a way how it *should* be done so that I can use that as a basis for restructuring. Thanks for you comments! Sat, 29 Sep 2007 01:59:43 -0400 http://bugs.horde.org/ticket/5749#t37210 > In any case the main reason for restructuring was that I locally > patched nag for recurrence support in the Kolab driver. For task > recurrence I think you need a dedicated "CompleteTask" view which > would also allow to have more options on tasks with subtasks (e.g. > "Complete task including all subtasks"). In addition I also wanted to > add the quick deletion link so I needed another deletion confirmation > page. Adding two views that currently don't exist was the reason for > restructuring and looking at the UI parts of Horde. Okay. > Care to explaine "editing truly inline"? :) Maybe you can point out > if there is another app in Horde currently doing it in a way how it > *should* be done so that I can use that as a basis for restructuring. There is not inline editing that I know of anywhere in Horde. What I mean by that is having the display view also be the edit view - whether that means clicking a piece of text to turn it into an input control, or styling the inputs nicely enough that they look good for display, either is fine with me. Wed, 03 Oct 2007 20:50:54 -0400 http://bugs.horde.org/ticket/5749#t37382 >> Care to explaine "editing truly inline"? :) Maybe you can point out >> if there is another app in Horde currently doing it in a way how it >> *should* be done so that I can use that as a basis for restructuring. > > There is not inline editing that I know of anywhere in Horde. What I > mean by that is having the display view also be the edit view - > whether that means clicking a piece of text to turn it into an input > control, or styling the inputs nicely enough that they look good for > display, either is fine with me. Yes, this would definitely be nice. I know I'm unable to deliver such thing at the moment but maybe I can look at it later - especially when I know more about java script :). I'll keep this around as a local patch for my work environment at the moment so that I can use recurrence in nag. Thanks for the comments! Thu, 04 Oct 2007 01:11:32 -0400 http://bugs.horde.org/ticket/5749#t37385