well, everything in general. haxeui is still the best library in haxe :) generally speaking, it has everything you need (apart from custom components). What I always find exhausting is the support of interfaces to the operating system. For example, I just want to display an audio level. That works great with haxeui-core but do I get the data beforehand? In many other environments such as python, I can simply use pyaudio, in java there is also enough C#, etc. etc. and haxe? Haxe has hardly anything for this or it has not been supported for a long time and simply no longer works.

ah, right, you mean to actually get the value from the OS?

> apart from custom components haxeui totally supports custom components btw 🙂

unless you mean custom drawn, cross framework, in which case - yeah, it'd need that canvas thing first

as for getting / setting the mic level... what OS are you targeting? What haxe target are you using?

> PyAudio provides Python bindings for PortAudio, the cross-platform audio I/O library

so briefly looking at that lib (PortAudio), it defo seems more than possible to create externs for that - the reason this does it exist it probably as simple as no one has ever had the need for it - you have to remember the haxe community is MUCH smaller than the, say, python community

that's what annoys me. haxe is so wonderful. Why so few use it. It deserves a bigger community.

and in externs I have to look again Just with https://github.com/Aurel300/ammer I just can't deal with it at the moment.

> that's what annoys me. haxe is so wonderful. Why so few use it. It deserves a bigger community. well, thats true - for sure - my advice (personally) is if there really isnt a lib that exists then why not write it (assuming you have time). Ie, that pyaudio - why not make hxaudio externs? That way you might save someone else getting annoyed at the lib not existing 🙂

python externs are easily possible. I always have problems with native support. Let's say hashlink and c++. Most of the time I can't manage to write externs for it. All this compiling and linking correctly and then connecting with haxe garbarage collector is really not my strength. I would love to pay someone to do it for me but ... that will be really expensive xD.

precisely because you do it as a hobby. I mean, you won't find anyone who will write portaudio externs (for hashlink, c++) for 50€.

well, another problem would be the externs that work for hxcpp wouldnt work for hashlink

at least, i dont think they would

with https://github.com/Aurel300/ammer it should work

right, ive never used that... defo read a little about it, seems neat for sure

is just ffi. So based on dlls (oups xD I wrote German by mistake)

i dont speak german 🙂

that's when you always switch back and forth with the languages. Sry xD

yeah, it defo looks like its the right tool for this type of stuff

I don't really like ammer. It's a nice library, but personally I prefer writing things manually, that way I can haxify things a bit where needed. And it also rebuilds everything on each compile iirc, so compilation can get very slow if you need to deal with large C libraries. It's also a big macro mess, so combined with haxeui it could nuke the completion server.

yeah, i get that, for some reason externs (hand crafted or generated) feel "nicer" to me... also it means i can compile the source directly and not have to use dlls, etc

out of interest, how easy / hard is it to write externs for HL?

i mean, are they very different from hxcpp?

Easy enough, in my opinion. And they are indeed quite different from hxcpp.

right, so thats a pain

Here's my hashlink externs for Kinc: And Kha's hxcpp backend for comparison :

I just don't understand, for example, how to teach haxe how to use the lib. Take portaudio for example. It has a makefile. Now how do I teach it to connect to each other. I'm just too stupid for that xD

Too bad it doesn't define struct access semantics but only pointers to structs

And pointers in general