There are some rough edges left, but it seems the wayland/client is otherwise ready for action.
There's the first screenshot about a client that's written entirely in coffeescript. It draws a checkerboard into a shared memory buffer: https://raw.github.com/cheery/node-wayland/master/screenshots/2013-4-13-simple-shm.jpg I'll probably write some more examples, none of them will use opengl. Although I already have opengl ES2 bindings that I'd need to tune only slightly to get them work with wayland. I think I'll first want to get some functioning windowing related demos and wayland-server bindings done. perjantai, 12. huhtikuuta 2013 1.46.55 UTC+3 Henri Tuhola kirjoitti: > > If you look into https://github.com/cheery/node-wayland now, you'd see > that I have one new example. > > The example list an output from the registry. It only needs the code > generator and after that we should be able to write considerably more > complex clients. > > keskiviikko, 10. huhtikuuta 2013 1.33.29 UTC+3 Henri Tuhola kirjoitti: >> >> Since Wayland is becoming stable finally, it's the time to implement >> bindings for several dynamic languages. As it can fertilize Linux for >> large-scale GUI design&development efforts. I plan doing exactly this, but >> I have forgotten several things about node.js bindings. >> >> There's several simple things I need to solve: >> >> I need to get a pointer to my wrappings that let me route events through >> those proxies. I wonder how to get such pointer (that doesn't change at the >> next garbage collect cycle), and how to turn all those proxies into event >> dispatchers.. or is it okay that they call regular functions? >> >> As a second thing, I should pick up the known interface descriptors from >> the libwayland and provide them to the generated functions name-by-name. >> >> As a third thing, I should hook the node.js event listener to the >> display. I remember I'd have some reference code in node-udev, but this >> needs to be verified. >> >> Fourth thing, I wonder if the generated code from IDL should be .js or >> .cc. >> >> Fifth thing, once things are autogenerated, I should supply some >> functions into them. I wonder how to do this. >> >> If you need some extra references to answer, they can be found from: >> http://wayland.freedesktop.org/docs/html/ >> http://www.jlekstrand.net/jason/wayland-language-bindings-guide/ >> >> I plan getting this done within this weekend. Everything seems simple >> enough so it won't probably need more time than that. If you have answers >> to some of my problems, I guess I might get through it even faster. >> > -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en --- You received this message because you are subscribed to the Google Groups "nodejs" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
