Unused forward declarations will be removed separately

In D16039#340061, @asemke wrote:

@sdepiets for the sake of completeness, can you please tell what the issue were with compiling (or rather linking?) on windows?

The problem was with lib/test and python/backend libraries sharing the same export flag than lib.

Include only when needed

Improved non-gui win32 executable method

Suggested improvements

Fix description

Remove unused header

Requested changes

Do not copy the export header

Remove export from libsound/qtplugins

Fix method signature in MultiSource.py

Requested changes

What about a reservation system within lokalize, a coordinator would be able to update a reservation status on each file from the Project View then commit the reservations to SVN.

Continuous integration support

In D15850#334144, @vonreth wrote:

In D15850#334143, @sdepiets wrote:

In D15850#334137, @vonreth wrote:

We need to handle ci mode

Do you mean disable the prompt when ci mode is enabled ?

I think that would be best, or to automatically use the default response.
On the other hand using the default could result in endless loops (not with your prompts but in general)

In D15850#334137, @vonreth wrote:

We need to handle ci mode

Improve the security logic

chmod

Memory leak fix + limit to one KProcess at a time

Patch improvements

Patch improvements

I've made the following changes :

• Moved the config from project to application
• Set up default values for the command lines
• Gray out the option in the editor tab when pology is disabled
• Add a pop-up on success (else you don't know when it's over)

• Redirect error messages

• Escaping the file names with double-quotes (maybe that's where your problem is coming from, now the command line is output if you launch from a terminal so you should be able to try the command manually)

In D15759#332366, @huftis wrote:

As for displaying the results, having a separate ‘Pology results’ pane showing the results would be nice (click on an error to jump to the message with the error).

And perhaps a ‘Pology errors’ column in the Project View (which would show the number of errors in each file – ‘0’ if no errors, ‘–’ if the file hasn’t been checked yet, or if it has been changed since the last check).