Thread: [Doxygen-develop] Feature request: group dependency diagram
Brought to you by:
dimitri
From: Ruud A. <ru...@st...> - 2011-03-18 10:56:30
|
Hello, For a project I'm working on we have our packages and modules sorted into groups: - layer - package - module Most of these modules depend on other packages/modules. We'd like to generate a diagram that shows these depedencies. We were thinking about defining a new command, '\dependgroup', that gets used the same way as '\ingroup'. So you define a group, where it falls under and on which groups it depends as well. This way dependency diagrams can be generated, just like with header includes. The reason that the header inclusion diagram isn't working for us is that multiple includes can fit into a single package, we want to group those together. I was looking at the Doxygen sources to create this functionality myself, but I wasn't sure what I can reuse or what I need to change. If someone can give me directions I can look into it myself. -- With regards, Ruud Althuizen - www.stack.nl - Unix commissie |
From: Dimitri V. H. <do...@gm...> - 2011-03-18 11:13:59
|
Hi Ruud, There is already a GROUP_GRAPHS option that shows group relations when enabled (in combination with HAVE_DOT=YES). Maybe it already does what you want? Regards, Dimitri On Mar 18, 2011, at 11:56 , Ruud Althuizen wrote: > Hello, > > For a project I'm working on we have our packages and modules sorted into groups: > - layer > - package > - module > > Most of these modules depend on other packages/modules. We'd like to > generate a diagram that shows these depedencies. > > We were thinking about defining a new command, '\dependgroup', that gets > used the same way as '\ingroup'. So you define a group, where it falls under > and on which groups it depends as well. > > This way dependency diagrams can be generated, just like with header > includes. The reason that the header inclusion diagram isn't working for us > is that multiple includes can fit into a single package, we want to group > those together. > > I was looking at the Doxygen sources to create this functionality myself, > but I wasn't sure what I can reuse or what I need to change. If someone can > give me directions I can look into it myself. > > -- > With regards, > Ruud Althuizen > - www.stack.nl > - Unix commissie > ------------------------------------------------------------------------------ > Colocation vs. Managed Hosting > A question and answer guide to determining the best fit > for your organization - today and in the future. > http://p.sf.net/sfu/internap-sfd2d_______________________________________________ > Doxygen-develop mailing list > Dox...@li... > https://lists.sourceforge.net/lists/listinfo/doxygen-develop |
From: Ruud A. <ru...@st...> - 2011-03-18 13:45:13
|
Hello, Those graphs only show the hierarchy of the groups withing Doxygen. What we have is a module defined as the group layer1/package2/module4 depending on layer3/package5/module1 and layer4/package10/module2. (The group names in this example are only used to represent their location in the layers of the below layout.) What this means is that one module can depend on other modules residing in a completely other layer and/or package. We could create these diagrams manually per module, but then we have to manually add dependencies of dependencies. On Fri 18 Mar 2011 12:13 PM, Dimitri Van Heesch wrote: > There is already a GROUP_GRAPHS option that shows group relations > when enabled (in combination with HAVE_DOT=YES). Maybe it already does > what you want? > On Mar 18, 2011, at 11:56 , Ruud Althuizen wrote: > > For a project I'm working on we have our packages and modules sorted into groups: > > - layer > > - package > > - module > > > > Most of these modules depend on other packages/modules. We'd like to > > generate a diagram that shows these depedencies. > > > > We were thinking about defining a new command, '\dependgroup', that gets > > used the same way as '\ingroup'. So you define a group, where it falls under > > and on which groups it depends as well. > > > > This way dependency diagrams can be generated, just like with header > > includes. The reason that the header inclusion diagram isn't working for us > > is that multiple includes can fit into a single package, we want to group > > those together. > > > > I was looking at the Doxygen sources to create this functionality myself, > > but I wasn't sure what I can reuse or what I need to change. If someone can > > give me directions I can look into it myself. > > > > -- > > With regards, > > Ruud Althuizen > > - www.stack.nl > > - Unix commissie > > ------------------------------------------------------------------------------ > > Colocation vs. Managed Hosting > > A question and answer guide to determining the best fit > > for your organization - today and in the future. > > http://p.sf.net/sfu/internap-sfd2d_______________________________________________ > > Doxygen-develop mailing list > > Dox...@li... > > https://lists.sourceforge.net/lists/listinfo/doxygen-develop > -- Met vriendelijke groet, Ruud Althuizen - www.stack.nl - Unix commissie |