If you consider a set of abstract widgets, reasonable enough, you could map them to native implementations in
-a browser -cocoa -gnome -add your one here. then, there could be a portable shared component speaking to those and gatewaying to your favorite protocol (9p, ix), and you could have a clean interface and reasonable bindings for it. cocoa was going to be my first move here, btw. didn't even start, though. -- using ipad keyboard. excuse any typos. On Apr 18, 2012, at 6:28 PM, Charles Forsyth <charles.fors...@gmail.com> wrote: > i thought the easiest way to begin and be cross-platform would be to talk to > a component running in a browser, > similar in principle to a viewer in Octopus. > a browser client will be needed anyway, and there is a browser on many things > (often only a browser); thus > your first step won't be your last, but it would cover a big distance. > it might also make it quicker to experiment. >
