Add support for render() outside of each() data-query

[astoilkov]

As per suggestion: #58

[henrikekblad]

+1

[Kanaye]

I read the suggestion and I see a problem as far as I understeand the issue.
If you have an expression in an images source like so:

<img src="{{myImage}}" />

the problem (at least for me) is that the browser would have the error that {{myImage}} is not a correct url. An other case might be a mobile device where you don't want some images to load to smaller your apps/pages traffic.
something like that:

<img src="big-image.jpg" data-query="render(!isMobile)" />

The problem is, that the browser would have parsed the attributes and started the request before the dom is ready.
So we have no chance to remove that image before the browser starts the request.

Tell me if there are other cases an element should be removed instead of hidden.

I saw the attr()-data-query is currently not capable to set the src attribute.
Maybe we should implement that, cause the attr data-query combined with the visible data-query would be my suggstion for the described case.

[astoilkov]

Yes. I thought the attr data-query works correctly. Otherwise it really doesn't make sense.

[Kanaye]

short update:
The attr data-query works as expected with the src attribute.
For some reason it fails on one of my computers in chrome, but seems to be an issue with the installation and not with jsblocks.
[edit:]
Works perfectly on the computer it failed before after reinstalling chrome...
[/edit]