User:Qaisjp

I've been here since October 2010... ah the good times. You can find me at quite a few places...

• Skype, Twitter, IRC, pretty much everything: qaisjp
• GitHub

I maintain hedit, contribute to Blue, and have been a contributor to many servers.

You'll find me on #mta on GTANet.

mtasa-blue

issue 8714 Vehicle door/component desync on vehicle stream-in/out

reference for network stuff

issue 0008985 setCameraFOV aiming

reference for aiming

hedit 3.0

The resource has an internal API and the GUI works independently of it. The log syncing and response sending is handled by the the internal API on the client side and the gui core uses this API to apply this to the UI.

The gui core does not handle the showing/hiding of the GUI, it works through a public API

Folders

client/*

• sync/: Has an internal API that handles the sync, access locks and log streaming
• gui/: Has a public API that manages the rendering and the application to access lock.
• play/: This uses the public API to provide the default capabilities expected of hedit. It injects several things for usability into the GUI.

stuff

resources -> container

• many instances of containers can be created
• containers are managed by the resource "plug-in and play" code

Containers

Containers have:

• x button (injected by plugin and play)
• titlebar
• pane selector
• pane

Log windows

Log windows are managed by the plug-in and play code, many can exist at once due to the modular code but this feature will never be used. Log windows use the developer log api. (Log windows just utilise the log api to show it to ht euser)

mta ide using atom

ideas

• hook into server (remote or local) to allow features like restart-resource on: focus loss/save
• blue/red/orange colors for shared/server/client functions
• Lua 5.1 syntax highlighting
• linting
• inline wiki-ing

oop

• finish oop documentation
• do some tables
• do colour class
• learn LuaVM