• cosmin

    Hello everyone!

    I just fixed a longstanding bug with objc that makes it work with OSX 10.10+. Details are here: https://github.com/luapower/objc/issues/4

    If you used objc with OSX 10.10+ before you might have noticed that your code doesn't work on OSX 10.9-. Likewise, your 10.9- code doesn't work on 10.10+. This change solves the compatibility but at the cost of disabling property access via dot notation, which breaks your 10.10+only code. To make it work again, you need to call objc.with_properties(true) after you load objc.

    posted in General Discussion read more
  • cosmin

    Oh, I almost forgot. I also published the dependency database in this meta-package: https://luapower.com/luapower_db and added a bit of documentation on the luapower-repos meta-package as well here: https://luapower.com/luapower-repos

    posted in General Discussion read more
  • cosmin

    Hello everyone!

    For those of you who are new to luapower or just need a quick reference on the structure of the source tree, you can now browse the whole tree online with annotations on every file and directory at this link: https://luapower.com/tree

    It's a new thing that I hacked over the past few days so there might be some bugs. If found, please shout them out. Thank you.

    Enjoy!

    posted in General Discussion read more
  • cosmin

    Ok, I'll make a short guide on the directory layout. Thanks for the tip. Until then, if you want the extended version of that guide check out https://luapower.com/get-involved

    posted in General Discussion read more
  • cosmin

    Hi. Thanks for the feedback. I think the site layout needs improving. For instance, there is a FAQ link at the top. Did you missed it? Also, luajit comes with precompiled binaries and build scripts (all packages do). You can download the package from the download link on luapower.com/luajit or from github.

    posted in General Discussion read more
  • cosmin

    Hi pupp!

    Luapower author here. Looks like you encountered a few issues with luapower since you started. Can you make a list of things that you found surprising or frustrating or took a while to grasp? I'd like to improve the documentation if I can, maybe make a getting-started guide. Thanks!

    posted in General Discussion read more
  • cosmin

    The window's WNDPROC is bound to MessageRouter.proc which calls the window's __handle_message() method which calls the WM_PAINT() method or the on_paint() method. If you're using CairoPanel, that descends from BitmapPanel which defines the on_paint() method. Hope this helps.

    posted in General Discussion read more
  • cosmin

    Can you tell us which one?

    posted in General Discussion read more
  • cosmin

    Hi Robert!

    Luapower hasn't seen much input this year but it will in the future. Not sure when exactly and what packages will be updated but I suspect it will be rewriting cplayer over nw and probably an IMGUI lib. I will also set up a build/test/CI server with multiple versions of Windows, Linux and OSX which will keep the binaries updated and will make the package metadata more accurate (right now I might have forgotten to update the package metadata for some packages on some platforms since I have to do that manually, and I rarely switch on my Mac these days).

    posted in General Discussion read more
  • cosmin

    Hi helmut,

    There's a xml module in luapower called expat, check it out.

    For 2D graphics check out cairo which is better than gd and the bindings are ffi-based, not C based and it also integrates well with libpng, freetype, winapi etc. bindings.

    If you need to use cmake then that's that (currently only libjpeg-turbo requires it because I was too lazy to make a build script for it) but an effort to make a simple shell script would be appreciated. In any case, even if you require cmake you should still make bash wrapper scripts with the correct cmake invocations so that it works out-of-the-box with the prescribed toolchain (that's a very important feature for me).

    posted in General Discussion read more
  • cosmin

    @robertmuench said:

    You have to place your own code in the luapower directory

    Done.

    posted in General Discussion read more
  • cosmin

    Oh I see, it comes as a size_t which is a uint64 on x64. Thanks for the find. Corrected in master.

    posted in General Discussion read more
  • cosmin

    Yap, cplayer needs reimplementing on top of nw. It's currently implemented on top of winapi.

    nw is in WIP indeed, but it's quite stable, give it a try. Missing functionality is organized here: https://github.com/luapower/nw/issues

    posted in General Discussion read more
  • cosmin

    Bundle doesn't handle paths. As the manual says "it assumes luapower's toolchain and directory layout".

    posted in General Discussion read more
  • cosmin

    Hi Robert,

    When would dsz not be a number such that it requires wrapping in tonumber() ?

    posted in General Discussion read more
  • cosmin

    Hi

    I for one am reading all the posts but I can't respond to debugging questions.

    posted in General Discussion read more
  • cosmin

    Hi tejo!

    For TLS I was thinking maybe extracting the abstraction layer from libcurl since it supports a ton of backends and so you can use the native implementation of each OS. For generic encryption I'd use a cross platform lib like libsodium or openssl but I don't have finished bindings for those AFAIR.

    posted in General Discussion read more
  • cosmin

    -m compiles the module and you can load it via require()
    -b adds any file as a binary blob which you can then load as a string via bundle.load()

    posted in General Discussion read more
  • cosmin

    1. -b is for including binaries that you then load via the bundle module. You won't be able to just require() those.
    2. .lua modules (added with -m) are compiled so you can't get their source code (but you can -m them and also -b them to get the source code).

    posted in General Discussion read more
Internal error.

Oops! Looks like something went wrong!