You can find me in quite a few places...
- Skype, Twitter, IRC, pretty much everything: qaisjp
I maintain hedit, contribute to Blue, and have been a contributor to many servers.
You'll find me on #mta on GTANet. I'm on Discord as well. Happy to chat!
- 1 mtasa-blue
- 2 hedit 3.0
- 3 sandbox
httrack "http://wiki.localhost/wiki/Main_Page" "+http://wiki.localhost/images/*" "+http://wiki.localhost/extensions/*" "+http://wiki.localhost/resources/*" -c3 -%c0 -%v2 -A0 -#L30000000 -s0 -%k -%F '' --disable-security-limits
:thinking: HTTrack Website Copier/3.48-20 mirror complete in 23 minutes 17 seconds : 30975 links scanned, 22989 files written (606020297 bytes overall) [394444732 bytes received at 282351 bytes/sec], 509114662 bytes transferred using HTTP compression in 25278 files, ratio 28%, 95.5 requests per connection
MORE STUFF HERE https://www.mediawiki.org/wiki/Category:Import/Export
ncurses is keg-only, which means it was not symlinked into /usr/local, because macOS already provides this software and installing another version in parallel can cause all kinds of trouble. If you need to have ncurses first in your PATH run: echo 'export PATH="/usr/local/opt/ncurses/bin:$PATH"' >> ~/.zshrc For compilers to find ncurses you may need to set: export LDFLAGS="-L/usr/local/opt/ncurses/lib" export CPPFLAGS="-I/usr/local/opt/ncurses/include" For pkg-config to find ncurses you may need to set: export PKG_CONFIG_PATH="/usr/local/opt/ncurses/lib/pkgconfig"
==== Building Core (debug_x64) ==== Linking Core ld: warning: text-based stub file /System/Library/Frameworks//CoreFoundation.framework/CoreFoundation.tbd and library file /System/Library/Frameworks//CoreFoundation.framework/CoreFoundation are out of sync. Falling back to library file for linking.
I had to do the rm -rf thing after updating xcode. Fix works after doing reboot and doing a clean build.
Lua Test Suite
- LUA_DECLARE regexp for visual studio 2012+: static int *\t*(\S*) *\t*\( lua_State ?\* luaVM \); replacing LUA_DECLARE ( $1 );
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
- 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.
resources -> container
- many instances of containers can be created
- containers are managed by the resource "plug-in and play" code
- x button (injected by plugin and play)
- pane selector
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)