Merging appwizard into kdevplatform, remove documentview

[Matt Rogers]

On Wed, Dec 17, 2008 at 02:29:44PM +0100, Andreas Pakulat wrote:
> Hi,
> 
> I'd like to get some opinions on that.
> 
> appwizard hardly has any connection to kdevelop-specific projects right now
> and to implement the creation of kdevelop projects from kapptemplate
> template's (which lack a .kdev4 file currently) it would be good to have
> the code in shell. The reason is that it needs to open the project and
> right now that will lead to having to type in the project name and manager
> _again_ while this is already available from the new-project-wizard. OTOH I
> don't want to add a public API for opening a project with some information
> associated with it to iprojectcontroller, hence moving this to shell/ is
> the alternative.
> 
> For documentview: IIRC it has a few bugs, nobody touched it in a long time
> and it doesn't really provide a lot of information. Its basically just a
> grouping of opened files depending on their mimetype (I guess, didn't look
> at the code). I'm unsure wether we really need this, does anybody use it?
> Would it make sense to convert it into a plain list that works similar to
> kate's document-list (i.e. using background coloring for showing the order
> of last access)?
> 
> Andreas
> 

I use the documentview all the time, since I don't use tabs at all. So I
would prefer to keep it. I haven't noticed any bugs with it though.
--
Matt