It work until make, but dont install, that part was what i did. now i now what should do later of make (i get the ansewr on the telegram group thanks to x512 and others) then create links to libX11.so.6, libXext.so.6 in /boot/home/config/non-packaged/lib
And now include the header paths(i dont know how yet).
I know this is not a stable work but can be funny to try to build some opensource
Here’s a fresh screenshot of GTK, now with an open menu:
The menus still have some glitches and do not always work the first time, however. More work still to be done … but the TODO list is getting much shorter.
I understand the discussions of native applications vs external toolkits, but for me these developments are going to enable me to make the switch to Haiku permanently.
Being able to run Inkscape through Xlib, some Windows applications/games through Wine and hopefully running virtual machines with virtualization in the future, would bring a non-hostile and sane UI to my daily workflow.
I think this moment is still a ways off for me. My big concerns are (in no particular order):
User passwords (and disk encryption)
Multi-display setups.
Native GPU rendering with 3D and 2D acceleration.
Remote desktop support (as in, connecting TO an existing Haiku session).
And I’m pretty sure none of those are coming soon. But, people have long thought about the first three, and the last one is kind of obscure despite how much I use it.
But, Xlibe, Wine, GTK are very cool and promising developments for improving quality-of-life for daily drivers, and discussions of us being close to R1 are also exciting.
We have a remote_app_server built in every Haiku install. You don’t even need a specific client for it: it can act as an http server and render your desktop using an html5 canvas. So you just need a web browser. Connection is established with ssh and port forwarding. All it needs is a bit of UI in the network preferences to configure it (and bugfixes in places where it doesn’t render things the same as the native display system).
@3dEyes, I built and was testing with it locally, it seems to work pretty well. Feel free to post a recipe if you want, I just did not get around to that.
This is actually intentional. Most of those libraries need a real X server and are thus disabled so Xlibe can be used instead.
the wrong inverted mask in xlibe turns them into something weird ).
there is a crash when delete cursor in the XFreeCursor function (when exiting the program).
thread 9562: AzPainter (main)
state: Exception (Segment violation)
Frame IP Function Name
-----------------------------------------------
00000000 00000000 ?
Unable to retrieve disassembly for IP 0: address not contained in any valid image.
0x7f6f912d6e60 0x156ce9b73df XFreeCursor + 0xf
0x7f6f912d6e90 0x1ecdac4eca9 AppCursor_free + 0x19
PS: I purposely put disabling cursors in a separate patch to make it easier to discard this patch after fixing the problems in xlibe.
As impressive as the progress of GTK on Haiku has been so far, they really do not fit in well with the rest of the system. Hopefully that aspect can be improved on later.
Or maybe it should stay that way? Make it work just well enough to be useful, but still bad enough to remind people that Haiku is meant to run its own native apps, not ported Linux or Windows ones