gloomyandy wrote:I've not looked at any sort of menu system yet so please feel free to do so. Not really sure what should be in it, or how it should work really, but being able to
choose a program to run would be a start.
gloomyandy wrote:Not sure what we can do to handle things like aborting a program if it gets into trouble.
gloomyandy wrote:Also not really sure how well the EV3 would cope with having multiple instances of the JVM running. At the moment I see the menu being used to run programs that have already been developed but that you want to use on a free-standing EV3. But as I say I've not really thought about it. Maybe start a new thread to discus?
gloomyandy wrote:The command to use nfs is already in the startup script (just commented out). At the moment I mount things on /legovm but I like the idea of making it /home/lejos. I'll update things so that I use that as well. It works really well for me. Yes the EV3 is the client and my dev system (A VirtualBox image running under windows which in my case is called legovm) is the server.
gloomyandy wrote:In terms of a network I simply add it to my home network. Interesting idea to add it to your dev PC. Wouldn't work for me as my main dev system does not have wireless (it uses wired ethernet). It would be nice to have an easy way to join an ev3 to a network, but it is never going to be easy to enter PSKs via the EV3 interface.
gloomyandy wrote:Hi Sven,
I don't consider using nfs etc. as an end user solution, mainly one for now to allow people to start developing fast. The problem with any non TCP based solution is that we have to get Bluetooth or USB working and so far there has not been much progress on that, obviously you can't use a TCP based solution to set your WiFi password...
gloomyandy wrote:At the moment it takes about 10 seconds or so to start a JVM.
gloomyandy wrote:Why not have the program be a jar? Isn't that the normal Java deployment mechanism?
skoehler wrote:I still hope, that we can make the EV3 emulate a USB network card that works with the majority of operating systems. Then, we don't need to support USB via the hidapi stuff and we can use plain TCP to communicate with the EV3. Unfortunately, I can't contribute to that right now
Not sure about what to do with the bluetooth module. Is the built-in bluetooth module more general than the one inside the NXT? Or is it also limited to a certain type of device?
skoehler wrote:Wow! That's a lot! Maybe we want to switch back to TinyVM? I didn't expect that
(I'm joking about TinyVM)
skoehler wrote:The classic deployment is, that you package your own (and only your own!) classes into a JAR (or multiple JARs if you so desire) and leave the JAR files of the libraries you use as they are. That's what I intend to do in case of the EV3 as well.
skoehler wrote:However, for some reason, in contrast to the classical deployment of having multiple JAR files, the so-called "big fat JARs" have gained popularity, where you basically unpack all JARs, and then repack them into a single JAR. I don't like them.
gloomyandy wrote:skoehler wrote:Wow! That's a lot! Maybe we want to switch back to TinyVM? I didn't expect that
(I'm joking about TinyVM)
Yes it is a lot but all of the VMs I tried on the EV3 had a long start up. I suspect it is the size of the class library (at least partly). It is one of the things I've been talking to the Oracle Java folks about. I hope we can speed it up a bit. My understanding is that it also seems to take about this long on the Pi. But having a full VM is just so good, I certainly wouldn't want to lose that! Perhaps the Java 8 Compact Profiles will help with this?
gloomyandy wrote:skoehler wrote:The classic deployment is, that you package your own (and only your own!) classes into a JAR (or multiple JARs if you so desire) and leave the JAR files of the libraries you use as they are. That's what I intend to do in case of the EV3 as well.
So you do intend to package the thing up as a jar? I don't understand why you would need any extra files to tell you want to run as my understanding is that a runnable jar contains some sort of meta information that tells the VM all of that. Can't we just use that mechanism?
gloomyandy wrote:a start would be to create threads on the forum for whatever areas you are interested in. I don't think many people have an EV3 yet so it is not hard to organise. I'm going to take a quick look at adding the USB kernel modules to allow TCP over USB today. Will let you know how I get on...
Users browsing this forum: No registered users and 0 guests