Calligra/Meetings/Fall 2011 meeting/Minutes: Difference between revisions
Line 32: | Line 32: | ||
=====KoReports and/or mail merge?===== | =====KoReports and/or mail merge?===== | ||
Mail merge CAN be superset of KoReports BUT the latter less complex code because of lack of ODF dependency and flake editing code that is not all needed for reports. | Mail merge CAN be superset of KoReports BUT the latter less complex code because of lack of ODF dependency and flake editing code that is not all needed for reports. | ||
=====Tasks===== | |||
*Radek: unit tests for Predicate | |||
*Radek: Chart form widget, look as possibilities of sharing code with koreport chart | |||
*Dimitrios: | |||
===Sunday=== | ===Sunday=== |
Revision as of 17:13, 12 November 2011
..
Kexi BoF
Friday
- OwnCloud integration for Kexi storage, contributors needed
- WebForms, contributors needed
- Fullscreen: TODO
- Define object model for public Kexi APIs, then start to implement using QtScript. Documentation of the object model would become a base for section in the Kexi Handbook (minus development notes).
Saturday
Branding
- Good news: we have calligra.org!
- The community has decided on the logo, it's not up for discussion now. We go further to helping users/3rd parties to properly refer to our project in a way so we feel comfortable enough.
- Calligra Branding presentation (jstaniek)
- Logo guidelines draft 1, please discuss (jstaniek)
Kexi
Plan: Move plugin tabbed toolbars to plugins
- define KexiTabInfo { QString name; QString toolTip; QString whatsThis; QString tabText; QColor tabColor; QWidget* widget; }
- implement virtual QList<KexiTabInfo*> KexiPart::createMenuTabs() const = 0;
- implement createMenuTabs() is kexi form and report plugins.
Idea: User feedback module
- design & implement user feedback module
- ask users to participate in anonymous gathering of statistical data
- collect user
- user can sign up using nick name to see her contribution!
Idea: New developers in Kexi Mobile sub-project
SPOILER! Three new Kexi devs are N9* owners now and two of them look forward to contribute something.
Practices
- Use //! @todo, Q_ASSERT(), see techbase for more hints
KoReports and/or mail merge?
Mail merge CAN be superset of KoReports BUT the latter less complex code because of lack of ODF dependency and flake editing code that is not all needed for reports.
Tasks
- Radek: unit tests for Predicate
- Radek: Chart form widget, look as possibilities of sharing code with koreport chart
- Dimitrios: