Jenkins-kde-ci: calligra master kf5-qt5 » Linux,gcc - Build # 103 - Still Unstable!

GENERAL INFO BUILD UNSTABLE Build URL: https://build.kde.org/job/calligra%20master%20kf5-qt5/PLATFORM=Linux,compiler=gcc/103/ Project: PLATFORM=Linux,compiler=gcc Date of build: Tue, 20 Sep 2016 18:15:33 + Build duration: 2 hr 54 min CHANGE SET Revision a40aec1add461332916ddedd41e454ba97e17

Jenkins-kde-ci: calligra master kf5-qt5 » Linux,gcc - Build # 102 - Still Unstable!

GENERAL INFO BUILD UNSTABLE Build URL: https://build.kde.org/job/calligra%20master%20kf5-qt5/PLATFORM=Linux,compiler=gcc/102/ Project: PLATFORM=Linux,compiler=gcc Date of build: Tue, 20 Sep 2016 14:50:54 + Build duration: 2 hr 24 min CHANGE SET Revision f0b2b969707b37350d13293020d9dc3285069

[Differential] [Closed] D364: Move KoFindToolbar to Words, it's only user

This revision was automatically updated to reflect the committed changes. Closed by commit rCALLIGRAd628f85b24b3: Move KoFindToolbar to Words, it's only user (authored by kossebau). CHANGED PRIOR TO COMMIT https://phabricator.kde.org/D364?vs=895&id=6836#toc REPOSITORY rCALLIGRA Calligra CHA

Kexi 3.0.0 Beta 1 and libraries released

Dear All, Kexi 3.0.0 Beta 1 and related libraries has been released for testing and packaging. Downloads & change logs: https://community.kde.org/Kexi/Releases/3#3.0.0_Beta_1 Report bug or wishes: https://community.kde.org/Calligra/File_a

[Maniphest] [Closed] T3755: Kexi API docs missing in the calligra section

staniek closed this task as "Resolved". staniek claimed this task. staniek added a comment. @bcooksley Yep, generalizing the scripts is not practical or safe. Thanks. TASK DETAIL https://phabricator.kde.org/T3755 EMAIL PREFERENCES https://phabricator.kde.org/settings/panel/emailpreference

[Maniphest] [Commented On] T3755: Kexi API docs missing in the calligra section

bcooksley added a comment. At this point i'd suggest simply going ahead with the short term pain, long term gain method of adopting KApiDox for building your API Documentation, as the legacy scripts and mechanisms are fragile - I certainly don't want to touch them. TASK DETAIL https://pha

[Maniphest] [Commented On] T3755: Kexi API docs missing in the calligra section

staniek added a comment. In https://phabricator.kde.org/T3755#55509, @kossebau wrote: > > @staniek I would recommend to move src/Mainpage.dox to the toplevel dir (and adopting the EXCLUDE entry). Because right now this results in the additional subsection "Kexi" on https:/

Re: [Maniphest] [Commented On] T3755: Kexi API docs missing in the calligra section

On 20 September 2016 at 12:08, Adam Pigg wrote: > Are the Kexi plugins libs not part of a public Kexi API? > ​ > > ​Public within Kexi, yes. Public so that independent vendors distribute own extensions? Not quite, that's not maintained. To save the overhead we're distributing all plugins that de

[Maniphest] [Commented On] T3755: Kexi API docs missing in the calligra section

kossebau added a comment. In https://phabricator.kde.org/T3755#55412, @staniek wrote: > Are we sure? > > For example KDevelop has kdevplatform https://api.kde.org/extragear-api/kdevelop-apidocs/index.html, just released yesterday, but Calligra does not: > > https://api.kde.org/bu

Re: state of release and release plan

Kreport has dropped kross for qjsengine, as part of being wrong, so it would be preferable to convert python to js On Sat, 2 Jul 2016, 19:37 Dag, wrote: > Preliminary input for Plan. Note that I have not even open all views > much less tried much functionality, so there may be (a lot) more... >

Re: [Maniphest] [Commented On] T3755: Kexi API docs missing in the calligra section

Are the Kexi plugins libs not part of a public Kexi API? Also, the Kexi specific parts of the report plugin scripting side should be documented as user api On Tue, 20 Sep 2016, 09:37 staniek (Jarosław Staniek), < nore...@phabricator.kde.org> wrote: > staniek added a comment. > > The domain name

Jenkins-kde-ci: calligra master kf5-qt5 » Linux,gcc - Build # 101 - Still Unstable!

GENERAL INFO BUILD UNSTABLE Build URL: https://build.kde.org/job/calligra%20master%20kf5-qt5/PLATFORM=Linux,compiler=gcc/101/ Project: PLATFORM=Linux,compiler=gcc Date of build: Tue, 20 Sep 2016 07:59:23 + Build duration: 1 hr 2 min CHANGE SET Revision ce3c8595e72cfb3d851062bcdd8dd90f3caa09

[Maniphest] [Commented On] T3755: Kexi API docs missing in the calligra section

staniek added a comment. The domain name is secured and it's KDE's already. TASK DETAIL https://phabricator.kde.org/T3755 EMAIL PREFERENCES https://phabricator.kde.org/settings/panel/emailpreferences/ To: staniek Cc: kossebau, Calligra-Devel-list, bcooksley, ochurlaud, sysadmin, staniek,

[Maniphest] [Commented On] T3755: Kexi API docs missing in the calligra section

ochurlaud added a comment. @bcooksley can correct me if I'm wrong, but if you want to have the website under the kde umbrella, come with a new website, open a ticket to have a domain name like the ones you named, and //Sail for Adventure//. =) TASK DETAIL https://phabricator.kde.org/T3755

[Maniphest] [Commented On] T3755: Kexi API docs missing in the calligra section

staniek added a comment. Very good, either solution that declutters the API pages would work for me. So the question is where to generate project's docs. Generating from within kexi-project.org comes to my mind, what would be feasible as part of a larger challenge: (finally) moving the s

[Maniphest] [Commented On] T3755: Kexi API docs missing in the calligra section

ochurlaud added a comment. > Hiding the docs won't move us closer to publishing. No, but if the project as a whole wants to be published, they/you'll have to work on it. A middle step would be to add kexi to the older scripts, but I don't know how. With the current scripts, it's seems no

[Maniphest] [Commented On] T3755: Kexi API docs missing in the calligra section

ochurlaud added a comment. The things KApiDox deals with (what is on the front page) is only public libraries. What is not on the front page is done by other scripts that I don't take care of, so they might do anything. We spoke about enabling the private libs in KApiDox. It's feasi