Re: UI for authoring SCXML documents
David Junger <[email protected]> Fri, 31 Jul 2015 08:42:54 +0200
| Newsgroups | gmane.comp.web.voice |
|---|---|
| Message-ID | <[email protected]> |
--Apple-Mail=_320CF678-E939-418D-B155-5448E1488587 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Le 31 juil. 2015 =C3=A0 01:33, Michael Bodell <[email protected]> a = =C3=A9crit : >=20 > In all cases, however, once the machines become a little bigger the = automatic visualizations become much harder to follow. I tried loading = a couple of real state machines that aren=E2=80=99t too terrible (623 = lines of code and 989 lines of code) and in both cases the picture was = only marginally illuminating and quite a bit harder to follow. But they = would be step-by-step-able and would also help newer people do their = first few state machines and/or help with tutorials or sample state = machines and the assertion state machines. Are you saying they're harder to follow graphically than by reading 989 = lines of code? ;) I know the current simple layout in JSSC's viewer doesn't scale well. = That doesn't mean the whole idea of a graphical representation is = doomed. By positionning the states better and automatically collapsing = large inactive compound states, I think you'd get a useful view of even = large SCs. After all, hierarchical states are in here, among other = reasons, to abstract away some of the complexity of the machine. David= --Apple-Mail=_320CF678-E939-418D-B155-5448E1488587 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 <html><head><meta http-equiv=3D"Content-Type" content=3D"text/html = charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; = -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" = class=3D"">Le 31 juil. 2015 =C3=A0 01:33, Michael Bodell <<a = href=3D"mailto:[email protected]" class=3D"">[email protected]</a>> = a =C3=A9crit :<br class=3D""><div><blockquote type=3D"cite" class=3D""><br= class=3D"Apple-interchange-newline"><div class=3D""><div = class=3D"WordSection1" style=3D"page: WordSection1; font-family: = Helvetica; font-size: 12px; font-style: normal; font-variant: normal; = font-weight: normal; letter-spacing: normal; line-height: normal; = orphans: auto; text-align: start; text-indent: 0px; text-transform: = none; white-space: normal; widows: auto; word-spacing: 0px; = -webkit-text-stroke-width: 0px;"><div style=3D"margin: 0in 0in 0.0001pt; = font-size: 12pt; font-family: 'Times New Roman', serif;" class=3D""><span = style=3D"color: rgb(31, 73, 125); font-family: Calibri, sans-serif; = font-size: 11pt;" class=3D"">In all cases, however, once the machines = become a little bigger the automatic visualizations become much harder = to follow. I tried loading a couple of real state machines that = aren=E2=80=99t too terrible (623 lines of code and 989 lines of code) = and in both cases the picture was only marginally illuminating and quite = a bit harder to follow. But they would be step-by-step-able and = would also help newer people do their first few state machines and/or = help with tutorials or sample state machines and the assertion state = machines.</span></div></div></div></blockquote></div><br class=3D""><div = class=3D"">Are you saying they're harder to follow graphically than by = reading 989 lines of code? ;)</div><div class=3D"">I know the current = simple layout in JSSC's viewer doesn't scale well. That doesn't mean the = whole idea of a graphical representation is doomed. By positionning the = states better and automatically collapsing large inactive compound = states, I think you'd get a useful view of even large SCs. After all, = hierarchical states are in here, among other reasons, to abstract away = some of the complexity of the machine.</div><div class=3D""><br = class=3D""></div><div class=3D""><span class=3D"Apple-tab-span" = style=3D"white-space:pre"> = </span>David</div></body></html>= --Apple-Mail=_320CF678-E939-418D-B155-5448E1488587--