[RFC] Transform workspace into session

[Andreas Pakulat]

On 01.07.08 16:18:42, Vladimir Prus wrote:
> On Monday 30 June 2008 00:23:52 Andreas Pakulat wrote:
> > Hi,
> > 
> > at the kdevelop sprint we pretty much agreed that some "central" place
> > to store metadata is needed, so I implemented a "workspace" thing thats
> > part of our project tree model. However thinking about this, it doesn't
> > make too much sense there and it also introduces space-wasting in the
> > treeview.
> > 
> > Now other apps in KDE have a concept of "session" which IMHO fits here
> > pretty well, we can assign a data-area to a session. So plugins that
> > still want to store some project-unrelated metadata (like teamwork for
> > example, or svn-plugin for repositories) can do it. Also looking at kate
> > this works pretty well, people not interested in it (like Alex) can just
> > tell KDevelop once on first startup to use the default session and never
> > ask again for session-choosing.
> > 
> > What do others think? Should we(I) look at how Kate's doing it and
> > eventually try to move some code to kdelibs for 4.2 so we can share code
> > with kate (or else just copy)?
> 
> I think the key advantage of Eclipse way is that this "workspace" thing
> is associated with a directory. So, if I have, for whatever reason, 100
> different projects I no longer care about, I can wipe this directory away.
> Also, workspace includes a log -- which is very nice thing for debugging
> issues with Eclipse itself.

Forgot to answer this one back then...

regarding having the projects in one place: KDevelop never enforced that
and I'm pretty happy with that. And in KDevelop you can always just
remove a project from disk and KDevelop won't re-create an entry in the
project tree for it - thats different in Eclipse. So I think we're not
really needing to enforce this "projects in one directory" notion. We
can still use a standard directory for creation of new projects or
importing from vcs systems. Something like $HOME/Projects. Maybe
xdg-dirs already support that...

Regarding the log: We don't have a logging system, but that would indeed
be something that could work really well. And we can just associate a
session with a KDEDIRS/share/apps/kdevplatform/session1 dir where the
log gets stored.

Andreas

-- 
You will be married within a year.