Hi Juergen, you wrote > One initial problem will be to decide what to do, > there is now so much memory that there are a lot of options: > > - Extend the existing Lejos code > - Keep 16bit pointers and all objects in RAM? A good first step > - Or go to 32bit pointers and use flash, too? Do this rewrite later > - How much flash can we use? What to put there? > - VM > - Java program code > - Classes? > - Constant objects? > - Persistent objects? > - Files? As much as possible - this list looks like a good priority order.
> - Go for some other existing Java VM? Which one? > - Open source > - Small > - Simple (no JIT) > - Real-time I don't know enough to recommend. > - Should we aim for an official Java profile, What is the advantage in the short run? > or pick our own part of the API as before? Yes, for now. After all, we are developing for a robot, not an applications server. > For a start just using the existing Lejos with the 64K RAM > would probably be easiest and fastest, and get us quite far. Sounds right to me. We would learn a lot about the NXT in doing it. The experience should help in pick among all the other options. Perhaps the quickest path to the ultimate system is to begin with something simple even if it gets replaced later. Roger ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ Lejos-discussion mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/lejos-discussion
