I’m not blocked on this now, but I want to bring it up for a discussion because I think allowing scripting will lead to much more interesting custom templates. I can’t really approach this kind of problem without being able to include scripts. This should allow me to generate multiple examples for the DB when they do finally accept/reject the example. I’m interested in generating more than one example from a single example being reviewed, so I would like to add new interactions that let the user give slightly more feedback before a yes/no. ![]() With open('recipes/textcat_eval.js') as txt: with open('recipes/textcat_eval.html') as txt: Perhaps a new recipe option to specify a single script file that will be injected into the base page, when combined with an html_template, e.g. ![]() I saw a suggestion that maybe static/index.html could be modified to include a script, but I don’t think that’s a very workable solution (unless I misunderstand) because you’d have to copy the files into or out of site-packages. ![]() There’s a react github discussion about it, but the TLDR is it looks like ele.innerHTML = '.' doesn’t work. ![]() I’m having a difficult time getting prodigy to allow custom scripts in my recipe specific templates, e.g.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |