sverweij
commented
9 years ago Thanks for this suggestion ..
I've actually been been toying with persistency:
- In 'debug' mode it is already possible to create a location hash (check out this example see below for the HOWTO). This works in most situations - I use this in fix-test-debug-fix cycles. It has some drawbacks, inherent to URIs:
- The maximum length of a url is limited - depending on the host. Most sane (mscgen) sequence charts work (on github.io the url for test: all arcs you'll get a Error 756 Too long request string).
- With some (smaller, mainly msgenny) charts it was possible to trip up the program - it's been a while since I was able to reproduce that, though.
- I've kept it in the 'debug' (or 'beta') mode because of these drawbacks.
- local storage looks as a promising alternative - I've run some successful tests with that (which spawned wordywordy b.t.w.) and plan to integrate that in a future release.
HOWTO
- Go into 'debug mode' by passing the 'debug' parameter to mscgen_js, e.g. http://sverweij.github.io/mscgen_js/?debug=true
- For your current chart click the button on the top right:
- This opens a new window that contains the URL - it seems that your suggestion to use 'history.push' would deliver a better user experience. I will look into that!
fflorent
When entering some texts, you could make the changes persistent, using the location hash or the history API (history.push, ...).
For example, here is how the sweetjs editor stores the text in the URL: [click here](http://sweetjs.org/browser/editor.html#/*%0AWelcome to sweet.js!%0A%0AYou can play around with macro writing here on the left side and%0Ayour code will automatically be compiled on the right. This page%0Awill also save your code to localStorage on every successful%0Acompile so feel free to close the page and come back later!%0A*/%0A%0A// Here is a really simple identity macro to get started.%0A%0A// The
macrokeyword is used to create and name new macros.%0Amacro id {%0A rule {%0A // after the macro name, match:%0A // %281%29 a open paren%0A // %282%29 a single token and bind it to$x%0A // %283%29 a close paren%0A %28$x%29%0A } => {%0A // just return the token we bound to$x%0A $x%0A }%0A}%0Aid %28 42 %29;%0A%0A// Note that a single token to sweet.js includes matched%0A// delimiters not just numbers and identifiers. For example,%0A// an array with all of its elements counts as one token:%0Aid %28[1,2,3]%29%0A%0A// One of the really important things sweet.js does is protect%0A// macros from unintentionally binding or capturing variables they%0A// weren't supposed to. This is called hygiene and to enforce hygiene%0A// sweet.js must carefully rename all variable names.%0A%0Avar x; // note the different name on the right --->%0A%0A// For example, let's look at the swap macro that uses a temporary%0A// variable to swap the contents of two other vars:%0Amacro swap {%0A rule {%0A %28$x, $y%29%0A } => {%0A var tmp = $y;%0A $y = $x;%0A $x = tmp;%0A }%0A}%0A%0Avar foo = 100;%0Avar bar = 200;%0Avar tmp = 'my other temporary variable';%0A%0Aswap %28foo, bar%29%0A%0A// Notice that even though thetmpvariable we made outside of%0A// the macro had the same name as thetmpvariable inside the%0A// macro, sweet.js kept them distinct.%0A)Florent