{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
8/12/2013 12:23:04 AM
4
Nice. This kind of customization is less prone to breaking, as it is based on our service platform instead of modification of the UI. The platform also supports the mobile devices, which means that we are much more careful about breaking backward compatibility (except when absolutely necessary).
At some point, we may get around to documenting the full capabilities. Think of it like the Reach Stats API, except for all functionality of bungie.net.
English
-
I really love great documentation. Plus it would be sweet to build my own view of BNet. Plus this means faster website release cycles for everyone. I would really like not waiting another 10 years for a major front-end redesign.
-
Edited by Decimator Omega: 8/29/2013 2:28:10 AMTake what Daz is doing and implement Bungie classic mode! I still can't stand this new website look. I like it old and big and 'disorganized' just like the old website.
-
The entire website is implemented as a service. Basically, this means with enough time, you can write your own user interface (like he has) and view bungie.net however you want (think the Reach Stats API, but for everything). Daz couldn't really do what he's doing unless we already implemented this service layer. That being said, the old style isn't coming back in a Bungie supported fashion.
-
So we can make a classic mode with this? Good. Please don't get rid of it!
-
I have no intention of getting rid of it. Bungie.next itself uses the service to render its pages. So does the mobile app. It exists because we wanted to have both our web and mobile clients talk to the same backend. Using it is waaaay better than the old way of modifying our UI - that would break regularly. This service is unlikely to have breaking changes very often.
-
Good to know. Thanks Achronos.
-
Mother of God... Well, the fact of the matter is that there's a ginormous amount of work being done for the new Destiny hawtness (or hawtnesses), and shifting time and resources to making that possible is an obviously bad idea right now. It's not like we're going anywhere!
-
Wow. That's be amazing.
-
Indeed!
