and if you wanted .myStyle to be more dynamic then you could build that style at runtime using something like:

fyi: .styleString just splits and parses the css string into .customStyle (iirc)

oh... that's very interresting :) thanks again for your time. time to lunch for now ^^ I'll try to show you the "final product" asap 🙂

Any new thoughts on trimming down the file size a bit? I know tooltip work added a new font in haxeui-openfl. Wonder if there's a way to not include certain resources like fonts, images, etc if the style that calls for them maps to something not used in a project.

yeah, im defo going to look at it... i have a couple of unrelated thoughts, some on how to make hscript not needed so dont need to "include all" and other ways that modules can have settings to "unset" other parts of other modules and also conditions in modules to trim things down

but nothing as of yet

My solution is a disclaimer at the beginning: “yeah the file size is kinda big, but dude look at these ANIMATED TOOLTIPS” if js

haha

to be fair, its all completely doable to make much smaller

its just low(ish) priority to me... as yeah, i can probably get a few 100kb for a button, but as an app UI grows you'll probably end up with everything anyway

ie, you have 2mb for a button (which is shit), but you also have 2mb for everything... and 1 button apps arent really "a thing"

still, that all said and done, im defo going to trim it down as something reallys are just not needed

What targets are people trying to minimise? Closure obfuscation for JS or `strip`ing native binaries can bring file sizes down 25%-50% in my experience. With that, linux builds of Realmkit come to 15mb, which is pretty excellent for desktop apps these days. 2.9MB for the HTML5 build, which will be compressed a bit more across the network by the server. Decent sized Kha + Haxe UI app 😄

Time to venture into the deep dark forest of Custom Components for my dialog boxes 😕

Custom components are the best! You'll learn a lot from it and it's really not too difficult.

I manged to get themes working so I should be able to figure that out. I know I'll get some help if I can't find the answer hidden in here

@User - so i think, generally, its the js build that feels (and indeed is) a little bloated - i think people are far more forgiving for a native build, and as you say, 15mb aint bad at all. And yeah, gzipping can help alot with js, the fact still remains though that if you dont use a certain component in your app, you'll likely have reference to it anyway (because of the main module), and it defo could be a cheap fix to have "slim" builds (based on conditions in the module.xml) that dont do that.... will it save lots? unlikely. Should components you dont use be in the final js output? Not if you dont want them to be.... so ill defo look to sorting out, not just for size, but also just for correctness to be honest

@User - custom components are the way forward... i use them for pretty much everything, thinking about changing the default template that "haxeui create ..." uses to create one with a custom component for the main view - it just make things sooooo much simpler, especially for me when i wanna knock out a test project real fast

Yes, that sounds fair enough. > you dont use Also good reminder to have full dead code elimination 😄

Hi, if I wanted to create a desktop application with lots of charts, some tables and user inputs which target would I choose for haxeui? wxwidgets? Also are there charting libraries similar to d3.js for haxe?

(currently trying to figure out if there is a "good" alternative to an electron/js/d3.js app)

hey - so the hard part is going to be the actual drawing of the charts

ie, the d3.js part

yea i guess if i had to roll my own I probably would go with electron

It’s hardly d3, but if you know JS canvas, Kha offers a similar API.

you can always use haxeui with electron too (just an fyi)

i guess that but not sure if it makes things easier 🙂 what i dislike most about js is the whole tooling.

adding another layer there is probably not simplifying things 🙂