I agree with Birgitta; those new to RDi would get confused and discouraged. We don't need that!

Regards,

Barry Colson | Sr. Programmer, Shared Services | Community Health Systems
4000 Meridian Blvd | Franklin, TN 37067 | Tel: 615.628.6719 | Fax: 615.465.3026 | http://www.chs.net


-----Original Message-----
From: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of Birgitta Hauser
Sent: Thursday, June 26, 2014 1:36 AM
To: 'Rational Developer for IBM i / Websphere Development Studio Clientfor System i & iSeries'
Subject: Re: [WDSCI-L] Should the labels in the outline view use free-form syntax

Hi,

I personally would like to see the new free form syntax.
Even better would be if the user could decide which style he wants to use.
There are still a lot of programmers outside who not even moved to free format C-Specs (and those who cannot use the new syntax because they have to compile still everything for V5R4 or even older releases).
I think the first category of programmers would be overwhelmed and the second category could get confused with the completely free syntax ... new keywords, keywords for data types etc.

Mit freundlichen Grüßen / Best regards

Birgitta Hauser

"Shoot for the moon, even if you miss, you'll land among the stars." (Les
Brown)
"If you think education is expensive, try ignorance." (Derek Bok) "What is worse than training your staff and losing them? Not training them and keeping them!"

-----Ursprüngliche Nachricht-----
Von: WDSCI-L [mailto:wdsci-l-bounces@xxxxxxxxxxxx] Im Auftrag von Edmund Reinhardt
Gesendet: Wednesday, 25.6 2014 19:38
An: wdsci-l@xxxxxxxxxxxx
Betreff: [WDSCI-L] Should the labels in the outline view use free-form syntax



Hi folks
I am revisiting the outline view labels because I need to support the new TIMESTAMP fractional seconds.
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 information with less screen real estate.
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, TEMPLATE, QUALIFIED, ALIAS

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



--
This is the Rational Developer for IBM i / Websphere Development Studio
Client for System i & iSeries (WDSCI-L) mailing list To post a message
email: WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list
options,
visit: http://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
http://archive.midrange.com/wdsci-l.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 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.