Re: [anjuta-devel] Improvements in project manager
- From: Sébastien Granjoux <seb sfo free fr>
- To: Johannes Schmid <jhs jsschmid de>
- Cc: anjuta-devel-list <anjuta-devel-list gnome org>
- Subject: Re: [anjuta-devel] Improvements in project manager
- Date: Fri, 30 Dec 2011 19:28:03 +0100
Hi Johannes,
Le 30/12/2011 18:26, Johannes Schmid a écrit :
* Do you think it is useful to remove the difference between a group and
a target?
Hmm, the "group" concept is very intransparent for the user so probably
it would be easier to remove the difference if possible. But we still
need to be able to map every autotools project at least. I don't have a
strong opinion here as I cannot really see the consequences.
Currently, I have hidden this concept by naming "group" as "directory"
in the user interface but I think it would be perhaps better to keep the
name "group" and improve the documentation because it's a bit more than
a directory. In autotools project, it is a directory, listed in the
configure.ac file and a new Makefile.am. I think we can define a group
as a way to group groups and targets allowing to set common properties.
It looks clear enough for me and I think we keep it.
Else, we can remove the "add group" menu item, and use the "add target"
dialog instead selecting directory or group as target type. But I'm
afraid it will not be really better as it reduce the difference between
a group and a target while it's quite different at least in autotools
project.
Another issue is that it could be useful to order groups and targets.
Currently as a target cannot include another target, it is possible
because you can select a sibling target instead of a parent group when
adding a new one. I prefer this situation because the dialog is simple
even if it's not obvious.
When adding a new group, I cannot know is the selected group is a parent
or a sibling. Currently, it's always a parent. I can add a combo box to
choose but I find a bit annoying to add additional widgets.
Anyway, it's possible to do it and it doesn't need any change in the
project API. The main blocking point is that I think we need at least to
renamed target to something more general but I haven't found a better
name: perhaps item, component, part?
Sounds like a useful option in the dialog like "Remove files that are
(only) part of this target". But we would need to check that the files
aren't references in other groups/targets
Yes, sure.
Regards,
Sébastien
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]