To make it explicit, the plan I have is to throw away o/live and o/mero and write something native for macos, linux, and perhaps ios such that the UI widgets are abstract and handled in a similar way they are handled in o/live.
Only that they'd be native widgets with the look of the native system (that's not to say you can't implement an editable text-pannel with the mouse language we all love). Also, as Forsyth points out, the set of widgets has to be rethought, e.g., there should be a web widget. Then it's a matter of using those files from inferno, and remote systems. But, as I said, I don't have a single line of code yet for all of this. On Apr 18, 2012, at 2:27 PM, Charles Forsyth wrote: > I should add that "along the lines" of Octopus meant that, > as often happens, many of the details might change to account > for experience and second thoughts, and for changed technology. > Obvious candidates for the latter would be the increased availability of 3D, > and vastly greater browser capabilities (for good or ill). >
