-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to use @html, @touch widgets #15
Comments
Yes that's a good point. In the beginning I wanted to prevent the user to change the classpath of his classes (which would break the application). But I leaked it already for the templateScript, so I can just go ahead and put it everywhere. tldr; I agree, I'll change this. |
BTW I've discovered that when editing the tpl script, there are real HTTP requests done to retrieve the URL matching the classpath. Just try adding some new method to the script, and writing some dummy code, with Fiddler open: Perhaps some hack is needed after initializing the app to prevent it. Funny enough, it's always |
The call is coming from the Template, not the template script, so it will always try to load TestScript. But thanks for the info, I'll have a look. |
Small comment : html widgets can already be used because they were added to the Aria Templates environment of instantat. I just added the touch widget lib as well so it should be usable as well.
Still working on removing the magic though ... |
As mentioned above, touch widget library has been added by commit 60b32ce |
@jakub-g what about moving this issue to https://github.com/ariatemplates/instant.ariatemplates.com ? There's no link between this repository and the new one, and even though I like shuffling around this old piece of code, I think it would be better to push for improvements on the official app ? |
update : I have a "magic-free" version working, and which remains backward compatible with previously created snippets. I'll upload it on monday. 404 on TestScript : It occurs as soon as you change the classpath defined in the tplScript. The template is always configured with |
@juliandescottes thanks! I'll let you know if I spot something. |
Trying to use a widget from the library other than
@aria
, likeresults in an error message:
but since in the template view, there's no
{Template}
statement, it's impossible to addwlibs
by the user.I'm wondering if it wouldn't be better to not do any magical insertion of
{Template}
in TPL, or wrapping the code in the tpl script in a function call, but just initialize the textareas with the full skeletons needed?Regarding tpl scripts, with the default value of
there's a warning in the last line about missing semicolon. But when one inserts it, there's a parse error, probably because the code from the textarea is then appended to the function name and evaled, so there's sth like
someFunc(({ // json here });)
The text was updated successfully, but these errors were encountered: