Breadcrumbs, baby. In order to create them properly, I had to learn how to make a python plugin, since the TAL limitations prevented me from creating working suborganizer bread crumbs. As such, I decided to created a 66-line plugin for the graphTemplates that reduced it by almost 200 lines --- and thus setting my template up for the device handling that was needed to build the graphs for Wes as well as the future aggregates I intend to add.
My makeshift changelog is as follows: ---------- 1.3-0 * converted TAL-layers into graphDevice.py plugin, reducing the graphTemplate by almost 200 lines, and adding the structure for the deviceControlBlock as well as future enhancements * added "any"-conditions for gtype,dev,net * created Device listing report/graphs example (for Wes) ---------- 1.2-2 * added BreadCrumbs and proper suborg dropdown navigation * changed all arguments to 3 chars for easy stacking * created new Custom_Layout.rpt to illustrate user modifications ---------- 1.2-1 * added the ability for tab labels and exact gtype matching ---------- Wesley and Sven should be able to combine the SubSystems_Graphs and Device_Graphs examples in order to obtain the type of switch interfaces graphs that he needs link: http://lists.zenoss.org/pipermail/zenoss-users/attachments/20070412/aa11b380/zenoss-organized-graphs-1.3-0.bin md5sum: 845e37f26f9b3ae4145855d0dd29d785 zenoss-organized-graphs-1.3-0.tgz Next on my agenda is to create the custom tab and the aggregates that Allen is itching for. -------------------- m2f -------------------- Read this topic online here: http://community.zenoss.com/forums/viewtopic.php?p=5517#5517 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [EMAIL PROTECTED] http://lists.zenoss.org/mailman/listinfo/zenoss-users
