×

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.




David,

Under Preferences, you can go to LPEX Editor and then Appearance. Here you can change the font. Per a session about WDSCi tips with Aaron Bartell, he shared that the font of Lucinda Console-regular-8 is a fine font to use to be able to see more at once.

I'm also on a 19" monitor. I don't get as many lines as Bryce, but I do see 70 lines.

Bon Chance!
-Kurt

-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of David FOXWELL
Sent: Monday, March 15, 2010 11:43 AM
To: Rational Developer for IBM i / Websphere Development Studio Client for System i & iSeries
Subject: [WDSCI-L] 86 lines of code

-----Message d'origine-----
[mailto:midrange-l-bounces@xxxxxxxxxxxx] De la part de Bryce Martin
The main advantage of RDi over PDM/SEU is in the time to
analyze a program and produce code. If you can see 86 lines
of code (in my setup) at a time in RDi(WDSC) versus only 19
in SEU then I don't know how you can ignore the productivity
gains that gives you.

Bryce, what are your preferences set at? I only have 51 lines and I haven't found another setting that is easy on the eye. My screen is only 17", I think.

Another comparaison with the number of lines : I find that greenscreeners are less likely to use long names in their code. So you tend to get a lot more comment lines, thus amplifying even more the difference. They may be lazy about writing subprocedures as that slows them down. I still sometimes use SEU for a quick look at something, but it has to be really quick because often I have to page and page before finding any code!



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

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

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