Re: [Nxtcommand-developers] CLDC

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

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