[kune issues] #170: Simple is better, and I've got a good idea how to do it!
#170: Simple is better, and I've got a good idea how to do it! -------------------------+------------------- Reporter: ogoldberg@… | Owner: vjrj Type: enhancement | Status: new Priority: major | Milestone: Component: Usability | Version: Keywords: | Blocked By: Blocking: | -------------------------+------------------- I really love what you guys are doing here, but you have a major usability problem. Your interface is just too complicated and too confusing, and it looks old. When I show Kune to my friends they don't understand it, and they think it is "primitive"--which is the opposite of the truth! This can be fixed! I have a great idea to make things really simple and easy to understand without compromising any functionality. '''What if there was only page to interact with and it had three columns?''' 1. one narrow column on the far left listing the different groups (one group could be "all waves", one group could be "public waves", and then whatever groups the user adds--and a plus sign to make new groups) 2. another narrow column that lists the different types of waves within that group (barter, document, wiki, tasks, etc. and a plus sign to create a new 'type' of wave)--similar to the one currently on the left, but with the ability to add new "types". 3. a third column (wider) that lists the waves in that group, or the currently selected wave, depending on whether a wave is selected (the same way it is now) I think that would be ideal. Everything would be much more simple and easy to understand. What do you think? -- Ticket URL: <http://kune.ourproject.org/issues/ticket/170> kune issues <http://kune.ourproject.org/issues/>
#170: Simple is better, and I've got a good idea how to do it! --------------------------+------------------ Reporter: ogoldberg@… | Owner: vjrj Type: enhancement | Status: new Priority: major | Milestone: Component: Usability | Version: Resolution: | Keywords: Blocked By: | Blocking: --------------------------+------------------ Comment (by anonymous): I have a wave where I am refining these ideas here: [[BR]]http://kune.cc/waveref/kune.cc/w+12976zqc0e083Ck/~/conv+root/b+16rwa08l3y0rn... !wave://kune.cc/w+12976zqc0e083Ck/~/conv+root/b+16rwa08l3y0rnCl -- Ticket URL: <http://kune.ourproject.org/issues/ticket/170#comment:1> kune issues <http://kune.ourproject.org/issues/>
#170: Simple is better, and I've got a good idea how to do it! --------------------------+------------------ Reporter: ogoldberg@… | Owner: vjrj Type: enhancement | Status: new Priority: major | Milestone: Component: Usability | Version: Resolution: | Keywords: Blocked By: | Blocking: --------------------------+------------------ Comment (by vjrj): Great, if you can add a simple mockup, will be easy to understand your proposal. Some fast comment. Take in to account some things: - There exist contents (waves) from users to users (1-to-1 comunication) that not belong to any groups - Wave is not the only content type (think in chat rooms, etc, but more to come) - The part we evalute now is the client "backend", "the content generator". The other big goal is to produce a public customizable frontend, the public web space of groups, more static, etc. Thanks for your feedback -- Ticket URL: <http://kune.ourproject.org/issues/ticket/170#comment:2> kune issues <http://kune.ourproject.org/issues/>
#170: Simple is better, and I've got a good idea how to do it! --------------------------+------------------ Reporter: ogoldberg@… | Owner: vjrj Type: enhancement | Status: new Priority: major | Milestone: Component: Usability | Version: Resolution: | Keywords: Blocked By: | Blocking: --------------------------+------------------ Comment (by ogoldberg@…): Great idea! I will try to mock something up. to your comments: * In the far left column, there could an "ungrouped" group, or something like that..."general communication" maybe...anyways, the name might be tough, but the idea is simple. A group for threads without a group. * I guess I didn't realize there would be different kinds of content, but the second column could list all those things, and the big column could have waves, chatrooms, etc. * makes sense for you to prioritize whatever you think is most important. A solid back end is very important. However, I don't think a customizable frontend should be a priority. I would recommend focusing on making an end product that works great the way it is, and add customizing later. It seems less important to me than having something that looks attractive by default, just works, and has as small a learning curve as possible for new users. The ability to customize appearance is not a substitute for something that looks good out of the box, and if the product isn't really easy to understand and use, then there will be no users around to use the customization features. -- Ticket URL: <http://kune.ourproject.org/issues/ticket/170#comment:3> kune issues <http://kune.ourproject.org/issues/>
#170: Simple is better, and I've got a good idea how to do it! --------------------------+------------------ Reporter: ogoldberg@… | Owner: vjrj Type: enhancement | Status: new Priority: major | Milestone: Component: Usability | Version: Resolution: | Keywords: Blocked By: | Blocking: --------------------------+------------------ Comment (by vjrj): Can you add @kune.cc to the participants of that wave? (to make it public) so we can continue there... -- Ticket URL: <http://kune.ourproject.org/issues/ticket/170#comment:4> kune issues <http://kune.ourproject.org/issues/>
#170: Simple is better, and I've got a good idea how to do it! --------------------------+------------------ Reporter: ogoldberg@… | Owner: vjrj Type: enhancement | Status: new Priority: major | Milestone: Component: Usability | Version: Resolution: | Keywords: Blocked By: | Blocking: --------------------------+------------------ Comment (by ogoldberg@…): Didn't know I could do that! Cool. Done! Please come join the conversation! Replying to [comment:4 vjrj]:
Can you add @kune.cc to the participants of that wave? (to make it public) so we can continue there...
-- Ticket URL: <http://kune.ourproject.org/issues/ticket/170#comment:5> kune issues <http://kune.ourproject.org/issues/>
#170: Simple is better, and I've got a good idea how to do it! --------------------------+------------------ Reporter: ogoldberg@… | Owner: vjrj Type: enhancement | Status: new Priority: major | Milestone: Component: Usability | Version: Resolution: | Keywords: Blocked By: | Blocking: --------------------------+------------------ Comment (by anonymous): I posted a mockup on the wave referenced above. I have since refined my idea, but it won't let me post the new version or make any additional changes to the wave at all. I made a new wave to post my revision: [[BR]]http://kune.cc/waveref/kune.cc/w+HNFqlGcsihA/~/conv+root/b+HNFqlGcsihB !wave://kune.cc/w+HNFqlGcsihA/~/conv+root/b+HNFqlGcsihB -- Ticket URL: <http://kune.ourproject.org/issues/ticket/170#comment:6> kune issues <http://kune.ourproject.org/issues/>
#170: Simple is better, and I've got a good idea how to do it! --------------------------+------------------ Reporter: ogoldberg@… | Owner: vjrj Type: enhancement | Status: new Priority: major | Milestone: Component: Usability | Version: Resolution: | Keywords: Blocked By: | Blocking: --------------------------+------------------ Comment (by vjrj): Sorry, we have some hardware problems with kune.cc. We'll try to follow with this issue (and fix the problem) ASAP. Some nice logs: [545451.972708] ata1.00: status: { DRDY } [545451.973350] ata1: soft resetting link [545452.423981] ata1.00: configured for MWDMA1 [545452.424599] ata1.01: configured for MWDMA2 [545452.424618] ata1.00: device reported invalid CHS sector 0 [545452.424630] ata1: EH complete [545535.917105] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen [545535.917832] ata1.00: failed command: WRITE DMA [545535.918351] ata1.00: cmd ca/00:08:f0:98:54/00:00:00:00:00/e0 tag 0 dma 4096 out [545535.918353] res 40/00:01:00:00:00/00:00:00:00:00/a0 Emask 0x4 (timeout ... -- Ticket URL: <http://kune.ourproject.org/issues/ticket/170#comment:7> kune issues <http://kune.ourproject.org/issues/>
#170: Simple is better, and I've got a good idea how to do it! --------------------------+------------------ Reporter: ogoldberg@… | Owner: vjrj Type: enhancement | Status: new Priority: major | Milestone: Component: Usability | Version: Resolution: | Keywords: Blocked By: | Blocking: --------------------------+------------------ Comment (by vjrj): The hw Issue is solved (thanks to Javier)... more comments in that waves... -- Ticket URL: <http://kune.ourproject.org/issues/ticket/170#comment:8> kune issues <http://kune.ourproject.org/issues/>
participants (1)
-
kune issues