On Thu, Jul 14, 2011 at 9:35 PM, Phaneendra Hegde <[email protected]> wrote: > Hello everyone , > I'm a GSoCer and working on a nepomuk based project called Fancy-Bookmarking > for Rekonq. Details and current state of my project can be found here and > source code can be found here > Main feature of this bookmarking tool is to provide > rating,tagging,commenting on a webpage. One more Important feature is to > provide the facility to relate the webpage to different nepomuk resources > (like pimo::person,project,task,location etc) . I have already pushed a > working model to a branch (fancy-bookmarking) . > I have a couple of questions here - > > Now I'd like to separate tagging,rating module from resource linking module. > So I'd like to open resource linking dialog in one click/key stroke . Where > can I add this button/link in the main window of rekonq? Just like, how edit > bookmark widget appears whenever I click on bookmark icon,I would like to > have a button in the main window itself. > Tagging,commenting and rating have been merged with existing editbookmark > widget. How can I improve it's GUI? What kind of UI do you recommend for > showing previously created tags? > > I have discussed this in #rekonq (freenode irc) and I'm asking all of your > opinion in order to give best result. Feel free to mail me or contact me in > #rekonq or #nepomuk-kde (IRC nick- pnh7) > You can also give your suggestions in the techbase project page . I welcome > your comments and suggestions. > > Regards > Phaneendra Hegde > - PNH
Why do you want to separate the resource specification and bookmarking interfaces? This seems to me to complicate the interface and separate what I think should be related actions. I also don't think there is a way to do this without either cluttering the UI or making it hard to find. I would think it would be better to integrate the functionality into the existing boomark creation dialog (what you get when you click the "make bookmark" button twice). As I see it, you need to be able to do various things in the dialog: 1. Rename the bookmark 2. Remove the bookmark 3. Rate the bookmark 4. Set the bookmark folder 5. Set the bookmark tags 6. Link the bookmark to resources 1 and 2 are already there. 3 is easy to add, just left or right-align the "remove" button and then add stars next to it. 4, 5, and 6 are more difficult, since they need relatively large UI's. I see a few ways to integrate them: 1. Have a quick way to add the features, and a button next to each one that, when clicked, expands the dialog to include a more complete interface. This is how firefox does it. So for example the folder list has a list of common folders that expands to a list of all folders, tags has a text entry field (probably with autocompletion) that expands to include a list of checkboxes for existing tags, and the resource would probably start as a dropdown with common and/or in-use resources and expand to have checkboxes for all resources. This has the advantage of making everything readily available, but has the disadvantage of taking a lot of vertical space. 2. Just have the buttons to expand the interface. So there would be the basic interface with the name, remove, and ratings buttons, then at the bottom would be three more buttons: tags, folders, and resources (or whatever you want to call the last one). When clicked each button would expand to show the interface for that action (similar to the interfaces in 1). This makes doing simple actions harder, but taks much less vertical space (since all the buttons can be in one row). 3. Use tabs or buttons that switch between modes. Initially it would open to the default view, and when a tab or button is clicked it switches to the interface for that action, changing size as-needed. The tabs or buttons would be the same as in 2. This takes up even less space than 2 since the more specialized interfaces would not include the basic interface. 4. Rework everything to use the messadialog interface (like the password dialog) or add something at the top of the page similar to the new dolphin search interface. This would put everything in one or two rows, and would probably have buttons to expand dialogs with the specialized interfaces at the bottom. This would have the advantage of not blocking the web page, but has the disadvantage of requiring larger mouse movements. Otherwise it is similar to 2 or 3. -Todd _______________________________________________ rekonq mailing list [email protected] https://mail.kde.org/mailman/listinfo/rekonq
