We don't just want to see examples of models (as is currently implemented in the models tab). Instead, we want to have examples for users to use to see how Perfume works.
To see one example of structuring example logs/arguments on the input tab, take a look at http://synoptic.cs.washington.edu . Click on "Shopping cart web app" on the left and see how the fields on the right get filled in automatically. Then, you can click "parse log", etc. The current perfume version, with the "Example 1" and "Example 2" in the models tab is not the same thing.
[Issue created by bestchai: 2014-03-17]
[Last updated on bitbucket: 2014-04-22]
[Comment created by bestchai: 2014-04-12]
To clarify, the model tab should be disabled on page load -- there should be no example models that the user can view before processing a log.
Further, when a user processes a log, just the model for the input log should appear. No other models should be shown.
We don't just want to see examples of models (as is currently implemented in the models tab). Instead, we want to have examples for users to use to see how Perfume works.
To see one example of structuring example logs/arguments on the input tab, take a look at http://synoptic.cs.washington.edu . Click on "Shopping cart web app" on the left and see how the fields on the right get filled in automatically. Then, you can click "parse log", etc. The current perfume version, with the "Example 1" and "Example 2" in the models tab is not the same thing.
[Issue created by bestchai: 2014-03-17] [Last updated on bitbucket: 2014-04-22]
[Comment created by bestchai: 2014-04-12] To clarify, the model tab should be disabled on page load -- there should be no example models that the user can view before processing a log.
Further, when a user processes a log, just the model for the input log should appear. No other models should be shown.