Re: [LogiLogi-list] UI Integration - Editing
Status: Beta
Brought to you by:
wybow
|
From: Bruno <bs...@gm...> - 2008-09-16 11:41:50
|
On Tue, Sep 16, 2008 at 8:13 AM, Wybo Wiersma <wy...@lo...> wrote: > The new logi here overlaps, just like in Bruno's proposal, but I added > a check for existing logis, and a little tabbed tool at the top for > selecting wheither to add a logi, a link or a remark. > > Besides, I think that because of the width of the new logi wizzard we > cannot have it embedded at the bottom for remarks, so always have > commenting logis via this little wizzard. Also I think the eye-candy > idea of replacing the surroundings with the wizzard won't work for the > same reasons (and having just the logi in the middle to select a bit > from and then the commenting logi to add below is neater...), so it's > in the middle now... > First of all I like it, but I see some problems. Also I'm starting to enjoy this creative process we are all doing. We propose opposite things, and after that you start making tests with my proposal and I start making with yours. I'm more convinced about the new-logi-editing should be at the right now than at the middle. I already thought we have it decided, but this las proposal has many variations, that would go for the logi on the right side too. There ara two problems I see now with the new-logi overlaping the other. First the one that convinced me, as you said that you cannot read the rest of the logi, and I think this will be a problem. The other is that I don't like to move the log arround anymore. Although it's clear and it would work, I really liked the approach of keeping the logi static and moving things arround, it was kind of a strong concept. On the other hand, it would be nice to make a entire UI layout where the logi is at the center, but... not now the time to thing about that :) Other potential problem I see is the comment, remark, link tabs being a bit out of sight. At first I think this tabs could be right on top of the wizzard, as this is the only part that would change when the tabs change, but this need to be thinked in global. Those are the problems I see, but still, this is already a great approach and we have just to decide little problems. > Tags are added via an add-tag button, just like in the navigation/query- > bar. This makes the check possible, and when in the tagg-add-textfield: > - enter adds the just typed tag > - backspace in the empty field removes the previous tag > It is just as easy as a normal text-field with added advantage of easy > checks and auto-completion for existing tags... > > Idea is to have this new logi box also when editing a logi, but then > without the check. > I love the compact logi creation wizzard we'll have, and the tag addition, removal and verification is very neat :) > We might by the way consider having the new logi not overlapping, but > going there via an anchor when selecting some bit of text. At least > otherwise we must not make it disappear & lose all data when the user > selects (or wants to select) a different snippet of text, as that > would be hugely frustrating; selecting a bit, typing a whole logi, > then wanting to add or remove a word in the selected snippet and > losing all work... > it would be good to have some temp memory, drafts :) > Hope we can move to a better wizzard in this way :) > > (maybe what we also could do is have the user to select a bit of text, > then via anchor to the tabbed tool-thingy, which is now below the logi > & then allow him to fill in the fields for the new one, but don't know > about this...) > I didn't understand this well... We'll talk this at the #logilogi now :) Although with some problems, the overlaping option seems rasonable, and maybe it centered too, but I would like to meditate this a little bit more... not much :) greetings -- Bruno |