Re: [Kile-devel] discussion [was: Re: doc update]

[Holger D. <h-d...@ve...>]

Hi,

> > I'd say that we should enter feature freeze for Kile 2.0 soon and
> > concentrate our efforts on documentation writing then.
>
> But before I would like discuss the behaviour of kile-svn which
> don't please me at the moment:
>
> - Emtpy documents, still confusing and unimportant for the user

Agreed. Do we really need different empty documents?

Currently some empty documents support syntax hightlighting, some not. 
And saving them with a different extension should also switch their 
document type. But this will give rather different and surprising 
results at tghis moment. Very annoying. 

> - Reopen docs on startup: no upgradepath for old projects and not
> honoring the abortion of the project open dialog (Question "This
> project file was created with an newer version of kile...", the
> problem lies completely in kile-svn and not in kile 1.9.x)

Yes, the DocsOpenOnStart problem, which means the backward 
compatibility of the config file. This should be preserved.

> Having resolved these issues before the first beta should be best.

Yes. And there is another important point: Kile-Scripting.

Kile-Scripting must at least support all features of 
Kate-Scripting. So all scripts, which are running with Kate, should 
also run with Kile, as Kile uses KatePart.

ciao holger