2 Questions for Teamwork

Andreas Pakulat apaku at gmx.de
Wed Jul 4 18:25:55 UTC 2007

On 04.07.07 19:28:01, David Nolden wrote:
> Am Mittwoch, 4. Juli 2007 19:01:11 schrieb Andreas Pakulat:
> > Hi,
> >
> > as it was just "resurrected" I gave it a little test (two kdevelops on
> > the same computer) and got two questions:
> >
> > a) Do you plan an overhaul of the GUI? IMHO its unusable, cluttered and
> > missing various labels (not to mention the broken popup dialogs)
> Yes of course it needs an overhaul. It mainly needs a little work on the 
> ui-files, one or two labels filled, and some stuff should probably go out of 
> the tab into some configuration-dialog or sub-dialogs, but those didn't exist 
> when it was created. I don't know whether there is a usable 
> configuration-system now. 
> Then it needs some support from kdevplatform to signalize that a new message 
> has arrived.
> I don't know though why it's unusable though.

I didn't mean unusable as in "one can't do anything with it", unusable
means: Not easy to use, hard to understand. When the Ui is refactored
you should have a look at the HIG wiki and follow the rule's they set up
for user interfaces.

> > b) I didn't look at the code, but the plugin states that it creates a
> > workspace-thing, why is that needed? We tried to avoid having a
> > workspace in KDevelop4 to place the projects in. Or is this more like a
> > workspace per project where stuff that is being worked on using teamwork
> > stored?
> >
> > Andreas
> The plugin was designed when kdevelop was a one-project application,

Then it needs a redesign ;)

> When partially porting it so it works with multi-project, I renamed the 
> project-folder to workspace-folder because workspace is what fits the name 
> best. A space where you "teamwork". It could contain multiple projects, so 
> you can teamwork on all of them. We can think about a way to make it work 
> with all open projects, by using some kind of a "virtual workspace" or 
> similar.

Why can't you use project/.kdev4 on a per-project base? There was an
agreement that needing a workspace is not a good idea, because people
are bound to have their projects inside the workspace to use them. I
find this the most problematic part of Eclipse' project handling. 
This leads developers to store settings in the workspace, which in turn
leads to problems when having to move to a new workspace, which in turn
is needed on each minor version upgrade for eclipse.


Don't kiss an elephant on the lips today.

More information about the KDevelop-devel mailing list