|
----- Message from Edmund Reinhardt <edmund.reinhardt@xxxxxxxxxx> onsyntax
Wed, 25 Jun 2014 13:38:26 -0400 -----
To: wdsci-l@xxxxxxxxxxxx
Subject: [WDSCI-L] Should the labels in the outline view use free-form
new
Hi folks
I am revisiting the outline view labels because I need to support the
TIMESTAMP fractional seconds.information
It occurs to be that the outline labels are verbose compared to the new
free form syntax. The new free form syntax could provide more
with less screen real estate.TEMPLATE,
For example for files
myExternal: DISK Externally Described
myInternal: PRINTER Program Described
vs
myExternal: DISK(*EXT)
myInternal: PRINTER(132)
This would even allow for more keywords to be shown like EXTDESC,
QUALIFIED, ALIASshown
For fields we currently have
myField: Character (100) VARYING(4)
myUcs: UCS-2(40) VARYING(2)
myPtr: Pointer(16) PROCPTR DIM(10)
myNum: Packed Decimal (10: 2)
vs
myField: VARCHAR(100:4)
myUcs: VARUCS(40)
myPtr: POINTER(*PROC) DIM(10)
myNum: PACKED(10:2)
Here the difference is not as clear but there are many more keywords
on fields that could be obscured by the longer names.
On the other hand, the data type names are translated to your local
language and may make things like UNS (Unsigned) to be obvious.
Please let me know whether you would prefer things shown in the terser
standard free form RPG or the the Verbose translated labels?
I do not want to have a preference, I would prefer to switch and have a
single standard way of doing this.
Regards,
Edmund (E.H.) Reinhardt
Technical Architect for Rational Developer for i
Phone: 1-905-413-3125 | Home: 1-905-854-6195 IBM
E-mail: edmund.reinhardt@xxxxxxxxxx
RDi YouTube: 8200
Warden Ave
www.youtube.com/user/IBMRational#g/c/62DF24D5BCD43501 Markham,
ON L6G 1C7
Find me on: LinkedIn: Canada
http://ca.linkedin.com/in/edmundreinhardt/
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.