OpenFL 8.0.2 released

Announcements
#21

Can work:

var object:Dynamic = {};
if (object != null)
    trace(name, object);

Can not work:

var object:Dynamic = {};
if (object)
    trace(name, object);

I found these two judgments, the following one will never be established in C++. This discovery comes from the code of Starling2.3.3’s AssetManager:

if (object)
      addObject(name, object);
#22

Is this the one you’re looking at?

#23

Yes, at the same time I found out that Starling’s C++ version is far from the Openfl native version.
:joy:

#24

Far in what way? Very different? Better, worse? More features, less features?

#25

More is the performance difference, Starling’s performance will be very weak on the Android platform of C + +, drawing 4 or 5 will consume a lot of CPU.

#27

I understand that DOMElement is the new method, I just can’t figure out how to implement it, particularly without more complete documentation.

If I simply replace DOMSprite with DOMElement it throws an error when trying to use with IFrameElement…

js.html.DOMElement does not have a constructor

#28

Emmm, I am using Android Studio to modify some information, such as AndroidMainifest.xml and the main activity of the code, as long as I run a Command + Shift + B compiler, everything will disappear. How to correctly modify or extend your own Android project?

#29

Do you mean that the OpenFL native output is much slower than the C++ version of Starling (I forget what it is called) or that it is faster? Android is very different than desktop in performance, but there already are large projects using OpenFL Starling/C++ successfully :slight_smile:

#30

It sounds like there is an import conflict, perhaps you could use the in keyword for your imports

import openfl.display.DOMElement in OpenFLDOMElement;
import js.html.DOMElement;

...

var element = new OpenFLDOMElement ();

You can also use openfl.display.DOMElement instead of using an import

#31

You would have to override your template.

Lime and OpenFL have templates directories. This works like a class path. You can add your own templates directory, and the tools will allow you to override individual files from OpenFL or Lime, such as your AndroidManifest.xml.

Add <template path="templates" /> to your project.xml, and a “templates” directory (you can also put it in a different place in your project structure, if you prefer).

Look at the Lime templates directory structure and mirror it in your own, until you override the file you want. For example, “templates/android/MainActivity.java”

#32

I’m very sorry, I mean Openfl’s native performance will be faster, Starling is slow.:grin:

#33

Thank you!:rofl::rofl:

#34

Excellent, yes that works, didn’t spot import openfl.display.DOMElement as an option, was still working with the js route :slight_smile:

#35

7 posts were split to a new topic: How to use HaxeUI?

#38

A post was split to a new topic: Java to Haxe communication

#39

Was Neko ridiculously sped up? I think I am getting 3x the fps when testing my project.

#41

Why HTML5 fonts are particularly vague?Is there a way to make it look clear?:disappointed_relieved:

#42

If you were using Tilemap or drawTriangles, then yes

#43

I believe this is a general HTML5 issue. We use webfonts, and canvas text APIs to render. You could use bitmap fonts, or perhaps there are other ways to make it behave better, like generating a different version of a webfont, or disabling CSS scaling of your project in your output HTML. There should be other topics here on the forums as well about <window allow-high-dpi="true" />

#44

This is very useful.:grinning: