Welcome to the official BlackBerry Support Community Forums.

This is your resource to discuss support topics with your peers, and learn from each other.

inside custom component

Java Development

Posts: 167
Registered: ‎11-12-2008
My Device: Not Specified

Refactoring in older JDEs

[ Edited ]

I'm developing in the BlackBerry JDE 4.2.1 and am finding it pretty hard to do simple refactoring.  For those of you that are targeting older devices and therefore can't use Eclipse, how have you handled refactoring? Is manually changing classes the only option?  Also, as far as just formatting my code I've just been pasting code into Netbeans and doing Alt-Shift-F, but obviously this is a pain.


Any insight would be appreciated.  Thanks.

Message Edited by bo on 12-23-2008 02:50 PM
Message Edited by bo on 12-23-2008 02:51 PM
Posts: 1,415
Registered: ‎07-30-2008
My Device: Not Specified

Re: Refactoring in older JDEs

I'm building to 4.0.2 for all targets although I can optionally build others with conditional code.

I'm using g++ preprocessor and other command line utilities with a more or less ignorant editor

( it does have syntax highlighting but that is about it).

You could try this,

$ astyle -h |head -n 20

Artistic Style 1.15.3   (http://www.bigfoot.com/~davidsont/astyle)
                       (created by Tal Davidson, davidsont@bigfoot.com)

Usage  :  astyle [options] < Original > Beautified
          astyle [options] Foo.cpp Bar.cpp  [...]

When indenting a specific file, the resulting indented file RETAINS the
original file-name. The original pre-indented file is renamed, with a
suffix of ".orig" added to the original filename.

By default, astyle is set up to indent C/C++/C# files, with 4 spaces per
indent, a maximal indentation of 40 spaces inside continuous statements,
and NO formatting.

Option's Format:
    Long options (starting with '--') must be written one at a time.
    Short options (starting with '-') may be appended together.
    Thus, -bps4 is the same as -b -p -s4.