When Html5 target works?

150 views
Skip to first unread message

Wei Litao

unread,
Jun 14, 2015, 12:34:28 AM6/14/15
to geno...@googlegroups.com
Hi, When I try using Genome2D to build html5 example, following error occurred:

$ haxe build_examples.hxml
Genome2D-ContextCommon/src/com/genome2d/context/IGContext.hx:23: characters 7-40 : Type not found : com.genome2d.input.GKeyboardInput

It looks that Genome2D-ContextHTML lacks many Class. So do you have any plan on html5 target?


sHTiF

unread,
Jun 16, 2015, 3:18:04 AM6/16/15
to geno...@googlegroups.com, weili...@gmail.com
Hi yep, the HTML target isn't yet refactored for the 1.1 version of Genome2D. This is in the TODO after 1.1 RC is released. Can't give any deadline yet but it is definitely on a high priority list that isn't going to be sidetracked.

Михаил Лобачевский

unread,
Nov 11, 2016, 8:01:43 AM11/11/16
to Genome2D
I had problems with the engine assembly on java-script. Adjusting some compilation errors, I was able to gather a working application for java-script. If interested, I can commit a patch, or put the library under haxe. I hope it does not violate anyone's rights.

sHTiF

unread,
Nov 11, 2016, 8:08:40 AM11/11/16
to Genome2D
Genome2D is currently under prototype refactoring which should be completed next month, I will release more info with some great news around Christmas.

During this refactoring only Flash context is refactored on the fly to latest changes in the core which may result in HTML5 context disparity. Right after refactor finish late December I will bring HTML5 context back into focus to establish current feature parity atleast.

If you have any bug fixes or feature requests code feel free to submit a pull request I will definitely look into it. Just keep in mind that I may decline some request due to it being already in the plan and things may change until the requested fix/feature makes sense in its final form not to mention that core is changing daily now.

Just to ease your mind we actually have big plans with HTML5 target so don't worry about it being obsolete or forgotten its just not in current priority list right now which is targeted for 1.1.2017

Михаил Лобачевский

unread,
Jun 10, 2017, 5:56:29 AM6/10/17
to Genome2D
Will the stencil mask, and filters work (webgl)?

Peter Stefcek

unread,
Jun 11, 2017, 6:58:29 AM6/11/17
to Михаил Лобачевский, Genome2D

Hi

stencil should work atleast we use it, filters have set date to work by the end of this year since we are moving all our projects to webgl as well and need them to work too. Its problematic since they are completely different from agal and the shader injection is tricky.

P


On Sat, Jun 10, 2017, 11:56 AM Михаил Лобачевский <caspe...@gmail.com> wrote:
Will the stencil mask, and filters work (webgl)?

--
You received this message because you are subscribed to the Google Groups "Genome2D" group.
To unsubscribe from this group and stop receiving emails from it, send an email to genome2d+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Михаил Лобачевский

unread,
Jun 11, 2017, 8:14:31 AM6/11/17
to Genome2D, caspe...@gmail.com
There is no implementation of the stencil in the repository. I wrote the working code for the stencil (GWebGlContext). I can expose it if need.

Михаил Лобачевский

unread,
Jul 7, 2017, 8:38:07 AM7/7/17
to Genome2D, caspe...@gmail.com
-- bug?

PS Sorry, i have no time for make pull request etc.

Михаил Лобачевский

unread,
Jul 7, 2017, 11:21:05 AM7/7/17
to Genome2D, caspe...@gmail.com
https://gyazo.com/2f0df7dbb8320dcf82f514e96c0ac17c
-- fix

(in default version in run on my android -- event "touchend" is ignored -- i think occurs exception)
Message has been deleted

Михаил Лобачевский

unread,
Jul 7, 2017, 11:43:10 AM7/7/17
to Genome2D, caspe...@gmail.com
GWebGlContext, line 485

var te:TouchEvent = cast event;

mx = my = Math.NaN;

if (te.type != "touchend" && te.targetTouches != null && te.targetTouches.length > 0) {
  // as in current time
mx = te.targetTouches[0].pageX;
my = te.targetTouches[0].pageY;
}
if (te.type == "touchend" && te.changedTouches != null && te.changedTouches.length > 0) {
// need points is changed (removed from active-touch-points-list)
   mx = te.changedTouches[0].pageX;
my = te.changedTouches[0].pageY;
}
Reply all
Reply to author
Forward
0 new messages