Qt's been ported to OSX. It's not really worth it though,
better to go native drawing libraries with Cocoa or OpenGL.
On Apr 18, 2012, at 8:37 PM, hiro wrote:
> Is this a joke? Has cocoa been ported to qt now?
Is this a joke? Has cocoa been ported to qt now?
> > having to write the same set of GUI interfaces
> > three times (X11, windows, Mac OS).
>
> I'd like to put in a good word for Plan 9, in case it gets forgotten.
> And, yes, Qt does not support Plan 9, I guess we'll need to find some
> compromise, if at all possible.
>
> ++L
Good point. Unfortu
> having to write the same set of GUI interfaces
> three times (X11, windows, Mac OS).
I'd like to put in a good word for Plan 9, in case it gets forgotten.
And, yes, Qt does not support Plan 9, I guess we'll need to find some
compromise, if at all possible.
++L
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 cl
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,
ah, if you said just to leverage a
native kit, yes, that was the plan I had.
but abstracting it.
--
iphone kbd. excuse typos :)
On Apr 18, 2012, at 6:09 PM, arn...@skeeve.com wrote:
>> Is it exported as files?
>>
>> I thought I knew Qt, but, if it provides a file interface, I missed that.
>
> Is it exported as files?
>
> I thought I knew Qt, but, if it provides a file interface, I missed that.
No - but I would suggest building on Qt, to let it handle all the interface
to the native graphics, and you provide the file service / translation
over it.
I think that would be challenging an
Is it exported as files?
I thought I knew Qt, but, if it provides a file interface, I missed that.
On Apr 18, 2012, at 5:45 PM, arn...@skeeve.com wrote:
> Hi.
>
>> 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 perh
Hi.
> 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 th
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
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 capabiliti
Sure. I'm using it (and nix/plan9) to develop nix.
Drop me a line off-list if you want help, but you should have
everything you need in the web site, including the distribution of the system.
On Apr 18, 2012, at 2:26 AM, kokam...@hera.eonet.ne.jp wrote:
>> I was thinking along the lines of http:
13 matches
Mail list logo
