KOffice GUI Competition Winner 204
Boudewijn Rempt writes "The KOffice GUI Competition has been won by Martin Pfeiffer. His entry was chosen from eighteen submissions by the jury because of its innovative, ground-breaking approach to workflow and document handling. Many submitters broke away from the beaten path and explored wild and wonderful ideas. The results page also has all submitted entries available for review."
Koffice only has one disadvantage (Score:1, Interesting)
uhgg (Score:4, Interesting)
I can't say that I'm very impressed with the winner or any of the runner ups. The OS community should seize the opportunity to accept and leverage professional interactive design.
The commercial software industry doesn't do this very well... does it's make sense to exploit this weakness?
Re:The actual proposal (Score:3, Interesting)
That would [protopage.com] never [palm.com] ever [chrischandler.com] happen [google.com].
We want verifiable results (Score:5, Interesting)
The issue is to do with fonts. I'd like to have a situation where the entire KDE desktop respects fonts selected by the still missing font manager. Right now, we have two areas where fonts can be configured and these are not [neccessarily] respected by all KDE apps! A wish issue has already been submitted.
Re:It's not shiney enough. (Score:2, Interesting)
Re:It's not shiney enough. (Score:5, Interesting)
What you need is "can't live without it once you've used it" features that aren't available elsewhere. I would have to say, after reading through his PDF submission, that, at the very least, there is the beginnings of a much more overview and workflow oriented approach to working with office documents that could be exceptionally powerful. Yes it needs to be implemented well and have decent scope. Ideally some manner of workflow view for an entire corpus of related documents - reports, spreadsheets, presentations, the lot - would be ideal. It takes a little imagination to see the full possibilities, but I think they really might be on to something here, and I am keen to see the final results.
Jedidiah.
What I'd like (Score:4, Interesting)
What I'd really like to see is a tool to remember what documents are associated with different projects. When I'm working on my "river1" report, for instance, I want to have "river1 draft manuscript.doc", "river1 budget.xls" and "river1 project plan.doc" open for easy access, and Matlab up with the path set to the river1 directory. I should be able to do all this with a single click.
When I'm working on the "Lake Suchandsuch" project, I want to be able to open a different set of tools and documents with one click: perhaps a putty terminal connected to my high performance computer account, a gvim window with "buggy code.c" open, and a PDF of a scientific manuscript with details of the algorithm I am trying to implement. Does anyone know of a tool that can do this?
Re:Check it out (Score:5, Interesting)
Re:The actual proposal (Score:2, Interesting)
It will be a nice concept, that will hopefully spawn more user friendly and easier to edit documents. I don't know how many times, I use OO.o, and wonder why they haven't tried anything new when it comes to GUI. There are a lot of problems with programs failing to try and "learn" the habits of a specific user. If I happen to use a certain tool a lot more than others. I want the icon to be on the toolbar if it isn't already. They are making improvements, but it will be a while before a dynamically created GUI specific to a user is automatically done over time.
When the program is your COMPLETE bitch, only then is it right to use.
Re:Koffice only has one disadvantage (Score:5, Interesting)
Actually, kword can open PDF files, which is something that openoffice still can't do AFAIK.
Re:It's not shiney enough. (Score:3, Interesting)
Some difference from iWorks??! (Score:4, Interesting)
Sorry for my blindness. But does somebody can point me the difference in the principle between this proposal and Apple iWorks already developed? I see the same style drawer, same page thumbnailer and so on. Currently I see worse iWorks clone, since iWorks/Pages2 offers you better working space since you use only the tools you need actually.
IMHO, @ KDE there was much better proposals than this one.
Am I missing something?..
Internal desktop (Score:4, Interesting)
Call it sour grapes... (Score:5, Interesting)
I don't know if my idea sucked or was plain and obvious, but it's a huge bummer it's not even on the results page for some reason, as though they never received it. Mine was an interface reorganization with an emphasis on a context-sensitive area to keep things familiar and free of clutter (first thing to go was that horrible toolbar).
I can't believe all this time I've been sitting here thinking they were reading it. I put a lot of work into it. I wonder what the heck happened.
Since it doesn't matter now, I offer it to Slashdot. Click here to read my entry in original PDF form [scaredlittleboy.org] if you want to check it out. Let me know what you think. It's nothing revolutionary, but it's not intended to be. These crazy experimental office interfaces are exactly what the user doesn't need.
Man, what a disappointment that they never even got it. Figures. But hey, I offer mine here as GPL too--if someone wants to use it for something, go right ahead.
Re:The actual proposal (Score:1, Interesting)
Re:The sorry state of Open Source user interfaces (Score:3, Interesting)
Out of curiousity, what are the various UI-related annoyances that are kicking around still? I'm not arguing, I'm just honestly curious as to what bugs you - maybe I, or someone, can try and help fix some of it.
Jedidiah.
Re:In search of the elusive paper replacement (Score:2, Interesting)
But as a synthesis on top of what I gather is the spirit of your comment, jotting ideas is naturally messy, and the act of refining and reflecting on these ideas before they are crystalized is an important part of the process. But since this interface might be so efficient with all of its patterns, someone will have made a permanent visual design decision while still in the middle of writing the content. That piece of paper in your pocket is the equivalent of the software throw-away prototype which should never be released (yeah right that rule never gets violated).
So it may turn out that this doesn't promote any process, but instead it creates a One-Stop Document Shop -- like email, it can be written and delivered before the author has even had time to realize what ended up in the document. (I just searched the document and didn't find any reference to KMail, I would have expected some challenge to Outlook in this integration.) On the other hand, when a word processor is too hard to use, the user might just click a template button, enter some content and press print.
BTW, while we're rethinking the word processor, isn't the save button antiquated? Shouldn't the application be journaling all my actions and if it crashes it opens in the exact state it left? There should really be more of a tagged version scheme where versions are explicitly tagged, but many more versions are automatically created and garbage collected over time when they aren't tagged for keeping. I would have to be retrained if this was implemented because I currently have a habit of hitting Ctrl + S pretty much after each mental breath I take.
Here's my usage model:
I immediately turn on the paragraph marks, get rid of a toolbars and menus and make the document full screen. The paragraph marks add extra noise to the document to help keep the flow going and make the big blank document not so intimidating.
It's only after I have at least a page of content before I start breaking it up with headings or however else I need to start bring more form to the document.
Re:The actual proposal (Score:1, Interesting)
What if KOffice could represent a complex koffice document in a virtual manner, the same way KDE media:// ioslaves can represent one audio CD as several virtual collections or the way amarok breaks down my music collection into several smart lists.
That is my new koffice view of a complex document could be represented simply as "(all) What I worked on last week", "Code-review of project-x for next week", "Your 2-weekly status notes for tomorrows meeting", disguising the fact each of those 'views' represents a mix of docs, sheets, slides, journal and calendar entries, etc.
Re:Call it sour grapes... (Score:3, Interesting)
The contest called only for an interface redesign searching for ideas that may be implemented in KOffice 2; perhaps it wouldn't have mattered either way if my submission went through, but I gave the link for anyone curious. Sidebars are hardly new, but I tried my best to document a set of workflow behaviors for each application to follow that makes the sidebar a useful tool. You can make things easier to remember for users, and that will go a long way toward speeding up their productivity. Office 12, despite its ribbon controls, is still a massive orgy of toolbar buttons that you'll hunt and peck through because it's all exposed at once. I tried to organize functionality so that you're always looking at only the functions you need at the time, yet you can easily move to a different set when needed (like clicking the Wrap tab to get functions to modify an object's layout, or clicking the List tab to format it as a bullet item).
Functional clarity (Score:3, Interesting)
I must say that your PDF reads much like an Apple GUI guideline, and not like something intended for KDE. What I mean to say is that it shows how much you value functional clarity (perhaps too much so, in the eyes of