$PH/COOL-BDE/whereis_bde2ht_demos.txt (revised 080126) (Formerly ~lechner/public_html/97sbde2ht{1,2}) (copied to $CASE/97f522/bde2ht_demos.hlp on 97/10/30 - RJL) These are linked to $CASE/97s523/bde2ht{1,2}. bde2ht1 contains a working demo of linkops.cc; bde2ht2 contains nearly working demos of nodeops.cc and textops.cc. (As of 97/10/30, rsesham and ksuresh needed to modify the URLs of map files in their *.htm* files to include absolute paths from ~lechner's index.html thru his local project subdirectories to the corresponding $CASE project directories. See lechner's public_html/ nodes or links: 97sbde2gif -> /usr/proj3/case/97s523/bde2gif 97sbde2gif_index.html -> /usr/proj3/case/97s523/bde2gif/bde2gifSCD/index.htm 97sbde2ht1 -> /usr/proj3/case/97s523/bde2ht1/lechner/public_html 97sbde2ht2/NODEOPSDEMO -> /usr/proj3/case/97s523/bde2ht2/PROJECT/NODEOPSDEMO 97sbde2ht2/TEXTOPSDEMO -> /usr/proj3/case/97s523/bde2ht2/PROJECT/TEXTOPSDEMO The bde2gif and bde2ht* demos show hotspot links from structure chart diagrams (SCD's are like the labeled call trees in structured design, except their links show the nesting structure of switch on state/event code blocks inside a module instead of calls to local or external functions). The goal of asgnt5 in 97f522 is to replace these structure tree diagrams by actual state diagrams that correspond to the most recent bde source code (the code checked out from CVS to /usr/proj3/case/95s523/95sbde/bde/src). . ~lechner/96sbde2ht1/: ------------------- This demo has two hotspots. The upper one is to an expansion diagram, if one exists (hint to reader: if the node name contains the text "LINK"). The lower hotspot is a hyperlink from each entity type on the ER_diagram to a form-based email reply. The form contains a entry block for each field of the entity type. A related project based on gendflt (which has not yet been used with bde), pre-fills the value entries with default values, so the user needs only to change these values where appropriate. Key fields are not shown, so the returned values must be post-processed by a processmail utility to add them or use our BB...EB encoding and expansion technique. ~lechner/96fbde2ht1/bde2ht1_menu.html: ------------------------------------- This demo contains state models for bde canvas drawing operations, which should contain two hotspots per node (to HN.HGLink and to source code). Source code for these is in $CASE/95s523/95sbde/bde/src/*ops.cc. File bde2ht1_menu.html lists these diagrams: (I updated status at right:) Demo1: State Model for Link Create (no HN-->HA-text - CG-->GX is used) Data Model for BDE ([not] linked to 95fbde_schema.h - Bad map URLs) Text Create State Model Demo (not linked - bad map URLs) link_create State Model Action Links Demo (not linked - bad map URLs) link_delete Demo-anchen (not linked - bad map URLs) Schools Demo (not linked - bad map URLs) link_create Demo-bpatel (not linked - bad map URLs) node_resize Demo-gfu (not linked) link_create Demo-gfu (not linked) node_resize Demo-gfu (not linked) Note added by RJL - 080126 : The JP2htm project ($PH/COOL-LCP/COOL-LCP/JP2html) used bde2ht to produce browsable versions of data models, state diagrams and code for the JuicePlant case study in Shlaer & Mellor: Object Life Cycles. Not all nodes contain expansion links, and the default behavior (linking back to the same diagram) hides this fact in a confusing way. Some implementors drew Graph Caption nodes instead of HN table rows to capture the text on the linked-to diagrams.