Ticking certainly, however my dreadful js tells me that whatever whacky
functions I've made can be parameterised-in-a-template to be received by a
t5 component.
Extract their name (interface like) or some other more integrated language
binding thing..
Linking them within tapestry and it sounds like mod_perl mod_php mod_jquery
mod_app
In the case of a "calendar app" using bootstrap and joda time, say an
interface had inXDays() and the html day div highlights or pops up an edit
bubble, and that edit bubble had the
next+cool+mobile+version+of+a+js+gesture+framework, a la today's WYSIWYG
widgets. Gesture or camera, with websockets in html5, those divs are gonna
need some kind of policy applied in internetworking projects.
Js abstraction sounds timely, will be interesting to see what can happen in
html5 land.
Bringing it back to the issue at hand, a <t:Script src="alert(hello)" />
that could wrap the ugly bits at least. Java class stuff for
managed/designed/schedulable script dev though... A dreamable maven task -
although I'd do it in bash separately cos its quicker and simpler and
delegatable and heaps more l33t :P
Cheers
Chris
On 06/02/2014 9:21 pm, "Lance Java" <lance.j...@googlemail.com> wrote:
> In theory, the data URL approach sounds perfect.
>
> But in reality we'd be swapping this:
> <script>alert('hello');</script>
>
> For this:
> <script src="data:text/javascript;charset=utf-8,alert('hello');" />
>
> As you mentioned, it's likely that at least on browser won't support this
> (I'm looking at you IE!). As I said, I'm not sure it actually achieves
> anything in terms of security (apart from ticking a box).
>
