Problem: If i have an error, server goes down, things go uugly. server down, special/upload last, re-request, lots of windows-switches.
Suggestion: integrate browser more.
(disable damned mouse-capture while editing
Fire up browser with http://www.syntensity.com:8888/tracker/ ... _log/view/?
Have the special/reupload in main menu, where upload is.
Open the request-page for the current project after special/reupload (like http://www.syntensity.com:8888/tracker/ ... 04edff277/ )
Load some feedback after some seconds in the browser. Still alive? (at least server-instances) else error-log.
Switcharound down to one extra window-switches.
Also: Most editors can call "make" or something. Can you make the client upload-only, so it can be called from the commandline? I think the client can be already started with a init-script, if that just does what special/reupload does. (but must do auto-login to the same account and such?)
Then i can stick in the editor for a few tries.
Also: Can you reload the last successfull map insted of crashing? No, that would overwrite the local changed data..
Teleport to the lobby, in the room with the user-servers? (But special/last-reload has a bug, it will then upload to the lobby.)
Also: can you add a "browse"-command so that i can set "bookmarks" to click? To launch external browser. then you could add some like "restart this crashed server", "spawn other game" in the lobby. Maps can have helptexts etc. (on linux needs an (automated) fullscreen-toggle more present than in the config).
Wish for "christmas" (bigger changes): Can you make a splitscreen with half 3d/ half integrated browser? I would love that with bespin/etherpad. click on an entity, open a page with a real editor. in case you get etherpad running, that is great to explain, because chat is inline.
Both see the same code, master writes:
//no, works like that:
changes some code
learner happy.
And could be used with the inworld-browsers, no problem with finding a good view-position, just click on it and browse it on the 2d-side.
PS: I am not a good api-reader. To understand apis i need a good overview and then trying with lots of of logging and reading examples/source. The overviews and sources look good, but the trying..