https://community.kde.org/api.php?action=feedcontributions&user=Cyrille&feedformat=atomKDE Community Wiki - User contributions [en]2024-03-29T06:33:48ZUser contributionsMediaWiki 1.40.2https://community.kde.org/index.php?title=Krita/Scripting&diff=42485Krita/Scripting2015-05-29T17:42:09Z<p>Cyrille: </p>
<hr />
<div>This page is going to collect ideas on how to write the new scripting API for Krita 3.x<br />
<br />
== IRC log ==<br />
19:22 < a----> C------B perhaps I think layer management would be important and useful to start with<br />
19:22 < a----> E.g. adding a layer, positioning a layer and controlling common attributes like opacity special layers like masks etc. can come later.<br />
19:23 < C------B> a----: that is actually what I am looking at now<br />
19:24 < a----> that would be a good place to start I think.<br />
19:24 < a----> Things like brush engines, brush opacity control are better done from within Krita and should not need to be used externally.<br />
19:28 < A-----o> C------B, I'd love to make a plugin that deletes the current layer (or fills it with a color) when I lift the pen from the tablet, so I guess being able to listen to pen <br />
events would be cool<br />
19:28 < A-----o> C------B, I'd also love to make some plugins that allow you to use external hardware to control e.g. brush parameters, so that would be cool<br />
19:33 < a----> C------B I think its better to start from the outside gross functionalioty and then go to more deeper layers of Krita like an onion.</div>Cyrillehttps://community.kde.org/index.php?title=Calligra/Braindump&diff=42142Calligra/Braindump2015-04-12T09:46:22Z<p>Cyrille: </p>
<hr />
<div>= Braindump 3.x =<br />
<br />
== Application purpose ==<br />
<br />
The purpose of Braindump is to allow users to dump the content of their brain in the computer. The software is used as support of thinking. Users should be able to write text, add shapes, images, or videos and draw. Users should also be able to connect objects. The applications is modelled as a computer version of the real life whiteboard.<br />
<br />
If you wonder what I have in mind for braindump, look for "crime board" in a search engine.<br />
<br />
== Persona ==<br />
<br />
=== Helena, Researcher ===<br />
<br />
Helena holds a PhD in Computer Science and she is conducting research on software intensive systems. She often have to reason with formulas, images, concepts and how they relate to each others.<br />
<br />
=== John, Project Manager ===<br />
<br />
John holds a MBA, with a technical background. He is the project leader for the development of a system involving hardware and software.<br />
<br />
== Interaction design ==<br />
<br />
=== Mockup ===<br />
[[File:BraindumpMockup1.png]]</div>Cyrillehttps://community.kde.org/index.php?title=File:BraindumpMockup1.png&diff=42141File:BraindumpMockup1.png2015-04-12T09:46:13Z<p>Cyrille: </p>
<hr />
<div></div>Cyrillehttps://community.kde.org/index.php?title=Calligra/Braindump&diff=42138Calligra/Braindump2015-04-12T08:48:26Z<p>Cyrille: </p>
<hr />
<div>= Braindump 3.x =<br />
<br />
== Application purpose ==<br />
<br />
The purpose of Braindump is to allow users to dump the content of their brain in the computer. The software is used as support of thinking. Users should be able to write text, add shapes, images, or videos and draw. Users should also be able to connect objects. The applications is modelled as a computer version of the real life whiteboard.<br />
<br />
== Persona ==<br />
<br />
=== Helena, Software Architect ===<br />
<br />
Helena holds a PhD in Computer Science and she is conducted research on software intensive systems.<br />
<br />
=== Paul, Mathematician ===<br />
<br />
Paul is a researcher in mathematics.<br />
<br />
=== John, Project Manager ===<br />
<br />
John holds a MBA, with a technical background. He is the project leader for the development of a system involving hardware and software.<br />
<br />
== Interraction design ==</div>Cyrillehttps://community.kde.org/index.php?title=Calligra/Braindump&diff=42134Calligra/Braindump2015-04-12T07:57:07Z<p>Cyrille: Created page with "= Braindump 3.x ="</p>
<hr />
<div>= Braindump 3.x =</div>Cyrillehttps://community.kde.org/index.php?title=Calligra/Schedules/2.9/Release_Plan&diff=41784Calligra/Schedules/2.9/Release Plan2015-03-01T15:04:56Z<p>Cyrille: </p>
<hr />
<div>See also: [[../../Feature Plan/]], [[../Quality Control/]]<br />
{{Note|Status: unreleased}}<br />
__TOC__<br />
<br />
= Freezes =<br />
<br />
Master is never frozen for features or strings. The branch calligra/2.9 is always frozen for features or strings.<br />
<br />
= Testing =<br />
<br />
== Beta 1 (2.8.90) ==<br />
* Tagging and branching (calligra/2.9) December 6th (no big merge on that day)<br />
* Release December 10th<br />
<br />
== Beta 2 (2.8.91) ==<br />
* Tagging January 11th<br />
* Release January 15th<br />
<br />
== Beta 3 (2.8.92) ==<br />
* Tagging February 8th<br />
* Release February 12th<br />
<br />
= Stable releases =<br />
<br />
== 2.9.0 ==<br />
* Tagging February 22nd<br />
* Release February 26th<br />
<br />
== 2.9.1 ==<br />
* Tagging March 7th<br />
* Release March 11th<br />
<br />
== 2.9.2 ==<br />
* Tagging March 28th<br />
* Release April 1st<br />
<br />
== 2.9.3 ==<br />
* Tagging April 25th<br />
* Release 29th<br />
<br />
== 2.9.4 ==<br />
* Tagging May 23rd<br />
* Release 27th<br />
<br />
Subsequent release will be planned on a case-by-case basis.</div>Cyrillehttps://community.kde.org/index.php?title=Calligra/Schedules/2.9/Release_Plan&diff=40397Calligra/Schedules/2.9/Release Plan2014-11-20T16:32:23Z<p>Cyrille: /* Beta 1 (2.8.90) */</p>
<hr />
<div>See also: [[../../Feature Plan/]], [[../Quality Control/]]<br />
{{Note|Status: unreleased}}<br />
__TOC__<br />
<br />
= Freezes =<br />
<br />
Master is never frozen for features or strings. The branch calligra/2.9 is always frozen for features or strings.<br />
<br />
= Testing =<br />
<br />
== Beta 1 (2.8.90) ==<br />
* Tagging and branching (calligra/2.9) December 6th (no big merge on that day)<br />
* Release December 10th<br />
<br />
== Beta 2 (2.8.91) ==<br />
* Tagging December 27th<br />
* Release December 30th<br />
<br />
== Beta 3 (2.9.2) ==<br />
* Tagging January 4th<br />
* Release January 7th<br />
<br />
= Stable releases =<br />
<br />
== 2.9.0 ==<br />
* Tagging December [???]<br />
* Release December [???]<br />
<br />
== 2.9.1 ==<br />
* Tagging [???]<br />
* Release [???]<br />
<br />
== 2.9.2 ==<br />
* Tagging [???]<br />
* Release [???]<br />
<br />
== 2.9.3 ==<br />
* Tagging [???]<br />
* Release [???]<br />
<br />
== 2.9.4 ==<br />
* Tagging [???]<br />
* Release [???]</div>Cyrillehttps://community.kde.org/index.php?title=Calligra/Schedules/2.8/Release_Plan&diff=40396Calligra/Schedules/2.8/Release Plan2014-11-20T16:29:15Z<p>Cyrille: </p>
<hr />
<div>See also: [[../../Feature Plan/]], [[../Quality Control/]]<br />
{{Note|Status: released}}<br />
__TOC__<br />
<br />
= Freezes =<br />
<br />
Master is never frozen for features or strings. The branch calligra/2.8 is always frozen for features or strings.<br />
<br />
= Testing =<br />
<br />
== Beta 1 (2.7.90) ==<br />
* Tagging and branching (calligra/2.8) November 30th (no big merge on that day)<br />
* Release December 3rd<br />
<br />
== Beta 2 (2.7.91) ==<br />
* Tagging January 11th (no big merge on that day)<br />
* Release January 15th<br />
<br />
== Beta 3 (2.7.92) ==<br />
* Tagging February 9th<br />
* Release February 12th<br />
<br />
= Stable releases =<br />
<br />
== 2.8.0 ==<br />
* Tagging March 2<br />
* Release March 5<br />
<br />
== 2.8.1 ==<br />
* Tagging March 24th<br />
* Release March 28th<br />
<br />
== 2.8.2 ==<br />
* Tagging April 12th<br />
* Release April 16th<br />
<br />
== 2.8.3 ==<br />
* Tagging May 10th<br />
* Release May 14th<br />
<br />
== 2.8.4 ==<br />
'''Postponed because of found regressions [http://lists.kde.org/?l=calligra-devel&m=140386344927957&w=2]; 2.8.5 planned shortly instead.'''<br />
* <strike>Tagging June 14th</strike><br />
* <strike>Release June 18th</strike><br />
<br />
== 2.8.5 ==<br />
This release replaces 2.8.4.<br />
* Tagging July 3<br />
* Release July 5<br />
<br />
== 2.8.6 ==<br />
* Tagging September 20<br />
* Release September 24<br />
<br />
== 2.8.7 ==<br />
* Tagging November 30th <br />
* Release December 3rd</div>Cyrillehttps://community.kde.org/index.php?title=Calligra/Schedules/2.8/Release_Plan&diff=37290Calligra/Schedules/2.8/Release Plan2014-04-03T14:26:41Z<p>Cyrille: </p>
<hr />
<div>See also: [[../../Feature Plan/]], [[../Quality Control/]]<br />
{{Note|Status: released}}<br />
__TOC__<br />
<br />
= Freezes =<br />
<br />
Master is never frozen for features or strings. The branch calligra/2.8 is always frozen for features or strings.<br />
<br />
= Testing =<br />
<br />
== Beta 1 (2.7.90) ==<br />
* Tagging and branching (calligra/2.8) November 30th (no big merge on that day)<br />
* Release December 3rd<br />
<br />
== Beta 2 (2.7.91) ==<br />
* Tagging January 11th (no big merge on that day)<br />
* Release January 15th<br />
<br />
== Beta 3 (2.7.92) ==<br />
* Tagging February 9th<br />
* Release February 12th<br />
<br />
= Stable releases =<br />
<br />
== 2.8.0 ==<br />
* Tagging March 2<br />
* Release March 5<br />
<br />
== 2.8.1 ==<br />
* Tagging March 24th<br />
* Release March 28th<br />
<br />
== 2.8.2 ==<br />
* Tagging April 12th<br />
* Release April 16th<br />
<br />
== 2.8.3 ==<br />
* Tagging May 10th<br />
* Release May 14th<br />
<br />
== 2.8.4 ==<br />
* Tagging June 14th<br />
* Release June 18th</div>Cyrillehttps://community.kde.org/index.php?title=Calligra/Meetings/Spring_2014_Sprint&diff=36838Calligra/Meetings/Spring 2014 Sprint2014-03-11T08:16:09Z<p>Cyrille: </p>
<hr />
<div>You learned that Copenhagen as sprint location misses someone to organize hosting.<br />
<br />
Thankfully we have two (new) offers for the sprint by these possible hosts:<br />
* Blue Systems in Barcelona<br />
* KDAB in Berlin<br />
<br />
Beware: Sprint date continues to be on WE '''30 May to 01 Jun'''<br />
<br />
Both offers can be considered more or less equivalent (central in big cities with good connectivity, nice hosts, good internet, lots of space for up to 15 people, affordable accomodation, etc). So let's make a vote, and also have some numbers for better comparability.<br />
<br />
'''Deadline for voting on host: March 12th'''<br />
<br />
After that and once the host confirms our decision, we will update https://sprints.kde.org/sprint/170 with the new location. Then everyone will need to update their sponsoring details until March 25th on sprints.kde.org (will send reminder email). We need to have all data ideally still in this first quartal of the year, because e.V. likes to get sponsoring requests in the quartal before the one with the sprint.<br />
<br />
So please enter your details below. Accomodation should not be that different in both cities, so no estimate needed on that, travel costs will be more deciding. Still tell if you would need accomodation sponsored or not.<br />
<br />
{| cellspacing="0" cellpadding="5" border="1" class="wikitable"<br />
|- style="color: blue;"<br />
|<br />
|<br />
| colspan="4"| Barcelona<br />
| colspan="4"| Berlin<br />
|<br />
|- style="color: blue;"<br />
| Name <br />
| Favourite (Barcelona/Berlin)<br />
| Arrival<br />
| Departure <br />
| Travel costs estimate<br />
| Sponsoring needed? (Accomodation/Travel)<br />
| Arrival<br />
| Departure<br />
| Travel costs estimate<br />
| Sponsoring needed? (Accomodation/Travel)<br />
| Comment<br />
|-<br />
| Camilla Boemann<br />
| (Favourite)<br />
| (BAR arrival)<br />
| (BAR departure)<br />
| (BAR travel costs)<br />
| (BAR sponsoring: Accom./Travel)<br />
| (BER arrival)<br />
| (BER departure)<br />
| (BER travel costs)<br />
| (BER sponsoring: Accom./Travel)<br />
| (Comment)<br />
|-<br />
| Friedrich W. H. Kossebau<br />
| Barcelona<br />
| May 30<br />
| Jun 2<br />
| 300 EUR<br />
| Accomodation/Travel<br />
| May 30, 18h<br />
| Jun 1, 18h<br />
| 60 EUR<br />
| Accomodation<br />
| <br />
|-<br />
| mojtaba shahi<br />
| (Favourite)<br />
| (BAR arrival)<br />
| (BAR departure)<br />
| (BAR travel costs)<br />
| (BAR sponsoring: Accom./Travel)<br />
| (BER arrival)<br />
| (BER departure)<br />
| (BER travel costs)<br />
| (BER sponsoring: Accom./Travel)<br />
| (Comment)<br />
|-<br />
| Jarosław Staniek<br />
| (Favourite)<br />
| (BAR arrival)<br />
| (BAR departure)<br />
| (BAR travel costs)<br />
| (BAR sponsoring: Accom./Travel)<br />
| (BER arrival)<br />
| (BER departure)<br />
| (BER travel costs)<br />
| (BER sponsoring: Accom./Travel)<br />
| (Comment)<br />
|-<br />
| Inge Wallin<br />
| (Favourite)<br />
| (BAR arrival)<br />
| (BAR departure)<br />
| (BAR travel costs)<br />
| (BAR sponsoring: Accom./Travel)<br />
| (BER arrival)<br />
| (BER departure)<br />
| (BER travel costs)<br />
| (BER sponsoring: Accom./Travel)<br />
| (Comment)<br />
|-<br />
| Jigar Raisinghani<br />
| Barcelona<br />
| 30.5<br />
| 1.6<br />
| 785 Euros(Travel+ Accomodation)<br />
| Travel + Accomodation<br />
| 30.5<br />
| 1.6<br />
| 650 Euros(Travel + Accomodation)<br />
| Travel + Accomodation<br />
| These are the rates as per 10.3.14 and may vary depending on day of booking.<br />
|-<br />
| Thorsten Zachmann<br />
| BER<br />
| 30.5.<br />
| 1.6.<br />
| 400-500€<br />
| Accom./Travel<br />
| 30.5.<br />
| 1.6.<br />
| 200-300€<br />
| Accom./Travel<br />
| (Comment)<br />
|-<br />
| Dmitry Kazakov<br />
| BER<br />
| 30.05<br />
| 01.06<br />
| 360eur<br />
| Accom + Travel<br />
| 30.05<br />
| 01.06<br />
| 200eur<br />
| Accom + Travel<br />
| (Comment)<br />
|-<br />
| Dan Leinir Turthra Jensen<br />
| (Favourite)<br />
| (BAR arrival)<br />
| (BAR departure)<br />
| (BAR travel costs)<br />
| (BAR sponsoring: Accom./Travel)<br />
| (BER arrival)<br />
| (BER departure)<br />
| (BER travel costs)<br />
| (BER sponsoring: Accom./Travel)<br />
| (Comment)<br />
|-<br />
| Arjen Hiemstra<br />
| (Favourite)<br />
| (BAR arrival)<br />
| (BAR departure)<br />
| (BAR travel costs)<br />
| (BAR sponsoring: Accom./Travel)<br />
| (BER arrival)<br />
| (BER departure)<br />
| (BER travel costs)<br />
| (BER sponsoring: Accom./Travel)<br />
| (Comment)<br />
|-<br />
| Boudewijn Rempt<br />
| (Berlin)<br />
| (BAR thurs)<br />
| (BAR monday)<br />
| (BAR 200)<br />
| (BAR sponsoring: Accom./Travel)<br />
| (BER friday)<br />
| (BER sunday)<br />
| (BER 200)<br />
| (BER sponsoring: Accom./Travel)<br />
| (Comment)<br />
|-<br />
| Sebastian Sauer<br />
| (Favourite)<br />
| (BAR arrival)<br />
| (BAR departure)<br />
| (BAR travel costs)<br />
| (BAR sponsoring: Accom./Travel)<br />
| (BER arrival)<br />
| (BER departure)<br />
| (BER travel costs)<br />
| (BER sponsoring: Accom./Travel)<br />
| (Comment)<br />
|-<br />
| (Name)<br />
| (Favourite)<br />
| (BAR arrival)<br />
| (BAR departure)<br />
| (BAR travel costs)<br />
| (BAR sponsoring: Accom./Travel)<br />
| (BER arrival)<br />
| (BER departure)<br />
| (BER travel costs)<br />
| (BER sponsoring: Accom./Travel)<br />
| (Comment)<br />
|-<br />
|}</div>Cyrillehttps://community.kde.org/index.php?title=Calligra/Schedules/2.8/Release_Plan&diff=36352Calligra/Schedules/2.8/Release Plan2014-02-09T10:07:43Z<p>Cyrille: </p>
<hr />
<div>See also: [[../../Feature Plan/]], [[../Quality Control/]]<br />
{{Note|Status: released}}<br />
__TOC__<br />
<br />
= Freezes =<br />
<br />
Master is never frozen for features or strings. The branch calligra/2.8 is always frozen for features or strings.<br />
<br />
= Testing =<br />
<br />
== Beta 1 (2.7.90) ==<br />
* Tagging and branching (calligra/2.8) November 30th (no big merge on that day)<br />
* Release December 3rd<br />
<br />
== Beta 2 (2.7.91) ==<br />
* Tagging January 11th (no big merge on that day)<br />
* Release January 15th<br />
<br />
== Beta 3 (2.7.92) ==<br />
* Tagging February 9th<br />
* Release February 12th<br />
<br />
= Stable releases =<br />
<br />
== 2.8.0 ==<br />
* Tagging February ...<br />
* Release February ...<br />
<br />
== 2.8.1 ==<br />
* Tagging ...<br />
* Release ...<br />
<br />
== 2.8.2 ==<br />
* Tagging ...<br />
* Release ...<br />
<br />
== 2.8.3 ==<br />
* Tagging ...<br />
* Release ...<br />
<br />
== 2.8.4 ==<br />
* Tagging ...<br />
* Release ...</div>Cyrillehttps://community.kde.org/index.php?title=Calligra/Schedules/2.8/Release_Plan&diff=36040Calligra/Schedules/2.8/Release Plan2014-01-11T20:37:06Z<p>Cyrille: </p>
<hr />
<div>See also: [[../Feature Plan/]], [[../Quality Control/]]<br />
{{Note|Status: released}}<br />
__TOC__<br />
<br />
= Freezes =<br />
<br />
Master is never frozen for features or strings. The branch calligra/2.8 is always frozen for features or strings.<br />
<br />
= Testing =<br />
<br />
== Beta 1 (2.7.90) ==<br />
* Tagging and branching (calligra/2.8) November 30th (no big merge on that day)<br />
* Release December 3rd<br />
<br />
== Beta 2 (2.7.91) ==<br />
* Tagging January 11th (no big merge on that day)<br />
* Release January 15th</div>Cyrillehttps://community.kde.org/index.php?title=Calligra/Schedules/2.8/Release_Plan&diff=35322Calligra/Schedules/2.8/Release Plan2013-11-20T08:20:39Z<p>Cyrille: </p>
<hr />
<div>See also: [[../Feature Plan/]], [[../Quality Control/]]<br />
{{Note|Status: released}}<br />
__TOC__<br />
<br />
= Freezes =<br />
<br />
Master is never frozen for features or strings. The branch calligra/2.8 is always frozen for features or strings.<br />
<br />
= Testing =<br />
<br />
== Beta 1 (2.7.90) ==<br />
* Tagging and branching (calligra/2.8) November 30th (no big merge on that day)<br />
* Release December 3rd<br />
<br />
== Beta 2 (2.7.91) ==<br />
* Tagging January 4th (no big merge on that day)<br />
* Release January 8th</div>Cyrillehttps://community.kde.org/index.php?title=Calligra/Schedules/2.8/Release_Plan&diff=35260Calligra/Schedules/2.8/Release Plan2013-11-17T10:07:08Z<p>Cyrille: Created page with "See also: ../Feature Plan/, ../Quality Control/ {{Note|Status: released}} __TOC__ = Freezes = Master is never frozen for features or strings. The branch calligra/2.8..."</p>
<hr />
<div>See also: [[../Feature Plan/]], [[../Quality Control/]]<br />
{{Note|Status: released}}<br />
__TOC__<br />
<br />
= Freezes =<br />
<br />
Master is never frozen for features or strings. The branch calligra/2.8 is always frozen for features or strings.<br />
<br />
= Testing =<br />
<br />
== Beta 1 (2.7.90) ==<br />
* Tagging and branching (calligra/2.8) November 23rd (no big merge on that day)<br />
* Release November 26th<br />
<br />
== Beta 2 (2.7.91) ==<br />
* Tagging December 14th (no big merge on that day)<br />
* Release December 17th</div>Cyrillehttps://community.kde.org/index.php?title=Calligra&diff=35259Calligra2013-11-17T10:03:14Z<p>Cyrille: </p>
<hr />
<div>__NOTOC__<br />
<table border="0" style="background-color:white;padding-top:0.6em;" width="100%"><tr><td>http://kexi-project.org/pics/ads/calligra/calligra-logo-100.png</td><br />
<td><div style="font-size:150%;padding:0px;margin:0px;">'''Welcome to the Calligra Development Wiki'''</div><br/>'''Current versions:''' stable=<div style="background:#bbffbb;padding:0.2em;display:inline-block;">{{Calligra/Stable}}</div> development=<div style="background:#bbffbb;padding:0.2em;display:inline-block;">{{Calligra/Unstable}} {{Calligra/Stage}}</div><br/><br />
'''Project home site is:''' http://www.calligra.org, see our [[/Mission Statement//]]</td><br />
<td align="center">https://www.ohloh.net/p/calligra/widgets/project_partner_badge.gif<br/><br/>https://www.ohloh.net/p/calligra/analyses/latest/commits_spark.png<br/>&rarr; [https://www.ohloh.net/p/calligra Stats at ohloh.net]</td><br />
</tr></table><br />
<br />
<br />
'''Shortcuts to some information:'''<br/><br />
<table border="0" width="100%"><br />
<tr><br />
<td valign="top" width="33%" style="background:#ff5555;padding:0.5em;margin:5px;">'''<span style="font-size:130%;">[[/FAQ|FAQ]]</span>'''<br/>Frequently Asked Questions</td><br />
<br />
<td valign="top" width="33%" rowspan="4" style="background:#bfd0d7;padding:0.5em;margin:5px;">'''<span style="font-size:130%;">[[/Schedules/]]</span>'''<br />
<br />
<ul><br />
<br />
<li>Roadmaps:<br/>[[/Roadmaps/2.4/Roadmap|2.4]]</li><br />
<br />
<li>Feature plans:<br/>[[Calligra/Schedules/KOffice/2.3/Feature_Plan|2.3]], [[/Schedules/2.4/Feature_Plan|2.4]], [[/Schedules/2.5/Feature_Plan|2.5]], '''[[/Schedules/Feature_Plan|2.6 and later]]'''</li><br />
<br />
<li>Release plans:<br/>[[Calligra/Schedules/KOffice/2.3/Release_Plan|2.3]], [[/Schedules/2.4/Release_Plan|2.4]], [[/Schedules/2.5/Release_Plan|2.5]], '''[[/Schedules/2.6/Release_Plan|2.6]], [[/Schedules/2.7/Release_Plan|2.7]], [[/Schedules/2.8/Release_Plan|2.8]], [[/Schedules/3.0/Release_Plan|3.0]]'''</li><br />
<br />
</ul><br />
<br />
</td><br />
<br />
<td valign="top" width="33%" rowspan="4" valign="top" style="background:#bbbbbb;padding:0.5em;margin:5px;">'''<span style="font-size:130%;">Current Matters</span>'''<br />
<ul><br />
<li>Karbon and Plan needs new maintainers</li><br />
<li>[[/Calligra Academy/]]</li><li>We're developing the [[/FAQ/]], please help!</li><li>[[:Category:Pages in progress for Calligra|Pages in progress]]</li><li>[http://www.calligra.org/press Calligra in the press]</li></ul></td><br />
</tr><br />
<br />
<tr><br />
<br />
<td valign="top" style="background:#88ff88;padding:0.5em;margin:5px;font-size:100%;">'''<span style="font-size:130%;">[http://userbase.kde.org/Calligra/Download Download Calligra]</span>'''<br/>For users</td><br />
</tr><br />
<br />
<tr><td valign="top" style="background:yellow;padding:0.5em;margin:5px;">'''<span style="font-size:130%;">[[/Building/|How to build Calligra]]</span>'''<br/>For developers</td><br />
</tr><br />
<br />
<tr><br />
<td valign="top" style="background:#ffffaa;padding:0.5em;margin:5px;">'''<span style="font-size:130%;">[[/File a bug or wish/]]</span>'''</td><br />
</tr><br />
</table><br />
<br />
<br />
'''<span style="font-size:1.5em;">Overview over the Applications and UIs:</span>'''<br />
* [[/Libs|Libraries]]<br />
* Office Applications: [[/Words/]], [[/Sheets/]], [[/Stage/]], [[/Plan/]], [[/Flow/]], [[Kexi]], [[Braindump]]<br />
* Creativity Applications: [[Krita]], [[/Karbon/]]<br />
* Shapes: [[/Chart Shape/|Chart]], [[/Formula Shape/|Formula]]<br />
* [[/Calligra Mobile/]] The mobile version of Calligra, originally for the Nokia N900 smartphone.<br />
* [[Calligra Active]] The QML based UI version of Calligra that fits well into the Plasma Active environment.<br />
<br />
<br />
'''<span style="font-size:1.5em;">Information for different people.</span>''' Check which category you belong to:<br/><br />
<table border="0"><tr style="vertical-align:top;"><td width="50%"><br />
== For Developers ==<br />
=== Getting started ===<br />
* Getting started: <span style="font-size:130%;font-weight:bold;">[[/First Contact/]]</span><br />
* '''[[/Junior Jobs|Junior Jobs: Easy Coding, Lots of Fun!]]''' - jobs that will get you started<br />
* [[/Contributing a Patch/]]<br />
* '''[[/Calligra Academy/]]''' - A formal training programme<br />
<br />
=== Communicating with the Developers ===<br />
* Join the development IRC channel: [irc://irc.freenode.net/calligra #calligra on irc.freenode.net]<br />
* Use [https://mail.kde.org/mailman/listinfo/calligra-devel calligra-devel@kde.org mailing list] (also available as a [http://news.gmane.org/gmane.comp.kde.devel.calligra newsgroup])<br />
<br />
=== Overview of the Code ===<br />
* [http://api.kde.org/bundled-apps-api/calligra-apidocs/ Calligra API reference]<br />
* [[Calligra/Architecture|Architecture overview]] High-level descriptions of the architecture of the whole suite as well as certain subsystems.<br />
** [[Calligra/Architecture/Styles|An overview of how styles work internally]]<br />
* The [http://techbase.kde.org/Development/Tutorials#KOffice_Plugin_Tutorials Tutorials] are on techbase.<br />
<br />
* [[Calligra/Projects|Ongoing long or short term projects]]<br />
** [[Calligra/Projects/Autoshapes|Autoshapes support in Calligra/]]<br />
* [[Calligra/Ideas|Ideas for projects and extensions]]<br />
* [[Calligra/ODF Problems]]<br />
<br />
* [[/Filters/]]<br />
* [[/How To Use libMSOOXML/]]<br />
* [[/Rdf/]]<br />
<br />
=== Quality Assurance ===<br />
* Quality assurance: [http://quality.calligra-suite.org/ Summary of issues in the current builds (tests, crash bugs, etc)]<br />
* Build server with [http://community.kde.org/Sysadmin/Jenkins Jenkins]: http://build.kde.org/job/calligra_master<br />
* Testing: http://community.kde.org/Calligra/Testing<br />
</td><br />
<td width="50%"><br />
<br />
== For Testers ==<br />
* [[/File a bug or wish/]]<br />
* [[/FAQ#I_need_to_send_a_test_document.2C_how_to_do_it.3F|Recommended way to send a test document]]<br />
* [http://opendocumentfellowship.com/validator OpenDocument online Validator]<br />
* [http://develop.opendocumentfellowship.com/testsuite/ OpenDocument Test Suite]<br />
* For early birds: [[/Building/]]<br />
<br />
== For Designers ==<br />
*[[/Build Stencils for Flow/]]<br />
*[[/Logos/]]<br />
<br />
== For Promoters ==<br />
* [[/Marketing/]]<br />
* [[/Marketing/Strategy/|Marketing Strategy]]<br />
<br />
== Other ==<br />
* [[/Meetings/]]<br />
* [[/Policies/]]<br />
* [[/Maintainers/]] List of maintainers of the applications and other parts of the code.<br />
* [[/Release Howto/]], checklists<br />
* [[/How to Package/]]<br />
* [[/Guidelines/]] (draft)<br />
* [[/Summer Of Code/]]<br />
* [[/Usability and UX/]]<br />
<br />
=== Uncategorized yet ===<br />
*[[/End-user readiness/]]<br />
*[[/2.2 Changelog/]]<br />
*[[/Following bugs reports/]]<br />
*[[/Proposal for scripting in ODF/]]<br />
<br />
</td></tr></table><br />
<br />
== Editing This Documentation ==<br />
''A meeting of minds works so much better when there is a whiteboard in the room.''<br />
<br />
This wiki is provided for Calligra Suite developers to be a digital whiteboard where people can exchange notes, work on problems together and basically be productive. It is encouraged to use this wiki to write down feature lists, TODO lists, designer talks and past discussions.<br />
<br />
Calligra contributors can create an account [[Special:Userlogin|here]] and request write access from one of the [[/Admins|admins]]. Please read the [[/Wiki editing hints/]].<br />
<br />
We have started a compilation of the icons we need from the oxygen team. See [[/Icons/]].<br />
<br />
[[Category:Testing]]</div>Cyrillehttps://community.kde.org/index.php?title=Calligra&diff=35258Calligra2013-11-17T10:02:41Z<p>Cyrille: </p>
<hr />
<div>__NOTOC__<br />
<table border="0" style="background-color:white;padding-top:0.6em;" width="100%"><tr><td>http://kexi-project.org/pics/ads/calligra/calligra-logo-100.png</td><br />
<td><div style="font-size:150%;padding:0px;margin:0px;">'''Welcome to the Calligra Development Wiki'''</div><br/>'''Current versions:''' stable=<div style="background:#bbffbb;padding:0.2em;display:inline-block;">{{Calligra/Stable}}</div> development=<div style="background:#bbffbb;padding:0.2em;display:inline-block;">{{Calligra/Unstable}} {{Calligra/Stage}}</div><br/><br />
'''Project home site is:''' http://www.calligra.org, see our [[/Mission Statement//]]</td><br />
<td align="center">https://www.ohloh.net/p/calligra/widgets/project_partner_badge.gif<br/><br/>https://www.ohloh.net/p/calligra/analyses/latest/commits_spark.png<br/>&rarr; [https://www.ohloh.net/p/calligra Stats at ohloh.net]</td><br />
</tr></table><br />
<br />
<br />
'''Shortcuts to some information:'''<br/><br />
<table border="0" width="100%"><br />
<tr><br />
<td valign="top" width="33%" style="background:#ff5555;padding:0.5em;margin:5px;">'''<span style="font-size:130%;">[[/FAQ|FAQ]]</span>'''<br/>Frequently Asked Questions</td><br />
<br />
<td valign="top" width="33%" rowspan="4" style="background:#bfd0d7;padding:0.5em;margin:5px;">'''<span style="font-size:130%;">[[/Schedules/]]</span>'''<br />
<br />
<ul><br />
<br />
<li>Roadmaps:<br/>[[/Roadmaps/2.4/Roadmap|2.4]]</li><br />
<br />
<li>Feature plans:<br/>[[Calligra/Schedules/KOffice/2.3/Feature_Plan|2.3]], [[/Schedules/2.4/Feature_Plan|2.4]], [[/Schedules/2.5/Feature_Plan|2.5]], '''[[/Schedules/Feature_Plan|2.6 and later]]'''</li><br />
<br />
<li>Release plans:<br/>[[Calligra/Schedules/KOffice/2.3/Release_Plan|2.3]], [[/Schedules/2.4/Release_Plan|2.4]], [[/Schedules/2.5/Release_Plan|2.5]], '''[[/Schedules/2.6/Release_Plan|2.6]], [[/Schedules/2.7/Release_Plan|2.8]], [[/Schedules/3.0/Release_Plan|3.0]]'''</li><br />
<br />
</ul><br />
<br />
</td><br />
<br />
<td valign="top" width="33%" rowspan="4" valign="top" style="background:#bbbbbb;padding:0.5em;margin:5px;">'''<span style="font-size:130%;">Current Matters</span>'''<br />
<ul><br />
<li>Karbon and Plan needs new maintainers</li><br />
<li>[[/Calligra Academy/]]</li><li>We're developing the [[/FAQ/]], please help!</li><li>[[:Category:Pages in progress for Calligra|Pages in progress]]</li><li>[http://www.calligra.org/press Calligra in the press]</li></ul></td><br />
</tr><br />
<br />
<tr><br />
<br />
<td valign="top" style="background:#88ff88;padding:0.5em;margin:5px;font-size:100%;">'''<span style="font-size:130%;">[http://userbase.kde.org/Calligra/Download Download Calligra]</span>'''<br/>For users</td><br />
</tr><br />
<br />
<tr><td valign="top" style="background:yellow;padding:0.5em;margin:5px;">'''<span style="font-size:130%;">[[/Building/|How to build Calligra]]</span>'''<br/>For developers</td><br />
</tr><br />
<br />
<tr><br />
<td valign="top" style="background:#ffffaa;padding:0.5em;margin:5px;">'''<span style="font-size:130%;">[[/File a bug or wish/]]</span>'''</td><br />
</tr><br />
</table><br />
<br />
<br />
'''<span style="font-size:1.5em;">Overview over the Applications and UIs:</span>'''<br />
* [[/Libs|Libraries]]<br />
* Office Applications: [[/Words/]], [[/Sheets/]], [[/Stage/]], [[/Plan/]], [[/Flow/]], [[Kexi]], [[Braindump]]<br />
* Creativity Applications: [[Krita]], [[/Karbon/]]<br />
* Shapes: [[/Chart Shape/|Chart]], [[/Formula Shape/|Formula]]<br />
* [[/Calligra Mobile/]] The mobile version of Calligra, originally for the Nokia N900 smartphone.<br />
* [[Calligra Active]] The QML based UI version of Calligra that fits well into the Plasma Active environment.<br />
<br />
<br />
'''<span style="font-size:1.5em;">Information for different people.</span>''' Check which category you belong to:<br/><br />
<table border="0"><tr style="vertical-align:top;"><td width="50%"><br />
== For Developers ==<br />
=== Getting started ===<br />
* Getting started: <span style="font-size:130%;font-weight:bold;">[[/First Contact/]]</span><br />
* '''[[/Junior Jobs|Junior Jobs: Easy Coding, Lots of Fun!]]''' - jobs that will get you started<br />
* [[/Contributing a Patch/]]<br />
* '''[[/Calligra Academy/]]''' - A formal training programme<br />
<br />
=== Communicating with the Developers ===<br />
* Join the development IRC channel: [irc://irc.freenode.net/calligra #calligra on irc.freenode.net]<br />
* Use [https://mail.kde.org/mailman/listinfo/calligra-devel calligra-devel@kde.org mailing list] (also available as a [http://news.gmane.org/gmane.comp.kde.devel.calligra newsgroup])<br />
<br />
=== Overview of the Code ===<br />
* [http://api.kde.org/bundled-apps-api/calligra-apidocs/ Calligra API reference]<br />
* [[Calligra/Architecture|Architecture overview]] High-level descriptions of the architecture of the whole suite as well as certain subsystems.<br />
** [[Calligra/Architecture/Styles|An overview of how styles work internally]]<br />
* The [http://techbase.kde.org/Development/Tutorials#KOffice_Plugin_Tutorials Tutorials] are on techbase.<br />
<br />
* [[Calligra/Projects|Ongoing long or short term projects]]<br />
** [[Calligra/Projects/Autoshapes|Autoshapes support in Calligra/]]<br />
* [[Calligra/Ideas|Ideas for projects and extensions]]<br />
* [[Calligra/ODF Problems]]<br />
<br />
* [[/Filters/]]<br />
* [[/How To Use libMSOOXML/]]<br />
* [[/Rdf/]]<br />
<br />
=== Quality Assurance ===<br />
* Quality assurance: [http://quality.calligra-suite.org/ Summary of issues in the current builds (tests, crash bugs, etc)]<br />
* Build server with [http://community.kde.org/Sysadmin/Jenkins Jenkins]: http://build.kde.org/job/calligra_master<br />
* Testing: http://community.kde.org/Calligra/Testing<br />
</td><br />
<td width="50%"><br />
<br />
== For Testers ==<br />
* [[/File a bug or wish/]]<br />
* [[/FAQ#I_need_to_send_a_test_document.2C_how_to_do_it.3F|Recommended way to send a test document]]<br />
* [http://opendocumentfellowship.com/validator OpenDocument online Validator]<br />
* [http://develop.opendocumentfellowship.com/testsuite/ OpenDocument Test Suite]<br />
* For early birds: [[/Building/]]<br />
<br />
== For Designers ==<br />
*[[/Build Stencils for Flow/]]<br />
*[[/Logos/]]<br />
<br />
== For Promoters ==<br />
* [[/Marketing/]]<br />
* [[/Marketing/Strategy/|Marketing Strategy]]<br />
<br />
== Other ==<br />
* [[/Meetings/]]<br />
* [[/Policies/]]<br />
* [[/Maintainers/]] List of maintainers of the applications and other parts of the code.<br />
* [[/Release Howto/]], checklists<br />
* [[/How to Package/]]<br />
* [[/Guidelines/]] (draft)<br />
* [[/Summer Of Code/]]<br />
* [[/Usability and UX/]]<br />
<br />
=== Uncategorized yet ===<br />
*[[/End-user readiness/]]<br />
*[[/2.2 Changelog/]]<br />
*[[/Following bugs reports/]]<br />
*[[/Proposal for scripting in ODF/]]<br />
<br />
</td></tr></table><br />
<br />
== Editing This Documentation ==<br />
''A meeting of minds works so much better when there is a whiteboard in the room.''<br />
<br />
This wiki is provided for Calligra Suite developers to be a digital whiteboard where people can exchange notes, work on problems together and basically be productive. It is encouraged to use this wiki to write down feature lists, TODO lists, designer talks and past discussions.<br />
<br />
Calligra contributors can create an account [[Special:Userlogin|here]] and request write access from one of the [[/Admins|admins]]. Please read the [[/Wiki editing hints/]].<br />
<br />
We have started a compilation of the icons we need from the oxygen team. See [[/Icons/]].<br />
<br />
[[Category:Testing]]</div>Cyrillehttps://community.kde.org/index.php?title=Calligra/Schedules/2.7/Release_Plan&diff=34354Calligra/Schedules/2.7/Release Plan2013-09-12T14:09:00Z<p>Cyrille: /* 2.7.5 */</p>
<hr />
<div>See also: [[../Feature Plan/]], [[../Quality Control/]]<br />
{{Note|Status: released}}<br />
__TOC__<br />
<br />
= Freezes =<br />
<br />
Master is never frozen for features or strings. The branch calligra/2.6 is always frozen for features or strings.<br />
<br />
= Testing =<br />
<br />
== Beta 1 (2.6.90) ==<br />
* Tagging and branching (calligra/2.6) April 27th (no big merge on that day)<br />
* Release April 30th (or May 1st)<br />
<br />
== Beta 2 (2.6.91) ==<br />
* Tagging May 18th (no big merge on that day)<br />
* Release May 22nd<br />
<br />
= Stable releases =<br />
<br />
== 2.7.2 ==<br />
* Tagging August 17th<br />
* Release August 21st<br />
<br />
== 2.7.3 ==<br />
* Tagging September 14th<br />
* Release September 18th<br />
<br />
== 2.7.4 ==<br />
* Tagging October 12th<br />
* Release October 16th<br />
<br />
== 2.7.5 ==<br />
* Tagging November 9th<br />
* Release November 15th</div>Cyrillehttps://community.kde.org/index.php?title=Calligra/Schedules/2.7/Release_Plan&diff=34353Calligra/Schedules/2.7/Release Plan2013-09-12T14:08:49Z<p>Cyrille: /* 2.7.4 */</p>
<hr />
<div>See also: [[../Feature Plan/]], [[../Quality Control/]]<br />
{{Note|Status: released}}<br />
__TOC__<br />
<br />
= Freezes =<br />
<br />
Master is never frozen for features or strings. The branch calligra/2.6 is always frozen for features or strings.<br />
<br />
= Testing =<br />
<br />
== Beta 1 (2.6.90) ==<br />
* Tagging and branching (calligra/2.6) April 27th (no big merge on that day)<br />
* Release April 30th (or May 1st)<br />
<br />
== Beta 2 (2.6.91) ==<br />
* Tagging May 18th (no big merge on that day)<br />
* Release May 22nd<br />
<br />
= Stable releases =<br />
<br />
== 2.7.2 ==<br />
* Tagging August 17th<br />
* Release August 21st<br />
<br />
== 2.7.3 ==<br />
* Tagging September 14th<br />
* Release September 18th<br />
<br />
== 2.7.4 ==<br />
* Tagging October 12th<br />
* Release October 16th<br />
<br />
== 2.7.5 ==<br />
* Tagging November 2nd<br />
* Release November 6th</div>Cyrillehttps://community.kde.org/index.php?title=Calligra/Schedules/2.7/Release_Plan&diff=34352Calligra/Schedules/2.7/Release Plan2013-09-12T14:08:39Z<p>Cyrille: /* 2.7.3 */</p>
<hr />
<div>See also: [[../Feature Plan/]], [[../Quality Control/]]<br />
{{Note|Status: released}}<br />
__TOC__<br />
<br />
= Freezes =<br />
<br />
Master is never frozen for features or strings. The branch calligra/2.6 is always frozen for features or strings.<br />
<br />
= Testing =<br />
<br />
== Beta 1 (2.6.90) ==<br />
* Tagging and branching (calligra/2.6) April 27th (no big merge on that day)<br />
* Release April 30th (or May 1st)<br />
<br />
== Beta 2 (2.6.91) ==<br />
* Tagging May 18th (no big merge on that day)<br />
* Release May 22nd<br />
<br />
= Stable releases =<br />
<br />
== 2.7.2 ==<br />
* Tagging August 17th<br />
* Release August 21st<br />
<br />
== 2.7.3 ==<br />
* Tagging September 14th<br />
* Release September 18th<br />
<br />
== 2.7.4 ==<br />
* Tagging October 5th<br />
* Release October 9th<br />
<br />
== 2.7.5 ==<br />
* Tagging November 2nd<br />
* Release November 6th</div>Cyrillehttps://community.kde.org/index.php?title=Calligra/Release_Howto&diff=33709Calligra/Release Howto2013-08-11T07:46:48Z<p>Cyrille: /* Translation */</p>
<hr />
<div>This page contains notes on what needs to be done when releasing a new version of Calligra.<br />
<br />
{{InProgress}}<br />
<br />
__TOC__<br />
<br />
= Tarball creation =<br />
<br />
= Branching =<br />
<br />
== Code ==<br />
git checkout -b calligra/${VERSION}<br />
git push origin calligra/${VERSION}<br />
(VERSION = 2.4, 2.5, etc.)<br />
<br />
== Translation ==<br />
<br />
As a general advice it's better to move messages when scripty is not running, so before 1 AM CE(S)T (or UTC, I don't remember now) or after ~8:30 AM (same timezone as starting time).<br />
<br />
Prepare yourself for a lot of suffering:<br />
* warn the i18n coordinator in advance<br />
* copy translation to stable-kde4 (use the calligra-release.rb scripts in [http://quickgit.kde.org/index.php?p=scratch%2Fberger%2Fcalligra-release-scripts.git&a=summary calligra's release scripts ])<br />
* update scripty for stable translations (edit scripts/get_paths change the get_path function, and check that list_modules contains calligra):<br />
svn co svn+ssh://svn@svn.kde.org/home/kde/branches/stable/l10n-kde4/scripts scripts-stable<br />
* update scripty for trunk translations<br />
svn co svn+ssh://svn@svn.kde.org/home/kde/trunk/l10n-kde4/scripts scripts-trunk<br />
* update branches/stable/l10n-kde4/scripts/documentation_paths with the calligra git branch<br />
* announce it to translators (CCMAIL:kde-i18n-doc@kde.org)<br />
* update branch in calligra project page settings: https://projects.kde.org/projects/calligra/settings<br />
<br />
= Information updates =<br />
*Update version info in the source code:<br />
**bump version info to '''N''' for libs in calligra/CMakeLists.txt (10 for 2.5, 11 for 2.6...)<br/><tt>set(GENERIC_CALLIGRA_LIB_VERSION "'''N'''.0.0")<br/>set(GENERIC_CALLIGRA_LIB_SOVERSION "'''N'''")</tt><br />
**update version info in calligra/libs/main/calligraversion.h:<br/><tt>#define CALLIGRA_VERSION_STRING "<b>x.y Pre-Alpha|Alpha|Beta|RC</b>"<br/>#define CALLIGRA_VERSION_MAJOR '''x'''<br/>#define CALLIGRA_STABLE_VERSION_MINOR <b>y</b><br/>#define CALLIGRA_VERSION_RELEASE '''89 (Pre-Alpha)|90 (Alpha)|91 (Beta)|92 (RC)'''<br/>#define CALLIGRA_ALPHA '''0|1'''<br/>#define CALLIGRA_BETA '''0|1'''<br/>#define CALLIGRA_RC '''0|1'''<br/>#define CALLIGRA_STABLE '''0|1'''<br/></tt><br />
* Collect changelog items<br />
* Collect screenshots<br />
* Write announcement for calligra.org<br />
** See which packages will be ready at release day (*Linux, Windows, OSX), push people to have them ready<br />
* Set version tag in git repo to the commit the tarball is made from<br />
* Add version for all Calligra bug.kde.org products<br />
* Major release:<br />
**Create tour<br />
**Update stable major version at [http://community.kde.org/index.php?title=Template:Calligra/StableBranch&action=edit community.kde.org] and [http://userbase.kde.org/index.php?title=Template:Calligra/StableBranch&action=edit userbase.kde.org]<br />
**Update unstable major version at [http://community.kde.org/index.php?title=Template:Calligra/UnstableBranch&action=edit community.kde.org] and [http://userbase.kde.org/index.php?title=Template:Calligra/UnstableBranch&action=edit userbase.kde.org]<br />
**Update color at http://community.kde.org/Calligra/Schedules#Important_information<br />
* Update info on http://userbase.kde.org/Calligra/Download<br />
* Update stable release version at [http://community.kde.org/index.php?title=Template:Calligra/Stable&action=edit community.kde.org] and [http://userbase.kde.org/index.php?title=Template:Calligra/Stable&action=edit userbase.kde.org]<br />
* Update info in channel topic of #calligra<br />
* Update unstable stage at [http://community.kde.org/index.php?title=Template:Calligra/Stage&action=edit community.kde.org] and [http://userbase.kde.org/index.php?title=Template:Calligra/Stage&action=edit userbase.kde.org]<br />
* Kexi<br />
** Update kexi-project.org<br />
*** Add link to the Calligra announcement<br />
*** Update Kexi version on the front page<br />
** Update version on [http://kde-apps.org/content/show.php?content=12365 KDE-Apps.org]<br />
** Optional: Publish news on http://forum.kde.org/viewforum.php?f=220<br />
** Publish news on http://identi.ca/kexi and https://twitter.com/kexi_project<br />
** Publish news on kexi@kde.org<br />
** Major release: Publish news on http://www.linkedin.com<br />
* Wikipedia<br />
** Update version at http://en.wikipedia.org/wiki/Calligra and http://pl.wikipedia.org/wiki/Calligra</div>Cyrillehttps://community.kde.org/index.php?title=Calligra/Release_Howto&diff=33707Calligra/Release Howto2013-08-10T04:54:26Z<p>Cyrille: /* Translation */</p>
<hr />
<div>This page contains notes on what needs to be done when releasing a new version of Calligra.<br />
<br />
{{InProgress}}<br />
<br />
__TOC__<br />
<br />
= Tarball creation =<br />
<br />
= Branching =<br />
<br />
== Code ==<br />
git checkout -b calligra/${VERSION}<br />
git push origin calligra/${VERSION}<br />
(VERSION = 2.4, 2.5, etc.)<br />
<br />
== Translation ==<br />
Prepare yourself for a lot of suffering:<br />
* warn the i18n coordinator in advance<br />
* copy translation to stable-kde4 (use the calligra-release.rb scripts in [http://quickgit.kde.org/index.php?p=scratch%2Fberger%2Fcalligra-release-scripts.git&a=summary calligra's release scripts ])<br />
* update scripty for stable translations (edit scripts/get_paths change the get_path function, and check that list_modules contains calligra):<br />
svn co svn+ssh://svn@svn.kde.org/home/kde/branches/stable/l10n-kde4/scripts scripts-stable<br />
* update scripty for trunk translations<br />
svn co svn+ssh://svn@svn.kde.org/home/kde/trunk/l10n-kde4/scripts scripts-trunk<br />
* update branches/stable/l10n-kde4/scripts/documentation_paths with the calligra git branch<br />
* announce it to translators (CCMAIL:kde-i18n-doc@kde.org)<br />
* update branch in calligra project page settings: https://projects.kde.org/projects/calligra/settings<br />
<br />
= Information updates =<br />
*Update version info in the source code:<br />
**bump version info to '''N''' for libs in calligra/CMakeLists.txt (10 for 2.5, 11 for 2.6...)<br/><tt>set(GENERIC_CALLIGRA_LIB_VERSION "'''N'''.0.0")<br/>set(GENERIC_CALLIGRA_LIB_SOVERSION "'''N'''")</tt><br />
**update version info in calligra/libs/main/calligraversion.h:<br/><tt>#define CALLIGRA_VERSION_STRING "<b>x.y Pre-Alpha|Alpha|Beta|RC</b>"<br/>#define CALLIGRA_VERSION_MAJOR '''x'''<br/>#define CALLIGRA_STABLE_VERSION_MINOR <b>y</b><br/>#define CALLIGRA_VERSION_RELEASE '''89 (Pre-Alpha)|90 (Alpha)|91 (Beta)|92 (RC)'''<br/>#define CALLIGRA_ALPHA '''0|1'''<br/>#define CALLIGRA_BETA '''0|1'''<br/>#define CALLIGRA_RC '''0|1'''<br/>#define CALLIGRA_STABLE '''0|1'''<br/></tt><br />
* Collect changelog items<br />
* Collect screenshots<br />
* Write announcement for calligra.org<br />
** See which packages will be ready at release day (*Linux, Windows, OSX), push people to have them ready<br />
* Set version tag in git repo to the commit the tarball is made from<br />
* Add version for all Calligra bug.kde.org products<br />
* Major release:<br />
**Create tour<br />
**Update stable major version at [http://community.kde.org/index.php?title=Template:Calligra/StableBranch&action=edit community.kde.org] and [http://userbase.kde.org/index.php?title=Template:Calligra/StableBranch&action=edit userbase.kde.org]<br />
**Update unstable major version at [http://community.kde.org/index.php?title=Template:Calligra/UnstableBranch&action=edit community.kde.org] and [http://userbase.kde.org/index.php?title=Template:Calligra/UnstableBranch&action=edit userbase.kde.org]<br />
**Update color at http://community.kde.org/Calligra/Schedules#Important_information<br />
* Update info on http://userbase.kde.org/Calligra/Download<br />
* Update stable release version at [http://community.kde.org/index.php?title=Template:Calligra/Stable&action=edit community.kde.org] and [http://userbase.kde.org/index.php?title=Template:Calligra/Stable&action=edit userbase.kde.org]<br />
* Update info in channel topic of #calligra<br />
* Update unstable stage at [http://community.kde.org/index.php?title=Template:Calligra/Stage&action=edit community.kde.org] and [http://userbase.kde.org/index.php?title=Template:Calligra/Stage&action=edit userbase.kde.org]<br />
* Kexi<br />
** Update kexi-project.org<br />
*** Add link to the Calligra announcement<br />
*** Update Kexi version on the front page<br />
** Update version on [http://kde-apps.org/content/show.php?content=12365 KDE-Apps.org]<br />
** Optional: Publish news on http://forum.kde.org/viewforum.php?f=220<br />
** Publish news on http://identi.ca/kexi and https://twitter.com/kexi_project<br />
** Publish news on kexi@kde.org<br />
** Major release: Publish news on http://www.linkedin.com<br />
* Wikipedia<br />
** Update version at http://en.wikipedia.org/wiki/Calligra and http://pl.wikipedia.org/wiki/Calligra</div>Cyrillehttps://community.kde.org/index.php?title=Calligra/Schedules/2.7/Release_Plan&diff=33706Calligra/Schedules/2.7/Release Plan2013-08-10T04:38:08Z<p>Cyrille: </p>
<hr />
<div>See also: [[../Feature Plan/]], [[../Quality Control/]]<br />
{{Note|Status: released}}<br />
__TOC__<br />
<br />
= Freezes =<br />
<br />
Master is never frozen for features or strings. The branch calligra/2.6 is always frozen for features or strings.<br />
<br />
= Testing =<br />
<br />
== Beta 1 (2.6.90) ==<br />
* Tagging and branching (calligra/2.6) April 27th (no big merge on that day)<br />
* Release April 30th (or May 1st)<br />
<br />
== Beta 2 (2.6.91) ==<br />
* Tagging May 18th (no big merge on that day)<br />
* Release May 22nd<br />
<br />
= Stable releases =<br />
<br />
== 2.7.2 ==<br />
* Tagging August 17th<br />
* Release August 21st<br />
<br />
== 2.7.3 ==<br />
* Tagging September 7th<br />
* Release September 11th<br />
<br />
== 2.7.4 ==<br />
* Tagging October 5th<br />
* Release October 9th<br />
<br />
== 2.7.5 ==<br />
* Tagging November 2nd<br />
* Release November 6th</div>Cyrillehttps://community.kde.org/index.php?title=Calligra/Schedules/Release_Blockers&diff=31994Calligra/Schedules/Release Blockers2013-05-30T12:51:24Z<p>Cyrille: </p>
<hr />
<div>This page gives access to information on the blocker of a Calligra release. A summay of release blockers is available on [http://quality.calligra-suite.org Calligra's quality website].<br />
<br />
= Release blockers =<br />
A Calligra release can only happen when:<br />
* there is no failing test in<br />
* there is no release critical bugs<br />
<br />
= Test suite =<br />
<br />
Results build server are available here:<br />
* [http://my.cdash.org/index.php?project=Calligra&display=project Calligra on cdash]<br />
* [http://158.36.191.251:8080/viewLog.html?buildTypeId=bt7&buildId=lastFinished&guest=true Loading files from the test suite] [http://158.36.191.251:8080/guestAuth/feed.html?itemsType=builds&buildStatus=successful&buildStatus=failed&itemsType=changes&userKey=guest rss]<br />
* [http://158.36.191.251:8080/viewLog.html?buildTypeId=bt6&buildId=lastFinished&guest=true Running the unit tests]<br />
<br />
<br />
= Release critical bugs =<br />
<br />
Release critical bugs are marked in [https://bugs.kde.org KDE's bugzilla] using the ''release_blocker'' keyword.<br />
<br />
== Definition of a Release Critical bug ==<br />
<br />
A Release Critical Bug is:<br />
* data loss<br />
* crash that prevent the use of the application (for instance crash at startup)<br />
<br />
A Release Critical Bug isn't:<br />
* user interaction (for instance a feature that can be done better)<br />
* appearance (for instance a docker that is X pixels wider than it should)<br />
<br />
== Link to Release critical bugs ==<br />
* [http://bugs.kde.org/buglist.cgi?query_format=advanced&product=calligracommon&product=calligraactive&product=calligrachart&product=calligraflow&product=kexi&product=calligraformula&product=calligrakarbon&product=calligra-plan&product=calligrastage&product=calligrasheets&product=calligrawords&product=krita&keywords=release_blocker all calligra], [http://bugs.kde.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=calligracommon&product=calligraactive&product=calligra-chart&product=calligraflow&product=kexi&product=calligraformula&product=karbon&product=calligraplan&product=calligrastage&product=calligrasheets&product=calligrawords&product=krita&long_desc_type=allwordssubstr&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=release_blocker&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&bug_status=CONFIRMED&emailtype1=substring&email1=&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= unclosed]<br />
* [http://bugs.kde.org/buglist.cgi?query_format=advanced&product=calligracommon&keywords=release_blocker&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED calligra libraries and plugins]<br />
* [http://bugs.kde.org/buglist.cgi?query_format=advanced&product=calligrawords&keywords=release_blocker&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED words]<br />
* [http://bugs.kde.org/buglist.cgi?query_format=advanced&product=calligrasheets&keywords=release_blocker&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED sheets]<br />
* [http://bugs.kde.org/buglist.cgi?query_format=advanced&product=calligrastage&keywords=release_blocker&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED stage]<br />
* [http://bugs.kde.org/buglist.cgi?query_format=advanced&product=kexi&keywords=release_blocker&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED kexi]<br />
* [http://bugs.kde.org/buglist.cgi?query_format=advanced&product=calligraplan&keywords=release_blocker&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED plan]<br />
* [http://bugs.kde.org/buglist.cgi?query_format=advanced&product=karbon&keywords=release_blocker&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED karbon]<br />
* [http://bugs.kde.org/buglist.cgi?query_format=advanced&product=krita&keywords=release_blocker&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED krita]</div>Cyrillehttps://community.kde.org/index.php?title=Calligra/Schedules/2.7/Release_Plan&diff=31173Calligra/Schedules/2.7/Release Plan2013-04-16T10:05:39Z<p>Cyrille: Created page with "See also: ../Feature Plan/, ../Quality Control/ {{Note|Status: released}} __TOC__ = Freezes = Master is never frozen for features or strings. The branch calligra/2.6..."</p>
<hr />
<div>See also: [[../Feature Plan/]], [[../Quality Control/]]<br />
{{Note|Status: released}}<br />
__TOC__<br />
<br />
= Freezes =<br />
<br />
Master is never frozen for features or strings. The branch calligra/2.6 is always frozen for features or strings.<br />
<br />
= Testing =<br />
<br />
== Beta 1 (2.6.90) ==<br />
* Tagging and branching (calligra/2.6) April 27th (no big merge on that day)<br />
* Release April 30th (or May 1st)<br />
<br />
== Beta (2.6.91) ==<br />
* Tagging May 18th (no big merge on that day)<br />
* Release May 22nd</div>Cyrillehttps://community.kde.org/index.php?title=Calligra/Schedules/2.6/Release_Plan&diff=29871Calligra/Schedules/2.6/Release Plan2013-02-05T12:31:27Z<p>Cyrille: /* 2.6.1 */</p>
<hr />
<div>See also: [[../Feature Plan/]], [[../Quality Control/]]<br />
{{Note|Status: in development, {{Calligra/Stage}}}}<br />
__TOC__<br />
<br />
= Freezes =<br />
<br />
Master is never frozen for features or strings. The branch calligra/2.6 is always frozen for features or strings.<br />
<br />
= Testing =<br />
<br />
== Alpha (2.5.90) ==<br />
* Tagging October 5th (no big merge on that day)<br />
* Release October 10th<br />
<br />
== Beta (2.5.91) ==<br />
* Tagging and branching (calligra/2.6) October 26th (no big merge on that day)<br />
* Release October 31th<br />
<br />
== RC (2.5.92) ==<br />
* Tagging November 24th (no big merge on that day)<br />
* Release November 28th<br />
<br />
== RC2 (2.5.93) ==<br />
<br />
Was sometime in december<br />
<br />
== RC3 (2.5.94) ==<br />
* Tagging 12th December<br />
* Release 15th December<br />
<br />
= Stable releases =<br />
<br />
== 2.6.0 ==<br />
* Tagging 2nd February<br />
* Release 5/6th February<br />
<br />
== 2.6.1 ==<br />
* Tagging 16th February<br />
* Release 20th February<br />
<br />
== 2.6.2 ==<br />
* Tagging 9th March<br />
* Release 13th March<br />
<br />
== 2.6.3 ==<br />
* Tagging 6th April<br />
* Release 10th April<br />
<br />
== 2.6.4 ==<br />
* Tagging 4th May<br />
* Release 8th May</div>Cyrillehttps://community.kde.org/index.php?title=Calligra/Schedules/2.6/Release_Plan&diff=29870Calligra/Schedules/2.6/Release Plan2013-02-05T12:31:19Z<p>Cyrille: /* 2.6.0 */</p>
<hr />
<div>See also: [[../Feature Plan/]], [[../Quality Control/]]<br />
{{Note|Status: in development, {{Calligra/Stage}}}}<br />
__TOC__<br />
<br />
= Freezes =<br />
<br />
Master is never frozen for features or strings. The branch calligra/2.6 is always frozen for features or strings.<br />
<br />
= Testing =<br />
<br />
== Alpha (2.5.90) ==<br />
* Tagging October 5th (no big merge on that day)<br />
* Release October 10th<br />
<br />
== Beta (2.5.91) ==<br />
* Tagging and branching (calligra/2.6) October 26th (no big merge on that day)<br />
* Release October 31th<br />
<br />
== RC (2.5.92) ==<br />
* Tagging November 24th (no big merge on that day)<br />
* Release November 28th<br />
<br />
== RC2 (2.5.93) ==<br />
<br />
Was sometime in december<br />
<br />
== RC3 (2.5.94) ==<br />
* Tagging 12th December<br />
* Release 15th December<br />
<br />
= Stable releases =<br />
<br />
== 2.6.0 ==<br />
* Tagging 2nd February<br />
* Release 5/6th February<br />
<br />
== 2.6.1 ==<br />
* Tagging 16th February<br />
* Release 19th February<br />
<br />
== 2.6.2 ==<br />
* Tagging 9th March<br />
* Release 13th March<br />
<br />
== 2.6.3 ==<br />
* Tagging 6th April<br />
* Release 10th April<br />
<br />
== 2.6.4 ==<br />
* Tagging 4th May<br />
* Release 8th May</div>Cyrillehttps://community.kde.org/index.php?title=Calligra/Schedules/2.6/Release_Plan&diff=29661Calligra/Schedules/2.6/Release Plan2013-01-23T10:27:52Z<p>Cyrille: /* 2.6.0 */</p>
<hr />
<div>See also: [[../Feature Plan/]], [[../Quality Control/]]<br />
{{Note|Status: in development, {{Calligra/Stage}}}}<br />
__TOC__<br />
<br />
= Freezes =<br />
<br />
Master is never frozen for features or strings. The branch calligra/2.6 is always frozen for features or strings.<br />
<br />
= Testing =<br />
<br />
== Alpha (2.5.90) ==<br />
* Tagging October 5th (no big merge on that day)<br />
* Release October 10th<br />
<br />
== Beta (2.5.91) ==<br />
* Tagging and branching (calligra/2.6) October 26th (no big merge on that day)<br />
* Release October 31th<br />
<br />
== RC (2.5.92) ==<br />
* Tagging November 24th (no big merge on that day)<br />
* Release November 28th<br />
<br />
== RC2 (2.5.93) ==<br />
<br />
Was sometime in december<br />
<br />
== RC3 (2.5.94) ==<br />
* Tagging 12th December<br />
* Release 15th December<br />
<br />
= Stable releases =<br />
<br />
== 2.6.0 ==<br />
* Tagging 2nd February<br />
* Release 5th February<br />
<br />
== 2.6.1 ==<br />
* Tagging 16th February<br />
* Release 19th February<br />
<br />
== 2.6.2 ==<br />
* Tagging 9th March<br />
* Release 13th March<br />
<br />
== 2.6.3 ==<br />
* Tagging 6th April<br />
* Release 10th April<br />
<br />
== 2.6.4 ==<br />
* Tagging 4th May<br />
* Release 8th May</div>Cyrillehttps://community.kde.org/index.php?title=Calligra/Schedules/2.6/Release_Plan&diff=29660Calligra/Schedules/2.6/Release Plan2013-01-23T10:25:54Z<p>Cyrille: </p>
<hr />
<div>See also: [[../Feature Plan/]], [[../Quality Control/]]<br />
{{Note|Status: in development, {{Calligra/Stage}}}}<br />
__TOC__<br />
<br />
= Freezes =<br />
<br />
Master is never frozen for features or strings. The branch calligra/2.6 is always frozen for features or strings.<br />
<br />
= Testing =<br />
<br />
== Alpha (2.5.90) ==<br />
* Tagging October 5th (no big merge on that day)<br />
* Release October 10th<br />
<br />
== Beta (2.5.91) ==<br />
* Tagging and branching (calligra/2.6) October 26th (no big merge on that day)<br />
* Release October 31th<br />
<br />
== RC (2.5.92) ==<br />
* Tagging November 24th (no big merge on that day)<br />
* Release November 28th<br />
<br />
== RC2 (2.5.93) ==<br />
<br />
Was sometime in december<br />
<br />
== RC3 (2.5.94) ==<br />
* Tagging 12th December<br />
* Release 15th December<br />
<br />
= Stable releases =<br />
<br />
== 2.6.0 ==<br />
* Tagging 2nd February<br />
* Release 5th February<br />
<br />
The first stable release should happen about three weeks after the RC, if everything is in order.</div>Cyrillehttps://community.kde.org/index.php?title=Calligra/Schedules/2.5/Release_Plan&diff=29464Calligra/Schedules/2.5/Release Plan2013-01-15T12:16:59Z<p>Cyrille: </p>
<hr />
<div>See also: [[../Feature Plan/]], [[../Quality Control/]]<br />
{{Note|Status: in development, {{Calligra/Stage}}}}<br />
__TOC__<br />
<br />
= Freezes =<br />
<br />
Master is never frozen for features or strings. The branch calligra/2.5 is always frozen for features or strings.<br />
<br />
= Testing =<br />
<br />
== Alpha (2.4.90) ==<br />
* Tagging May 25th (no big merge on that day)<br />
* Release May 30th<br />
<br />
== Beta (2.4.91) ==<br />
* Tagging and branching (calligra/2.5) June 15th (no big merge on that day)<br />
* Release June 20th<br />
<br />
== RC (2.4.92) ==<br />
* Tagging July 13th (no big merge on that day)<br />
* Release July 18th<br />
<br />
= Stable releases =<br />
<br />
== 2.5.0 ==<br />
* Tagging August 3rd (no big merge on that day)<br />
* Release August 8th<br />
<br />
== 2.5.1 ==<br />
* Tagging August 26th (no big merge on that day) - 4c48c0be38d6<br />
* Release August 29th<br />
<br />
== 2.5.2 ==<br />
* Tagging September 8th (no big merge on that day)<br />
* Release September 12th<br />
<br />
== 2.5.3 ==<br />
* Tagging October 5th (no big merge on that day)<br />
* Release October 10th<br />
<br />
== 2.5.4 ==<br />
* Tagging November 17th (no big merge on that day)<br />
* Release November 21st<br />
<br />
== 2.5.5 ==<br />
* Tagging January 19th (no big merge on that day)<br />
* Release January 22nd</div>Cyrillehttps://community.kde.org/index.php?title=Calligra/Schedules/2.4/Release_Plan&diff=29463Calligra/Schedules/2.4/Release Plan2013-01-15T12:16:44Z<p>Cyrille: </p>
<hr />
<div>See also: [[../Feature Plan/]], [[../Quality Control/]]<br />
<br />
{{Note|Status: released}}<br />
<br />
For this release, we aim at making Calligra ready for users. We will start making a plan for beta and final releases once the feautres mark for user-readiness in the [[../Feature Plan/]] are implemented, for the time being, we will make monthly snapshots release for people interesting in watching the progress.<br />
<br />
__TOC__<br />
<br />
= Freezes =<br />
<br />
== Soft Freeze, August 31th, 2011 ==<br />
<br />
No more features in master. Features in master are restricted to features discussed before hand and that can justify to be necesserary for user readiness.<br />
<br />
It is worthwhile to remember that while new features are allowed in the beta cycle, it should be the exception, not the norm.<br />
<br />
== String Freeze, October 12th, 2011 ==<br />
<br />
Any changes to a string needs to be discussed with the translation teams (except for typo that are bug fix and you only need to ping the translation teams). It also means no new features can be added.<br />
<br />
= Snapshots =<br />
== 2.3.70 ==<br />
Unreleased.<br />
<br />
== Alpha 1 (2.3.71) ==<br />
* Tagging May 12th (no big merge on that day)<br />
* Release May 18th<br />
<br />
== Alpha 2 (2.3.72) ==<br />
* Tagging June 10th (no big merge on that day)<br />
* Release June 16th<br />
<br />
== Alpha 3 (2.3.73) ==<br />
* Tagging July 8th (no big merge on that day)<br />
* Release July 13th<br />
<br />
== Alpha 4 (2.3.74) ==<br />
* Tagging August 12th (no big merge on that day)<br />
* Release August 17th<br />
<br />
= Betas =<br />
<br />
== Beta 1 (2.3.81) ==<br />
* Tagging September 7th (no big merge on that day)<br />
* Release September 14th<br />
<br />
== Beta 2 (2.3.82) ==<br />
* Tagging September 30th (no big merge on that day)<br />
** {{CalligraGitCommit|ea57cb68b4c7ea46c5916b2a54084159c8dce1ed}}<br />
* Release October 5th<br />
<br />
== Beta 3 (2.3.83) ==<br />
* Tagging October 21th (no big merge on that day)<br />
** {{CalligraGitCommit|49808577a77267dc7f4cd917588312e4aad59681}}<br />
* Release October 26th<br />
<br />
== Beta 4 (2.3.84) ==<br />
* Tagging November 18th (no big merge on that day)<br />
* Release November 23th<br />
<br />
== Beta 5 (2.3.85) ==<br />
* Tagging December 9th (no big merge on that day)<br />
* Release December 14th<br />
<br />
== Beta 6 (2.3.86) ==<br />
* Tagging January 6th (no big merge on that day)<br />
* Release January 11th<br />
<br />
== Beta 7 (2.3.87) ==<br />
* Tagging January 27th (no big merge on that day)<br />
* Release February 1th<br />
<br />
= Release Candidate =<br />
<br />
There is no realistic way to be certain when the RC1 will be available, hopefully in 2012, we invite you to check [http://quality.calligra.org/] and when the number of tests failure and release critical bugs is near zero, then the time for the RC1 will be very close.<br />
<br />
== RC 1 (2.3.91) ==<br />
* Tagging March 2nd (no big merge on that day), branching into the calligra/2.4 branch will happen at that time<br />
* Release March 7th<br />
<br />
= Final release and maintenance schedule =<br />
<br />
== 2.4.0 ==<br />
Hopefully, it will happen three weeks after the RC, if no major problem is discovered.<br />
<br />
* Tagging April 6th (no big merge on that day)<br />
* Release April 11th<br />
<br />
== 2.4.1 ==<br />
* Tagging April 21th (no big merge on that day)<br />
* Release April 25th<br />
<br />
== 2.4.2 ==<br />
* Tagging May 25th (no big merge on that day)<br />
* Release May 30h<br />
<br />
== 2.4.3 ==<br />
* Tagging June 26th (no big merge on that day)<br />
* Release June 27th<br />
<br />
== 2.4.4 ==<br />
* Tagging January 19th (no big merge on that day)<br />
* Release January 22nd</div>Cyrillehttps://community.kde.org/index.php?title=Calligra/Schedules/2.5/Release_Plan&diff=26456Calligra/Schedules/2.5/Release Plan2012-11-16T09:06:58Z<p>Cyrille: /* 2.5.4 */</p>
<hr />
<div>See also: [[../Feature Plan/]], [[../Quality Control/]]<br />
{{Note|Status: in development, {{Calligra/Stage}}}}<br />
__TOC__<br />
<br />
= Freezes =<br />
<br />
Master is never frozen for features or strings. The branch calligra/2.5 is always frozen for features or strings.<br />
<br />
= Testing =<br />
<br />
== Alpha (2.4.90) ==<br />
* Tagging May 25th (no big merge on that day)<br />
* Release May 30th<br />
<br />
== Beta (2.4.91) ==<br />
* Tagging and branching (calligra/2.5) June 15th (no big merge on that day)<br />
* Release June 20th<br />
<br />
== RC (2.4.92) ==<br />
* Tagging July 13th (no big merge on that day)<br />
* Release July 18th<br />
<br />
= Stable releases =<br />
<br />
== 2.5.0 ==<br />
* Tagging August 3rd (no big merge on that day)<br />
* Release August 8th<br />
<br />
== 2.5.1 ==<br />
* Tagging August 26th (no big merge on that day) - 4c48c0be38d6<br />
* Release August 29th<br />
<br />
== 2.5.2 ==<br />
* Tagging September 8th (no big merge on that day)<br />
* Release September 12th<br />
<br />
== 2.5.3 ==<br />
* Tagging October 5th (no big merge on that day)<br />
* Release October 10th<br />
<br />
== 2.5.4 ==<br />
* Tagging November 17th (no big merge on that day)<br />
* Release November 21st</div>Cyrillehttps://community.kde.org/index.php?title=Calligra/Schedules/2.6/Release_Plan&diff=25924Calligra/Schedules/2.6/Release Plan2012-10-28T06:18:44Z<p>Cyrille: </p>
<hr />
<div>See also: [[../Feature Plan/]], [[../Quality Control/]]<br />
{{Note|Status: in development, {{Calligra/Stage}}}}<br />
__TOC__<br />
<br />
= Freezes =<br />
<br />
Master is never frozen for features or strings. The branch calligra/2.6 is always frozen for features or strings.<br />
<br />
= Testing =<br />
<br />
== Alpha (2.5.90) ==<br />
* Tagging October 5th (no big merge on that day)<br />
* Release October 10th<br />
<br />
== Beta (2.5.91) ==<br />
* Tagging and branching (calligra/2.6) October 26th (no big merge on that day)<br />
* Release October 31th<br />
<br />
== RC (2.5.92) ==<br />
* Tagging November 24th (no big merge on that day)<br />
* Release November 28th<br />
<br />
= Stable releases =<br />
<br />
The first stable release should happen about three weeks after the RC, if everything is in order.</div>Cyrillehttps://community.kde.org/index.php?title=Calligra/Schedules/2.5/Release_Plan&diff=25207Calligra/Schedules/2.5/Release Plan2012-10-04T15:46:42Z<p>Cyrille: </p>
<hr />
<div>See also: [[../Feature Plan/]], [[../Quality Control/]]<br />
{{Note|Status: in development, {{Calligra/Stage}}}}<br />
__TOC__<br />
<br />
= Freezes =<br />
<br />
Master is never frozen for features or strings. The branch calligra/2.5 is always frozen for features or strings.<br />
<br />
= Testing =<br />
<br />
== Alpha (2.4.90) ==<br />
* Tagging May 25th (no big merge on that day)<br />
* Release May 30th<br />
<br />
== Beta (2.4.91) ==<br />
* Tagging and branching (calligra/2.5) June 15th (no big merge on that day)<br />
* Release June 20th<br />
<br />
== RC (2.4.92) ==<br />
* Tagging July 13th (no big merge on that day)<br />
* Release July 18th<br />
<br />
= Stable releases =<br />
<br />
== 2.5.0 ==<br />
* Tagging August 3rd (no big merge on that day)<br />
* Release August 8th<br />
<br />
== 2.5.1 ==<br />
* Tagging August 26th (no big merge on that day) - 4c48c0be38d6<br />
* Release August 29th<br />
<br />
== 2.5.2 ==<br />
* Tagging September 8th (no big merge on that day)<br />
* Release September 12th<br />
<br />
== 2.5.3 ==<br />
* Tagging October 5th (no big merge on that day)<br />
* Release October 10th<br />
<br />
== 2.5.4 ==<br />
* Tagging November 2nd (no big merge on that day)<br />
* Release November 7th</div>Cyrillehttps://community.kde.org/index.php?title=Calligra/Schedules/2.6/Release_Plan&diff=25206Calligra/Schedules/2.6/Release Plan2012-10-04T15:29:37Z<p>Cyrille: Created page with "See also: ../Feature Plan/, ../Quality Control/ {{Note|Status: in development, {{Calligra/Stage}}}} __TOC__ = Freezes = Master is never frozen for features or string..."</p>
<hr />
<div>See also: [[../Feature Plan/]], [[../Quality Control/]]<br />
{{Note|Status: in development, {{Calligra/Stage}}}}<br />
__TOC__<br />
<br />
= Freezes =<br />
<br />
Master is never frozen for features or strings. The branch calligra/2.6 is always frozen for features or strings.<br />
<br />
= Testing =<br />
<br />
== Alpha (2.5.90) ==<br />
* Tagging October 5th (no big merge on that day)<br />
* Release October 10th<br />
<br />
== Beta (2.5.91) ==<br />
* Tagging and branching (calligra/2.6) October 26th (no big merge on that day)<br />
* Release October 31th<br />
<br />
== RC (2.5.92) ==<br />
* Tagging November 16th (no big merge on that day)<br />
* Release November 21th<br />
<br />
= Stable releases =<br />
<br />
The first stable release should happen about three weeks after the RC, if everything is in order.</div>Cyrillehttps://community.kde.org/index.php?title=Calligra/Schedules/2.5/Release_Plan&diff=23886Calligra/Schedules/2.5/Release Plan2012-09-06T05:57:39Z<p>Cyrille: /* 2.5.3 */</p>
<hr />
<div>See also: [[../Feature Plan/]], [[../Quality Control/]]<br />
{{Note|Status: in development, {{Calligra/Stage}}}}<br />
__TOC__<br />
<br />
= Freezes =<br />
<br />
Master is never frozen for features or strings. The branch calligra/2.5 is always frozen for features or strings.<br />
<br />
= Testing =<br />
<br />
== Alpha (2.4.90) ==<br />
* Tagging May 25th (no big merge on that day)<br />
* Release May 30th<br />
<br />
== Beta (2.4.91) ==<br />
* Tagging and branching (calligra/2.5) June 15th (no big merge on that day)<br />
* Release June 20th<br />
<br />
== RC (2.4.92) ==<br />
* Tagging July 13th (no big merge on that day)<br />
* Release July 18th<br />
<br />
= Stable releases =<br />
<br />
== 2.5.0 ==<br />
* Tagging August 3rd (no big merge on that day)<br />
* Release August 8th<br />
<br />
== 2.5.1 ==<br />
* Tagging August 26th (no big merge on that day) - 4c48c0be38d6<br />
* Release August 29th<br />
<br />
== 2.5.2 ==<br />
* Tagging September 7th (no big merge on that day)<br />
* Release September 12th<br />
<br />
== 2.5.3 ==<br />
* Tagging October 5th (no big merge on that day)<br />
* Release October 10th</div>Cyrillehttps://community.kde.org/index.php?title=Calligra/Schedules/2.5/Release_Plan&diff=23885Calligra/Schedules/2.5/Release Plan2012-09-06T05:57:05Z<p>Cyrille: /* 2.5.2 */</p>
<hr />
<div>See also: [[../Feature Plan/]], [[../Quality Control/]]<br />
{{Note|Status: in development, {{Calligra/Stage}}}}<br />
__TOC__<br />
<br />
= Freezes =<br />
<br />
Master is never frozen for features or strings. The branch calligra/2.5 is always frozen for features or strings.<br />
<br />
= Testing =<br />
<br />
== Alpha (2.4.90) ==<br />
* Tagging May 25th (no big merge on that day)<br />
* Release May 30th<br />
<br />
== Beta (2.4.91) ==<br />
* Tagging and branching (calligra/2.5) June 15th (no big merge on that day)<br />
* Release June 20th<br />
<br />
== RC (2.4.92) ==<br />
* Tagging July 13th (no big merge on that day)<br />
* Release July 18th<br />
<br />
= Stable releases =<br />
<br />
== 2.5.0 ==<br />
* Tagging August 3rd (no big merge on that day)<br />
* Release August 8th<br />
<br />
== 2.5.1 ==<br />
* Tagging August 26th (no big merge on that day) - 4c48c0be38d6<br />
* Release August 29th<br />
<br />
== 2.5.2 ==<br />
* Tagging September 7th (no big merge on that day)<br />
* Release September 12th<br />
<br />
== 2.5.3 ==<br />
* Tagging November 2th (no big merge on that day)<br />
* Release November 7th<br />
<br />
The final release should happen within three weeks after the RC.</div>Cyrillehttps://community.kde.org/index.php?title=Calligra/Schedules/2.5/Release_Plan&diff=23727Calligra/Schedules/2.5/Release Plan2012-08-27T08:07:42Z<p>Cyrille: </p>
<hr />
<div>See also: [[../Feature Plan/]], [[../Quality Control/]]<br />
{{Note|Status: in development, {{Calligra/Stage}}}}<br />
__TOC__<br />
<br />
= Freezes =<br />
<br />
Master is never frozen for features or strings. The branch calligra/2.5 is always frozen for features or strings.<br />
<br />
= Testing =<br />
<br />
== Alpha (2.4.90) ==<br />
* Tagging May 25th (no big merge on that day)<br />
* Release May 30th<br />
<br />
== Beta (2.4.91) ==<br />
* Tagging and branching (calligra/2.5) June 15th (no big merge on that day)<br />
* Release June 20th<br />
<br />
== RC (2.4.92) ==<br />
* Tagging July 13th (no big merge on that day)<br />
* Release July 18th<br />
<br />
= Stable releases =<br />
<br />
== 2.5.0 ==<br />
* Tagging August 3rd (no big merge on that day)<br />
* Release August 8th<br />
<br />
== 2.5.1 ==<br />
* Tagging August 26th (no big merge on that day) - 4c48c0be38d6<br />
* Release August 29th<br />
<br />
== 2.5.2 ==<br />
* Tagging October 5th (no big merge on that day)<br />
* Release October 10th<br />
<br />
== 2.5.3 ==<br />
* Tagging November 2th (no big merge on that day)<br />
* Release November 7th<br />
<br />
The final release should happen within three weeks after the RC.</div>Cyrillehttps://community.kde.org/index.php?title=Calligra/Schedules/Feature_Plan&diff=23629Calligra/Schedules/Feature Plan2012-08-18T06:45:29Z<p>Cyrille: </p>
<hr />
<div>See also: [[../Release Plan/]], [[../Quality Control/]]<br />
<br />
This is a list of planned features for Calligra Suite.<br />
<br />
{{Note|Status: in development, {{Calligra/Stage}}}}<br />
<br />
__TOC__<br />
<br />
== Common stuff ==<br />
{{CalligraFeatureTableStart}}<br />
{{CalligraTodo |Ui - make it possible to select and manipulate shapes with every tool|boemann|2.7}}<br />
{{CalligraTodo |Ui - possibly move snapping widget from tool option back into a dedicated docker|boemann|2.7}}<br />
{{CalligraTodo |Ui - do something with the strokprops and stroke/fill dockers|boemann|2.7}}<br />
{{CalligraInProgress |Core - separate document class from part class|boemann+|2.7}}<br />
|}<br />
<br />
== Calligra Words, and everything text related ==<br />
{{CalligraFeatureTableStart}}<br />
{{CalligraInProgress |Page layout - direct manipulation of layout and reorganize option widget |divyam|2.6}}<br />
{{CalligraInProgress |Text editing - ui for lists, direct manipulation of list|gopalK|2.6}}<br />
{{CalligraInProgress |Grammar checking - using link grammar|garima|2.6}}<br />
{{CalligraTodo |Stylemanager - make it always accessable|moji|2.6}}<br />
{{CalligraTodo |Stylemanager - shortcuts for styles|moji|2.6}}<br />
{{CalligraTodo |Stylemanager - delete style|moji|2.6}}<br />
{{CalligraInProgress |Stylemanager - changable parent style|pierreSt|2.6}}<br />
{{CalligraInProgress |Bibliography - api for external engines|smitpatel|2.6}}<br />
{{CalligraTodo |Layout - new bookmark system|boemann|2.7}}<br />
{{CalligraTodo |Layout - Section columns|boemann|2.7}}<br />
{{CalligraTodo |Changetracking - reenable, and stabalize|pierreSt|3.0}}<br />
{{CalligraTodo |Captions and index|tbd}}<br />
|}<br />
<br />
== Calligra Stage ==<br />
See also Calligra Words above for text related features<br />
<br />
{{CalligraFeatureTableStart}}<br />
{{CalligraTodo |lorum ipsum|zagge|2.5}}<br />
|}<br />
<br />
== Calligra Sheets ==<br />
{{CalligraFeatureTableStart}}<br />
{{CalligraTodo |lorum ipsum|mek|2.5}}<br />
|}<br />
<br />
== Calligra Plan ==<br />
{{CalligraFeatureTableStart}}<br />
{{CalligraDone |lorum ipsum|Dag|2.5}}<br />
|}<br />
<br />
== Calligra Flow, and connections ==<br />
{{CalligraFeatureTableStart}}<br />
{{CalligraInProgress |lorum ipsum|yue|2.5}}<br />
|}<br />
<br />
== Braindump ==<br />
{{CalligraFeatureTableStart}}<br />
{{CalligraTodo |text tool|Cyrille Berger|2.6}}<br />
|}<br />
<br />
== Formula Shape ==<br />
{{CalligraFeatureTableStart}}<br />
{{CalligraInProgress|Tool to create formula from matlab equations|Berger|2.5|formulashape-matlab_tool-cyrille_berger}}<br />
|}<br />
<br />
== Chart Shape ==<br />
{{CalligraFeatureTableStart}}<br />
{{CalligraInProgress|something|erione|2.5}}<br />
|}<br />
<br />
== Karbon ==<br />
{{CalligraFeatureTableStart}}<br />
{{CalligraInProgress|something|jaham|2.5}}<br />
|}<br />
<br />
== Krita ==<br />
{{CalligraFeatureTableStart}}<br />
{{CalligraInProgress|something|boud|2.5}}<br />
|}<br />
<br />
== Kexi ==<br />
See also [[Kexi/TODOs|long-term Kexi plans]] and [[Kexi/Releases/Kexi_2.5#List_of_changes|the changelog]]. This release is somewhat compatible with the [http://en.wikipedia.org/wiki/Worse_is_Better Worse is Better] idea.<br />
<br />
{{CalligraFeatureTableStart}}<br />
<!-- ---- KexiDB ---- --><br />
{{CalligraInProgress|KexiDB - Move core parts of KexiDB lib to calligra/libs/db (libcalligradb) for reuse by Word's Biblio module. [[Kexi/KexiDB#libCalligraDB|Details]]. Coordinate and support with Smit Patel <smitpatel24@gmail.com>.|jstaniek|2.6}}<br />
{{CalligraInProgress|KexiDB - [[Kexi/KexiDB/User_data|Add support for user data storage]]|jstaniek|2.6}}<br />
<!-- ---- Kexi Main Window ---- --><br />
{{CalligraDone|Main Window - [[Kexi/Main_Window#Full_Screen|Add full-screen mode]]|diggy|2.5}}<br />
<!-- ---- Kexi Imp/Exp ---- --><br />
{{CalligraTodo|Imp/Exp - Remove outdated mdbtools and reimplement with linked mdbtools - {{Bug|277583}}|piggz}}<br />
{{CalligraTodo|Imp/Exp - Add option for appending imported CSV data to existing table|}}<br />
<!-- ---- Kexi Tables ---- --><br />
{{CalligraInProgress|Tables - [[Kexi/Plugins/Tables/Remember_column_widths|Remember column widths in tabular data view]]|jstaniek|2.6}}<br />
<!-- ---- Kexi Forms ---- --><br />
{{CalligraDone|Forms - Add new form widgets: Command Link Button, Slider, Progress Bar, Date Picker|Oleg|2.5}}<br />
|}</div>Cyrillehttps://community.kde.org/index.php?title=Calligra/Schedules/Feature_Plan&diff=23628Calligra/Schedules/Feature Plan2012-08-18T06:44:30Z<p>Cyrille: </p>
<hr />
<div>See also: [[../Release Plan/]], [[../Quality Control/]]<br />
<br />
This is a list of planned features for Calligra Suite.<br />
<br />
{{Note|Status: in development, {{Calligra/Stage}}}}<br />
<br />
__TOC__<br />
<br />
== Common stuff ==<br />
{{CalligraFeatureTableStart}}<br />
{{CalligraTodo |Ui - make it possible to select and manipulate shapes with every tool|boemann|2.7}}<br />
{{CalligraTodo |Ui - possibly move snapping widget from tool option back into a dedicated docker|boemann|2.7}}<br />
{{CalligraTodo |Ui - do something with the strokprops and stroke/fill dockers|boemann|2.7}}<br />
{{CalligraInProgress |Core - separate document class from part class|boemann+|2.7}}<br />
|}<br />
<br />
== Calligra Words, and everything text related ==<br />
{{CalligraFeatureTableStart}}<br />
{{CalligraInProgress |Page layout - direct manipulation of layout and reorganize option widget |divyam|2.6}}<br />
{{CalligraInProgress |Text editing - ui for lists, direct manipulation of list|gopalK|2.6}}<br />
{{CalligraInProgress |Grammar checking - using link grammar|garima|2.6}}<br />
{{CalligraTodo |Stylemanager - make it always accessable|moji|2.6}}<br />
{{CalligraTodo |Stylemanager - shortcuts for styles|moji|2.6}}<br />
{{CalligraTodo |Stylemanager - delete style|moji|2.6}}<br />
{{CalligraInProgress |Stylemanager - changable parent style|pierreSt|2.6}}<br />
{{CalligraInProgress |Bibliography - api for external engines|smitpatel|2.6}}<br />
{{CalligraTodo |Layout - new bookmark system|boemann|2.7}}<br />
{{CalligraTodo |Layout - Section columns|boemann|2.7}}<br />
{{CalligraTodo |Changetracking - reenable, and stabalize|pierreSt|3.0}}<br />
{{CalligraTodo |Captions and index|tbd}}<br />
|}<br />
<br />
== Calligra Stage ==<br />
See also Calligra Words above for text related features<br />
<br />
{{CalligraFeatureTableStart}}<br />
{{CalligraTodo |lorum ipsum|zagge|2.5}}<br />
|}<br />
<br />
== Calligra Sheets ==<br />
{{CalligraFeatureTableStart}}<br />
{{CalligraTodo |lorum ipsum|mek|2.5}}<br />
|}<br />
<br />
== Calligra Plan ==<br />
{{CalligraFeatureTableStart}}<br />
{{CalligraDone |lorum ipsum|Dag|2.5}}<br />
|}<br />
<br />
== Calligra Flow, and connections ==<br />
{{CalligraFeatureTableStart}}<br />
{{CalligraInProgress |lorum ipsum|yue|2.5}}<br />
|}<br />
<br />
== Braindump ==<br />
{{CalligraFeatureTableStart}}<br />
{{CalligraInProgress |text tool|Cyrille Berger|2.6}}<br />
|}<br />
<br />
== Formula Shape ==<br />
{{CalligraFeatureTableStart}}<br />
{{CalligraInProgress|Tool to create formula from matlab equations|Berger|2.5|formulashape-matlab_tool-cyrille_berger}}<br />
|}<br />
<br />
== Chart Shape ==<br />
{{CalligraFeatureTableStart}}<br />
{{CalligraInProgress|something|erione|2.5}}<br />
|}<br />
<br />
== Karbon ==<br />
{{CalligraFeatureTableStart}}<br />
{{CalligraInProgress|something|jaham|2.5}}<br />
|}<br />
<br />
== Krita ==<br />
{{CalligraFeatureTableStart}}<br />
{{CalligraInProgress|something|boud|2.5}}<br />
|}<br />
<br />
== Kexi ==<br />
See also [[Kexi/TODOs|long-term Kexi plans]] and [[Kexi/Releases/Kexi_2.5#List_of_changes|the changelog]]. This release is somewhat compatible with the [http://en.wikipedia.org/wiki/Worse_is_Better Worse is Better] idea.<br />
<br />
{{CalligraFeatureTableStart}}<br />
<!-- ---- KexiDB ---- --><br />
{{CalligraInProgress|KexiDB - Move core parts of KexiDB lib to calligra/libs/db (libcalligradb) for reuse by Word's Biblio module. [[Kexi/KexiDB#libCalligraDB|Details]]. Coordinate and support with Smit Patel <smitpatel24@gmail.com>.|jstaniek|2.6}}<br />
{{CalligraInProgress|KexiDB - [[Kexi/KexiDB/User_data|Add support for user data storage]]|jstaniek|2.6}}<br />
<!-- ---- Kexi Main Window ---- --><br />
{{CalligraDone|Main Window - [[Kexi/Main_Window#Full_Screen|Add full-screen mode]]|diggy|2.5}}<br />
<!-- ---- Kexi Imp/Exp ---- --><br />
{{CalligraTodo|Imp/Exp - Remove outdated mdbtools and reimplement with linked mdbtools - {{Bug|277583}}|piggz}}<br />
{{CalligraTodo|Imp/Exp - Add option for appending imported CSV data to existing table|}}<br />
<!-- ---- Kexi Tables ---- --><br />
{{CalligraInProgress|Tables - [[Kexi/Plugins/Tables/Remember_column_widths|Remember column widths in tabular data view]]|jstaniek|2.6}}<br />
<!-- ---- Kexi Forms ---- --><br />
{{CalligraDone|Forms - Add new form widgets: Command Link Button, Slider, Progress Bar, Date Picker|Oleg|2.5}}<br />
|}</div>Cyrillehttps://community.kde.org/index.php?title=Calligra/Schedules/2.5/Release_Plan&diff=23461Calligra/Schedules/2.5/Release Plan2012-08-07T08:05:48Z<p>Cyrille: </p>
<hr />
<div>See also: [[../Feature Plan/]], [[../Quality Control/]]<br />
{{Note|Status: in development, {{Calligra/Stage}}}}<br />
__TOC__<br />
<br />
= Freezes =<br />
<br />
Master is never frozen for features or strings. The branch calligra/2.5 is always frozen for features or strings.<br />
<br />
= Testing =<br />
<br />
== Alpha (2.4.90) ==<br />
* Tagging May 25th (no big merge on that day)<br />
* Release May 30th<br />
<br />
== Beta (2.4.91) ==<br />
* Tagging and branching (calligra/2.5) June 15th (no big merge on that day)<br />
* Release June 20th<br />
<br />
== RC (2.4.92) ==<br />
* Tagging July 13th (no big merge on that day)<br />
* Release July 18th<br />
<br />
= Stable releases =<br />
<br />
== 2.5.0 ==<br />
* Tagging August 3rd (no big merge on that day)<br />
* Release August 8th<br />
<br />
== 2.5.1 ==<br />
* Tagging September 7th (no big merge on that day)<br />
* Release September 12th<br />
<br />
== 2.5.2 ==<br />
* Tagging October 5th (no big merge on that day)<br />
* Release October 10th<br />
<br />
== 2.5.3 ==<br />
* Tagging November 2th (no big merge on that day)<br />
* Release November 7th<br />
<br />
The final release should happen within three weeks after the RC.</div>Cyrillehttps://community.kde.org/index.php?title=Calligra/Schedules/2.5/Release_Plan&diff=22657Calligra/Schedules/2.5/Release Plan2012-07-09T18:17:14Z<p>Cyrille: /* RC (2.4.92) */</p>
<hr />
<div>See also: [[../Feature Plan/]], [[../Quality Control/]]<br />
{{Note|Status: in development, {{Calligra/Stage}}}}<br />
__TOC__<br />
<br />
= Freezes =<br />
<br />
Master is never frozen for features or strings. The branch calligra/2.5 is always frozen for features or strings.<br />
<br />
= Testing =<br />
<br />
== Alpha (2.4.90) ==<br />
* Tagging May 25th (no big merge on that day)<br />
* Release May 30th<br />
<br />
== Beta (2.4.91) ==<br />
* Tagging and branching (calligra/2.5) June 15th (no big merge on that day)<br />
* Release June 20th<br />
<br />
== RC (2.4.92) ==<br />
* Tagging July 13th (no big merge on that day)<br />
* Release July 18th<br />
<br />
= Stable releases =<br />
<br />
The final release should happen within three weeks after the RC.</div>Cyrillehttps://community.kde.org/index.php?title=Calligra/Contributing_a_Patch&diff=22629Calligra/Contributing a Patch2012-07-09T09:42:13Z<p>Cyrille: </p>
<hr />
<div>This page describes how one can send a contributed patch for discussion to the Calligra developers.<br />
<br />
<b>Quick Links:<br />
*[http://reviewboard.kde.org/groups/calligra/ Calligra review requests on KDE Review Board git.reviewboard.kde.org]<br />
*[[Calligra/Policies/Review board rules|Rules of the review board]]<br />
</b><br />
== Create a patch ==<br />
<br />
In order to create a patch with git:<br />
* in your branch: git diff master > filename<br />
* from master: git diff branchname > filename<br />
<br />
== Submit it to review board ==<br />
<br />
If you are new to Calligra development you should almost submit almost always your patch to [http://reviewboard.kde.org/groups/calligra/ Calligra on KDE's review board]. But some code need to be reviewed even if it is created by long time core developers. If you are<br />
unsure check out the [[Calligra/Policies/Review board rules|rules of the review board]].<br />
<br />
* Log in to the review board. It is using the KDE identity (if you do not have an account, you can get one from [http://identity.kde.org KDE identity], it is open to everyone)<br />
* Click on "New Review Request"<br />
* In Repository, choose calligra<br />
* In Diff select the patch you want to upload<br />
* Optionnaly in parent, give a patch that needs to be applied before yours (this is only needed if the patch is based on an other patch from reviewboard or on a branch different from master)<br />
* After clicking on "Create a review request" you will have to add "calligra" in the list of group and a description<br />
* Fill the summary and the title<br />
* Don't forget to press "publish" at the top of the page<br />
<br />
For previous requests, see also the [http://reviewboard.kde.org/groups/koffice/ old KOffice SVN reviewboard page].</div>Cyrillehttps://community.kde.org/index.php?title=Calligra/Schedules/2.4/Release_Plan&diff=22211Calligra/Schedules/2.4/Release Plan2012-06-26T04:01:35Z<p>Cyrille: /* 2.4.3 */</p>
<hr />
<div>See also: [[../Feature Plan/]], [[../Quality Control/]]<br />
<br />
{{Note|Status: released}}<br />
<br />
For this release, we aim at making Calligra ready for users. We will start making a plan for beta and final releases once the feautres mark for user-readiness in the [[../Feature Plan/]] are implemented, for the time being, we will make monthly snapshots release for people interesting in watching the progress.<br />
<br />
__TOC__<br />
<br />
= Freezes =<br />
<br />
== Soft Freeze, August 31th, 2011 ==<br />
<br />
No more features in master. Features in master are restricted to features discussed before hand and that can justify to be necesserary for user readiness.<br />
<br />
It is worthwhile to remember that while new features are allowed in the beta cycle, it should be the exception, not the norm.<br />
<br />
== String Freeze, October 12th, 2011 ==<br />
<br />
Any changes to a string needs to be discussed with the translation teams (except for typo that are bug fix and you only need to ping the translation teams). It also means no new features can be added.<br />
<br />
= Snapshots =<br />
== 2.3.70 ==<br />
Unreleased.<br />
<br />
== Alpha 1 (2.3.71) ==<br />
* Tagging May 12th (no big merge on that day)<br />
* Release May 18th<br />
<br />
== Alpha 2 (2.3.72) ==<br />
* Tagging June 10th (no big merge on that day)<br />
* Release June 16th<br />
<br />
== Alpha 3 (2.3.73) ==<br />
* Tagging July 8th (no big merge on that day)<br />
* Release July 13th<br />
<br />
== Alpha 4 (2.3.74) ==<br />
* Tagging August 12th (no big merge on that day)<br />
* Release August 17th<br />
<br />
= Betas =<br />
<br />
== Beta 1 (2.3.81) ==<br />
* Tagging September 7th (no big merge on that day)<br />
* Release September 14th<br />
<br />
== Beta 2 (2.3.82) ==<br />
* Tagging September 30th (no big merge on that day)<br />
** {{CalligraGitCommit|ea57cb68b4c7ea46c5916b2a54084159c8dce1ed}}<br />
* Release October 5th<br />
<br />
== Beta 3 (2.3.83) ==<br />
* Tagging October 21th (no big merge on that day)<br />
** {{CalligraGitCommit|49808577a77267dc7f4cd917588312e4aad59681}}<br />
* Release October 26th<br />
<br />
== Beta 4 (2.3.84) ==<br />
* Tagging November 18th (no big merge on that day)<br />
* Release November 23th<br />
<br />
== Beta 5 (2.3.85) ==<br />
* Tagging December 9th (no big merge on that day)<br />
* Release December 14th<br />
<br />
== Beta 6 (2.3.86) ==<br />
* Tagging January 6th (no big merge on that day)<br />
* Release January 11th<br />
<br />
== Beta 7 (2.3.87) ==<br />
* Tagging January 27th (no big merge on that day)<br />
* Release February 1th<br />
<br />
= Release Candidate =<br />
<br />
There is no realistic way to be certain when the RC1 will be available, hopefully in 2012, we invite you to check [http://quality.calligra.org/] and when the number of tests failure and release critical bugs is near zero, then the time for the RC1 will be very close.<br />
<br />
== RC 1 (2.3.91) ==<br />
* Tagging March 2nd (no big merge on that day), branching into the calligra/2.4 branch will happen at that time<br />
* Release March 7th<br />
<br />
= Final release and maintenance schedule =<br />
<br />
== 2.4.0 ==<br />
Hopefully, it will happen three weeks after the RC, if no major problem is discovered.<br />
<br />
* Tagging April 6th (no big merge on that day)<br />
* Release April 11th<br />
<br />
== 2.4.1 ==<br />
* Tagging April 21th (no big merge on that day)<br />
* Release April 25th<br />
<br />
== 2.4.2 ==<br />
* Tagging May 25th (no big merge on that day)<br />
* Release May 30h<br />
<br />
== 2.4.3 ==<br />
* Tagging June 26th (no big merge on that day)<br />
* Release June 27th</div>Cyrillehttps://community.kde.org/index.php?title=Calligra/Schedules/2.4/Release_Plan&diff=22125Calligra/Schedules/2.4/Release Plan2012-06-23T09:21:12Z<p>Cyrille: /* 2.4.3 */</p>
<hr />
<div>See also: [[../Feature Plan/]], [[../Quality Control/]]<br />
<br />
{{Note|Status: released}}<br />
<br />
For this release, we aim at making Calligra ready for users. We will start making a plan for beta and final releases once the feautres mark for user-readiness in the [[../Feature Plan/]] are implemented, for the time being, we will make monthly snapshots release for people interesting in watching the progress.<br />
<br />
__TOC__<br />
<br />
= Freezes =<br />
<br />
== Soft Freeze, August 31th, 2011 ==<br />
<br />
No more features in master. Features in master are restricted to features discussed before hand and that can justify to be necesserary for user readiness.<br />
<br />
It is worthwhile to remember that while new features are allowed in the beta cycle, it should be the exception, not the norm.<br />
<br />
== String Freeze, October 12th, 2011 ==<br />
<br />
Any changes to a string needs to be discussed with the translation teams (except for typo that are bug fix and you only need to ping the translation teams). It also means no new features can be added.<br />
<br />
= Snapshots =<br />
== 2.3.70 ==<br />
Unreleased.<br />
<br />
== Alpha 1 (2.3.71) ==<br />
* Tagging May 12th (no big merge on that day)<br />
* Release May 18th<br />
<br />
== Alpha 2 (2.3.72) ==<br />
* Tagging June 10th (no big merge on that day)<br />
* Release June 16th<br />
<br />
== Alpha 3 (2.3.73) ==<br />
* Tagging July 8th (no big merge on that day)<br />
* Release July 13th<br />
<br />
== Alpha 4 (2.3.74) ==<br />
* Tagging August 12th (no big merge on that day)<br />
* Release August 17th<br />
<br />
= Betas =<br />
<br />
== Beta 1 (2.3.81) ==<br />
* Tagging September 7th (no big merge on that day)<br />
* Release September 14th<br />
<br />
== Beta 2 (2.3.82) ==<br />
* Tagging September 30th (no big merge on that day)<br />
** {{CalligraGitCommit|ea57cb68b4c7ea46c5916b2a54084159c8dce1ed}}<br />
* Release October 5th<br />
<br />
== Beta 3 (2.3.83) ==<br />
* Tagging October 21th (no big merge on that day)<br />
** {{CalligraGitCommit|49808577a77267dc7f4cd917588312e4aad59681}}<br />
* Release October 26th<br />
<br />
== Beta 4 (2.3.84) ==<br />
* Tagging November 18th (no big merge on that day)<br />
* Release November 23th<br />
<br />
== Beta 5 (2.3.85) ==<br />
* Tagging December 9th (no big merge on that day)<br />
* Release December 14th<br />
<br />
== Beta 6 (2.3.86) ==<br />
* Tagging January 6th (no big merge on that day)<br />
* Release January 11th<br />
<br />
== Beta 7 (2.3.87) ==<br />
* Tagging January 27th (no big merge on that day)<br />
* Release February 1th<br />
<br />
= Release Candidate =<br />
<br />
There is no realistic way to be certain when the RC1 will be available, hopefully in 2012, we invite you to check [http://quality.calligra.org/] and when the number of tests failure and release critical bugs is near zero, then the time for the RC1 will be very close.<br />
<br />
== RC 1 (2.3.91) ==<br />
* Tagging March 2nd (no big merge on that day), branching into the calligra/2.4 branch will happen at that time<br />
* Release March 7th<br />
<br />
= Final release and maintenance schedule =<br />
<br />
== 2.4.0 ==<br />
Hopefully, it will happen three weeks after the RC, if no major problem is discovered.<br />
<br />
* Tagging April 6th (no big merge on that day)<br />
* Release April 11th<br />
<br />
== 2.4.1 ==<br />
* Tagging April 21th (no big merge on that day)<br />
* Release April 25th<br />
<br />
== 2.4.2 ==<br />
* Tagging May 25th (no big merge on that day)<br />
* Release May 30h<br />
<br />
== 2.4.3 ==<br />
* Tagging June 29th (no big merge on that day)<br />
* Release July 4th</div>Cyrillehttps://community.kde.org/index.php?title=Calligra/Schedules/Feature_Plan&diff=21935Calligra/Schedules/Feature Plan2012-06-19T20:40:50Z<p>Cyrille: </p>
<hr />
<div>See also: [[../Release Plan/]], [[../Quality Control/]]<br />
<br />
This is a list of planned features for Calligra Suite 2.5.<br />
<br />
{{Note|Status: in development, {{Calligra/Stage}}}}<br />
<br />
Legend:<br />
* todo => not started yet<br />
* in-progress => started, but not completed yet<br />
* done => completed<br />
<br />
__TOC__<br />
<br />
== Formula Shape ==<br />
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width:100%;"<br />
|- style="background: #ececec; white-space:nowrap;"<br />
! Status<br />
! Description<br />
! width=120 | branch<br />
! Contact<br />
! target<br />
|-<br />
|FeatureInProgress||Tool to create formula from matlab equations||[http://quickgit.kde.org/index.php?p=calligra.git&a=shortlog&h=refs/heads/formulashape-matlab_tool-cyrille_berger git]||Cyrille Berger||2.5<br />
|-<br />
|}</div>Cyrillehttps://community.kde.org/index.php?title=Calligra/Building&diff=21095Calligra/Building2012-05-26T06:42:20Z<p>Cyrille: </p>
<hr />
<div>These instructions are for Unix and similar operating systems. For Windows, see the [[Calligra/Building_Calligra_on_Windows|building Calligra on Windows]] page.<br />
<br />
= Preparation =<br />
{{Warning|First, to avoid conflicting copies of software, '''make sure you do not have other copy of Calligra or KOffice''' either installed through the package manager of your distribution or installed in any other way. Calligra and KOffice are mutually exclusive!}}<br />
<br />
== Recommended setup ==<br />
Here is recommendation of a directory structure:<br />
;$HOME/kde4/src/:source code<br />
;$HOME/kde4/build/calligra:directory that Calligra will be built in<br />
;$HOME/kde4/inst:directory that Calligra will be installed in<br />
<br />
The ''build'' directory is needed because you cannot (or should not) build Calligra inside the source directory; the source and build directory have to be separated. <br />
<br />
'''Advantages of this setup:'''<br />
*It is possible to have different builds (e.g. with different options out of the same source code)<br />
*[http://techbase.kde.org/Getting_Started/Increased_Productivity_in_KDE4_with_Scripts David Faure's scripts] can be used to make development easier. With those scripts "make" can be typed in the source directory and building will happen in the right (build) directory automatically. <br />
<br />
Also, check the [http://techbase.kde.org/Getting_Started/Build/KDE4 Techbase instructions on setting up a build environment]. That contains some useful scripts and functions.<br />
<br />
== Getting the source code ==<br />
There are two most useful options:<br />
#'''Get the source code for the latest stable version.'''<br />
#'''Get the source code for the current development version.''' Needed to test, check and give feedback about features that is in development and have not been released yet.<br />
<br />
If unsure pick the stable version.<br />
<br />
=== Getting the source code for the latest stable version ===<br />
<br />
The latest stable Calligra version is '''{{Calligra/Stable}}'''.<br />
<br />
It can be downloaded as single archive file from http://download.kde.org/stable/calligra-latest/calligra-{{Calligra/Stable}}.tar.bz2<br />
<br />
=== Get the source code for the development version ===<br />
<br />
<!-- not needed anymore? --><!-- {{Warning|You cannot convert your KOffice SVN checkout to a Calligra git checkout. You will need to get the Calligra source code using git and manually apply your changes again.}} --><br />
<br />
The latest development version of Calligra is '''{{Calligra/Unstable}}''' {{Calligra/Stage}}; developers always refer to it as to '''Master'''. Applications from ''Master'' should always compile and be reasonably stable. Calligra developers never place experimental features there. Once tested and released, ''Master'' becomes the new current stable version {{Calligra/UnstableBranch}}. <br />
<br />
''TODO: Here we should explain local branches, staging and always-release-ready Master, if we have that setup.''<br />
<br />
*'''Option 1: directly from git'''<br />
<br />
To retrieve the source code from Git you have to use the following setup:<br />
<br />
Add the following text to your ~/.gitconfig: <br />
<br />
<nowiki>[url "git://anongit.kde.org/"]</nowiki><br />
insteadOf = kde:<br />
[url "ssh://git@git.kde.org/"]<br />
pushInsteadOf = kde:<br />
<br />
Then execute<br />
<br />
$ git clone kde:calligra<br />
<br />
By using the kde: prefix, read access will automatically happen over Git, and authenticated SSH is only required for pushes.<br />
<br />
Note that pushing your changes will only work if you have a KDE developer identity (https://identity.kde.org/register.php).<br />
<br />
The $HOME/kde4/src/calligra directory will be created regardless of the way how the source code has been downloaded.<br />
<br />
*'''Option 2: download a repository tarball'''<br />
<br />
Go to https://projects.kde.org/projects/calligra/repository. Press the "Tarball" button. Copy the url text and paste it on your command line. It will look like:<br />
<br />
wget -c http://anongit.kde.org/calligra/calligra-latest.tar.gz<br />
<br />
Unpack and cd into directory, then run <br />
<br />
$ ./initrepo.sh<br />
<br />
From now on, you can run<br />
<br />
$ git pull<br />
<br />
to update, or<br />
<br />
$ git rebase origin/master<br />
<br />
if you have local changes<br />
<br />
<br />
*'''Option 3: if beta or rc version was released''', the source code for the latest beta can be found on KDE's ftp [ftp://ftp.kde.org/pub/kde/unstable/calligra-latest/ calligra-latest]. Uncompress the code so that $HOME/kde4/src/calligra is created.<br />
<br />
= Build requirements =<br />
This section provides information about '''hard''' (required) and '''optional''' software packages needed to build the Calligra software.<br />
<br />
== Hard dependencies ==<br />
<br />
{{Note|'''A note for developers:''' to add (or remove) a hard dependency, an explanation of the reason, and possibly a discussion must be posted in advance on calligra-devel@kde.org. The new dependency need to be packaged in the most widely used distributions (Debian, Fedora Core, OpenSuSE, (K)ubuntu). First try to make your new feature optional.}}<br />
<br />
Following are the general must-have dependencies for Calligra:<br />
* Qt 4.6.0 or newer<br />
*kdelibs and kdelibs development files<br />
**the minimal requirement is currently 4.3.0, any 4.3, 4.4 or 4.5 release packaged in your distribution is OK<br />
**On opensuse the development package is called libkde4-devel; on Ubuntu and Debian it is called kdelibs5-dev. (TODO: add info for other distributions)<br />
**Calligra should also build fine with either kdelibs from ''git'' repository (see [http://techbase.kde.org/Getting_Started/Build/KDE4 techbase] for an explanation on how to compile kdelibs from svn), needed for parts of Calligra build with the Mobile Frameworks Profile of the KDE platform (Calligra Words, Calligra Sheets, Calligra Stage, krita)<br />
* kdebase/runtime 4.3 or newer<br />
* cmake 2.6.2 or newer<br />
* lcms 1.18 or newer<br />
* libpng development package (libpng14-devel on opensuse, libpng-dev on Ubuntu/Debian)<br />
** development packages for other libraries may be needed; on ubuntu/Debian these can be installed using 'apt-get build-dep kdelibs5'<br />
<br />
For Calligra Sheets:<br />
* libeigen 2.0<br />
<br />
For Krita:<br />
* libeigen 2.0<br />
* libexiv2 >= 0.16<br />
* libqimageblitz<br />
<br />
For Stage:<br />
* boost<br />
<br />
For Kexi:<br />
* sqlite3 and sqlite3-devel packages (package names can differ on various distributions), version >= 3.7.10<br />
<br />
== Optional dependencies ==<br />
<br />
All optional dependencies are logged at the end of the cmake run, so it is easy to figure out what is missing. The buildsystem also reports what component will not be built because given missing dependency.<br />
<br />
== Simplified installation of dependencies on various distributions ==<br />
{{Note|Most distribution don't ship calligra yet, so you may replace it by "koffice" or "koffice2" in those command lines}}<br />
*'''deb-based distributions (Debian, Ubuntu...):''' All the dependencies used for the packages can be installed by running<br />
apt-get build-dep {packagename}<br />
for instance on Ubuntu:<br />
sudo apt-get build-dep calligra<br />
<br />
*'''OpenSuSE:''' All the dependencies used for building Calligra can be installed by running:<br />
zypper si -d calligra<br />
<br />
*'''Fedora:''' All the dependencies used for building Calligra can be installed by running:<br />
yum-builddep calligra<br />
<br />
*'''ArchLinux:''' All the dependencies used for building Calligra can be installed by running:<br />
<pre style="white-space:-moz-pre-wrap; white-space:-pre-wrap; white-space:-o-pre-wrap; white-space:pre-wrap; word-wrap:break-word">sudo pacman -S kdepimlibs eigen2 freetds kdegraphics-okular libgsf libwpd libwpg libwps libvisio pstoedit glew gsl cmake automoc4 boost libkdcraw libpqxx fftw opengtl lcms2</pre><br />
<br />
*'''Chakra:''' All the dependencies used for building Calligra can be installed by running:<br />
<pre style="white-space:-moz-pre-wrap; white-space:-pre-wrap; white-space:-o-pre-wrap; white-space:pre-wrap; word-wrap:break-word">sudo pacman -S kdelibs kdepimlibs eigen freetds kdegraphics-okular kdeedu-marble xbase libgsf libwpd libwpg libwps libvisio pstoedit glew gsl cmake automoc4 libspnav libqtgtl boost libkdcraw libpqxx fftw opengtl docbook-xsl create-resources lcms2 qrencode libdmtx</pre><br />
<br />
= Build Calligra =<br />
{{Note|It is '''not''' possible to build Calligra in the source directory. Set up your directories as described in the [[#Recommended_setup|Recommended setup]] section above}}<br />
<br />
Type:<br />
mkdir -p $HOME/kde4/build/calligra<br />
mkdir -p $HOME/kde4/inst<br />
cd $HOME/kde4/build/calligra<br />
cmake -DCMAKE_INSTALL_PREFIX=$HOME/kde4/inst $HOME/kde4/src/calligra -DCMAKE_BUILD_TYPE=RelWithDebInfo<br />
<br />
There is a bug in Qt 4.8.0 and 4.8.1 which crashes the textshape quite havily. The bug is fixed in Qt 4.8.2. There is a patch avaliable for Qt and most distributions that ship calligra have included the patch in their QT. See README.PACKAGERS for more information on the topic. If you have applied the patch here is the cmake command you need to use so all gets build.<br />
<br />
cmake -DCMAKE_INSTALL_PREFIX=$HOME/kde4/inst $HOME/kde4/src/calligra -DCMAKE_BUILD_TYPE=RelWithDebInfo -DIHAVEPATCHEDQT=true<br />
<br />
''cmakekde'' tool can be used as explained on [http://techbase.kde.org/Getting_Started/Build/KDE4 the build instructions for KDE4].<br />
<br />
Then type:<br />
make<br />
<br />
Note that on dual-core machines compilation can be '''greatly speed up''' with the -j parameter of the ''make'' program, for example for dual-core:<br />
make -j4<br />
and for quad-core:<br />
make -j8<br />
<br />
Then type this command to install the software:<br />
make install<br />
<br />
'''Debugging options.''' Instead of setting CMAKE_BUILD_TYPE to "RelWithDebInfo" for cmake which gives an optimized Calligra with debug information, useful for bug reporting, one can set CMAKE_BUILD_TYPE to "Debug" to get a slower Calligra but with even more interesting debuggong (backtrace) information. For this replace ''-DCMAKE_BUILD_TYPE=RelWithDebInfo'' in the above cmake command with ''-DCMAKE_BUILD_TYPE=Debug''.<br />
<br />
Please follow the [[Building/Building_Calligra#Running_Calligra_applications|Running Calligra Applications]] instructions before trying to run an application.<br />
<br />
= Updating the already built software =<br />
If the source code has been checked out Subversion from trunk or a branch, it is possible to update the source code with newly added changes and build again. Usually only changing parts will be built, so this operation would be faster than building the source code from scratch.<br />
<br />
Type:<br />
cd $HOME/kde4/src/calligra<br />
git pull --rebase<br />
cd $HOME/kde4/build/calligra<br />
make<br />
make install<br />
<br />
{{Note|''make -j4'' or ''make -j8'' can be used instead of ''make'' to speedup the build on multicore machines}}<br />
<br />
= Build only selected applications from Calligra =<br />
CMake comes with a command-line tool ''ccmake'' that lets you configure build options. You can use it after executing cmake and ''before'' executing make. To use it, go to the build directory and issue the following commands:<br />
cd $HOME/kde4/build/calligra<br />
ccmake .<br />
''ccmake'' is a text user interface application. Simple usage: move the selection using up/don arrow keys. Press Enter to set option ON/OFF (for text options, you enter the text). When you're done with setting the options, press c key to configure the source code to apply your changes. When done, press e key to exit. At any time you can press Ctrl+C to stop the application without saving your changes. Any change is saved to $HOME/kde4/build/calligra/CMakeCache.txt file. You can remove this file to get back to the default configuration (in this case you have to re-execute cmake first.<br />
<br />
For applications that you do '''not''' want to compile, set the corresponding BUILD_{application} variable to "off", replacing {application} by the app's name. For instance, setting ''BUILD_krita'' to ''off'' will prevent Krita from being built.<br />
<br />
Alternatively you can run "-DBUILD_{application}=off" from the cmake command line.<br />
<br />
= Running Calligra applications =<br />
There are two options to make the Calligra applications available for running.<br />
<br />
*'''Option 1: Being able to run Calligra applications from the command line.''' If you have installed Calligra in a different prefix than KDElibs (which was recommended in this document), you have to set the following environment variables:<br />
<br />
export KDEDIRS=/path/to/install:$KDEDIRS<br />
export PATH=/path/to/install/bin:$PATH<br />
export KDEHOME=/path/to/a/config/dir<br />
<br />
And then you need to execute:<br />
kbuildsycoca4<br />
<br />
For example for the recommended directory structure:<br />
export KDEDIRS=$HOME/kde4/inst:$KDEDIRS<br />
export PATH=$HOME/kde4/inst/bin:$PATH<br />
export KDEHOME=$HOME/kde4/.kde<br />
<br />
It is important to set KDEHOME to a directory different of $HOME/.kde, and if the directory does not exist, it will be created automatically.<br />
<br />
*'''Option 2: Being able to run Calligra applications from the menu or by clicking on desktop icons.''' Instead of using ''KDEDIRS'', you can add these lines to $HOME/.kde/share/config/kdeglobals file using text editor:<br />
<br />
[Directories]<br />
prefixes=/path/to/install<br />
<br />
And then you need to execute:<br />
kbuildsycoca4<br />
<br />
The advantage of this is that KDE4 will always look for the services where Calligra is installed. <br />
For example for the recommended directory structure:<br />
<br />
[Directories]<br />
prefixes=$HOME/kde4/inst.<br />
<br />
= Executing unit tests =<br />
To be able to execute unit tests, you need to explicitely enable them in the build configuration. To do so, set the KDE4_BUILD_TESTS variable to "ON", either by issuing the command in the build directory:<br />
<br />
cd $HOME/kde4/build/calligra<br />
cmake -DKDE4_BUILD_TESTS=ON .<br />
<br />
Or you can run <code>ccmake .</code> in the buld directory and set KDE4_BUILD_TESTS to "on".<br />
<br />
You can then run the test by executing:<br />
<br />
make test<br />
<br />
or individually in the tests directories.<br />
<br />
It is recommended to execute<br />
<br />
make install<br />
<br />
before running tests.<br />
<br />
= CMake Build Options =<br />
When you enter your build directory, you can type "ccmake ." to see many build options, e.g. you can turn off compilation of apps you don't want - you can save time when compiling.<br />
<br />
Here is list for Krita related options:<br />
* HAVE_MEMORY_LEAK_TRACKER [On/Off] - You can turn on compilation of the tool in krita which detects memory leak. If you want to help debug Krita memory usage, it is useful. Otherwise you just slow down your Krita.<br />
* HAVE_BACKTRACE_SUPPORT [On/Off] - It is related to the memory leak tool. If you activate, you will be able to see code path which leads to memory leak.<br />
<br />
= Resources =<br />
*[[DeveloperInfo|Useful hints for who wants to hack on Calligra]]<br />
*[http://wiki.opengtl.org/libraries:developers-resources opengtl debugging, or turning it off]<br />
*[http://winkde.org/pub/kde/ports/win32/dashboard/ Status of Calligra build on Windows (msvc 2008, mingw)]<br />
<br />
= Possible issues =<br />
<br />
If you get errors when running an application like:<br />
<br />
krita(8565)/calligra (lib komain) KoPluginLoader::load: Loading plugin "Animation Tool" failed, <br />
"Cannot load library /home/michael/kde4/inst/lib/kde4/kpresentertoolanimation.so: <br />
(/home/michael/kde4/inst/lib/libkopageapp.so.7: undefined symbol:<br />
_ZN28KoShapeContainerDefaultModel3addEP7KoShape)" ( 1 ) <br />
<br />
or crashes when starting an application, then you very likely have a version of Calligra installed through your package manager. '''As emphasized earlier in this document, you can only have one version of Calligra, and you should uninstall your packaged Calligra'''.<br />
<br />
See also:<br />
*[[/Nightly Builds/]]<br />
*[[/Developing With KDevelop/]]<br />
*[[/Developing With QtCreator/]]<br />
*[http://techbase.kde.org/Projects/KDE_on_Windows Pages about compiling KDE software for Windows]<br />
*[http://techbase.kde.org/Getting_Started/Build/KDE4/Mac_OS_X Pages about compiling KDE software for Mac OS X]<br />
*[https://wiki.kubuntu.org/CompilingKoffice2 Community HOWTO dedicated to building for Kubuntu]<br />
*[http://community.kde.org/Sysadmin/GitKdeOrgManual kde's git infrastructure manual]<br />
*[http://techbase.kde.org/Development/Tutorials/Git KDE and Git for developers]<br />
*[http://git.or.cz/course/svn.html git crash course]<br />
*[http://forum.kde.org/viewtopic.php?f=139&t=92880 script for building Calligra (build only krita by default, but easilly configurable)]<br />
*[http://community.kde.org/Calligra/Building_Calligra_on_Windows Bulding Calligra on Windows]<br />
<br />
Note: if you want to build FreOffice using the Nokia Qt SDK, please check out the [http://techbase.kde.org/index.php?title=User:Kumarafaque&oldid=54703 build instructions on techbase].</div>Cyrillehttps://community.kde.org/index.php?title=Calligra/Building&diff=21094Calligra/Building2012-05-26T06:41:22Z<p>Cyrille: </p>
<hr />
<div>These instructions are for Unix and similar operating systems. For Windows, see the [[Calligra/Building_Calligra_on_Windows building Calligra on Windows]] page.<br />
<br />
= Preparation =<br />
{{Warning|First, to avoid conflicting copies of software, '''make sure you do not have other copy of Calligra or KOffice''' either installed through the package manager of your distribution or installed in any other way. Calligra and KOffice are mutually exclusive!}}<br />
<br />
== Recommended setup ==<br />
Here is recommendation of a directory structure:<br />
;$HOME/kde4/src/:source code<br />
;$HOME/kde4/build/calligra:directory that Calligra will be built in<br />
;$HOME/kde4/inst:directory that Calligra will be installed in<br />
<br />
The ''build'' directory is needed because you cannot (or should not) build Calligra inside the source directory; the source and build directory have to be separated. <br />
<br />
'''Advantages of this setup:'''<br />
*It is possible to have different builds (e.g. with different options out of the same source code)<br />
*[http://techbase.kde.org/Getting_Started/Increased_Productivity_in_KDE4_with_Scripts David Faure's scripts] can be used to make development easier. With those scripts "make" can be typed in the source directory and building will happen in the right (build) directory automatically. <br />
<br />
Also, check the [http://techbase.kde.org/Getting_Started/Build/KDE4 Techbase instructions on setting up a build environment]. That contains some useful scripts and functions.<br />
<br />
== Getting the source code ==<br />
There are two most useful options:<br />
#'''Get the source code for the latest stable version.'''<br />
#'''Get the source code for the current development version.''' Needed to test, check and give feedback about features that is in development and have not been released yet.<br />
<br />
If unsure pick the stable version.<br />
<br />
=== Getting the source code for the latest stable version ===<br />
<br />
The latest stable Calligra version is '''{{Calligra/Stable}}'''.<br />
<br />
It can be downloaded as single archive file from http://download.kde.org/stable/calligra-latest/calligra-{{Calligra/Stable}}.tar.bz2<br />
<br />
=== Get the source code for the development version ===<br />
<br />
<!-- not needed anymore? --><!-- {{Warning|You cannot convert your KOffice SVN checkout to a Calligra git checkout. You will need to get the Calligra source code using git and manually apply your changes again.}} --><br />
<br />
The latest development version of Calligra is '''{{Calligra/Unstable}}''' {{Calligra/Stage}}; developers always refer to it as to '''Master'''. Applications from ''Master'' should always compile and be reasonably stable. Calligra developers never place experimental features there. Once tested and released, ''Master'' becomes the new current stable version {{Calligra/UnstableBranch}}. <br />
<br />
''TODO: Here we should explain local branches, staging and always-release-ready Master, if we have that setup.''<br />
<br />
*'''Option 1: directly from git'''<br />
<br />
To retrieve the source code from Git you have to use the following setup:<br />
<br />
Add the following text to your ~/.gitconfig: <br />
<br />
<nowiki>[url "git://anongit.kde.org/"]</nowiki><br />
insteadOf = kde:<br />
[url "ssh://git@git.kde.org/"]<br />
pushInsteadOf = kde:<br />
<br />
Then execute<br />
<br />
$ git clone kde:calligra<br />
<br />
By using the kde: prefix, read access will automatically happen over Git, and authenticated SSH is only required for pushes.<br />
<br />
Note that pushing your changes will only work if you have a KDE developer identity (https://identity.kde.org/register.php).<br />
<br />
The $HOME/kde4/src/calligra directory will be created regardless of the way how the source code has been downloaded.<br />
<br />
*'''Option 2: download a repository tarball'''<br />
<br />
Go to https://projects.kde.org/projects/calligra/repository. Press the "Tarball" button. Copy the url text and paste it on your command line. It will look like:<br />
<br />
wget -c http://anongit.kde.org/calligra/calligra-latest.tar.gz<br />
<br />
Unpack and cd into directory, then run <br />
<br />
$ ./initrepo.sh<br />
<br />
From now on, you can run<br />
<br />
$ git pull<br />
<br />
to update, or<br />
<br />
$ git rebase origin/master<br />
<br />
if you have local changes<br />
<br />
<br />
*'''Option 3: if beta or rc version was released''', the source code for the latest beta can be found on KDE's ftp [ftp://ftp.kde.org/pub/kde/unstable/calligra-latest/ calligra-latest]. Uncompress the code so that $HOME/kde4/src/calligra is created.<br />
<br />
= Build requirements =<br />
This section provides information about '''hard''' (required) and '''optional''' software packages needed to build the Calligra software.<br />
<br />
== Hard dependencies ==<br />
<br />
{{Note|'''A note for developers:''' to add (or remove) a hard dependency, an explanation of the reason, and possibly a discussion must be posted in advance on calligra-devel@kde.org. The new dependency need to be packaged in the most widely used distributions (Debian, Fedora Core, OpenSuSE, (K)ubuntu). First try to make your new feature optional.}}<br />
<br />
Following are the general must-have dependencies for Calligra:<br />
* Qt 4.6.0 or newer<br />
*kdelibs and kdelibs development files<br />
**the minimal requirement is currently 4.3.0, any 4.3, 4.4 or 4.5 release packaged in your distribution is OK<br />
**On opensuse the development package is called libkde4-devel; on Ubuntu and Debian it is called kdelibs5-dev. (TODO: add info for other distributions)<br />
**Calligra should also build fine with either kdelibs from ''git'' repository (see [http://techbase.kde.org/Getting_Started/Build/KDE4 techbase] for an explanation on how to compile kdelibs from svn), needed for parts of Calligra build with the Mobile Frameworks Profile of the KDE platform (Calligra Words, Calligra Sheets, Calligra Stage, krita)<br />
* kdebase/runtime 4.3 or newer<br />
* cmake 2.6.2 or newer<br />
* lcms 1.18 or newer<br />
* libpng development package (libpng14-devel on opensuse, libpng-dev on Ubuntu/Debian)<br />
** development packages for other libraries may be needed; on ubuntu/Debian these can be installed using 'apt-get build-dep kdelibs5'<br />
<br />
For Calligra Sheets:<br />
* libeigen 2.0<br />
<br />
For Krita:<br />
* libeigen 2.0<br />
* libexiv2 >= 0.16<br />
* libqimageblitz<br />
<br />
For Stage:<br />
* boost<br />
<br />
For Kexi:<br />
* sqlite3 and sqlite3-devel packages (package names can differ on various distributions), version >= 3.7.10<br />
<br />
== Optional dependencies ==<br />
<br />
All optional dependencies are logged at the end of the cmake run, so it is easy to figure out what is missing. The buildsystem also reports what component will not be built because given missing dependency.<br />
<br />
== Simplified installation of dependencies on various distributions ==<br />
{{Note|Most distribution don't ship calligra yet, so you may replace it by "koffice" or "koffice2" in those command lines}}<br />
*'''deb-based distributions (Debian, Ubuntu...):''' All the dependencies used for the packages can be installed by running<br />
apt-get build-dep {packagename}<br />
for instance on Ubuntu:<br />
sudo apt-get build-dep calligra<br />
<br />
*'''OpenSuSE:''' All the dependencies used for building Calligra can be installed by running:<br />
zypper si -d calligra<br />
<br />
*'''Fedora:''' All the dependencies used for building Calligra can be installed by running:<br />
yum-builddep calligra<br />
<br />
*'''ArchLinux:''' All the dependencies used for building Calligra can be installed by running:<br />
<pre style="white-space:-moz-pre-wrap; white-space:-pre-wrap; white-space:-o-pre-wrap; white-space:pre-wrap; word-wrap:break-word">sudo pacman -S kdepimlibs eigen2 freetds kdegraphics-okular libgsf libwpd libwpg libwps libvisio pstoedit glew gsl cmake automoc4 boost libkdcraw libpqxx fftw opengtl lcms2</pre><br />
<br />
*'''Chakra:''' All the dependencies used for building Calligra can be installed by running:<br />
<pre style="white-space:-moz-pre-wrap; white-space:-pre-wrap; white-space:-o-pre-wrap; white-space:pre-wrap; word-wrap:break-word">sudo pacman -S kdelibs kdepimlibs eigen freetds kdegraphics-okular kdeedu-marble xbase libgsf libwpd libwpg libwps libvisio pstoedit glew gsl cmake automoc4 libspnav libqtgtl boost libkdcraw libpqxx fftw opengtl docbook-xsl create-resources lcms2 qrencode libdmtx</pre><br />
<br />
= Build Calligra =<br />
{{Note|It is '''not''' possible to build Calligra in the source directory. Set up your directories as described in the [[#Recommended_setup|Recommended setup]] section above}}<br />
<br />
Type:<br />
mkdir -p $HOME/kde4/build/calligra<br />
mkdir -p $HOME/kde4/inst<br />
cd $HOME/kde4/build/calligra<br />
cmake -DCMAKE_INSTALL_PREFIX=$HOME/kde4/inst $HOME/kde4/src/calligra -DCMAKE_BUILD_TYPE=RelWithDebInfo<br />
<br />
There is a bug in Qt 4.8.0 and 4.8.1 which crashes the textshape quite havily. The bug is fixed in Qt 4.8.2. There is a patch avaliable for Qt and most distributions that ship calligra have included the patch in their QT. See README.PACKAGERS for more information on the topic. If you have applied the patch here is the cmake command you need to use so all gets build.<br />
<br />
cmake -DCMAKE_INSTALL_PREFIX=$HOME/kde4/inst $HOME/kde4/src/calligra -DCMAKE_BUILD_TYPE=RelWithDebInfo -DIHAVEPATCHEDQT=true<br />
<br />
''cmakekde'' tool can be used as explained on [http://techbase.kde.org/Getting_Started/Build/KDE4 the build instructions for KDE4].<br />
<br />
Then type:<br />
make<br />
<br />
Note that on dual-core machines compilation can be '''greatly speed up''' with the -j parameter of the ''make'' program, for example for dual-core:<br />
make -j4<br />
and for quad-core:<br />
make -j8<br />
<br />
Then type this command to install the software:<br />
make install<br />
<br />
'''Debugging options.''' Instead of setting CMAKE_BUILD_TYPE to "RelWithDebInfo" for cmake which gives an optimized Calligra with debug information, useful for bug reporting, one can set CMAKE_BUILD_TYPE to "Debug" to get a slower Calligra but with even more interesting debuggong (backtrace) information. For this replace ''-DCMAKE_BUILD_TYPE=RelWithDebInfo'' in the above cmake command with ''-DCMAKE_BUILD_TYPE=Debug''.<br />
<br />
Please follow the [[Building/Building_Calligra#Running_Calligra_applications|Running Calligra Applications]] instructions before trying to run an application.<br />
<br />
= Updating the already built software =<br />
If the source code has been checked out Subversion from trunk or a branch, it is possible to update the source code with newly added changes and build again. Usually only changing parts will be built, so this operation would be faster than building the source code from scratch.<br />
<br />
Type:<br />
cd $HOME/kde4/src/calligra<br />
git pull --rebase<br />
cd $HOME/kde4/build/calligra<br />
make<br />
make install<br />
<br />
{{Note|''make -j4'' or ''make -j8'' can be used instead of ''make'' to speedup the build on multicore machines}}<br />
<br />
= Build only selected applications from Calligra =<br />
CMake comes with a command-line tool ''ccmake'' that lets you configure build options. You can use it after executing cmake and ''before'' executing make. To use it, go to the build directory and issue the following commands:<br />
cd $HOME/kde4/build/calligra<br />
ccmake .<br />
''ccmake'' is a text user interface application. Simple usage: move the selection using up/don arrow keys. Press Enter to set option ON/OFF (for text options, you enter the text). When you're done with setting the options, press c key to configure the source code to apply your changes. When done, press e key to exit. At any time you can press Ctrl+C to stop the application without saving your changes. Any change is saved to $HOME/kde4/build/calligra/CMakeCache.txt file. You can remove this file to get back to the default configuration (in this case you have to re-execute cmake first.<br />
<br />
For applications that you do '''not''' want to compile, set the corresponding BUILD_{application} variable to "off", replacing {application} by the app's name. For instance, setting ''BUILD_krita'' to ''off'' will prevent Krita from being built.<br />
<br />
Alternatively you can run "-DBUILD_{application}=off" from the cmake command line.<br />
<br />
= Running Calligra applications =<br />
There are two options to make the Calligra applications available for running.<br />
<br />
*'''Option 1: Being able to run Calligra applications from the command line.''' If you have installed Calligra in a different prefix than KDElibs (which was recommended in this document), you have to set the following environment variables:<br />
<br />
export KDEDIRS=/path/to/install:$KDEDIRS<br />
export PATH=/path/to/install/bin:$PATH<br />
export KDEHOME=/path/to/a/config/dir<br />
<br />
And then you need to execute:<br />
kbuildsycoca4<br />
<br />
For example for the recommended directory structure:<br />
export KDEDIRS=$HOME/kde4/inst:$KDEDIRS<br />
export PATH=$HOME/kde4/inst/bin:$PATH<br />
export KDEHOME=$HOME/kde4/.kde<br />
<br />
It is important to set KDEHOME to a directory different of $HOME/.kde, and if the directory does not exist, it will be created automatically.<br />
<br />
*'''Option 2: Being able to run Calligra applications from the menu or by clicking on desktop icons.''' Instead of using ''KDEDIRS'', you can add these lines to $HOME/.kde/share/config/kdeglobals file using text editor:<br />
<br />
[Directories]<br />
prefixes=/path/to/install<br />
<br />
And then you need to execute:<br />
kbuildsycoca4<br />
<br />
The advantage of this is that KDE4 will always look for the services where Calligra is installed. <br />
For example for the recommended directory structure:<br />
<br />
[Directories]<br />
prefixes=$HOME/kde4/inst.<br />
<br />
= Executing unit tests =<br />
To be able to execute unit tests, you need to explicitely enable them in the build configuration. To do so, set the KDE4_BUILD_TESTS variable to "ON", either by issuing the command in the build directory:<br />
<br />
cd $HOME/kde4/build/calligra<br />
cmake -DKDE4_BUILD_TESTS=ON .<br />
<br />
Or you can run <code>ccmake .</code> in the buld directory and set KDE4_BUILD_TESTS to "on".<br />
<br />
You can then run the test by executing:<br />
<br />
make test<br />
<br />
or individually in the tests directories.<br />
<br />
It is recommended to execute<br />
<br />
make install<br />
<br />
before running tests.<br />
<br />
= CMake Build Options =<br />
When you enter your build directory, you can type "ccmake ." to see many build options, e.g. you can turn off compilation of apps you don't want - you can save time when compiling.<br />
<br />
Here is list for Krita related options:<br />
* HAVE_MEMORY_LEAK_TRACKER [On/Off] - You can turn on compilation of the tool in krita which detects memory leak. If you want to help debug Krita memory usage, it is useful. Otherwise you just slow down your Krita.<br />
* HAVE_BACKTRACE_SUPPORT [On/Off] - It is related to the memory leak tool. If you activate, you will be able to see code path which leads to memory leak.<br />
<br />
= Resources =<br />
*[[DeveloperInfo|Useful hints for who wants to hack on Calligra]]<br />
*[http://wiki.opengtl.org/libraries:developers-resources opengtl debugging, or turning it off]<br />
*[http://winkde.org/pub/kde/ports/win32/dashboard/ Status of Calligra build on Windows (msvc 2008, mingw)]<br />
<br />
= Possible issues =<br />
<br />
If you get errors when running an application like:<br />
<br />
krita(8565)/calligra (lib komain) KoPluginLoader::load: Loading plugin "Animation Tool" failed, <br />
"Cannot load library /home/michael/kde4/inst/lib/kde4/kpresentertoolanimation.so: <br />
(/home/michael/kde4/inst/lib/libkopageapp.so.7: undefined symbol:<br />
_ZN28KoShapeContainerDefaultModel3addEP7KoShape)" ( 1 ) <br />
<br />
or crashes when starting an application, then you very likely have a version of Calligra installed through your package manager. '''As emphasized earlier in this document, you can only have one version of Calligra, and you should uninstall your packaged Calligra'''.<br />
<br />
See also:<br />
*[[/Nightly Builds/]]<br />
*[[/Developing With KDevelop/]]<br />
*[[/Developing With QtCreator/]]<br />
*[http://techbase.kde.org/Projects/KDE_on_Windows Pages about compiling KDE software for Windows]<br />
*[http://techbase.kde.org/Getting_Started/Build/KDE4/Mac_OS_X Pages about compiling KDE software for Mac OS X]<br />
*[https://wiki.kubuntu.org/CompilingKoffice2 Community HOWTO dedicated to building for Kubuntu]<br />
*[http://community.kde.org/Sysadmin/GitKdeOrgManual kde's git infrastructure manual]<br />
*[http://techbase.kde.org/Development/Tutorials/Git KDE and Git for developers]<br />
*[http://git.or.cz/course/svn.html git crash course]<br />
*[http://forum.kde.org/viewtopic.php?f=139&t=92880 script for building Calligra (build only krita by default, but easilly configurable)]<br />
*[http://community.kde.org/Calligra/Building_Calligra_on_Windows Bulding Calligra on Windows]<br />
<br />
Note: if you want to build FreOffice using the Nokia Qt SDK, please check out the [http://techbase.kde.org/index.php?title=User:Kumarafaque&oldid=54703 build instructions on techbase].</div>Cyrillehttps://community.kde.org/index.php?title=Calligra/Building_Calligra_on_Windows&diff=21093Calligra/Building Calligra on Windows2012-05-26T06:40:11Z<p>Cyrille: </p>
<hr />
<div>{{Note|''These instructions are a work in progress, being based on the Linux Build instructions, there are some sections which need updating.''}}<br />
<br />
These instructions are for the Windows operating systems.<br />
<br />
See also:<br />
*Nightly Builds <!-- [[/Nightly Builds/]] --><br />
*Developing With...<!--[[/Developing With QtCreator/]]--><br />
*[http://techbase.kde.org/Projects/KDE_on_Windows Pages about compiling KDE software for Windows]<br />
*[http://community.kde.org/Sysadmin/GitKdeOrgManual kde's git infrastructure manual]<br />
*[http://techbase.kde.org/Development/Tutorials/Git KDE and Git for developers]<br />
*[http://git.or.cz/course/svn.html git crash course]<br />
<!--* Scripts? [http://forum.kde.org/viewtopic.php?f=139&t=92880 script for building Calligra (build only krita by default, but easilly configurable)]--><br />
<br />
<!--<br />
Note: if you want to build FreOffice using the Nokia Qt SDK, please check out the [http://techbase.kde.org/index.php?title=User:Kumarafaque&oldid=54703 build instructions on techbase].<br />
--><br />
<br />
Note: the 4.7 branch of emerge is no longer usable. Use the 4.8 or master branch. Those branches need Python 3.x. You also need 7za.exe instead of 7z.exe in the path.<br />
<br />
= Preparation =<br />
Before you begin, you will need to have a minimal set of software installed on your PC:<br />
* Python 2.7 (x86, not 64-bit)<br />
* Git<br />
* Microsoft Windows SDK 7.1 (Windows 7 with .NET Framework 4)<br />
* KDE on Windows' ''emerge'' tool, kde-4.8 branch<br />
<br />
First you will need to make sure that you have Git installed on your PC in order to be able to clone the KDE Windows emerge repository. Be sure to switch to the kde-4.7 branch. <br />
git clone git://anongit.kde.org/emerge.git<br />
cd emerge<br />
git checkout kde-4.8<br />
mkdir ..\etc<br />
copy kdesettings-example.bat ..\etc\kdesettings.bat<br />
<br />
You will need to make the following changes to etc/kdesettings.bat:<br />
* Update KDEROOT<br />
* Set KDECOMPILER=msvc2010<br />
* Update WINDOWSSDKDIR to point to your installation of the Windows SDK<br />
* Set EMERGE_USE_SHORT_PATH=1<br />
* Set PYTHONPATH (default assumes in Program Files)<br />
* Set EMERGE_SOURCEONLY=True<br />
<br />
<br />
One you have done this, you should navigate to the emerge directory and call<br />
kdeenv<br />
<br />
This sets up the development environment that you will need to use in order to build the KDE libraries, their dependencies and Calligra.<br />
<br />
In order to install the bare minimum set up of KDE libraries, you will need to run a series of calls to emerge, which will take some time:<br />
emerge qt<br />
emerge kdelib<br />
emerge kde-runtime<br />
<br />
Users familiar with development on Linux platforms may also wish to install another couple of libraries<br />
emerge coreutils<br />
emerge grep<br />
<br />
There are some additional optional libraries that can be used by Calligra, again ''emerge'' is used to install them:<br />
emerge lcms2<br />
emerge eigen2<br />
emerge boost<br />
emerge okular<br />
emerge exiv2<br />
emerge soprano<br />
emerge librdf-src<br />
<br />
Depending on your requirements, there are some additional libraries that may be useful<br />
emerge libwpd // Wordperfect document support <br />
emerge libwpg // Wordperfect graphics support<br />
<br />
<br />
== Recommended setup ==<br />
Here is recommendation of a directory structure:<br />
;<nowiki>C:\kderoot</nowiki>:KDE on Windows root directory<br />
<br />
From your %USERPROFILE% directory (assuming you will be the only local user)<br />
;kde4\src\:source code<br />
;kde4\build\calligra:directory that Calligra will be built in<br />
;kde4\inst\:directory that Calligra will be installed in<br />
<br />
The ''build'' directory is needed because you cannot build Calligra inside the source directory; the source and build directory have to be separated.<br />
<br />
You can create this structure by opening a command prompt (cmd.exe) and typing:<br />
cd %USERPROFILE% <br />
mkdir kde4<br />
mkdir kde4\build<br />
mkdir kde4\build\calligra<br />
mkdir kde4\inst<br />
mkdir kde4\src<br />
<br />
== Getting the source code ==<br />
As Windows support is still being improved, it is recommended that you use the development version. If you require stability, it is recommended that you take advantage of the nightly builds.<br />
<br />
The latest development version of Calligra is '''{{Calligra/Unstable}}''' {{Calligra/Stage}}; developers always refer to it as to '''Master'''. Once tested and released, it will become the new current stable version {{Calligra/UnstableBranch}}.<br />
<br />
<br />
To retrieve the source code from Git you have to use the following setup:<br />
<br />
Add the following text to %USERPROFILE%\.gitconfig: <br />
<br />
<nowiki>[url "git://anongit.kde.org/"]</nowiki><br />
insteadOf = kde:<br />
[url "ssh://git@git.kde.org/"]<br />
pushInsteadOf = kde:<br />
[core]<br />
autocrlf=false<br />
<br />
Then execute<br />
<br />
$ git clone kde:calligra<br />
<br />
By using the kde: prefix, read access will automatically happen over Git, and authenticated SSH is only required for pushes.<br />
<br />
Note that pushing your changes will only work if you have a KDE developer identity (https://identity.kde.org/register.php).<br />
<br />
This will create a 'calligra' subdirectory with the complete source tree.<br />
<br />
= Build Calligra =<br />
From your home directory, navigate to the build\calliga subdirectory and execute cmake to configure the project for building with the following lines:<br />
cd kde4\build\calligra<br />
cmake -DCMAKE_INSTALL_PREFIX=<nowiki>..\..\inst</nowiki> <nowiki>..\..\src\calligra</nowiki> -DCMAKE_BUILD_TYPE=%EMERGE_BUILDTYPE% -DTINY=off -DBUILD_active=off -DBUILD_mobile=off -DBUILD_kexi=off<br />
<br />
Here we are telling cmake that:<br />
* We want to install Calligra into ~/kde4/inst<br />
* The source files are located at ~/kde4/src/calligra<br />
* We are building to the same type (RelWithDebInfo / Debug) as used to build the Qt and KDE libraries, by reading the value of ''EMERGE_BUILDTYPE''<br />
* We are selectively disabling some portions of the build with the -DBUILD_xxxx=on|off commands. 'active' and 'mobile' are not applicable to the desktop build, while flow and kexi (at the time of writing) were still undergoing testing on the platform.<br />
<br />
<br />
{{Note|You can selectively build applications by using the <nowiki>-DBUILD_application=off</nowiki> command to disable building of those you do not want. If you have a full cmake install, you can use the ''<nowiki>cmake-gui</nowiki>'' application to let you make changes to the configuration.}}<br />
<br />
Then, to build Calligra, type:<br />
jom<br />
<br />
{{Note|''jom'' is a multi-core port of ''nmake''. By default it uses all of the cores on the machine, buy you can specify the number to use with the ''-j#'' parameter. e.g. ''jom -j2'' would force it to use 2 processes}}<br />
<br />
<br />
This will take a while, once it has completed, type this command to install the software:<br />
jom install<br />
<br />
<!-- Including "build debug" info<br />
'''Debugging options.''' Instead of setting CMAKE_BUILD_TYPE to "RelWithDebInfo" for cmake which gives an optimized Calligra with debug information, useful for bug reporting, one can set CMAKE_BUILD_TYPE to "Debug" to get a slower Calligra but with even more interesting debuggong (backtrace) information. For this replace ''-DCMAKE_BUILD_TYPE=RelWithDebInfo'' in the above cmake command with ''-DCMAKE_BUILD_TYPE=Debug''.<br />
--><br />
<br />
Please follow the [[Building/Building_Calligra_on_Windows#Running_Calligra_applications|Running Calligra Applications]] instructions before trying to run an application.<br />
<br />
= Running Calligra applications =<br />
There are two options to make the Calligra applications available for running.<br />
<br />
*'''Option 1: Being able to run Calligra applications from the command line.''' If you have installed Calligra in a different prefix than KDElibs (which was recommended in this document), you may want to set the following environment variable: <br />
<br />
set KDEDIRS=\path\to\install;%KDEDIRS%<br />
set PATH=\path\to\install\bin;%PATH%<br />
set KDEHOME=\path\to\a\config\dir<br />
<br />
And then you need to execute:<br />
kbuildsycoca4<br />
<br />
For example for the recommended directory structure:<br />
set KDEDIRS=%USERPROFILE%\kde4\inst;%KDEDIRS%<br />
set PATH=%USERPROFILE%\kde4\inst\bin;%PATH%<br />
set KDEHOME=%USERPROFILE%\kde4\.kde<br />
<br />
Here we are setting KDEHOME to be saved <br />
<br />
*'''Option 2: Being able to run Calligra applications from the menu or by clicking on desktop icons.''' Instead of using ''KDEDIRS'', you can add these lines to $HOME/.kde/share/config/kdeglobals file using text editor:<br />
<br />
[Directories]<br />
prefixes=%USERPROFILE%\kde4\inst<br />
<br />
And then you need to execute:<br />
update-mime-database %KDEROOT%\share\mime<br />
kbuildsycoca4 --noincremental<br />
<br />
The advantage of this is that KDE4 will always look for the services where Calligra is installed.<br />
<br />
<br />
= Updating the already built software =<br />
If the source code has been checked out, it is possible to update the source code with newly added changes and build again. Usually only changing parts will be built, so this operation would be faster than building the source code from scratch.<br />
<br />
Type:<br />
cd <nowiki>%USERPROFILE%\kde4\src\calligra</nowiki><br />
git pull<br />
cd <nowiki>%USERPROFILE%\kde4\build\calligra</nowiki><br />
jom<br />
jom install<br />
<br />
<!--<br />
= Build only selected applications from Calligra =<br />
<br />
CMake comes with a command-line tool ''ccmake'' that lets you configure build options. You can use it after executing cmake and ''before'' executing make. To use it, go to the build directory and issue the following commands:<br />
cd $HOME/kde4/build/calligra<br />
ccmake .<br />
''ccmake'' is a text user interface application. Simple usage: move the selection using up/don arrow keys. Press Enter to set option ON/OFF (for text options, you enter the text). When you're done with setting the options, press c key to configure the source code to apply your changes. When done, press e key to exit. At any time you can press Ctrl+C to stop the application without saving your changes. Any change is saved to $HOME/kde4/build/calligra/CMakeCache.txt file. You can remove this file to get back to the default configuration (in this case you have to re-execute cmake first.<br />
<br />
For applications that you do '''not''' want to compile, set the corresponding BUILD_{application} variable to "off", replacing {application} by the app's name. For instance, setting ''BUILD_krita'' to ''off'' will prevent Krita from being built.<br />
<br />
You can edit the cmake command line, with "-DBUILD_{application}=off" from the cmake command line.<br />
--><br />
<br />
= Executing unit tests =<br />
To be able to execute unit tests, you need to explicitely enable them in the build configuration. To do so, set the KDE4_BUILD_TESTS variable to "ON", either by issuing the command in the build directory:<br />
<br />
cd $HOME/kde4/build/calligra<br />
cmake -DKDE4_BUILD_TESTS=ON .<br />
<br />
Or you can run cmake-gui in the buld directory and set KDE4_BUILD_TESTS to "on".<br />
<br />
It is then recommended that before running the tests, you first execute<br />
<br />
jom install<br />
<br />
You can then run the test by executing:<br />
<br />
jom test<br />
<br />
or individually in the tests directories.<br />
<br />
= CMake Build Options =<br />
When you enter your build directory, you can type "cmake-gui ." to see many build options, e.g. you can turn off compilation of apps you don't want - you can save time when compiling.<br />
<br />
Here is list for Krita related options:<br />
* HAVE_MEMORY_LEAK_TRACKER [On/Off] - You can turn on compilation of the tool in krita which detects memory leak. If you want to help debug Krita memory usage, it is useful. Otherwise you just slow down your Krita.<br />
* HAVE_BACKTRACE_SUPPORT [On/Off] - It is related to the memory leak tool. If you activate, you will be able to see code path which leads to memory leak.<br />
<br />
= Resources =<br />
*[[DeveloperInfo|Useful hints for who wants to hack on Calligra]]<br />
*[http://wiki.opengtl.org/libraries:developers-resources opengtl debugging, or turning it off]<br />
*[http://winkde.org/pub/kde/ports/win32/dashboard/ Status of Calligra build on Windows (msvc 2008, mingw)]<br />
<br />
= Possible issues =<br />
<br />
== Calligra apps don't start ==<br />
<br />
If the Calligra applications do not start properly, or you see the window flash up then disappear, then you need to check the [[Building/Building_Calligra_on_Windows#Running_Calligra_applications|Running Calligra Applications]] section earlier and make sure you've run update-mime-database and kbuildsycoca4.<br />
<br />
You can get some additional insight by installing DebugView, which will let you see warnings and error messages reported by the programs.<br />
This is available on [http://technet.microsoft.com/en-us/sysinternals/bb896647 Microsoft Technet]<br />
<br />
<!--<br />
If you get errors when running an application like:<br />
<br />
krita(8565)/calligra (lib komain) KoPluginLoader::load: Loading plugin "Animation Tool" failed, <br />
"Cannot load library /home/michael/kde4/inst/lib/kde4/kpresentertoolanimation.so: <br />
(/home/michael/kde4/inst/lib/libkopageapp.so.7: undefined symbol:<br />
_ZN28KoShapeContainerDefaultModel3addEP7KoShape)" ( 1 ) <br />
<br />
or crashes when starting an application, then you very likely have a version of Calligra installed through your package manager. '''As emphasized earlier in this document, you can only have one version of Calligra, and you should uninstall your packaged Calligra'''.<br />
--><br />
<br />
<br />
The sources for the WIX-based installer for Calligra on Windows are at<br />
<br />
https://gitorious.org/calligra-installer-for-windows</div>Cyrillehttps://community.kde.org/index.php?title=Calligra/Schedules/Feature_Plan&diff=20172Calligra/Schedules/Feature Plan2012-04-24T18:00:19Z<p>Cyrille: </p>
<hr />
<div>See also: [[../Release Plan/]], [[../Quality Control/]]<br />
<br />
This is a list of planned features for Calligra Suite 2.5.<br />
<br />
{{Note|Status: in development, {{Calligra/Stage}}}}<br />
<br />
Legend:<br />
* todo => not started yet<br />
* in-progress => started, but not completed yet<br />
* done => completed<br />
<br />
__TOC__<br />
<br />
== Formula Shape ==<br />
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width:100%;"<br />
|- style="background: #ececec; white-space:nowrap;"<br />
! Status<br />
! Description<br />
! width=120 | branch<br />
! Contact<br />
! target<br />
|-<br />
|FeatureInProgress||Tool to create formula from matlab equations||[http://quickgit.kde.org/index.php?p=calligra.git&a=shortlog&h=refs/heads/formulashape-matlab_tool-cyrille_berger formulashape-matlab_tool-cyrille_berger]||Cyrille Berger||2.5<br />
|-<br />
|}</div>Cyrillehttps://community.kde.org/index.php?title=Calligra/Schedules/Feature_Plan&diff=20170Calligra/Schedules/Feature Plan2012-04-24T17:53:05Z<p>Cyrille: /* Formula Shape */</p>
<hr />
<div>See also: [[../Release Plan/]], [[../Quality Control/]]<br />
<br />
This is a list of planned features for Calligra Suite 2.5.<br />
<br />
{{Note|Status: in development, {{Calligra/Stage}}}}<br />
<br />
Legend:<br />
* todo => not started yet<br />
* in-progress => started, but not completed yet<br />
* done => completed<br />
<br />
__TOC__<br />
<br />
== Formula Shape ==<br />
{| class="sortable" border="1" cellpadding="5" cellspacing="0" style="border: gray solid 1px; border-collapse: collapse; text-align: left; width:100%;"<br />
|- style="background: #ececec; white-space:nowrap;"<br />
! Status<br />
! Description<br />
! width=120 | branch<br />
! Contact<br />
! target<br />
|-<br />
{{FeatureInProgress|Tool to create formula from matlab equations|[http://quickgit.kde.org/index.php?p=calligra.git&a=shortlog&h=refs/heads/formulashape-matlab_tool-cyrille_berger formulashape-matlab_tool-cyrille_berge]|Cyrille Berger|2.5}}<br />
|}</div>Cyrille