Re: [anjuta-devel] new project manager UI
- From: Abderrahim Kitouni <a kitouni gmail com>
- To: Johannes Schmid <jhs jsschmid de>
- Cc: anjuta-devel-list gnome org
- Subject: Re: [anjuta-devel] new project manager UI
- Date: Mon, 31 Jan 2011 19:36:52 +0100
Hello,
(I feel you didn't understand me, and I didn't either. Perhaps because
english isn't my native language).
في ن، 31-01-2011 عند 17:46 +0100 ، كتب Johannes Schmid:
In both cases, Anjuta[2] cannot know about all the different nodes.
While it is OK to just have generic icons for them, not showing them at
all wouldn't be nice (we may even end up with a blank project view).
Well, Anjuta has a list of known node types. Probably that isn't enough
for some project management systems but that is pretty hard to fix.
What I asked for is adding a "unknown node type", i.e. a generic node
type that would be used if the node is unknown. I know it is
unreasonable to assume the project manager knows all possible node
types.
I guess nobody wants to implement a full project-manager just because the
node type xyz doesn't look exactly like in eclipse.
But the problem is that it doesn't "look" at all. The project manager
shows only the nodes it knows about
(root/group/target/source/module/package), and only in the relationships
it knows about (i.e. it doesn't show a target if it is a child of root).
It is pretty natural
the every new project backend might need to add something to the
project-manager we didn't think of yet, but with a 6-months cycle it is
reasonable to just change that in the project-manager.
Anyway, it's unreasonable to assume it will work perfectly from the
start, but it should at least work somehow. If the backend needs some
special treatment (mainly icons), it can be done in the next cycle.
Regards,
Abderrahim
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]