Hi, Sergio. 2013/12/14 Sergio Tortosa Benedito <serto...@gmail.com>
> Hi guys, I'm writing this e-mail to announce a new project I made, which > it's called guilang. > First, guilang it's an "extension" (I don't know really how to describe > it) for the Lua programing language, it makes Lua a declarative, > event-driven language which aims to make it very easy for developers to > write applications. Second, applications written in guiLang are > platform-independent and toolkit agnostic, this is thanks to the fact that > guiLang has three parts the launcher (made for making live easier), the > guilang core (which implements all the logic needed for guiLang) and the > gui constructor (which is the responsible for "translating" guiLang to the > toolkit). > I think that guiLang it's not only a win for developers, but also a direct > win for users in platforms with more than one toolkit (namely Linux/BSD) > since the same program can run not only on differents toolkits, but also on > libraries which add own widgets (e.g: pure qt and kde). > I do not know Lua so please, forgive me if I missed something, but how would be the code binded to the GUI? For example, how would the source code change if, for example, on clicking the button a new window with "Hi!" text is supposed to appear? Is the exampleApp.lua only GUI description and the code resides someplace else? And is my understanding correct that the guilang "toolkit" would be basically a simplified interface to the common functionality of all the underlying toolkits? > GuiLang, was made initially with HelenOS in mind however, I later saw > it's cross-platform possibilities. > > For trying this you'll need luajit/lua (it's recomendable that you choose > lua 5.1 over 5.2 for two reasons: 1.for keeping compatibility with luajit > 2.because I had problems with 5.2 (i dont remember if what I had trouble > with was luarocks or lgi or both)), you'll also need lgi which you can > install it via luarocks or directly. The code it's in > lp:~sheosi/+junk/guilang.Note: although guiLang itself its crossplatform > the code it's right a proof-of-concept and only supports gtk, what's more > it only supoprts windows and buttons, however neither of both should take > long for adding more. > The code of the application itself looks pretty simple and readable. But one more question comes to my mind. HelenOS runs on several platforms and their display resolution differs a lot. Some of them do not provide a graphical (pixel-oriented) output at all. Thus, specifying width of any control in pixels may not be the best solution. At least, not for all architectures. Do you plan some kind of switchable layouts depending on the resolution or other ways to tackle this? Btw, I looked at your Lua branch and you do not need to add the setjmp for amd64 as there is a generic implementation in mainline since rev. 2041. Best regards, - Vojta > I'll be waiting your feedback, Sergio. > > > > _______________________________________________ > HelenOS-devel mailing list > HelenOS-devel@lists.modry.cz > http://lists.modry.cz/listinfo/helenos-devel > >
_______________________________________________ HelenOS-devel mailing list HelenOS-devel@lists.modry.cz http://lists.modry.cz/listinfo/helenos-devel
