Hi Robin,
Hi all (mostly Andrea),
I've noticed that when the inheritance diagrams are getting too wide that
the style settings in the browser are reducing it to fit the page width, as
shown in the attachment. Other than the obvious problem of readability
there is also a problem with the imagemap no longer corresponding to the
visible positions of the blocks in the image. For example, in the
attachment the tooltip shows that the mouse pointer is over the link for the
EvtHandler class.
Questions:
* How tricky would it be to keep the image full size but make that block in
the document a scrollable section so it doesn't affect the overall width of
the document?
* Can we have graphviz/dot generate those diagrams with a vertical layout
and a max width? (We may want to do that regardless of the answer for the
1st question.) Or better yet, can we have it use a more compact layout that
is a combination of horizontal and vertical so it makes full use of the
space given without being overly wide or tall?
This is mostly a GraphViz question, and I am not such an expert with
it... I can get the vertical layout quite easily (and it appears to me
that wxWidgets has the vertical layout by default, as there does not
seem to be any special settings in the "DoxygenLayout.xml" file, and
Doxygen uses Graphviz to generate the graphs). I'll switch to vertical
layout by default.
* It would be nice to be able to make the inheritance diagram sections be
collapsible like the wxWidgets docs do, and remember the setting in a cookie
or something for when the user browses to the next page.
I believe it's possible, it's just another piece of JavaScript to add
to the documentation builder. Other than that, I will have to add that
in the post-processing of the generated HTML documentation, as the
inheritance diagram section will need to be wrapped in a section
divider and the JavaScript script will toggle its visibility on and
off. I'll see what I can do.
* Is there value in having the inheritance diagrams on the module pages in
addition to the class pages? I see myself only using it to easily jump to
the class page, and I can already do that in the sections following the
diagram.
This is a remnants of AGW and the Namespace Diff Tool, I'll remove the
module-level inheritance diagram.
* Can we exclude showing the object, sip.simplewrapper and sip.wrapper types
in the diagrams?
Uh, that's very weird... I am sure it didn't happen with the Classic
binaries (i.e., with SWIG)... I will have to figure out an intelligent
way to manipulate the dot inheritance diagrams to remove the
intermediate sip classes.
I am not sure how much of this I will be able to do in the near
future, I am finally going on holiday tonight for a couple of weeks.
I'll commit any solid change I may make when I get back this evening.
Andrea.
"Imagination Is The Only Weapon In The War Against Reality."
http://xoomer.alice.it/infinity77/
# ------------------------------------------------------------- #
def ask_mailing_list_support(email):
if mention_platform_and_version() and include_sample_app():
send_message(email)
else:
install_malware()
erase_hard_drives()
# ------------------------------------------------------------- #
···
On 17 July 2012 01:52, Robin Dunn wrote:
. If no one