From: SourceForge.net <no...@so...> - 2012-02-25 04:38:41
|
Plugin Feature Requests item #3491574, was opened at 2012-02-22 19:39 Message generated for change (Comment added) made by daleanson You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=997936&aid=3491574&group_id=588 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Project Viewer Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Edward Diener (eldienerlee) Assigned to: Jarek Czekalski (jarekczek) Summary: Project and group linking Initial Comment: I would like to see ProjectViewer allow a project or group under more than one group without having to respecify the project or group name and files again. Essentially one should be allowed to "link" to the same project or group more than once in the ProjectViewer tree. I was told this perthaps will work by manually modifying the pv.xml file. But clearly if this is possible it should be supported fully by the ProjectViewer GUI interface. ---------------------------------------------------------------------- >Comment By: Dale Anson (daleanson) Date: 2012-02-24 20:38 Message: I agree with Edward. There have been several times that I'd like to group projects and subprojects, where subprojects are duplicated because they represent shared libraries or utilities. In Projectviewer, the tree is stored as xml, so I would think it would be fairly straightforward to be able to duplicate a node (even down to the file level) any where that seemed useful to the user. There is already a move to command, a copy to command would probably be very similar. I haven't looked at the code, though, so maybe it is more than I think. ---------------------------------------------------------------------- Comment By: Edward Diener (eldienerlee) Date: 2012-02-24 20:22 Message: My justification for this feature is that in my mind a group defines a series of interrelated projects. There appears to me nothing wrong in having a given project appear in more than one group. Let's say I have group A, which has project X and project Y, since they are related. Why should I not have group B, which has project X and project S, since project X is also being used by project S. It seems silly that I have to look at project X somewhere else in my project PV tree while I am looking at project S in a totally other place. This has nothing to do with actual folders on persisten storage but rather with the convenience of viewing/working with a project in two different places in PVs display. If we view project's as libraries, we know that some module ( exe, library ) may link to certain libraries while another module links to other libraries and the libraries linked to in both cases may contain the same or different ones. Likewise in PV any group should be allowed to contain any projects, even if a project is contained in more than one group. Similarly I would argue that it is as justifiable for a group to be in more than one place in a PV tree. Surely this can be done somehow by internally linking the name of a group or project into more than one place in the PV tree without interanally replicating everything below a group or project. ---------------------------------------------------------------------- Comment By: Jarek Czekalski (jarekczek) Date: 2012-02-24 00:30 Message: Computers taught as to create files in folders. Every file is created in a single folder where it belongs. Project viewer follows this logic. Please give some background and justification for the feature you request, because I don't feel such need. I see only implementation problems if a project could appear in several groups. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=997936&aid=3491574&group_id=588 |