java.lang.NumberFormatException from java.io.Writer.write()

[billfen]

It seems to me that adding non-fundamental libraries to the default
NetRexx imports would not be appropriate.  The proper way (in my
opinion) is the appropriate manipulation of the classpath.

Once additional libraries are added to the default list, when does it
stop?  If you add Swing, then certainly adding SWT is appropriate as
well.  Then, shouldn't the Android libraries be added as well?  Or any
of who knows how many other peripheral but important libraries?

My objection is not related to Eclipse.  It is to prevent the additional
performance impact and to minimize the possibility of library conflicts.

As for Eclipse, I've just provided an update which makes the addition of
external jars and folders to the class path somewhat easier.  If an
external graphics or other library is needed, it is simply located (by
using a "browse" button) and added in a NetRexx preference page.

For example, for Android app development the appropriate Android jar is
added, thus allowing the Eclipse Android plugin and emulator to be used
with the NetRexx plugin.  It works quite smoothly including the
automatic and continuous building of an Android module.   Android apps
can be easily written entirely in NetRexx, without ever coding in Java.  
(Thanks to Kermit for sending me a sample Android app written in NetRexx
for testing.)

In addition, the ability to specify a different version of the NetRexx
translator is now provided, so custom versions can be developed and
tested.  The translator distributed with the plugin need not be used,
allowing the lastest version from NetRexx.org to be used instead.

The NetRexx AST is a tree in which each language element in the program
(e.g. statement, expression, etc.) is a node optionally with child
nodes, and each node references the related token or tokens.  The AST is
automatically generated (during parsing) based on the grammar
specification in the NetRexx plugin.  Once the AST specification settles
into a final form, an interface can be developed so that other plugins
will be able to access it.

Bill

On 10/25/2011 4:44 PM, Dave Woodman wrote:

> AST = Abstract Syntax Tree - an in-core representation of the program after it has been parsed.
>
> My thoughts were exactly that Bill's work could bear bonus fruit - once the WindowBuilder guys have generalised their tool.
>
> Dave.
>
> -----Original Message-----
> From: [hidden email] [mailto:[hidden email]] On Behalf Of Kermit Kiser
> Sent: 25 October 2011 21:29
> To: IBM Netrexx
> Subject: Re: [Ibm-netrexx] Should I bother getting "package Redbook" to work?
>
> Also strange - I had just added a change request to Kenai to add Swing
> to the default NetRexx imports to make graphics use a bit easier. But I
> was worried that Eclipse users might object if they were using SWT
> instead of Swing. Is that an issue?
>
> Is the AST a language definition? Didn't Bill create something like that
> for the Eclipse plugin?
>
> -- Kermit
>
> On 10/25/2011 9:12 AM, Dave Woodman wrote:
>> Strange that this should come up today - I am looking (as of today) at WindowBuilder in Eclipse and doing the "real" work in NetRexx, much as René suggests
>>
>> As an observation, The WindowBuilder guys reckon that their model should be extensible to any language where an Eclipse AST exists, so we may, eventually, be in a position to go native with a visual GUI designer.
>>
>>      Dave.
>>
>> -----Original Message-----
>> From: [hidden email] [mailto:[hidden email]] On Behalf Of rvjansen
>> Sent: 25 October 2011 16:28
>> To: IBM Netrexx
>> Subject: Re: [Ibm-netrexx] Should I bother getting "package Redbook" to work?
>>
>> Kenneth,
>>
>>
>> this is a good book but as you already suspected, the GUI section is
>> outdated - that is to say, everything in it still works (like AWT GUIs)
>> but you would want to look into Swing userinterfaces, or even JavaFX (or
>> a hundred other possibilities, fow which I am probably opening the door
>> to be discussed on the mailing list).
>>
>> What I personally did in a number of projects, was to use NetBeans for
>> the work of drawing the userinterface (assembling the parts of it on a
>> canvans, creating the dialog boxes etc) and let it create the event loop
>> for you, and in there use NetRexx classes to do the actual work. The
>> good integration between the two languages make for an enjoyable time
>> doing that.
>>
>> The added benefit when you do it this way is, that you can reuse the
>> NetRexx classes if the need for another interface pops up, like a JFC
>> web interface for example.
>>
>> best regards,
>>
>> René
>>
>>
>> On Tue, 25 Oct 2011 09:43:24 -0400, [hidden email]
>> wrote:
>>> International Technical Support Organization
>>> CREATING JAVA APPLICATIONS USING NETREXX
>>> September 1997
>>>
>>> Or is this obsolete? Is there some tutorial that I would benefit from
>>> faster? My goal is to convert some netrexx text oriented programs to
>>> a
>>> gui interface (currently on Windoze xp).

_______________________________________________
Ibm-netrexx mailing list
[hidden email]
Online Archive : http://ibm-netrexx.215625.n3.nabble.com/

[ThSITC]

Kenneth,

   I did find this RED-Book very valuable in learning NetRexx (1.01) years ago.

  My personal feeling is, however, that you should replace the 'awt' based samples by the more modern swingx components for screen I/O.

Thomas.
===========================================================
Am 25.10.2011 15:43, schrieb [hidden email]

International Technical Support Organization
Creating Java Applications Using NetRexx
September 1997

Or is this obsolete? Is there some tutorial that I would benefit from faster? My goal is to convert some netrexx text oriented programs to a gui interface (currently on Windoze xp).

_______________________________________________
Ibm-netrexx mailing list
[hidden email]
Online Archive : http://ibm-netrexx.215625.n3.nabble.com/

_______________________________________________
Ibm-netrexx mailing list
[hidden email]
Online Archive : http://ibm-netrexx.215625.n3.nabble.com/