On 20 June 2012 12:31, Jaroslaw Staniek <[email protected]> wrote: > On 20 June 2012 08:53, C. Boemann <[email protected]> wrote: > >> No No. We don't need filtering or anything. Just an update version of what we >> had. Updated meaning that it handles the extra column for version and a >> narrow >> column (1 char) for link to git. > > OK, so here's my proposed solution: > > http://community.kde.org/Calligra/Feature_Plan#Proposed_table > > - the usage is as simple as currently possible > - I wasn't able to change Feature* templates as these are used by other > project, so I added: CalligraInProgress, CalligraTodo, CalligraDone, > and extra CalligraWish > (at least I'll use CalligraWish for planned features without clear > version assigned) > - status column is narrowed as much as possible > - git branch is narrower and link is created automatically, skipping > is accepted as you can see on the sample table > - MOST VISIBLE CHANGE: added Component column, so all items can be now > put in a single table what gives ability to sort the table globally > (useful to get version/status plans overview) > > Please give you feedback :)
A hint: if we keep proper prefixing in the Component column (e.g. Kexi Forms (not Forms for Kexi), Kexi Reports, Shapes), grouping would work best. -- regards / pozdrawiam, Jaroslaw Staniek http://www.linkedin.com/in/jstaniek Kexi & Calligra (kexi-project.org, identi.ca/kexi, calligra.org/kexi) KDE Software Development Platform on MS Windows (windows.kde.org) _______________________________________________ calligra-devel mailing list [email protected] https://mail.kde.org/mailman/listinfo/calligra-devel
