[Date Prev][Date Next][Thread Prev][Thread Next][Author Index][Date Index][Thread Index]
Re: Udanax Green crash, error response from back-end
- To: Berend van Berkum <berend@xxxxxxxxxx>
- Subject: Re: Udanax Green crash, error response from back-end
- From: roger gregory <roger@xxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 08 Jan 2007 11:38:27 -0800
- Cc: "udanax@xxxxxxxxxx" <udanax@xxxxxxxxxx>
- In-reply-to: <20070108162520.GA2769@xxxxxxxxxx>
- References: <20070105143654.GA4136@xxxxxxxxxx> <1168119634.5828.2.camel@rogerx2> <20070108162520.GA2769@xxxxxxxxxx>
On Mon, 2007-01-08 at 17:25 +0100, Berend van Berkum wrote:
> g and creating links
> doesn't seem to work though, I can go into edit mode and insert
> text but none of it is saved.
This one I have an immediate answer to. The trick is, you have to exit
pyxi with <alt>q , Not very friendly or intuitive, but his is a hack
demo anyway. Rather than clean it up as a demo, I've been trying to
find a real use for green, and use that to drive development.
I now have a clear idea of what to do for bebe (or backup, as subset of
bebe), and the disk allocation has to be modified for large datasets.
Disk allocation was the first thing we wrote in 1979, and it didn't
allow for more than some hundreds of megabytes of disk, it never was
intended to be the final version (we were developing on floppies and
later a 10Mbyte disk).
However until I find a real use for it, I'm not going to do much to it
except fix bitrot. I don't think the 23vs64 bit ints is such a thing,
but I might change my mind, It depends on what it takes to make it work
Your other questions I'll try to get to today, at least to confirm them.
If you fix anything, or make any good changes, send them to me and I'll
fold them back in. It shouldn't be too hard to catch the interrupt, or
the close window event, or whatever it is to make pyxi exit properly.
Maybe I'll get to that tomorrow, it should take 5 lines or so.