Re: Unit test coverage
>From my perspective it will be really very important to increase the unit test >coverage of the software particularly for the applications currently: Words, >Stage and Tables as these applications are important in our investigation of >making Mobile Office Viewer(FreOffice) usable for real end users. As a >practice in general it would be good if we agree some fundamental unit test >policy in each application. Do we have a general understanding on what is the target which is good from your perspective. I think it would be good if the code coverage is atleast close to 80% ? Is there a way to see the code coverage break down per application level regards, Suresh Chande ___ calligra-devel mailing list calligra-devel@kde.org https://mail.kde.org/mailman/listinfo/calligra-devel
Development of FreOffice towards Calligra Mobile
Greetings for the new Year !! As FreOffice is maturing and getting better day by day it would be good to start to develop the Calligra way of working in planning future development of FreOffice and aligning with the Calligra release plans. Currently the code base is all part of Calligra trunk under tools. We think it would best fit into Calligra as a mobile edition of the suite and we could consider relocating or structuring FreOffice as mobile UI. We have been discussing that it would also be a good time to consider renaming FreOffice to align more closer to Calligra. Calligra Mobile is an option which might align with Calligra. It would be good to hear your opinion about this way of development for FreOffice. One of the key and fundamental next step in development of Calligra Mobile suite is to make it end user ready (as mobile clients in Maemo, MeeGo, etc, environments). This basically means that it would require atleast the following from my perspective: - Clean up the code architecturally and make it clean and modular (Already being actively developed by Mani and Jaroslaw and more) - Ensure there are no crashes in the UI and is stable - Make the mobile office stable and address some of the usability issues identified by the analysis made so far - Identify and Document the APIs required to use Calligra backend and agree these to be become API Calligra suite will provide - Agree if we should merge the IRC channel(currently #FreOffice @ Freenode) or just keep the mobile stream and desktop discussions parallel - Clean up the UI plug-in architecture and make the current plug-ins stable and utilize only stable plugins for the next release - Update the software based on end user feedback and improve usability issues which are stopping from using the FreOffice for real world use cases - For Maemo 5 move the application from development edition to end user ready version and get real users to use- For MeeGo environment Move the current Qt version of FreOffice on Maemo 5 with minimal updates and repackaging into MeeGo platform 1.2 (Under development) - Later plan to enhance the UI by developing QML based UI for MeeGo Platform and contribute as a reference implementation for Office viewer there - In future: MeeGo has multiple Ux environments and we would like to enhance the Mobile Ux to scalable to other ux if time permits. - Others please add any other wish list or things I have missed out.. We are also having a lot of interest from university students to consider projects in mobile office area as their research project areas so we will make a place holder in the wiki to list down a set of projects and report progress as students develop further. I created a wiki page in the Calligra wiki and invite us to comment and contribute to the above development plan. http://community.kde.org/Calligra/CalligraMobile Once we agree the way forward we should see an update on the features planned at the location: http://community.kde.org/Calligra/Schedules/2.4/Feature_Plan Thanks and with best regards, Suresh Chande on behalf of all contributors of FreOffice ___ calligra-devel mailing list calligra-devel@kde.org https://mail.kde.org/mailman/listinfo/calligra-devel
Re: Development of FreOffice towards Calligra Mobile
> Great list, Suresh. > I would add a small but important thing: making Calligra Mobile look > and feel ok when running on desktop. For now it lacks some icons (as > these have hardcoded share path for maemo). If the missing icons are > proprietary, replacements would be needed. Also some popups look a bit > strange, e.g. the one for alignment actions. Perhaps some ifdefs could > be added for desktop builds without simulator so the UI is more > similar in look and feel to a mobile UI. > Other than that, FreOffice/Calligra Mobile is already on good way. > Thanks for comments Jaroslaw, All icons are also open sourced to Calligra(Koffice) so there should be no maemo specific proprietary things left anymore. Will check that , yes sure there is certainly some more improvements we can put into FreOffice. What you suggest is doable, I will consult with Mani and Lassi, will aim to fix the above aspects. > Maybe a Meego Tablet version? Seems to be more usefull than smart phone > version. Yes this is on wish list,I hope we can address the netbook ux for MeeGo platform after the mobile ux. I see it could be very useful One of the topic I listed down is put down a cleaner API between UI Layer and the Calligra Core Engine. In the last developer sprint we discussed about collecting all the APIs we have used of the core engine for developing the UI, so that we can make these APIs more stable. I would like to start discussing this as these set of APIs if well documented and kept unchanged or with minimal changes or well managed could help demonstrate how to create new UIs and as well as help evolve multiple UIs on top of Calligra Core leading to the ODFOfficeKit ideas we were discussing in earlier sprints. We made a list of APIs used and documented earlier I believe we did not share this yet, maybe it would be good to discuss this at the sprint but meanwhile worthwhile sharing this document across for discussion over email. As I received general supporting emails in renaming FreOffice to Calligra Mobile over email and IRC can I assume it is ok to proceed with renaming to Calligra Mobile ? We may also want to use a different logo for the application. Currently FreOffice uses KOffice Logo, is there a subset of Calligra logo we can use for Calligra (Mobile) where (mobile) can be in subset ? Who can help in graphics from the KDE community ? Regards, Suresh Chande ___ calligra-devel mailing list calligra-devel@kde.org https://mail.kde.org/mailman/listinfo/calligra-devel
