Le 18/06/2012 22:40, Elliott Sprehn a écrit :
Browsers allow unescaped @'s already in the URL field. You can't
hijack it to mean something different like that.
On Sun, Jun 17, 2012 at 7:32 AM, Florent FAYOLLE
<florent.fayoll...@gmail.com <mailto:florent.fayoll...@gmail.com>> wrote:
Hello,
I have written a proposal that introduces a new way to include
remote contents into the document (in other (bad) word, to
"Ajaxise" it) using a declarative way.
This proposal is named At Inclusion, and can be read here :
http://fflorent.github.com/At-Inclusion-Proposal/
To rapidly sum up, At Inclusion is a part of the URL that
describes pairs. Each pair is composed of :
- the ID of the target element (the element that gets the remote
content);
- the URL leading to the content to include.
and the At Inclusion has this form :
@TARGET_ID1=URL1,TARGET_ID2=URL2...
For example, let's suppose we have this main document (located at
http://myserver/mypage.html) :
<html>
<head>...</head>
<body>
...
<a href="@myTarget=/myaddition.html">click me</a>
...
<div id="myTarget"><p>default content here</p></div>
...
</body>
</html>
and the content to include in myTarget (located at /myaddition.html) :
<p>hello world</p>
By clicking on the link, the HTML code of #myTarget will be
replaced with this one :
<div id="myTarget"><p>hello world</p></div>
and the new location of the page will be :
http://myserver/mypage.html@myTarget=/myaddition.html
Feedbacks welcome.
Thanks,
Florent
Yes, I have suspected that... It's written at the "10. Remaining
questions" section of my document (at the bottom). I have kept @ to show
the idea.
