Thread: [Nxtcommand-developers] CLDC
Status: Beta
Brought to you by:
bbagnall
From: Brian B. <bba...@mt...> - 2006-11-22 17:51:06
|
Hi Stefano, Just wondering how you are coming along with the CLDC code? Also, Vic Wintriss wrote Sunday and was wondering what the timeline with the NetBeans is. - Brian === Brian: Any word on getting iCommand working with NetBeans? My offer for the sensors is still good. Awhile back you said that you were coming out with a new release soon. Status? To do some of my own testing, I'd like to write a simple program that calls on a method in NXTComm. I don't think I even get past open(). With this simple program: package nxtbttest; import icommand.nxtcomm.*; import icommand.platform.nxt.*; public class Main { public static void main(String[] args) { UltrasonicSensor us = new UltrasonicSensor(Sensor.S1); } } I get the following when I try to run it: init: deps-jar: Compiling 1 source file to /Users/vwpro/NxtBtTest/build/classes compile: run: java.lang.Exception: NXTCOMM is not defined as a system Environment Variable NXTCOMM = null at icommand.nxtcomm.NXTComm.open(NXTComm.java:46) Error while connecting NXTCommand() constructor at icommand.nxtcomm.NXTCommand.<clinit>(NXTCommand.java:16) at icommand.platform.nxt.Sensor.setTypeAndMode(Sensor.java:32) at icommand.platform.nxt.I2CSensor.<init>(I2CSensor.java:20) at icommand.platform.nxt.UltrasonicSensor.<init> (UltrasonicSensor.java:13) at nxtbttest.Main.main(Main.java:10) Exception in thread "main" java.lang.NullPointerException at icommand.nxtcomm.NXTComm.sendData(NXTComm.java:105) at icommand.nxtcomm.NXTCommand.sendRequest(NXTCommand.java:617) at icommand.nxtcomm.NXTCommand.setInputMode(NXTCommand.java: 401) at icommand.platform.nxt.Sensor.setTypeAndMode(Sensor.java:32) at icommand.platform.nxt.I2CSensor.<init>(I2CSensor.java:20) at icommand.platform.nxt.UltrasonicSensor.<init> (UltrasonicSensor.java:13) at nxtbttest.Main.main(Main.java:10) Java Result: 1 BUILD SUCCESSFUL (total time: 0 seconds) I paid Sun to trouble shoot it for me, but they gave up because there was too much code behind the problem. Perhaps if I made it real simple for them, they might be able to fix it. Vic |
From: Peter J. <ptg...@ch...> - 2006-12-13 19:29:57
|
Bian, I have got here: icommand-0.5_CLDCpre2.zip Do you have a more recent version ? The instuctions are at: http://www.vortoj.com/sjpp/readme.html ;-) 1. I will make the changes in my working directory, and when I have a working setup (eclipse and netbeans) I will commit them to subversion, together with some instructions. There are not that many changes. Could you send met te latest sources! 2. I will see if there is a netbeans module for subversion support. If not, TortoiseSVN is a good option. I think Stefano is using a Mac. I hope that Mac OS X is supported. We will see. 3. Change the build script to make an icommand-cldc.jar > Which solution do you like, preprocessor or split code? Do you have the > instructions to install the preprocessor software, setup, etc...? > I'd like > to get this set up so that we can call try out the preprocessor > and see how > it works. I've got his CLDC code so maybe we could implement |
From: Peter J. <ptg...@ch...> - 2006-12-13 19:45:30
|
subversion support for netbeans: http://subversion.netbeans.org/ > > 2. I will see if there is a netbeans module for subversion support. > If not, TortoiseSVN is a good option. I think Stefano is using a Mac. > I hope that Mac OS X is supported. We will see. > |
From: Brian B. <bba...@mt...> - 2006-12-15 00:42:29
|
----- Original Message ----- From: "Peter Joosten" <ptg...@ch...> > I have got here: icommand-0.5_CLDCpre2.zip > Do you have a more recent version ? That's the one I've got. I'm not sure if Stefano has done any more work on it since then. > The instuctions are at: http://www.vortoj.com/sjpp/readme.html ;-) > > 1. I will make the changes in my working directory, and when I have > a working setup (eclipse and netbeans) I will commit them to subversion, > together with some instructions. There are not that many changes. > > Could you send met te latest sources! All my changes are commited to subversion. > 2. I will see if there is a netbeans module for subversion support. > If not, TortoiseSVN is a good option. I think Stefano is using a Mac. > I hope that Mac OS X is supported. We will see. Are you looking for subversion support for NetBeans because there is no Eclipse for MacOSX? Stefano, are you using MacOSX with NetBeans as an IDE? - Brian > 3. Change the build script to make an icommand-cldc.jar > >> Which solution do you like, preprocessor or split code? Do you have the >> instructions to install the preprocessor software, setup, etc...? >> I'd like >> to get this set up so that we can call try out the preprocessor >> and see how >> it works. I've got his CLDC code so maybe we could implement > |
From: Peter J. <ptg...@ch...> - 2006-12-15 15:35:32
|
> > Are you looking for subversion support for NetBeans because there is no > Eclipse for MacOSX? Stefano, are you using MacOSX with NetBeans as an IDE? > There IS an eclipse version for Mac OSX. I thougth Sefano was using NetBeans on OSX. That was the only reason that I was looking for subversion suppot for NetBeans. The following fragment suggests he is using Windows for CLDC. - It would be interesting to know what IDE and OS Stefano is using (?). > Maybe I missed some messages: what is it needed to do on Mac? My default > platform (outside the mobile world, which requires Windows :-( ) is Mac > OS X 10.4 on PPC platform. |
From: Peter J. <ptg...@ch...> - 2006-12-15 16:23:36
|
Supporting multiple runtime environments / platforms with different development kits, requieres different project settings. These can not coexist in 1 project. (In eclipse terms: there can only be 1 .project, 1 .classpath, and 1 .settings). Therefore each platform should have its own project(s). I suggest the next setup: project icommand-sources : contains only the java sources (with prepocessor commands) these sources are linked into the other projects as an external source folder. project icommand : the sources of icommand-sources are linked as an external source folder in this project and prepocessed & compiled according the settings of the icommand project. project icommand-cldc : the sources of icommand-sources are linked as an external source folder in this project and prepocessed & compiled according the settings of the icommand-cldc project. The name of the project "icommand-cldc" is just an example. - In this ways every project only has 1 set of files for the project settings. - In this way we can use netbeans (if requied) for one project and eclipse for another. - we have 1 source tree in the project icommand-sources - This will break the ant build system, but that can be fixed. Agree/Disagree ? Questions ? If I get a GO a start implementing it, and will integrate icommand-0.5_CLDCpre2.zip into icommand-sources. Stefano, is icommand-0.5_CLDCpre2.zip the latest version ? Peter. |
From: Brian B. <bba...@mt...> - 2006-12-16 04:56:40
|
With this setup will we still be able to make changes to iCommand code and use it "realtime" in Eclipse? Or will we have to manually run an ANT build after every change to the iCommand source? ----- Original Message ----- From: "Peter Joosten" <ptg...@ch...> To: "Brian Bagnall" <bba...@mt...>; "iCommand Developers" <nxt...@li...> Sent: Friday, December 15, 2006 10:23 AM Subject: RE: [Nxtcommand-developers] CLDC > Supporting multiple runtime environments / platforms > with different development kits, requieres different > project settings. These can not coexist in 1 project. > (In eclipse terms: there can only be 1 .project, 1 > .classpath, and 1 .settings). Therefore each platform > should have its own project(s). I suggest the next setup: > > project icommand-sources : contains only the java sources > (with prepocessor commands) these sources are linked into > the other projects as an external source folder. > > project icommand : the sources of icommand-sources are linked > as an external source folder in this project and prepocessed & > compiled according the settings of the icommand project. > > project icommand-cldc : the sources of icommand-sources are linked > as an external source folder in this project and prepocessed & > compiled according the settings of the icommand-cldc project. > > The name of the project "icommand-cldc" is just an example. > > - In this ways every project only has 1 set of files for the project > settings. > - In this way we can use netbeans (if requied) for one project and > eclipse for another. > - we have 1 source tree in the project icommand-sources > > - This will break the ant build system, but that can be fixed. > > Agree/Disagree ? Questions ? If I get a GO a start implementing it, and > will integrate icommand-0.5_CLDCpre2.zip into icommand-sources. > > Stefano, is icommand-0.5_CLDCpre2.zip the latest version ? > > Peter. > |
From: Peter J. <ptg...@ch...> - 2006-12-16 20:56:49
|
> With this setup will we still be able to make changes to iCommand > code and use it "realtime" in Eclipse? Yes. You will see sources in the projects icommand, icommand-cldc. You will edit / make changes to the sources in the projects icomand, icommand-cldc. (So for the developer the new icommand project will look and behave as before.) The differences are: 1. While it looks like you are editing the sources in icommand, icommand-cldc, you are actually editing the sources in the project icommand-sources. In this way we achieve our goal: 1 source tree. 2. The sources in projects icommand, icommand-cldc are compiled according their own project settings, which is a requirement to support the diffent platforms. Or will we have to manually run an > ANT build > after every change to the iCommand source? > > ----- Original Message ----- > From: "Peter Joosten" <ptg...@ch...> > To: "Brian Bagnall" <bba...@mt...>; "iCommand Developers" > <nxt...@li...> > Sent: Friday, December 15, 2006 10:23 AM > Subject: RE: [Nxtcommand-developers] CLDC > > > > Supporting multiple runtime environments / platforms > > with different development kits, requieres different > > project settings. These can not coexist in 1 project. > > (In eclipse terms: there can only be 1 .project, 1 > > .classpath, and 1 .settings). Therefore each platform > > should have its own project(s). I suggest the next setup: > > > > project icommand-sources : contains only the java sources > > (with prepocessor commands) these sources are linked into > > the other projects as an external source folder. > > > > project icommand : the sources of icommand-sources are linked > > as an external source folder in this project and prepocessed & > > compiled according the settings of the icommand project. > > > > project icommand-cldc : the sources of icommand-sources are linked > > as an external source folder in this project and prepocessed & > > compiled according the settings of the icommand-cldc project. > > > > The name of the project "icommand-cldc" is just an example. > > > > - In this ways every project only has 1 set of files for the project > > settings. > > - In this way we can use netbeans (if requied) for one project and > > eclipse for another. > > - we have 1 source tree in the project icommand-sources > > > > - This will break the ant build system, but that can be fixed. > > > > Agree/Disagree ? Questions ? If I get a GO a start implementing it, and > > will integrate icommand-0.5_CLDCpre2.zip into icommand-sources. > > > > Stefano, is icommand-0.5_CLDCpre2.zip the latest version ? > > > > Peter. > > > > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to > share your > opinions on IT & business topics through brief surveys - and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Nxtcommand-developers mailing list > Nxt...@li... > https://lists.sourceforge.net/lists/listinfo/nxtcommand-developers > |
From: Brian B. <bba...@mt...> - 2006-12-17 18:09:10
|
Your solution sounds good to me. I think we should go for it. ----- Original Message ----- From: "Peter Joosten" <ptg...@ch...> To: "Brian Bagnall" <bba...@mt...>; "iCommand Developers" <nxt...@li...> Sent: Saturday, December 16, 2006 2:56 PM Subject: RE: [Nxtcommand-developers] CLDC > >> With this setup will we still be able to make changes to iCommand >> code and use it "realtime" in Eclipse? > > Yes. > > You will see sources in the projects icommand, icommand-cldc. > You will edit / make changes to the sources in the projects icomand, > icommand-cldc. > (So for the developer the new icommand project will look and behave as > before.) > The differences are: > 1. While it looks like you are editing the sources in icommand, > icommand-cldc, > you are actually editing the sources in the project icommand-sources. > In this way we achieve our goal: 1 source tree. > 2. The sources in projects icommand, icommand-cldc are compiled according > their > own project settings, which is a requirement to support the diffent > platforms. > > Or will we have to manually run an >> ANT build >> after every change to the iCommand source? >> >> ----- Original Message ----- >> From: "Peter Joosten" <ptg...@ch...> >> To: "Brian Bagnall" <bba...@mt...>; "iCommand Developers" >> <nxt...@li...> >> Sent: Friday, December 15, 2006 10:23 AM >> Subject: RE: [Nxtcommand-developers] CLDC >> >> >> > Supporting multiple runtime environments / platforms >> > with different development kits, requieres different >> > project settings. These can not coexist in 1 project. >> > (In eclipse terms: there can only be 1 .project, 1 >> > .classpath, and 1 .settings). Therefore each platform >> > should have its own project(s). I suggest the next setup: >> > >> > project icommand-sources : contains only the java sources >> > (with prepocessor commands) these sources are linked into >> > the other projects as an external source folder. >> > >> > project icommand : the sources of icommand-sources are linked >> > as an external source folder in this project and prepocessed & >> > compiled according the settings of the icommand project. >> > >> > project icommand-cldc : the sources of icommand-sources are linked >> > as an external source folder in this project and prepocessed & >> > compiled according the settings of the icommand-cldc project. >> > >> > The name of the project "icommand-cldc" is just an example. >> > >> > - In this ways every project only has 1 set of files for the project >> > settings. >> > - In this way we can use netbeans (if requied) for one project and >> > eclipse for another. >> > - we have 1 source tree in the project icommand-sources >> > >> > - This will break the ant build system, but that can be fixed. >> > >> > Agree/Disagree ? Questions ? If I get a GO a start implementing it, and >> > will integrate icommand-0.5_CLDCpre2.zip into icommand-sources. >> > >> > Stefano, is icommand-0.5_CLDCpre2.zip the latest version ? >> > >> > Peter. >> > >> >> >> ------------------------------------------------------------------------- >> Take Surveys. Earn Cash. Influence the Future of IT >> Join SourceForge.net's Techsay panel and you'll get the chance to >> share your >> opinions on IT & business topics through brief surveys - and earn cash >> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV >> _______________________________________________ >> Nxtcommand-developers mailing list >> Nxt...@li... >> https://lists.sourceforge.net/lists/listinfo/nxtcommand-developers >> > |
From: Peter J. <ptg...@ch...> - 2006-12-17 22:40:33
|
In order to support multiple platforms I will make some changes to subversion. The first change I will make is to move the java sources of the icommand project to a new icommand-sources project. Actions: 1. I would ask you to finish your current work on the icommand project. 2. After this I will make the change. during this short period no commit is allowed 3. I will send an e-mail when I have finished action 2. After the change you must DELETE the icommand project in your workspace, and check out the project icommand and icommand-sources from subversion. You have to link the sources of the icommand-sources project to the icommand project. Than you can start editing the icommand sources from within the --> icommand <-- project, like before. I will send instructions how to link the sources of the icommand-sources project to the icommand project, for both eclipse and netbeans. Please let me know if you still have some work on icommand that you want to finish. I like to start with action 2 at wednesday. But if every one has commited his changes, I will start with action 2 now. Peter. |
From: Brian B. <bba...@mt...> - 2006-12-18 01:15:42
|
I have some speech stuff to check in. This brings up another question - the icommand.vision and icommand.speech packages rely on external JAR files. For speech it needs some sphinx4 jar files (2) and the Java Speech API (1 more jar). Do you think we should branch icommand.vision and icommand.speech into a seperate project in subversion? We should we just add these jars to the build-icommand/lib directory, same as rxtx and jmf. - Brian ----- Original Message ----- From: "Peter Joosten" <ptg...@ch...> To: "Brian Bagnall" <bba...@mt...>; "iCommand Developers" <nxt...@li...> Sent: Sunday, December 17, 2006 4:40 PM Subject: Supporting Multiple Platforms - Using the SJPP Simple Java PreProcessor > In order to support multiple platforms I will make some changes to > subversion. > > The first change I will make is to move the java sources of the icommand > project > to a new icommand-sources project. > > Actions: > 1. I would ask you to finish your current work on the icommand project. > 2. After this I will make the change. during this short period no commit > is > allowed > 3. I will send an e-mail when I have finished action 2. > > After the change you must DELETE the icommand project in your workspace, > and > check out the project icommand and icommand-sources from subversion. > > You have to link the sources of the icommand-sources project to the > icommand > project. Than you can start editing the icommand sources from within > the --> > icommand <-- project, like before. > > I will send instructions how to link the sources of the icommand-sources > project to the icommand project, for both eclipse and netbeans. > > Please let me know if you still have some work on icommand that you want > to > finish. > I like to start with action 2 at wednesday. But if every one has commited > his > changes, I will start with action 2 now. > > > Peter. > |
From: Steve P. <sp...@ge...> - 2006-12-18 01:58:44
|
While as a new guy I've been sitting here quietly and watching for a bit, I'll chime in on this one. It seems to me that the speech and vision functions are really host computer functions which are only related to the NXT brick itself as inputs to the host program which could influence what commands are sent to the brick. In fact it sounds like the vision and speech functions might be useful for programs which have nothing to do with NXT at all. I'd therefore make them an independent project from iCommand. Steve Brian Bagnall wrote: > I have some speech stuff to check in. This brings up another question - the > icommand.vision and icommand.speech packages rely on external JAR files. For > speech it needs some sphinx4 jar files (2) and the Java Speech API (1 more > jar). > > Do you think we should branch icommand.vision and icommand.speech into a > seperate project in subversion? We should we just add these jars to the > build-icommand/lib directory, same as rxtx and jmf. > > - Brian |
From: Peter J. <ptg...@ch...> - 2006-12-18 02:44:58
|
I think I have taken on the role of the "infrastructure" (subversion / ant, sjpp, ...) guy here, which suits me fine. So I did not have a look speech / vision packages yet. If I understand it correct vision and speach are more like lejos extension libraries. Brian, I assume since there is no Lejos NXT yet, you just run them on your PC That would be a very good reason to put them in seperate projects, and restrict the icommand project to the implementation of the Direct / System commands of the Bluetooth SDK. (If my assumption is correct, maybe it would even be better to make vision and speach part of the lejos project.) Another reason to split it up is, that Stefano is not using (yet?) any part of the vision and speach packages. So it would be nice having the option not to include them in the CLDC project(s). In the icommand-sources project i can make 3 source folders that can be linked into every other project that needs them: folder1: icommand.nxtcomm icommand.platform icommand.robotics folder2: icommand.speach folder3: icommand.vision -------------------- Your opinion please ! Should icommand.robotics in a seperate 4th folder ? Brian, I will wait for you to finish your work. Give me a sign when I can go ahead. Peter. > -----Original Message----- > From: nxt...@li... > [mailto:nxt...@li...]On Behalf Of > Steve Prior > Sent: Monday, December 18, 2006 2:59 AM > To: Brian Bagnall > Cc: iCommand Developers > Subject: Re: [Nxtcommand-developers] Supporting Multiple Platforms - > Using the SJPP Simple Java PreProcessor > > > While as a new guy I've been sitting here quietly and watching for a > bit, I'll chime in on this one. It seems to me that the speech and > vision functions are really host computer functions which are only > related to the NXT brick itself as inputs to the host program which > could influence what commands are sent to the brick. In fact it sounds > like the vision and speech functions might be useful for programs which > have nothing to do with NXT at all. > > I'd therefore make them an independent project from iCommand. > > Steve > > Brian Bagnall wrote: > > I have some speech stuff to check in. This brings up another > question - the > > icommand.vision and icommand.speech packages rely on external > JAR files. For > > speech it needs some sphinx4 jar files (2) and the Java Speech > API (1 more > > jar). > > > > Do you think we should branch icommand.vision and > icommand.speech into a > > seperate project in subversion? We should we just add these jars to the > > build-icommand/lib directory, same as rxtx and jmf. > > > > - Brian > > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to > share your > opinions on IT & business topics through brief surveys - and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Nxtcommand-developers mailing list > Nxt...@li... > https://lists.sourceforge.net/lists/listinfo/nxtcommand-developers |
From: Brian B. <bba...@mt...> - 2006-12-19 04:37:38
|
Hi Steve and Peter, >I think I have taken on the role of the "infrastructure" (subversion / ant, > sjpp, ...) > guy here, which suits me fine. So I did not have a look speech / vision > packages yet. > > If I understand it correct vision and speach are more like lejos extension > libraries. > Brian, I assume since there is no Lejos NXT yet, you just run them on your > PC They will always be run from PC since there's no microphone for the NXT and not enough memory. Lego released a Vision package for the RCX and Lawrie Griffiths did a similar package (the Vision package adapted for iCommand) in Java. Basically robot-helper packages (like Navigation) that makes it easy for people to do advanced robot tasks. > That would be a very good reason to put them in seperate projects, and > restrict the > icommand project to the implementation of the Direct / System commands of > the Bluetooth SDK. > > (If my assumption is correct, maybe it would even be better to make vision > and speach part of > the lejos project.) > > Another reason to split it up is, that Stefano is not using (yet?) any > part > of the vision and > speach packages. So it would be nice having the option not to include them > in the CLDC project(s). > > In the icommand-sources project i can make 3 source folders that can be > linked into every > other project that needs them: > > folder1: > icommand.nxtcomm > icommand.platform > icommand.robotics > > folder2: > icommand.speach > folder3: > icommand.vision > > -------------------- > Your opinion please ! > Should icommand.robotics in a seperate 4th folder ? I changed the icommand.robotics to icommand.navigation (haven't committed yet). Could speech, vision and navigation all go in folder 2? If some of these packages don't work out very well we can turf them later or try something else. - Brian |
From: Peter J. <ptg...@ch...> - 2006-11-22 20:07:35
|
On Wed, 2006-11-22 at 11:50 -0600, Brian Bagnall wrote: > Hi Stefano, > > Just wondering how you are coming along with the CLDC code? Also, Vic > Wintriss wrote Sunday and was wondering what the timeline with the NetBeans > is. >From one of the previous mails I understand that Vic only wants to be able to write and run icommand programs from within Netbeans. He does not any new Netbeans mode to be written. My 1st tought is "easy money", but I may be wrong. I can have a look into this, but I do not want to get into a race with Stefano for the sensor "trofee". I shall have a look. If I come up with a solution, I shall contact Stefano first. I am not in for the price, give it to person who is (voluntary) involved in teaching kids Robotics. Please add the 2 lines NXTCommand.open() and NXTCommand.close() in your code program. NXTCommand.close() is part of icommand for as long as i know icommand, NXTCommand.open() was introduced in the last release 0.5 package nxtbttest; > > import icommand.nxtcomm.*; > import icommand.platform.nxt.*; > > public class Main > { > public static void main(String[] args) > { NXTCommand.open(); // at the start of the program execution. > UltrasonicSensor us = new UltrasonicSensor(Sensor.S1); NXTCommand.close(); // at the end of the program execution > } > } > |
From: Peter J. <ptg...@ch...> - 2006-11-22 22:02:53
|
I am talking nonsense, NXTCommand.open() will (probably) be introduced in v0.6. So forget about the NXTCommand.open() command. In v0.5 the following change was introduced. In v0.4 the NXTCOMM environment variable was used to set the serial port to use for bluetooth. In v0.5 this no longer works. In v0.5 we introduced a file "icommand.properties". In this file the property nxtcomm should be set to the serial port for bluetooth. In the distribution is included a file IMPORTANT.txt where this is explained. See also the instructions in README.txt, and have a look at the icommand.properties file in the distribution. Peter Joosten. > > Please add the 2 lines NXTCommand.open() and NXTCommand.close() > in your code program. NXTCommand.close() is part of icommand for as > long as i know icommand, NXTCommand.open() was introduced in the last > release 0.5 > > > package nxtbttest; > > > > import icommand.nxtcomm.*; > > import icommand.platform.nxt.*; > > > > public class Main > > { > > public static void main(String[] args) > > { > NXTCommand.open(); // at the start of the program execution. > > > UltrasonicSensor us = new UltrasonicSensor(Sensor.S1); > > NXTCommand.close(); // at the end of the program execution > > } > > } > > > > > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to > share your > opinions on IT & business topics through brief surveys - and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Nxtcommand-developers mailing list > Nxt...@li... > https://lists.sourceforge.net/lists/listinfo/nxtcommand-developers |
From: Peter J. <ptg...@ch...> - 2006-11-22 20:27:46
|
I just saw the last part of the message. Please save your money. Every "average" Java programmer should be able to solve this problem, if he is willing to have a look at the code. Communicating and solving the problem over the phone is another thing. > I paid Sun to trouble shoot it for me, but they gave up because there > was too much code behind the problem. Perhaps if I made it real > simple for them, they might be able to fix it. > > Vic |
From: Stefano S. <ger...@ti...> - 2006-11-22 22:59:35
|
Hi Brian, hi all! :-) Brian Bagnall wrote: > Hi Stefano, > > Just wondering how you are coming along with the CLDC code? CLDC porting of iCommand 0.5... is here! I'm very sorry for this (very) late reply, but moving from Sardinia island to Rome had some drawbacks (some of them still to be solved...). Please, find a preliminary version of iCommand at: http://www.esnips.com/doc/58c447a6-b0bc-4eda-9a73-29d3c0bc0768/icommand-0.5_CLDCpre1.zip I've tried to send it to the mailing list but the message was refused. The version is called icommand-0.5_CLDCpre1 since it has been partially ported to CLDC Details: 1) JNXT (the gesture-based controller) has not been updated to iCommand 0.5; therefore I was not able to test it extensively; 2) vision package has been removed 3) ServoNavigator has been removed: I'm looking for a *easy* math library fof j2me (let me say, a mix between pure-java MIDP 1.0 approach and MIDP 2.0 float-enabled). Item (1) means that icommand-0.5_CLDCpre1 compiles for CLDC but I still have to complete tests. Tomorrow I'll send you the JNXT updated version (for Windows Mobile) and a fully tested version of iCommand_CLDC. Note about porting: a) portions of code not compatible with CLDC have been commented and marked as follows: // CLDC UNSUPPORTED /* Here is the JSE code! :-) */ // CLDC UNSUPPORTED b) code that substitutes or integrates JSE code has been commented and marked as follows: // CLDC // Here is the code for CLDC! :-) // CLDC For instance, in NXTCommand you will find: // CLDC UNSUPPORTED // int lastPos = name.indexOf(".") + 4; // CLDC UNSUPPORTED // CLDC int lastPos = name.toString().indexOf(".") + 4; //CLDC > Also, Vic > Wintriss wrote Sunday and was wondering what the timeline with the NetBeans > is. Did he write just to you or to the mailing list? I did not received his message. Best regards, Stefano. -- Stefano Sanna - ger...@ti... Personal web site: http://www.gerdavax.it AIM: gerdavax - Skype: gerdavax - Callsign: IS0DZE *** Solo chi non fa niente non sbaglia *** |
From: Brian B. <bba...@mt...> - 2006-11-25 01:10:33
|
> From one of the previous mails I understand that Vic only wants to be > able to write and run icommand programs from within Netbeans. He does > not any new Netbeans mode to be written. My 1st tought is "easy money", > but I may be wrong. I can have a look into this, but I do not want to > get into a race with Stefano for the sensor "trofee". I don't know much about Netbeans, but do we need to create seperate classes to work with Netbeans? If anyone knows, please speak up. Or does he just want tech support to allow regular iCommand code to work within an IDE? I was thinking Netbeans was a whole new thing, like JavaBeans. - Brian |
From: Peter J. <ptg...@ch...> - 2006-11-25 02:31:05
|
>I have just installed netbeans with icommand, and it would be running, if >I didn't get the infamous "gnu.io.PortInUseException" :-( at the moment. I really start to dislike rxtx :-( Netbeans is just an IDE. You only have to make icommand a library of your project within Netbeans. The program starts, but fails because of rxtx. I have put rxtx in the java extension library. You can put icommand also there, instead of configuring it as a library within you netbeans project. Peter Joosten. By the way: I am more an Eclipse user than Netbeans. My Netbeans experience is level "rookie". I do like however the Mobility pack. Build some simple program for my phone http://developer.motorola.com/ My phone doesn't support JSR-82 :-( Peter. > > I don't know much about Netbeans, but do we need to create > seperate classes > to work with Netbeans? If anyone knows, please speak up. Or does he just > want tech support to allow regular iCommand code to work within an IDE? I > was thinking Netbeans was a whole new thing, like JavaBeans. > > - Brian > |
From: Brian B. <bba...@mt...> - 2006-11-28 16:52:58
|
Hi Peter, Vic confirmed he just wants to use iCommand in the IDE. It sounds like you have the problem solved, so could you provide step-by-step instructions for him (including menu commands)? He will send you a sensor of your choice from Mindsensors.com or HiTechnic.com. - Brian ----- Original Message ----- From: "Peter Joosten" <ptg...@ch...> To: "iCommand Developers" <nxt...@li...> Sent: Friday, November 24, 2006 8:30 PM Subject: Re: [Nxtcommand-developers] CLDC > >>I have just installed netbeans with icommand, and it would be running, if >>I didn't get the infamous "gnu.io.PortInUseException" :-( at the moment. > > I really start to dislike rxtx :-( > > Netbeans is just an IDE. > You only have to make icommand a library of your project within Netbeans. > The program starts, but fails because of rxtx. > > I have put rxtx in the java extension library. You can put icommand also > there, instead of configuring it as a library within you netbeans project. > > Peter Joosten. > > By the way: I am more an Eclipse user than Netbeans. My Netbeans > experience > is > level "rookie". I do like however the Mobility pack. Build some simple > program > for my phone http://developer.motorola.com/ My phone doesn't support > JSR-82 > :-( > > Peter. > > > >> >> I don't know much about Netbeans, but do we need to create >> seperate classes >> to work with Netbeans? If anyone knows, please speak up. Or does he just >> want tech support to allow regular iCommand code to work within an IDE? I >> was thinking Netbeans was a whole new thing, like JavaBeans. >> >> - Brian >> > > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share > your > opinions on IT & business topics through brief surveys - and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Nxtcommand-developers mailing list > Nxt...@li... > https://lists.sourceforge.net/lists/listinfo/nxtcommand-developers > |
From: Peter J. <ptg...@ch...> - 2006-11-28 19:21:05
|
I will make a word document with screenshots and text, and generate a PDF from that. Maybe someone can check the document for faul language ;-) and spelling / grammatical errors, before generating the PDF. I have seen a configuration option in Netbeans to attach a zip with the javadocs to the jar with the class files. Maybe we should add such a javadocs zip to our distribution. >>I didn't get the infamous "gnu.io.PortInUseException" :-( at the moment. Until now I haven't been able to get past this error. Probably due to some bluetooth management software I have recently installed. I will revert to Windows BT support. We don't Vic to take the trouble to install the software only to end up with an RXTX error at the 1st line of his program. I will deliver the document end this week (Friday), Sunday ultimately. Hope he can wait another week. Like I have told before, I am not in for the sensor. Stefano, if you want the sensor, please grab your chance now! Since Vic is able to pay for Sun support, I wouldn't have any scrupulus taking money from him. Peter Joosten. On Tue, 2006-11-28 at 10:52 -0600, Brian Bagnall wrote: > Hi Peter, > > Vic confirmed he just wants to use iCommand in the IDE. It sounds like you > have the problem solved, so could you provide step-by-step instructions for > him (including menu commands)? He will send you a sensor of your choice from > Mindsensors.com or HiTechnic.com. > > - Brian > > ----- Original Message ----- > From: "Peter Joosten" <ptg...@ch...> > To: "iCommand Developers" <nxt...@li...> > Sent: Friday, November 24, 2006 8:30 PM > Subject: Re: [Nxtcommand-developers] CLDC > > > > > > > > I really start to dislike rxtx :-( > > > > Netbeans is just an IDE. > > You only have to make icommand a library of your project within Netbeans. > > The program starts, but fails because of rxtx. > > > > I have put rxtx in the java extension library. You can put icommand also > > there, instead of configuring it as a library within you netbeans project. > > > > Peter Joosten. > > > > By the way: I am more an Eclipse user than Netbeans. My Netbeans > > experience > > is > > level "rookie". I do like however the Mobility pack. Build some simple > > program > > for my phone http://developer.motorola.com/ My phone doesn't support > > JSR-82 > > :-( > > > > Peter. > > > > > > > >> > >> I don't know much about Netbeans, but do we need to create > >> seperate classes > >> to work with Netbeans? If anyone knows, please speak up. Or does he just > >> want tech support to allow regular iCommand code to work within an IDE? I > >> was thinking Netbeans was a whole new thing, like JavaBeans. > >> > >> - Brian > >> > > > > > > ------------------------------------------------------------------------- > > Take Surveys. Earn Cash. Influence the Future of IT > > Join SourceForge.net's Techsay panel and you'll get the chance to share > > your > > opinions on IT & business topics through brief surveys - and earn cash > > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > > _______________________________________________ > > Nxtcommand-developers mailing list > > Nxt...@li... > > https://lists.sourceforge.net/lists/listinfo/nxtcommand-developers > > > > > ------------------------------------------------------------------------- > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveys - and earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Nxtcommand-developers mailing list > Nxt...@li... > https://lists.sourceforge.net/lists/listinfo/nxtcommand-developers |
From: Peter J. <ptg...@ch...> - 2006-11-29 01:04:54
|
Another slip of the fingers on my keyboard. I think this one is quite funny. What I did mean: I do not get past the infamous "gnu.io.PortInUseException". So it's bugging me all the time. Hope this was clear from the context. > > >>I didn't get the infamous "gnu.io.PortInUseException" :-( at the moment. > > > Peter Joosten. > |
From: Brian B. <bba...@mt...> - 2006-11-29 03:12:49
|
Hi Peter, I saw your PDF preview and have to say it looks very in depth. We can include this in the distro for others who want to use the Netbeans IDE. BTW Why don't you want a sensor? There is an accelerometer sensor that looks really good (X, Y, Z axis and measures G-acceleration). There's also a compass sensor that works well. - Brian ----- Original Message ----- From: "Peter Joosten" <ptg...@ch...> To: "Brian Bagnall" <bba...@mt...> Cc: "iCommand Developers" <nxt...@li...> Sent: Tuesday, November 28, 2006 1:20 PM Subject: Re: [Nxtcommand-developers] CLDC >I will make a word document with screenshots and text, and generate a > PDF from that. Maybe someone can check the document for faul > language ;-) and spelling / grammatical errors, before generating the > PDF. > > I have seen a configuration option in Netbeans to attach a zip with the > javadocs to the jar with the class files. Maybe we should add such a > javadocs zip to our distribution. > >>>I didn't get the infamous "gnu.io.PortInUseException" :-( at the moment. > > Until now I haven't been able to get past this error. Probably due to > some bluetooth management software I have recently installed. I will > revert to Windows BT support. > > We don't Vic to take the trouble to install the software only to end up > with an RXTX error at the 1st line of his program. > > I will deliver the document end this week (Friday), Sunday ultimately. > Hope he can wait another week. > > Like I have told before, I am not in for the sensor. Stefano, if you > want the sensor, please grab your chance now! Since Vic is able to pay > for Sun support, I wouldn't have any scrupulus taking money from him. > > Peter Joosten. > > > On Tue, 2006-11-28 at 10:52 -0600, Brian Bagnall wrote: >> Hi Peter, >> >> Vic confirmed he just wants to use iCommand in the IDE. It sounds like >> you >> have the problem solved, so could you provide step-by-step instructions >> for >> him (including menu commands)? He will send you a sensor of your choice >> from >> Mindsensors.com or HiTechnic.com. >> >> - Brian >> >> ----- Original Message ----- >> From: "Peter Joosten" <ptg...@ch...> >> To: "iCommand Developers" <nxt...@li...> >> Sent: Friday, November 24, 2006 8:30 PM >> Subject: Re: [Nxtcommand-developers] CLDC >> >> >> > > >> > >> > I really start to dislike rxtx :-( >> > >> > Netbeans is just an IDE. >> > You only have to make icommand a library of your project within >> > Netbeans. >> > The program starts, but fails because of rxtx. >> > >> > I have put rxtx in the java extension library. You can put icommand >> > also >> > there, instead of configuring it as a library within you netbeans >> > project. >> > >> > Peter Joosten. >> > >> > By the way: I am more an Eclipse user than Netbeans. My Netbeans >> > experience >> > is >> > level "rookie". I do like however the Mobility pack. Build some simple >> > program >> > for my phone http://developer.motorola.com/ My phone doesn't support >> > JSR-82 >> > :-( >> > >> > Peter. >> > >> > >> > >> >> >> >> I don't know much about Netbeans, but do we need to create >> >> seperate classes >> >> to work with Netbeans? If anyone knows, please speak up. Or does he >> >> just >> >> want tech support to allow regular iCommand code to work within an >> >> IDE? I >> >> was thinking Netbeans was a whole new thing, like JavaBeans. >> >> >> >> - Brian >> >> >> > >> > >> > ------------------------------------------------------------------------- >> > Take Surveys. Earn Cash. Influence the Future of IT >> > Join SourceForge.net's Techsay panel and you'll get the chance to share >> > your >> > opinions on IT & business topics through brief surveys - and earn cash >> > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV >> > _______________________________________________ >> > Nxtcommand-developers mailing list >> > Nxt...@li... >> > https://lists.sourceforge.net/lists/listinfo/nxtcommand-developers >> > >> >> >> ------------------------------------------------------------------------- >> Take Surveys. Earn Cash. Influence the Future of IT >> Join SourceForge.net's Techsay panel and you'll get the chance to share >> your >> opinions on IT & business topics through brief surveys - and earn cash >> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV >> _______________________________________________ >> Nxtcommand-developers mailing list >> Nxt...@li... >> https://lists.sourceforge.net/lists/listinfo/nxtcommand-developers > |
From: Peter J. <ptg...@ch...> - 2006-11-30 17:05:19
|
> > BTW Why don't you want a sensor? There is an accelerometer sensor > that looks really good (X, Y, Z axis and measures G-acceleration). > There's also a compass sensor that works well. Its not that I do not want a sensor. Stefano already applied for the job, and I didn't want to take his chance to earn a sensor. I (we?) should have asked Stefano before taking over the initiative. So maybe I should ask now: Stefano, sorry for taking over the initative. My motives where not to get a sensor, but to help Vic. If you are still willing to help Vic within a reasonable period of time I will give the initiative back to you. (Waiting for an answer) Peter Joosten. 1. Independend of the outcome, I will continue to work on the "ICommand & Netbeans" manual. 2. I saw some movies demonstrating the accelerometer. You can do some very nice things with it |