 | | Re: What would I do and why would I do what I don't want to do :)
|
|
(...) Mike, a really good post. I know the geek inside all of us wants to explore and hack away at the NXT since it is literally a new toy. But for the Developer's Program, I'm going to take a leap of faith and claim that LEGO will really like to (...) (20 years ago, 17-Jan-06, to lugnet.robotics)
|
| |
| | Re: Why Java for Robots (was NXT and bluetooth enabled phones)
|
|
(...) The point about C++ is that you can overload the array indexing mechanism and build a 'class' to implement arrays that does array bounds checking (or implements the "array" as a linked list or stores it on disk or whatever else you can (...) (20 years ago, 17-Jan-06, to lugnet.robotics)
|
| |
| | What would I do and why would I do what I don't want to do :)
|
|
(...) My first idea is porting brickOS to the nxt. That could be cool, using more memory, better motors, better sensors, even the bluetooth, wow... But... When I look at me (and at some of the answers from fellow AFOLS), I'm not shure how Mindstorms (...) (20 years ago, 17-Jan-06, to lugnet.robotics)
|
| |
| | Re: How many people signed up for the NXT Developer's Program?
|
|
(...) I would help port leJOS (i.e. Java) to NXT, redo our leJOS website and write a sequel to my first book: (URL) I vouch for Juergen Stuber and Phillippe Hurbain. Juergen is our go-to guy on the leJOS project since Jose resigned, and Phillippe (...) (20 years ago, 17-Jan-06, to lugnet.robotics)
|
| |
| | Re: How many people signed up for the NXT Developer's Program?
|
|
(...) I'd work with the LDraw community to create LDraw parts for any new parts in the NXT bill of materials. I'd create a bunch of MOCs (probably a lot of walkers) limited to the NXT set, and probably write a book of building instructions. I'd (...) (20 years ago, 17-Jan-06, to lugnet.robotics)
|
| |
| | RE: Why Java for Robots (was NXT and bluetooth enabled phones)
|
|
(...) Well what about an indexation based on a sensor value? How could your compiler know the range the sensor has? Sample: int volatile *color_sensor = (int *) 0x4000; int getColor(void) { static int color[4] = { 123, 456, 789, 111 }; return (...) (20 years ago, 17-Jan-06, to lugnet.robotics)
|
| |
| | RE: Why Java for Robots (was NXT and bluetooth enabled phones)
|
|
(...) Well what about an indexation based on a sensor value? How could your compiler know the range the sensor has? Sample: int volatile *color_sensor = (int *) 0x4000; int getColor(void) { static int color[4] = { 123, 456, 789, 111 }; return (...) (20 years ago, 17-Jan-06, to lugnet.robotics)
|
| |
| | Re: How many people signed up for the NXT Developer's Program?
|
|
(...) I'm a software engineer, and I've written and tested code in many fields- education, games, graphics hardware, and web sites. All of these give me insight that should help me thoroughly test the suitability and functionality of both the (...) (20 years ago, 17-Jan-06, to lugnet.robotics)
|
| |
| | Why Java for Robots (was NXT and bluetooth enabled phones)
|
|
(...) Why? Full Java requires it but you're not trying to make a full Java implementation. Why can't all your data be statically allocated by the compiler (not allocated at run-time)? Sure, you'd have to tweak the language a little but so what? (...) (20 years ago, 17-Jan-06, to lugnet.robotics)
|
| |
| | Why Java for Robots (was NXT and bluetooth enabled phones)
|
|
(...) I was looking into Java as a small-robot programming language and examined a few implementations. I came to the conclusion that it simply wasn't suitable. Sure you can shoehorn a cut-down version into a small processor but you've had to (...) (20 years ago, 17-Jan-06, to lugnet.robotics)
|
