[stringtemplate-interest] visualizer mockup

[Terence Parr]

On Nov 24, 2009, at 4:47 PM, Barrie Treloar wrote:

> On Wed, Nov 25, 2009 at 5:03 AM, Terence Parr <parrt at cs.usfca.edu> wrote:
>> Oh, and another architectural issue.  Should this be a socket based thing like ANTLRWorks so C# and Python targets don't have to build their own GUI?  I'd say yes, but then it's harder to drill down into objects in the attribute table.  I'll have to YAML or JSON marshall objects across the socket.  Some objects like binary arrays might be hard to represent properly in language indep manner in gui too.
> 
> I think some of the discussion so far raised some misunderstandings.
> 
> Is this meant to be a static inspection of the template? i.e some
> meta-data about template generation - which either resides inside the
> template or perhaps in another source (file, socket stream, etc)

I think we should collect all data like a flight data recorder and then ship to the GUI.  Unlike AW, i doubt step by step eval is useful. 

> Or is this meant to be something dynamic so that as the template is
> generated you can see what is going on?

static data but interactive

> My understanding so far has been that this would be static inspection.
> And if so I am unclear what a socket implementation would provide.

Yeah, Gerald pointed out a file of text would be better all at once. sockets are more complicated. we want multiple targets to be able to use same gui.
T