Trying to resolve some dependency versioning stuff (I think) with haxeui-heaps on windows with hlsdl. When I go off the haxelib version for heaps I run into the issue described here: https://community.haxeui.org/t/haxeui-heaps-sample-gives-error-on-compile/412/2 Switching to the git version gives me:

C:\HaxeToolkit\haxe\lib\heaps/git/hxd/Window.hl.hx:175: characters 37-46 : sdl.Window has no field warpMouse
C:\HaxeToolkit\haxe\lib\heaps/git/hxd/Window.hl.hx:265: characters 13-22 : sdl.Window has no field warpMouse
C:\HaxeToolkit\haxe\lib\heaps/git/hxd/Window.hl.hx:219: characters 17-21 : sdl.Window has no field grab     
C:\HaxeToolkit\haxe\lib\heaps/git/hxd/Window.hl.hx:230: characters 17-21 : sdl.Window has no field grab

Switching to the git version of hlsdl changes that to:

C:\HaxeToolkit\haxe\lib\heaps/git/hxd/Window.hl.hx:10: characters 23-45 : Type not found : sdl.Window
C:\HaxeToolkit\haxe\lib\heaps/git/hxd/Cursor.hx:26: characters 20-30 : Type not found : sdl.Cursor

At which point I'm somewhat lost. Is hlsdl not supported / not recommended on Windows? I was able to get the "hello hashlink" project working before I started mucking around with haxelib. Is there another library I need to get from git? Should I ask all of this in #501408700142059520 instead?

so you almost certainly want to go with the git versions of everything: haxeui-core, haxeui-heaps, heaps, hlsld, etc, etc

but yeah, i would also see about trying to revert back to getting a heaps hello world work (no haxeui) via git versions, once that is working it should be trivial to start using haxeui

got it, thanks

Hey Sixtoe.... so.... i quickly tried it using the 1.9.0 Heaps .... it failed for the hl and js.... so i switched to git version of heaps.... they failed with the same error as displayed on my old post you shared the link to. So I installed heaps 1.8.0 out of curiosity.... that failed with different errors. I swapped back to git version of heaps, and now the js compiles and runs fine. The hl still giving the same error. Will see what I can figure out for the hl compile problem.

and thats with the hlsdl 1.10.0 installed I just noticed.

If you use git heaps you need to use git hashlink (and hlsdl/hldx) too.

thanks Zeta

For git hashlink, that means building from source?

Yes.

really? i dont think i build HL from source... and i use git versions, granted, quite out of date at this point

I get that but it makes the docs misleading if you don't already know that

Recent versions of heaps use hlsdl apis that are not present in the released versions of hashlink (I think).

right, so probably the fact im super out of date on heaps

what part of the docs is misleading?

i mean, i could certainly "allow" backgroundColor in css... but its very non standard

i figured it was kinda obvious that the css is css (background-color) and the haxe code is haxe code (backgroundColor)... but maybe that was a naive assumption on my part

that the expected style is kebab and not camalCase, I very much prefer kebab style but for anyone reading the docs and is new to haxeui it creates an issue

In fairness I vaguely call being tripped up by this early on, so some general doc page on conventions and exceptions would help I think.

isnt in the same in html5 though? I mean, you do

getElementById("x").style.backgroundColor

... but in html5 css its

background-color

... is there like a thing about that? Maybe there is, but i never remember reading it

you expect api docs to represent what works

but one is setting a property on the class, the other is using a DSL to style - they are quite different... im certainly not against some "conventions and concepts" page... but i dont think ive ever thought it to be confusing (outside of haxeui)

it's confusing if you're a programmer who hasn't used html or css before but I get that representing this on docs might be awkward

could add a toggle at the top of the page that flips between haxe code and style code

yeah, i mean... i guess... sounds like a set of pages (like the haxeui-guides) should a) be updated where they have content b) be created where they dont (like styling.md) and c) be put in the api docs somewhere, somehow

in other news, you can now do this: http://haxeui.org/builder/?6f586da2

this actually really neatly removes the need for creating haxe classes for custom components... ... at all... i still think haxe classes for custom components certainly have a place, but this is pretty useful for little "one off" type of things

(thanks @powerful-morning-89 btw, i probably would have thought "meh, not worth it" if you hadnt have shown me the metadata was nested)

I've built hashlink from source and swapped out my prior installation for that, switched to git heaps/hlsdl/hldx, and

C:\HaxeToolkit\haxe\lib\heaps/git/hxd/Window.hl.hx:10: characters 23-45 : Type not found : sdl.Window

got rid of the cursor type error at least. but I'm building my pre-haxeui-integration version now. If there's a better channel for general build issues I'll take this there. Is https://github.com/HaxeFoundation/hashlink.git the correct url to use with

haxelib git hlsdl

?

im not really well versed with the HL / heaps internals (though some people here certainly are). You might have more luck in #501408700142059520 or even #162395145352904705