AlanOfTheBerg wrote:aeytom wrote:It would be nice to have an official well documented papyrus plugin API. This makes it a lot easier to write community plugins for the editor. New functions can be tested as plugins.
I think the easy answer there is no API. What has been written merely accesses the data structures which Papyrus and the LiveMap create in the browser environment. I doubt Waze will ever make any kind of API. But you could be referring to documenting the data structures...
RickW-NC wrote:I would like the livemap to be as accurate as the client (like it was before they "improved" it).
gettingthere wrote:mapcat wrote:This is supposed to be a 6-hour meeting. I'd love it if we could present a list of problems, discuss each of them, and ultimately solve them, but...it's only 6 hours. With 20+ people in the room.
Since the list of issues is already posted here, hopefully someone from Waze has already seen it, knows about all of these issues, and is prioritizing fixing them.
jasonh300 wrote:AlanOfTheBerg wrote:RickW-NC wrote:I would like the livemap to be as accurate as the client (like it was before they "improved" it).
That goes right with the "vector livemap" discussion point. There should be no need to generate multiple zoom levels for the livemap. Just download the vector data and create the client-side code to build the map live from that vector data, just like the editor code does.
Can a web browser display a vector, or does the server-end have to rasterize it and send it as a bitmap?
bgodette wrote:... basically all modern web browsers except IE.
Users browsing this forum: jbarrios107