Pages: [1] :: one page |
|
Author |
Thread Statistics | Show CCP posts - 0 post(s) |
Jarg0n
New Tribe
0
|
Posted - 2014.11.15 13:12:07 -
[1] - Quote
I've been working on a new corp tool recently. Well, it's more of a framework since I managed to stumble at the first hurdle.
One of the things I tend to do these days when writing AJAX web apps is to hook into the URL fragment for page navigation. Twitter used to do this (first time I saw this approach and really liked it) and so does Grooveshark. Basically, immediately after the domain the separator #! is used before the rest of the URL (e.g. http://www.domain.com/#!/register), this allows navigation with absolute certainty that no page loads ever occur and the remainder of the URL can be used for either page location or arguments. This is achieved by hooking into the JavaScript event onhashchange and triggering the AJAX call.
While URL fragments do appear to work in the IGB in regards to anchors, it does not seem to update the URL in the address bar as expected from a web browser. I'm not sure if this is intended design or just a 'not yet implemented' scenario, as I was unable to find any other information about it. Unfortunately this does mean that the onhashchange event is never fired as it is never changed. Not even sure if the onhashchange event is implemented because I simply can't test it.
So my question is, does anyone know of this issue and have any suggestions about how to get it to work, or at least another approach that will work?
Cheers |
Dragonaire
Here there be Dragons
66
|
Posted - 2014.11.15 19:31:16 -
[2] - Quote
Just some things to think about before investing a lot of time on anything built around the IGB.
Quote: just a 'not yet implemented' scenario - no thats not it, its a 'never will be implemented' scenario. The reason for that as stated by CCP is long term the IGB will be removed completely once they have replace the functions they use it for internally etc. As to what long term means they don't really say but my guess would be some time within the next 4-5 years. The updated IGB we have now is several years old and highly modified version of browser engine to make it work with the Eve client and the people involve in doing it from what has filtered out from CCP no longer work there so to change it in anyway would means basically someone start over from the beginning which they don't feel is a good use of their time. I would be looking at CREST and some of the expected things we as third party developers will have access to because it is what CCP plans to replace the functions of the IGB and other stuff with. They've now released the SSO stuff and once that proves out I expect a lot of things starting to happen much faster with it than has been seen over the last 3+ years.
Finds camping stations from the inside much easier.
Designer of Yapeal-á for the Eve API.
Check out the Yapeal PHP API Library thread for more information.
|
Jarg0n
New Tribe
0
|
Posted - 2014.11.17 22:41:23 -
[3] - Quote
Ok, thanks for the info :)
Kind of a shame though, there's a lot of tools out there that help with EVE and it's nice to have them bookmarked in the IGB for fast access.
At least now I know I shouldn't worry about IGB compatibility if it's (relatively) short lived. |
|
|
|
Pages: [1] :: one page |
First page | Previous page | Next page | Last page |