nxtcommand-developers — Forum for developers to discuss changes and improvements to iCommand.

Re: [Nxtcommand-developers] iCommand 0.5 CLDC pre2

[Stefano S. <ger...@ti...>]

Peter Joosten wrote:
> My opinion (this should be our goal, if it is practically feasible ...?):

[...]

Using preprocessor seems nice, however it brings a new issue. Suppose we 
have a source code version 2.0. Somebody writes an enhancement to such 
version, just for the "JSE side", while the "JME side" is still to be 
update. How do we release this new version? 2.1? Yes and no. It is 2.1 
from the JSE point of view, while it is still a 2.0 from the JME point 
of view.

What I want to say is that merging JME and JSE code makes sense only if 
we synchronously release the same version for both platforms. Otherwise 
it will get confused. Moreover, Javadoc generation will have to take 
into account differences between JSE and JME.

Brian, you have the final word :-)

Cheers,
Stefano.

-- 
Stefano Sanna - ger...@ti...
Personal web site: http://www.gerdavax.it
AIM: gerdavax - Skype: gerdavax - Callsign: IS0DZE

Re: [Nxtcommand-developers] iCommand 0.5 CLDC pre2

[Stefano S. <ger...@ti...>]

Brian Bagnall wrote:
> 
> Could we keep the same source tree but just have two seperate releases: one 
> compiled for standard JVM and one compiled specifically for JME? (2 
> different downloads on the home page but one common source code base).  Some 
> of the other classes would be useless to the JME build and could be excluded 
> with the ANT-build script.

I experienced that it is better to separate code for JME and JSE, 
however it is ok for me to try the pre-processing way.

Stefano.

-- 
Stefano Sanna - ger...@ti...
Personal web site: http://www.gerdavax.it
AIM: gerdavax - Skype: gerdavax - Callsign: IS0DZE

Re: [Nxtcommand-developers] iCommand 0.5 CLDC pre2

[Brian B. <bba...@mt...>]

Hi Peter,

SJPP looks good. We probably won't have to use many preprocessor commands 
anyway - mostly the import I'm guessing, and the code that chooses which 
NXTComm to use. When you say it works with Eclipse, do you mean it works as 
a sort of plugin?

- Brian

----- Original Message ----- 
From: "Peter Joosten" <ptg...@ch...>
To: "iCommand Developers" <nxt...@li...>
Sent: Sunday, December 03, 2006 9:42 PM
Subject: Re: [Nxtcommand-developers] iCommand 0.5 CLDC pre2


> My opinion (this should be our goal, if it is practically feasible ...?):
>
> 1. One source tree for the icommand library using preprocessor macros
>   to differentiate between the execution environments.
> 2. Applications using the icommand library should be in seperate projects
>   These projects may have NXTComm implementations, because in my opinion
>   NXTComm implementations do not belong to the (core) icommand library.
>   (For convenience we will keep the "i386" NXTComm implementations where
>   they are.)
>   These projects however will have a dependency on the icommand
>   project, and should not contain a (modified) copy of the icommand
> sources.
>   Platform specific bytecode can be preprocessed/compiled from the 
> icommand
> source tree.
>
> Have look at the Simple Java PreProcessor (SJPP) :
> http://www.vortoj.com/sjpp/readme.html
>
> 1. I have a file pp.charset.properties in my home directory:
> charset = PRJ-J2SE \
>          PRJ-J2ME
>
> PRJ-J2SE.defines = J2SE
> PRJ-J2ME.defines = J2ME
> -----------------------
> 2. I have a java source that looks like this, when I open it with a text
> editor (notepad)
>
> public class Sample {
>
> public static void main(String[] args) {
> #ifdef J2ME
> System.out.println("J2ME");
> #endif
> #ifdef J2SE
> System.out.println("J2SE");
> #endif
> }
> }
>
> 3. But when I open the java source and I set the encoding of the project 
> to
> PRJ-J2ME
>   in the IDE it looks like (all non-J2ME code commented out):
>
> public class Sample {
>
> public static void main(String[] args) {
> //~#ifdef J2ME
> System.out.println("J2ME");
> //~#endif
> //~#ifdef J2SE
> //~ System.out.println("J2SE");
> //~#endif
> }
> }
>
> So with this preprocessor You do not first have to gerenerate platform
> specific
> source code, in order to run your program within the ide. I have tested 
> SJPP
> with Eclipse and NetBeans. Eclipse: OK. NetBeans: Nearly OK. It gives an
> error
> at the last statement of the code. I you delete the invisible character
> after
> the statement and then add a space, the error disappears. I think this is 
> an
> error in the sjpp generating some strange invisible character at the end
> (EOF ?).
> I will have to look into this. Maybe there are some better preprocessors,
> but this is the best I have found so far. With the other pre-processors I
> have
> found, you first have to generate the platform specific source code, 
> before
> you can
> run your application. I do not like that. Whether it's a good idea to use 
> a
> preprocessor ? It will depend on the preprocessors functionality.
>
> Peter Joosten.
>
>> -----Original Message-----
>> From: nxt...@li...
>> [mailto:nxt...@li...]On Behalf Of
>> Brian Bagnall
>> Sent: Sunday, December 03, 2006 10:40 PM
>> To: iCommand Developers
>> Subject: Re: [Nxtcommand-developers] iCommand 0.5 CLDC pre2
>>
>>
>> ----- Original Message -----
>> From: "Stefano Sanna" <ger...@ti...>
>> >>
>> >> If that is the case, maybe the best thing to do would be to use the
>> >> NXTComm interface, creating NXTCommCLDC. The user can choose
>> to use CLDC
>> >> via the icommand.properties file setting. So far we have NXTCommRXTX,
>> >> NXTCommBluez, and NXTCommSun (using the Java Communications API). It
>> >> looks like your changes to the code are exclusively in the
>> NXTComm class.
>> >
>> > I changed code in the Properties class and others. Even if we use
>> > different implementations for NXTComm interface, the bytecode
>> for standard
>> > edition will be not compatible with JME devices. In other
>> words, once the
>> > code as been modified, it must be compiled especially for the
>> JME target.
>> > The same is required for libraries.
>> >
>> > That's why I suggest to have to source tree for JSE and JME. It
>>
>> Could we keep the same source tree but just have two seperate
>> releases: one
>> compiled for standard JVM and one compiled specifically for JME? (2
>> different downloads on the home page but one common source code
>> base).  Some
>> of the other classes would be useless to the JME build and could
>> be excluded
>> with the ANT-build script.
>>
>> - 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
> 

[Nxtcommand-developers] off-topic

[Peter J. <ptg...@ch...>]

I am not a native speaker / writer, so I googled for the word "whether" that
I used in my previous e-mail.

I ran into:

The climate is made up of “weather”; whether it is nice out depends on
whether it is raining or not. A wether is just a castrated sheep.

(which I think is rather funny).

It's a quote from "Common Errors in English"
http://wsu.edu/~brians/errors/errors.html

I probably should by the book.

Peter Joosten.

Re: [Nxtcommand-developers] iCommand 0.5 CLDC pre2

[Peter J. <ptg...@ch...>]

My opinion (this should be our goal, if it is practically feasible ...?):

1. One source tree for the icommand library using preprocessor macros
   to differentiate between the execution environments.
2. Applications using the icommand library should be in seperate projects
   These projects may have NXTComm implementations, because in my opinion
   NXTComm implementations do not belong to the (core) icommand library.
   (For convenience we will keep the "i386" NXTComm implementations where
   they are.)
   These projects however will have a dependency on the icommand
   project, and should not contain a (modified) copy of the icommand
sources.
   Platform specific bytecode can be preprocessed/compiled from the icommand
source tree.

Have look at the Simple Java PreProcessor (SJPP) :
http://www.vortoj.com/sjpp/readme.html

1. I have a file pp.charset.properties in my home directory:
charset = PRJ-J2SE \
          PRJ-J2ME

PRJ-J2SE.defines = J2SE
PRJ-J2ME.defines = J2ME
-----------------------
2. I have a java source that looks like this, when I open it with a text
editor (notepad)

public class Sample {

	public static void main(String[] args) {
#ifdef J2ME
		System.out.println("J2ME");
#endif
#ifdef J2SE
		System.out.println("J2SE");
#endif
	}
}

3. But when I open the java source and I set the encoding of the project to
PRJ-J2ME
   in the IDE it looks like (all non-J2ME code commented out):

public class Sample {

	public static void main(String[] args) {
//~#ifdef J2ME
		System.out.println("J2ME");
//~#endif
//~#ifdef J2SE
//~		System.out.println("J2SE");
//~#endif
	}
}

So with this preprocessor You do not first have to gerenerate platform
specific
source code, in order to run your program within the ide. I have tested SJPP
with Eclipse and NetBeans. Eclipse: OK. NetBeans: Nearly OK. It gives an
error
at the last statement of the code. I you delete the invisible character
after
the statement and then add a space, the error disappears. I think this is an
error in the sjpp generating some strange invisible character at the end
(EOF ?).
I will have to look into this. Maybe there are some better preprocessors,
but this is the best I have found so far. With the other pre-processors I
have
found, you first have to generate the platform specific source code, before
you can
run your application. I do not like that. Whether it's a good idea to use a
preprocessor ? It will depend on the preprocessors functionality.

Peter Joosten.

> -----Original Message-----
> From: nxt...@li...
> [mailto:nxt...@li...]On Behalf Of
> Brian Bagnall
> Sent: Sunday, December 03, 2006 10:40 PM
> To: iCommand Developers
> Subject: Re: [Nxtcommand-developers] iCommand 0.5 CLDC pre2
>
>
> ----- Original Message -----
> From: "Stefano Sanna" <ger...@ti...>
> >>
> >> If that is the case, maybe the best thing to do would be to use the
> >> NXTComm interface, creating NXTCommCLDC. The user can choose
> to use CLDC
> >> via the icommand.properties file setting. So far we have NXTCommRXTX,
> >> NXTCommBluez, and NXTCommSun (using the Java Communications API). It
> >> looks like your changes to the code are exclusively in the
> NXTComm class.
> >
> > I changed code in the Properties class and others. Even if we use
> > different implementations for NXTComm interface, the bytecode
> for standard
> > edition will be not compatible with JME devices. In other
> words, once the
> > code as been modified, it must be compiled especially for the
> JME target.
> > The same is required for libraries.
> >
> > That's why I suggest to have to source tree for JSE and JME. It
>
> Could we keep the same source tree but just have two seperate
> releases: one
> compiled for standard JVM and one compiled specifically for JME? (2
> different downloads on the home page but one common source code
> base).  Some
> of the other classes would be useless to the JME build and could
> be excluded
> with the ANT-build script.
>
> - 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

Re: [Nxtcommand-developers] iCommand 0.5 CLDC pre2

[Brian B. <bba...@mt...>]

----- Original Message ----- 
From: "Stefano Sanna" <ger...@ti...>
>
> Excellent!
>
> I'm getting close to release code for Nokia devices (some Series 60).
> May I ask you (all) what kind of Java mobile phone you have? Just to
> focus my tests on devices actually available on the iCommand community.

Hi Stefano,

I have NO mobile devices. :( Not sure what I'm waiting for seeing as they 
are so cheap and full featured. I want one with GPS, Bluetooth, Wi-Fi, 
Camera, Cell Phone, Keyboard, and Windows Mobile 5.0. Some contenders are 
UTStarcom PPC 6700 (www.utstar.com), HP iPAQ, IMate Jasjar, or Palm Treo 
700W.

BTW Are you set up to commit code to subversion yet? If not there's a doc 
here on how to do it:
http://sourceforge.net/docman/?group_id=178176

- Brian 

Re: [Nxtcommand-developers] iCommand 0.5 CLDC pre2

[Brian B. <bba...@mt...>]

----- Original Message ----- 
From: "Stefano Sanna" <ger...@ti...>
>>
>> If that is the case, maybe the best thing to do would be to use the 
>> NXTComm interface, creating NXTCommCLDC. The user can choose to use CLDC 
>> via the icommand.properties file setting. So far we have NXTCommRXTX, 
>> NXTCommBluez, and NXTCommSun (using the Java Communications API). It 
>> looks like your changes to the code are exclusively in the NXTComm class.
>
> I changed code in the Properties class and others. Even if we use 
> different implementations for NXTComm interface, the bytecode for standard 
> edition will be not compatible with JME devices. In other words, once the 
> code as been modified, it must be compiled especially for the JME target. 
> The same is required for libraries.
>
> That's why I suggest to have to source tree for JSE and JME. It

Could we keep the same source tree but just have two seperate releases: one 
compiled for standard JVM and one compiled specifically for JME? (2 
different downloads on the home page but one common source code base).  Some 
of the other classes would be useless to the JME build and could be excluded 
with the ANT-build script.

- Brian 

[Nxtcommand-developers] change in ant build scripts

[Peter J. <ptg...@ch...>]

I have just changed the ant build scripts:
In the release distribution a dist directory will be created.
Contents:
icommand.properties (moved from root dir)
icommand.jar        (moved from root dir)
icommand-src.zip    (moved from root dir)
icommand-doc.zip    (new)

The new icommand-doc.zip contains the javadocs of icommand,
and makes it possible to lookup the icommand api quickly,
while writing your own icommand program.

I am now going to checkin the changes into subversion.

Peter.

Re: [Nxtcommand-developers] Darwin

[Peter J. <ptg...@ch...>]

Stefano,

You didn't miss anything. I just found out about some kind of
open source OS X called Darwin. I am writing some kind of
manual to help Vic: ICommand & NetBeans (for Dummmies). It
shows you step by step, with screenshots, how to setup icommand,
rxtx and use it from within NetBeans. It would be nice to have
some pictures from OS X, since Vic that the platform he is using.

I know the name of a users home directory under Windows, and
Linux, but not on OS X. That kind of "problems" I run into.

I will make some 1st version of the manual to get Vic going.

Then I will work on a definitive version. For this version
it would be nice to have some images of OS X, that are equivalent
to the images of Linux and Windows in the manual.

Peter.
 

> -----Original Message-----
> From: Stefano Sanna [mailto:ger...@ti...]
> Sent: Thursday, November 30, 2006 10:18 PM
> To: ptg...@ch...
> Cc: iCommand Developers
> Subject: Re: [Nxtcommand-developers] Darwin
> 
> 
> Peter Joosten wrote:
> > Darwin is the Open Sourced core distribution of OS X
> > 
> > It can be downloaded from http://www.opensource.apple.com/darwinsource/
> > 
> > Think I am going to give it a try, as soon as I find the time.
> > 
> > This is as close as I can get to the real thing. 
> > 
> > This will enable us to test ICommand on OS X, and
> > provide better support for this platform.   
> 
> 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.
> 
> Best regards,
> Stefano.
> 
> -- 
> Stefano Sanna - ger...@ti...
> Personal web site: http://www.gerdavax.it
> AIM: gerdavax - Skype: gerdavax - Callsign: IS0DZE

Re: [Nxtcommand-developers] iCommand 0.5 CLDC pre2

[Peter J. <ptg...@ch...>]

Stefano,

Brian is the BOSS here ;-) So maybe you should wait for his GO/NOGO
I am just a humble servent. (Brain did I earn my right to vote ?)

However, I have created the icommand-bluez project, without asking.

Peter.

> -----Original Message-----
> From: Stefano Sanna [mailto:ger...@ti...]
> Sent: Thursday, November 30, 2006 10:19 PM
> To: iCommand Developers
> Cc: ptg...@ch...
> Subject: Re: [Nxtcommand-developers] iCommand 0.5 CLDC pre2
> 
> 
> Peter Joosten wrote:
> > Vote +1
> > 
> > My thougths:
> > 
> > Make a separate project in subversion:
> > 1. You need one for the gui anyway.
> > 2. You need one because you are using NetBeans instead of Eclipse.
> >    NetBeans has better support for Mobile Apllications, so it's a good
> > choice.
> > 
> > At a later moment we can have a look if it is possible the reintegrate
> > the ICommand part of your application back into the ICommand project.
> > But than still you wiil have the need for a seperate project.
> 
> Excellent!
> 
> I'm getting close to release code for Nokia devices (some Series 60). 
> May I ask you (all) what kind of Java mobile phone you have? Just to 
> focus my tests on devices actually available on the iCommand community.
> 
> Thank you.
> 
> All the best
> Stefano.
> 
> -- 
> Stefano Sanna - ger...@ti...
> Personal web site: http://www.gerdavax.it
> AIM: gerdavax - Skype: gerdavax - Callsign: IS0DZE

Re: [Nxtcommand-developers] CLDC

[Stefano S. <ger...@ti...>]

Peter Joosten wrote:
>> 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

Peter, I really appreciate your correctness and I would be very happy if
you take the sensor. You made the work, you deserve it!

Since I'm going to start a work on other accelometer-equipped device,
I'll have other stuff to play with (that is: I will be able to make some
experiments with accelerometer). It would be nice if we could share
experiences about them.

Best regards,
Stefano.

-- 
Stefano Sanna - ger...@ti...
Personal web site: http://www.gerdavax.it
AIM: gerdavax - Skype: gerdavax - Callsign: IS0DZE

Re: [Nxtcommand-developers] iCommand 0.5 CLDC pre2

[Stefano S. <ger...@ti...>]

Peter Joosten wrote:
> Vote +1
> 
> My thougths:
> 
> Make a separate project in subversion:
> 1. You need one for the gui anyway.
> 2. You need one because you are using NetBeans instead of Eclipse.
>    NetBeans has better support for Mobile Apllications, so it's a good
> choice.
> 
> At a later moment we can have a look if it is possible the reintegrate
> the ICommand part of your application back into the ICommand project.
> But than still you wiil have the need for a seperate project.

Excellent!

I'm getting close to release code for Nokia devices (some Series 60). 
May I ask you (all) what kind of Java mobile phone you have? Just to 
focus my tests on devices actually available on the iCommand community.

Thank you.

All the best
Stefano.

-- 
Stefano Sanna - ger...@ti...
Personal web site: http://www.gerdavax.it
AIM: gerdavax - Skype: gerdavax - Callsign: IS0DZE

Re: [Nxtcommand-developers] Darwin

[Stefano S. <ger...@ti...>]

Peter Joosten wrote:
> Darwin is the Open Sourced core distribution of OS X
> 
> It can be downloaded from http://www.opensource.apple.com/darwinsource/
> 
> Think I am going to give it a try, as soon as I find the time.
> 
> This is as close as I can get to the real thing. 
> 
> This will enable us to test ICommand on OS X, and
> provide better support for this platform.   

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.

Best regards,
Stefano.

-- 
Stefano Sanna - ger...@ti...
Personal web site: http://www.gerdavax.it
AIM: gerdavax - Skype: gerdavax - Callsign: IS0DZE

Re: [Nxtcommand-developers] CLDC

[Stefano S. <ger...@ti...>]

Peter Joosten wrote:
>> 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

Peter, I really appreciate your correctness and I would be very happy if 
you take the sensor. You made the work, you deserve it!

Since I'm going to start a work on other accelometer-equipped device, 
I'll have other stuff to play with (that is: I will be able to make some 
experiments with accelerometer). It would be nice if we could share 
experiences about them.

Best regards,
Stefano.

-- 
Stefano Sanna - ger...@ti...
Personal web site: http://www.gerdavax.it
AIM: gerdavax - Skype: gerdavax - Callsign: IS0DZE

[Nxtcommand-developers] Darwin

[Peter J. <ptg...@ch...>]

Darwin is the Open Sourced core distribution of OS X

It can be downloaded from http://www.opensource.apple.com/darwinsource/

Think I am going to give it a try, as soon as I find the time.

This is as close as I can get to the real thing. 

This will enable us to test ICommand on OS X, and
provide better support for this platform.   

Peter Joosten

Re: [Nxtcommand-developers] iCommand 0.5 CLDC pre2

[Peter J. <ptg...@ch...>]

Vote +1

My thougths:

Make a separate project in subversion:
1. You need one for the gui anyway.
2. You need one because you are using NetBeans instead of Eclipse.
   NetBeans has better support for Mobile Apllications, so it's a good
choice.

At a later moment we can have a look if it is possible the reintegrate
the ICommand part of your application back into the ICommand project.
But than still you wiil have the need for a seperate project.

>
> Maybe the good solution is in the middle (in italian we say: "the truth
> is in the middle"). We may start with two separate source archives,
> having in mind that if complexity grows we may switch to macro approach.
>

Re: [Nxtcommand-developers] CLDC

[Peter J. <ptg...@ch...>]

> 
> 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
 

Re: [Nxtcommand-developers] CLDC

[Brian B. <bba...@mt...>]

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
> 

Re: [Nxtcommand-developers] CLDC

[Peter J. <ptg...@ch...>]

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.
>

Re: [Nxtcommand-developers] iCommand 0.5 CLDC pre2

[Stefano S. <ger...@ti...>]

Peter Joosten wrote:
>>> Preprocessing can be done by an Ant target of de build.xml
>> [...]
>>
>>  From my point of view, porting from JSE to JME is not an automatic 
>> task, it a creative work. The developer has to substitute classes of 
> 
> I agree it can not be automated. That was not the argument. My goal
> was to prevent duplicate code. The suggestion was to use 1 "master"
> source tree with preprocessor macros, from which the several platform
> dependend source code can be generated. This is an automated process.
> You still wil have to program ALL the code between the macros yourself. 
> 
> #define CLDC
> 
> #ifdef CLDC
> // CLDC
> int lastPos = name.toString().indexOf(".") + 4;
> //CLDC
> #else
> // CLDC UNSUPPORTED
> // int lastPos = name.indexOf(".") + 4;
> // CLDC UNSUPPORTED
> #endif
> 
> Generated source:
> // CLDC
> int lastPos = name.toString().indexOf(".") + 4;
> //CLDC

OK, sorry for my misunderstaning. It seems ok. It would be good to have
an ANT task for extracting source code for a certain platform.

>> standard edition with the (more or less) equivalent of micro edition, 
>> how event he/she has to optimize code if necessary. Moreover, JME 
>> version will be split into specialized versions for different kind of 
>> devices. For instance, current version of JNXT works on Windows Mobile
> 
> You are the better judge of how much code can be reused, and if this is
> a usefull suggestion, or not. The more platforms that will be supported,
> the greater the risk of cluttering the source code with macro statements.

Maybe the good solution is in the middle (in italian we say: "the truth
is in the middle"). We may start with two separate source archives,
having in mind that if complexity grows we may switch to macro approach.

>> I suggest to keep the two separate projects: iCommand and iCommand_CLDC. 
> 
> I have no objections.
> 
>> The more iCommand gets enhanced, the more we will have to carefully port 
>> it to CLDC.
> 
> That's why I suggest to keep as much code as possible platform independend.
> If this is feasible ? For the GUI layer and bluetooth interface is not.

You are right: Bluetooth and GUI not. However, we may evaluate to use a
JSR 82
stack on desktop platform: Avetana Bluetooth for Linux and Bluecove for
Windows.
In both cases we would have the same API of JME.

Best regards,
Stefano.

-- 
Stefano Sanna - ger...@ti...
Personal web site: http://www.gerdavax.it
AIM: gerdavax - Skype: gerdavax - Callsign: IS0DZE

Best of Banana

Fratelli D'Etails

Gerda: "Mi hanno contattato per avere idee nuove..."
Dada:  "... e le vanno a chiedere proprio a te???"

Re: [Nxtcommand-developers] CLDC

[Peter J. <ptg...@ch...>]

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

Re: [Nxtcommand-developers] CLDC

[Brian B. <bba...@mt...>]

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
> 

Re: [Nxtcommand-developers] icommand, some changes and SVN write privs

[Brian B. <bba...@mt...>]

Hi Steve,

Okay, you are all signed up. I guess some of the main things we want to 
happen with iCommand are:

- Improve accuracy of Motor.forward/backward(tacho) and 
SyncMotors.left/right(tacho)

- Enable remaining System commands: IO-Map Access commands, openWriteLinear, 
openReadLinear, openWriteData, openAppendData, boot, bluetoothFactoryReset 
message. (not urgent, but might open up new possibilities for us with 
writing to the LCD screen, etc...)

- Fix up GUI for NXTDirect. Make better control panel with simple 
motor/sensor commands, battery polling, keepalive. (Chueng is working on 
this)

- Add USB support via NXTCommUSB

- Multi-Brick support? (I don't know anyone with 2 NXT's so it's hard to 
find someone to work on this)

There's also a readme file with "future improvements". Let us know what 
interests you.
BTW You will have to sign up for the developers list to get in on these 
discussions:
 https://lists.sourceforge.net/lists/listinfo/nxtcommand-developers

- Brian

----- Original Message ----- 
From: "Steve Prior" <sp...@ge...>
To: "Brian Bagnall" <bba...@mt...>
Sent: Sunday, November 26, 2006 11:53 PM
Subject: Re: [Nxtcommand-developers] icommand, some changes and SVN write 
privs


> sprior913 is my Sourceforge id.  It turns out the static access problem
> was my using sv head for the library and the last release for the samples, 
> but I'll see what else I should muck with.
>
> BTW, the other home automation piece I've been playing with lately
> is using the Asterisk open source PBX (running as part of the Trixbox
> distribution) interfacing with the rest of smarthome.  One piece
> already in place is the ability to dial a phone number into the system
> which then retrieves a customized traffic report (filtered by my system to 
> only show incidents which affect my commute) runs it through text
> to speech over the phone.  I was also playing this weekend with writing
> Java code which glues Asterisk to smarthome such that I could turn on/off 
> devices through voice phone menus.
>
> How long were you with IBM?  Where did you work?  I was in various places 
> in Westchester and Poughkeepsie NY.
>
> Steve
>
> Brian Bagnall wrote:
>> Hi Steve,
>>
>> Welcome. Your contributions would be greatly valued. Please send your 
>> Sourceforge ID and I'll sign you up for Subversion access, etc...
>>
>> BTW The home automation looks cool.
>>
>> - Brian
>>
>> ----- Original Message ----- From: "Steve Prior" <sp...@ge...>
>> To: <nxt...@li...>
>> Sent: Sunday, November 26, 2006 8:34 PM
>> Subject: [Nxtcommand-developers] icommand, some changes and SVN write 
>> privs
>>
>>
>>> I'm just getting to the entry in my TODO list which is program to the
>>> Mindstorms NXT from Java and came across icommand.
>>>
>>> I checked out the current SVN head and found there are a number of
>>> warnings displayed when using Eclipse with most warnings on (mostly
>>> unread private fields) and some warnings about static references to
>>> non-static methods (this is more serious).
>>>
>>> I was wondering if I would need to be authorized with write privs to SVN
>>> or is it just open access?  I can't say I've got a huge amount of time
>>> I can spend on icommand, but I'd like to comment out the things which
>>> are declared but never used (they can be uncommented once they are
>>> useful) and maybe take a quick crack at the static/non-static issue.
>>>
>>> By way of introduction, like Brian I'm an IBM alum and now work in the
>>> financial sector where I've been doing mostly Java for 5 years now
>>> (before that I had been doing mostly C++ for about 12 years).  For
>>> my personal programming fun I've been integrating various things into
>>> a home automation system I wrote (more on that at
>>> http://smarthome.geekster.com).  I think it would fun to use Java to
>>> control a NXT robot from the rest of my system and contribute to
>>> icommand in the process.
>>>
>>> Thanks
>>> Steve
>>>
>>>
>>> -------------------------------------------------------------------------
>>> 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
>>>
> 

Re: [Nxtcommand-developers] icommand, some changes and SVN write privs

[Brian B. <bba...@mt...>]

Hi Steve,

Welcome. Your contributions would be greatly valued. Please send your 
Sourceforge ID and I'll sign you up for Subversion access, etc...

BTW The home automation looks cool.

- Brian

----- Original Message ----- 
From: "Steve Prior" <sp...@ge...>
To: <nxt...@li...>
Sent: Sunday, November 26, 2006 8:34 PM
Subject: [Nxtcommand-developers] icommand, some changes and SVN write privs


> I'm just getting to the entry in my TODO list which is program to the
> Mindstorms NXT from Java and came across icommand.
>
> I checked out the current SVN head and found there are a number of
> warnings displayed when using Eclipse with most warnings on (mostly
> unread private fields) and some warnings about static references to
> non-static methods (this is more serious).
>
> I was wondering if I would need to be authorized with write privs to SVN
> or is it just open access?  I can't say I've got a huge amount of time
> I can spend on icommand, but I'd like to comment out the things which
> are declared but never used (they can be uncommented once they are
> useful) and maybe take a quick crack at the static/non-static issue.
>
> By way of introduction, like Brian I'm an IBM alum and now work in the
> financial sector where I've been doing mostly Java for 5 years now
> (before that I had been doing mostly C++ for about 12 years).  For
> my personal programming fun I've been integrating various things into
> a home automation system I wrote (more on that at
> http://smarthome.geekster.com).  I think it would fun to use Java to
> control a NXT robot from the rest of my system and contribute to
> icommand in the process.
>
> Thanks
> Steve
>
>
> -------------------------------------------------------------------------
> 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
> 

[Nxtcommand-developers] icommand, some changes and SVN write privs

[Steve P. <sp...@ge...>]

I'm just getting to the entry in my TODO list which is program to the
Mindstorms NXT from Java and came across icommand.

I checked out the current SVN head and found there are a number of 
warnings displayed when using Eclipse with most warnings on (mostly
unread private fields) and some warnings about static references to
non-static methods (this is more serious).

I was wondering if I would need to be authorized with write privs to SVN
or is it just open access?  I can't say I've got a huge amount of time
I can spend on icommand, but I'd like to comment out the things which
are declared but never used (they can be uncommented once they are 
useful) and maybe take a quick crack at the static/non-static issue.

By way of introduction, like Brian I'm an IBM alum and now work in the
financial sector where I've been doing mostly Java for 5 years now 
(before that I had been doing mostly C++ for about 12 years).  For
my personal programming fun I've been integrating various things into
a home automation system I wrote (more on that at 
http://smarthome.geekster.com).  I think it would fun to use Java to
control a NXT robot from the rest of my system and contribute to
icommand in the process.

Thanks
Steve