Mailing-List: contact dev-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Jakarta Commons Developers List" <dev@commons.apache.org>
Received-SPF: pass (athena.apache.org: local policy)
Date: Thu, 10 Apr 2008 15:11:54 +0100 (BST)
From: Nick Burch <nick@torchbox.com>
To: Jakarta Commons Developers List <dev@commons.apache.org>
Subject: Re: j2me commons?
In-Reply-To: <f2e8eedf0804100703t6fdccea8sb1135142ee7658df@mail.gmail.com>
Message-ID: <Pine.LNX.4.58.0804101508170.28632@fluffy.internal.torchbox.com>
References: <Pine.LNX.4.58.0804101448060.28632@fluffy.internal.torchbox.com>
 <f2e8eedf0804100703t6fdccea8sb1135142ee7658df@mail.gmail.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Organization: Torchbox Ltd, Registered Company #3983354, Unit 9,
 Southill Business Park, OX7 3EW, UK

On Thu, 10 Apr 2008, James Carman wrote:
> That sounds more like something that would be a top-level-project,
> IMHO.

Possibly much longer term, if there was the interest to sustain it!

> I could see multiple modules in something like J2ME Commons. I'm sure
> there isn't a standard set of "things you want to do for j2me."  I would
> assume (having never written for the J2ME platform) that there are
> various categories of "things" you'd want to do.

Most j2me programs get passed through pre-processors which strip out
un-used classes and methods, before being packaged for the phone. So, in
theory, it wouldn't matter too much if we gathered quite a lot of code in
one library initially, as people would only end up with what they need on
the phone


(I'm not sure how much interest there will be in a j2me commons, as most
phones have very open source hostile security rules, lack of open source
friendly dev environments etc, so there might not be a huge ecosystem of
developers)

Nick

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org