 | | Re: Proposals, Bug Fixes, etc and tracking them with SourceForge
|
|
(...) Thanks for reading it. (...) I'll need time to play with this. It seems to me this is not the first time this has been mentioned in this news group. Has anybody thought of using the downloader as a means for setting the RCX id? Seems to me it (...) (23 years ago, 25-Mar-02, to lugnet.robotics.rcx.legos)
|
| |
| | Final RFC on next legOS release (would have been legOS 0.2.6)
|
|
We are now actively deciding what the next release of legOS will be. (yes there will be a name change and, likely, the numbering will change but -for now- let's call it legOS 0.2.6) I've put together a more formal description of what we know today. (...) (23 years ago, 25-Mar-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Proposals, Bug Fixes, etc and tracking them with SourceForge
|
|
I read over the proposed release changes for 0.2.6, just a few ideas. I recently picked up a second RCX and found it quite difficult to do development using legOS on two RCXs. I might just be missing something, but I had to maintain two seperate (...) (23 years ago, 24-Mar-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Proposals, Bug Fixes, etc and tracking them with SourceForge
|
|
This looks good so far Stephen. I agree with the time-to-release remarks (although I love to dive in to new code 8-) Also, I like the idea of not updating to a new compiler (as I just got this machine setup and the compiler working well). I am (...) (23 years ago, 23-Mar-02, to lugnet.robotics.rcx.legos)
|
| |
| | Name suggestion
|
|
I think I suggested this before, but how about Leg-OS. This isn't easily confusable with Lego, and allows us to keep saying "leg os". mark (23 years ago, 23-Mar-02, to lugnet.robotics.rcx.legos)
|
