Love2D WebPlayer (WebGL)

Discuss any ports of LÖVE to different platforms.
User avatar
Inner party member
Posts: 1492
Joined: Thu Jun 09, 2011 9:03 am

Re: Love2D WebPlayer (WebGL)

Post by T-Bone »

alberto_lara wrote:Hi, is this project still getting support? It doesn't look like :(
Doesn't look like it. If you want to target the web, use Love.js, which is under active development.
User avatar
Party member
Posts: 352
Joined: Wed Oct 30, 2013 8:59 pm

Re: Love2D WebPlayer (WebGL)

Post by alberto_lara »

T-Bone wrote:
alberto_lara wrote:Hi, is this project still getting support? It doesn't look like :(
Doesn't look like it. If you want to target the web, use Love.js, which is under active development.
User avatar
Party member
Posts: 132
Joined: Tue Jun 30, 2015 1:23 pm
Location: Canada

Re: Love2D WebPlayer (WebGL)

Post by CanadianGamer »

Sorry If this has been already answered but what parts of the api don't work?
My serious page:
My less serious page:
User avatar
Party member
Posts: 253
Joined: Sat Jan 16, 2016 10:30 am

Re: Love2D WebPlayer (WebGL)

Post by 4aiman »

not-yet-implemented (incomplete list)
* love 0.8 api (currently webplayer is mostly for 0.7, to test some 0.8 stuff add to index.html : <body onload="Love_Enable_Experimental_080(); ...>
* spritebatch,framebuf
* love.physics/box2d (started usign Box2dWeb)
* font truetype/ttf loading (rasterizer), pixelfonts should work (except a few special cases in text formatting/wrapping)
* network/luasocket
* love.thread
* love.sound sounddata/decoder stuff. audio itself should work, but is troublesome in some browsers, notably firefox (html5 audio)
* love.timer.sleep : not possible in js, would lead to browser hang in most browsers
* love.imagedata (load-from-file + imgdata.paste + graphics.newImage(imgdata) works, but not decoding, etc)
* love.filesystem stuff (some of it already works, but only if "localstorage" is available in the browser, stored in cookies or sth)
* debug.stacktrace and useful stacktraces on error in general (i recommend testing in native love first and if the problem is webplayer only litter the code with lots of print("pos01") to narrow it down)
* complex string matching pattern, especially balanced braces (e.g. xml parsers, see below)
* screensize wrong (-1,-1) during love.load :
* raw sound/audio editing : love.sound.newSoundData etc

known issues :
* audio : music formats .xm and .mod not supported by browsers usually
* 404 warning in webconsole when using "require somemodule", you can safely ignore this, this is just the only way javascript can do a file-exists check for the module loading behavior of require
* (TODO) workaround for 404 : call LoveFileList('filelist.txt') in index.html body onload to enable love.filesystem.enumerate
* images have to be listed in index.html onLoad call for preloading, otherwise .width/.height access can return 0, and it's not possible in chrome+firefox to pause running code without changing code-structure to callback
* ticket/issue at lua.js github :
* parser bug : clouds demo : parse error in keypressed : >> love.filesystem.load("main.lua")() << (already fixed for some generic cases) workaround : >> (love.filesystem.load("main.lua"))() <<
* parser NotImplemented : string.format("%d",5),debug.backtrace,coroutines,...
* firefox(11) is known to have issues with sound: lag,delay.. chrome (18.0.1025.151) works better for me on ubuntu 11.04 (2012-04)
* doesn't work with file:// url for some reason. so you need to upload stuff to a webserver to try, php and similar isn't needed.
* when changing lua files, be sure to clear browser cache to see your changes, pressing f5 is not enough since it doesn't refresh dynamically loaded files like the .lua ones
* lua string patterns aren't fully convertible to javascript regexp, so while most string patterns should work, more complex ones (like xml parsers) might fail
** if you need this for maploading or similar i'd recommend working around that by serialize the loaded table as .lua file
* functions not allowed as table key
* table with key-type=obj tends to slow down if inserted/deleted a lot every frame, usage of js:splice in lua-parser might be bad? further testing needed, example devmania2012veh pre 2012-10-12
Post Reply

Who is online

Users browsing this forum: No registered users and 3 guests