> Why not pray that you *are* a crazy visionary? :)
Too many years of logic, I'm a very rational materialist. But thank
you for the suggestion, it gave me reason to smile. I do get plenty,
in their lack of technical sophistication , my "previously
disadvantaged" neighbours have a great deal of wa
> IMO, there is nothing generally wrong with taking the path of least
> resistence, so long as open is open minded and also so long as it is not
> the only path being considered.
Except that by definition the path of least resistance is the only one
of its type. You buy the reason, you paint your
On Thu, Apr 19, 2012 at 1:56 PM, Lucio De Re wrote:
> > I may be biased, but still sure some general flavor of Comeau for
> > Plan 9 could be a near term and not expensive endeavor (though it
> > depends upon ones definition of inexpensive too I guess). And Qt
> > definitely has its place in the
> I may be biased, but still sure some general flavor of Comeau for
> Plan 9 could be a near term and not expensive endeavor (though it
> depends upon ones definition of inexpensive too I guess). And Qt
> definitely has its place in the world.
I've bought the Go faith lock, stock and barrel, to m
> On Apr 19, 2012, at 12:11 PM, Lucio De Re wrote:
>>> We would be glad to work further on such a C++ port with anybody who
>>> can handle the Qt end of things so anybody interested in exploring
>>> such an endeavor should discuss with us.
>>
>> I have a friend who is totally sold on LLVM, but I
On Thu, 19 Apr 2012 11:32:03 BST Charles Forsyth
wrote:
> I wasn't too worried about getting a file system interface to it.
> I'd supposed that would be tedious (from the size of the language) but
> straightforward, similar in principle to draw(2).
A filesystem interface seems to simplify thing
> We would be glad to work further on such a C++ port with anybody who
> can handle the Qt end of things so anybody interested in exploring
> such an endeavor should discuss with us.
I have a friend who is totally sold on LLVM, but I note that it is
itself written in C++, so bootstrapping would be
On Apr 18, 2012, at 2:05 PM, arn...@skeeve.com wrote:
>>> 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
>> c
I wasn't too worried about getting a file system interface to it.
I'd supposed that would be tedious (from the size of the language) but
straightforward, similar in principle to draw(2).
Draw's programming interface can, however, present Images, Screens,
Points, Rectangles, Screens, Fonts, and so o
On Apr 19, 2012, at 1:46 AM, Charles Forsyth wrote:
> "But wait!", I hear you cry. State, callbacks, no data structures to
> speak of, ... why don't we look
> at how they handle this stuff in ... Haskell! (Monads, and a learning
> curve, though you can then build
> up something that's not entirely
On 19 April 2012 09:16, Joseph Stewart wrote:
>
> Anyone here know if it's a model to learn from?
Another glance, and I'd say it's similar to the others (except for the
onXYZ style of programming).
Because GL is fairly big and complicated, everyone copies the original
interface conventions preci
I've intended to see if I can glean any wisdom from the Android interface
to OpenGL but have had neither the time nor motivation.
Anyone here know if it's a model to learn from?
-joe
On Thu, Apr 19, 2012 at 5:10 PM, Charles Forsyth
wrote:
> OpenGL (within its scope) covers several platforms at
OpenGL (within its scope) covers several platforms at once, and anyway has
to be handled somehow.
Early in Inferno's history, I looked at the then version OpenGL but since at
the time it kept drawing state hidden (similar to PostScript), and largely
global, and the
designers hadn't discovered data
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:
On Tue, Apr 17, 2012 at 9:07 PM, John Floren wrote:
> On Tue, Apr 17, 2012 at 5:26 PM, wrote:
>>> I was thinking along the lines of http://lsub.org/ls/octopus.html, myself,
>>> using a child of Inferno.
>>
>> Yeah, sound like interesting.
>> Can I try this octopus on some of the PC still now?
>>
On Tue, Apr 17, 2012 at 5:26 PM, wrote:
>> I was thinking along the lines of http://lsub.org/ls/octopus.html, myself,
>> using a child of Inferno.
>
> Yeah, sound like interesting.
> Can I try this octopus on some of the PC still now?
> because I didn't do it, and have no idea of this.
>
> Whe I
> I was thinking along the lines of http://lsub.org/ls/octopus.html, myself,
> using a child of Inferno.
Yeah, sound like interesting.
Can I try this octopus on some of the PC still now?
because I didn't do it, and have no idea of this.
Whe I tried inferno, I god bad feeling of its gui (sorry all
Funny, the "plan" I mentioned about the new window system
was also to provide inferno to some modern UI, retaining a simple
programmatic interface.
Since I don't have even a single line of code for this, I didn't say.
But I'm glad to see you did :)
On Apr 17, 2012, at 8:56 PM, Charles Forsyth wr
I was thinking along the lines of http://lsub.org/ls/octopus.html, myself,
using a child of Inferno.
> (3) plan9 or nix or 9front, traditional style of OS developement
> In basic, I like the (3) approarch, but undocumented device problem.
why not start with documented devices?
looks like there is at least some docs for the omap's opengl.
tristan
--
All original matter is hereby placed immedi
On Apr 17, 2012, at 10:41 AM, kokam...@hera.eonet.ne.jp wrote:
>
> Your intension is to develope two ways, one for
> server (nix), and one for terminal (like drawterm?)
>
Just to let you use your server(s) but assume that
your terminals might be running macos, linux, ios, ...
as their native sy
> I have in the todo yet another
> ui system to run on top
> of other systems. for terminals.
We have now:
(1) plan9port which is very clear where only
plan9 like user interface would be developed.
(2) inferno approach where proprietary language
is neccessary, and resists top of another O
I have in the todo yet another
ui system to run on top
of other systems. for terminals.
--
iphone kbd. excuse typos :)
On Apr 17, 2012, at 4:16 AM, kokam...@hera.eonet.ne.jp wrote:
>> http://lsub.org/ls/nix.html
>
> yeah, now I can browse individual files now,
> When I tried two days ago, on
I mean, a distributed file system on an actually distributed infrastructure
providing a ray-tracing environment across multiple cpu to a 9fs /dev/draw
has to have some potential use somewhere..
On Mon, Apr 16, 2012 at 11:53 PM, andy zerger wrote:
> I think a good start would be to establish por
I think a good start would be to establish port-projects for nearly
anything from freedesktop.org, esp nouveau, in your case.
Then, I have a question to all working for OS developement.
> Developping device drivers, such as 3D mode of nvidia card etc.,
> is very difficult now, because there is no
> http://lsub.org/ls/nix.html
yeah, now I can browse individual files now,
When I tried two days ago, onlt directories can be browsed.
Yes, I downloaded nix.tgz, and running it on my Ubuntu 11.10.
I'm also running 9front here, of course, Plan 9 itself which I'm now
writing this mail.
I retired t
2012/4/16 Noah Evans :
> There's a bit of drama going on right now. Here's what I wrote in a
> private mail to Steve Simon:
>
> I don't think anybody really liked hg from a technical standpoint.
>
> There were two reasons behind choosing it:
I thoght the disagreement was because a stupid thing lik
>
> [0] http://i.imgur.com/BFuZb.png
I hope people's sense of humour is still holding. _I_ do think it's
funny, but I would not be surprised if some sensitivities were hurt.
++L
> So what's this fork I'm hearing about?
http://9front.org/img/nofork.png
-sl
On Mon, Apr 16, 2012 at 10:32 AM, Noah Evans wrote:
> I think those of us sticking with hg are doing so more for social
> reasons than technical ones.
There are technical reasons as well. But, let it suffice to say that
the tree is forked, and let it go at that.
ron
I'd like to correct one more misunderstanding and expand a bit more.
Nix is not just work done at lsub (although I'll be the first to admit
that most of the recent work has been done at lsub), it was a
collaboration between Bell Labs, Sandia and lsub (of which my
technical contributions have been v
There's a bit of drama going on right now. Here's what I wrote in a
private mail to Steve Simon:
I don't think anybody really liked hg from a technical standpoint.
There were two reasons behind choosing it:
1. It would be trivial to get a 9vx nix distro up and running on Macs
and Linux machines.
Noah Evans wrote:
> To clarify, Nix development will be continuing at both
> nix-...@googlegroups.com and http://code.google.com/p/nix-os as well.
> The project has forked.
I don't understand what is going on. I though some people were very
unsatisfied with the rietveld code review tool offered by
Greetings.
On Mon, 16 Apr 2012 15:22:27 +0200 Francisco J Ballesteros
wrote:
> Just to say that we moved the development mailing list.
> Sorry about that.
>
> it's nix at lsub.org
> and you can subscribe by a mail to nix-request at lsub.org,
> should you want to do so.
>
> Sorry again.
Why is
To clarify, Nix development will be continuing at both
nix-...@googlegroups.com and http://code.google.com/p/nix-os as well.
The project has forked.
Noah
On Mon, Apr 16, 2012 at 12:47 PM, Francisco J Ballesteros wrote:
> Just to say that we moved the development mailing list.
> Sorry about that
Just to say that we moved the development mailing list.
Sorry about that.
it's nix at lsub.org
and you can subscribe by a mail to nix-request at lsub.org,
should you want to do so.
Sorry again.
On Apr 14, 2012, at 11:02 PM, Nemo wrote:
> Hi,
>
> just FYI,
>
> http://lsub.org/ls/nix.html
>
>
Awesome!
On Saturday, April 14, 2012, Nemo wrote:
> Hi,
>
> just FYI,
>
> http://lsub.org/ls/nix.html
>
> has links and pointers for anyone to get the
> distribution and updates and/or send changes.
>
> hth
>
>
>
Hi,
just FYI,
http://lsub.org/ls/nix.html
has links and pointers for anyone to get the
distribution and updates and/or send changes.
hth
50 matches
Mail list logo
