View Single Post
Posts: 875 | Thanked: 918 times | Joined on Sep 2010
#96
Originally Posted by Mitrandir View Post
Anyway, it seems that full-blown UI toolkit will need a couple of years of work And I don't see any reasons to consider UI toolkit as a goal.
Lets consider some practical things, like ASUI or Simp, as a goal.
If audioplayer will require text input — we will need to investigate how to implement it. If no — great, lets give up on text fields.
We don't need to add eveything to the toolkit, only what is needed at the moment. The full list of widgets was just a roadmap and if the toolkit is properly designed it can easily be extended with more widgets later on. And the entire toolkit as described in the doc is pretty easy to do, couple weeks of good development time. Even the keyboard would be easy, a simple markup language to define key names, key codes and key positions would generate widgets inside a container widget. The callbacks on the buttons just hook into the Xlib key handling code and invoke whatever callbacks are attached to them.

Code:
landscape (vbox
(hbox (key 'a' 30 (shift 'A')) (key SPACE 57) (key 'the' 'the'))
)
The hard part is coming up with a good themable and modular structure for the library that supports user-defined widgets. The widget structure just needs a bunch of callbacks to render itself, handle taps and keys, return its minimum and maximum sizes so the parent container can allocate and assign it a position and size.

Anyway, I can code up the keyboard widget and text fields after I get the file manager started since it will need them to rename files and later on for its text editor.

And good job on simp, should be fully functional by next week.
 

The Following 5 Users Say Thank You to auouymous For This Useful Post: