Re: [libreoffice-design] Welcome
Hi Budislav, Am 14.06.2011 01:14, schrieb Budislav Stepanov: I am student of Graphic Designs on University of Novi Sad, part of European University Network, I found this place where I think that i can show my abilities. Primarly I am web designer, but this includes almost all kind of graphic on web or softwere, and the user interface in general.I am willing to help in the further development :) Welcome here. You can inform yourself at our wiki pages and here on ml. There are many open issues on the sectors you named above. As start page have a look: http://wiki.documentfoundation.org/Design The work will come if you want some ;-). But if you want to do something now as a webdesigner please have a look at this threads belonging to our new Extension website: extension website: http://listarchives.libreoffice.org/global/website/msg04991.html extension logo: http://listarchives.libreoffice.org/global/design/msg02184.html -- Grüße k-j -- Unsubscribe instructions: E-mail to design+h...@global.libreoffice.org Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/design/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-design] Extra-large 'slide design windows' in Impress - Possible Usability Issue
Hi Christoph, Issue 38299 has been created @ https://bugs.freedesktop.org/show_bug.cgi?id=38299 personally I found the Impress behavior to not mis-use the vertical scrollbar more logical. I agree with you on this. I feel that if a vertical scroll bar is present in the Slide view then the Up and Down keys should scroll rather than flick through slides. This is why I was proposing to remove the Vertical and Horizontal scrollbars from the Slide view (at the default zoom at least - I reckon zoom is very rarely used in Impress) by having the Slide window sized to fit the slide with maybe 100 px of padding (as Powerpoint have done). However, in section 1.2.2 on Scrollbars in the Slide view, the OOo team have made the decision to remove the horizontal scrollbar but under vertical scrollbar it says TBD. Personally, I hope they took the decision to remove the vertical scrollbar since in section 1.6 they have determined that the up and down key should, in fact, change slides when used in the Slide view. It would be unnatural to have a scrollbar present and not have the arrow keys control it Thanks for your help on this, Patrick On 13 June 2011 20:29, Christoph Noack christ...@dogmatux.com wrote: Hi Patrick, thanks for you mail! Am Sonntag, den 12.06.2011, 17:56 +0100 schrieb Patrick Scott: Hi all, I have a lot more experience with Powerpoint 2007 than I have with LO Impress. One of the habits I brought from Powerpoint was flicking through slides while in design mode by pressing the Up and Down arrow keys. I immediately noticed that this doesn't work in Impress because the arrow keys are used to scroll up and down in the slide design window. That led me to ask the question; why is there a huge amount scrollable white space surrounding the slide in the Impress slide design window? In Powerpoint the window is 'fitted' to the slide but in Impress there is roughly 800 pixels of empty padding to the left and right of the slide and there is about 300 - 400 pixels of empty padding above and below the slide. I was considering filing a bug for this because I think it would be helpful for Powerpoint converts to abolish this empty space and free the Up and Down arrow keys for cycling through the slides. However, I thought it might be better to ask the question here first since I don't know the functional reason why this space exists or whether it's necessary. Impress experts, what are your thoughts on this? Is this worthy of a bug report? The behavior of both PowerPoint and Impress has its high- and lowlights - personally I found the Impress behavior to not mis-use the vertical scrollbar more logical. Hehe, and I just noticed a really weird issue: try to zoom out (e.g. 20%), then up/down jumps between the slides. However, we know that Impress behaves bad ... so the OpenOffice.org Renaissance project (driven by Sun/Oracle) addressed those issues. I thought these changes were already available within the recent LibreOffice builds. Here is the specification Slide View, Preview and Sorter Rendering that talks about keyboard behavior in section 1.6: http://specs.openoffice.org/renaissance/slide_view_sorter_and_preview.odt It would be great if you could file an issue for that - both referring to that specification and asking for a check whether these Renaissance changes have been included (OOo CWS name Renaissance1, OOo issue 107211). I hope this helped - at least a bit... Cheers, Christoph -- Unsubscribe instructions: E-mail to design+h...@global.libreoffice.org Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/design/ All messages sent to this list will be publicly archived and cannot be deleted -- Unsubscribe instructions: E-mail to design+h...@global.libreoffice.org Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/design/ All messages sent to this list will be publicly archived and cannot be deleted
[libreoffice-design] Formalized team work structures
Hi Phil, all I'm really sorry, that I don't have the time to contribute to the numbers of highly interesting and active threads here on the list. But I don't even manage to read all the mails I receive on the most important LibO lists. (I read all the mails here, even if I don't reply). This mail (sent already three weeks ago [1]) needs some follow-up, and it is important enough to deserve it's own thread. Phil Jackson schrieb (in the thread flying the ship ...: Hi Bernhard [...] If possible, I'd like to see a degree of formalisation of how the design team will work together with suggestions of stages for taking an idea and transforming it into a form that we have agreement on for submission to the pool of programmers. I support the idea of a common approach for proposals and idea development leading to a final stage agreed upon by the team and proposed to the developers in a way they can work on them. This is about building relationships between the design team members but also between the design team and programmers so they feel part of the design team. It's like selling ideas to management - well articulated ideas with supporting evidence should make a difference in getting done what the Design Team thinks by consensus is necessary to improve the product. It's all about convincing one single developer that a proposal is important, so he is interested in coding in this area. And with some kind of formalism this might be easier - especially as we are in a period where several important ideas are thrown together on the mailing list, while the next steps (collective work, integration with existing designs, UI / UX areas covered...) are not clear to the participants. Here are some suggestions for stages; 1) Someone comes up with an idea :-) should be the basic... 2) Idea is posted on Design/WhiteBoards and emailed to team members In my eyes the /WhiteBoard wiki page should become a table of links to all the items that have been proposed by people really interested in working on them. We definitely need another area, where people can post their ideas for improvement who can't spend the time or have the expertise to work on these ideas. Such ideas need a team member being attracted by the topic and interested in working on it. If there is nobody interested / able to work in it, it might be reactivated by someone scrolling the whiteboard site... 3) Idea is discussed and debated with ample opportunity to test idea and gather arguments for and against ... and improved by the input of other team members. 4) Goes to vote stage by design members after member proposes that they do this - if passed goes to Stage 5) I don't think that we need a formal voting on each and every idea. Small changes should need much less formalism than larger modifications. Consensual discussion on the list will lead to a positive feeling of the team towards this idea. In such a case formal voting is not necessary. 5) A Design/Whiteboards paper for the idea if constructed giving a formalised breakdown of the idea - i.e. Overview, Introduction, Main Body with evidence, conclusions (why idea is a good one) and references/bibliography. Designing a mockup to show my ideas to people dedicated to design and UX is not very hard in comparison to preparing a description of modifications leading to developers interest and understanding. 6) Submitted to programmers pool for their feedback. If possible, developers should be involved much earlier. Knowledge about the necessary amount of work on this topic is important for us too. And they are not only asked for feedback - we should try to attract them to work on this topic. Otherwise the idea will need to become pushed by someone else - without any guarantee that it will be worked on sometimes in the future. 7) Followup We need to make this reasonably professional without turning it into a Phd. It makes it transparent for all. I imagine a wiki page containing these steps (perhaps as a follow-up an other introductory wiki page with all the information a new team member searches for) and all the necessary information about how to attract developers for such work. Christoph already mentioned some kind of design Easy-hacks, an idea we definitely need to follow. I know that some of these things are already done, but using a system will make it more likely that progress is seen to be made on some very interesting and beneficial ideas. What does everybody think? I think we should try it - and find out about the areas we can improve and further LibO without all these formalisms... Best regards Bernhard Cheers Phil Jackson [1]: http://go.mail-archive.com/80STRNtdj-ankO94T0iTN0CD_MU= -- Unsubscribe instructions: E-mail to design+h...@global.libreoffice.org Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/design/ All messages sent to
