|
midrange.com
Sound like the LPEX team needs to be taken behind the programming woodshed.
Clearly the design is flawed: it's bad enough we're being forced into the
same blue "application development tool" suit (read "lowest common
denominator"); now we find we're stuck with shoddy development and
programming practices. Maybe the person making the decision to allow this
rubbish ought to try coding (CODE'ing) on a regular basis to find out what
it's like at the sharp end of the stick. It's "free"? Free for whom?
The LPEX design might have been appropriate years ago, but in the era of
gigahertz PC's and Windows 2000, I find it hard to believe "performance
reasons" is anything other than a CMA ("cover my ***") excuse. Let me make
sure I understand this: we're talking about IBM's enterprise-wide text
editing solution? I wonder if the LPEX team actually uses their product...
With code like this, it's easy to understand why it's impossible to keep
CODE up on a WAN or dial-up for more than two hours without losing your
source in TMP with some meaningless name. I'd hate to know what's really
going on inside my favorite piece of code, EVFCTCPD.exe.
We might live in a house or we might live in a high-rise apartment. What
makes IBM think we should be using the same tools or techniques to construct
them?
If Microsoft introduced non-standard behavior like this, we'd be howling.
Oh, that's right...we are!
Let me go recover my source and attempt to make some money so I can feed the
doggies.
-reeve
-----Original Message-----
From: code400-l-admin@midrange.com [mailto:code400-l-admin@midrange.com]On
Behalf Of batthish@ca.ibm.com
Sent: Monday, October 21, 2002 11:48 AM
To: code400-l@midrange.com
Subject: RE: Code Extras
I think I need to clarify the design, since everyone seems to be commenting
on it.
1) When you click the 'X', CODE Editor does not CLOSE. The window is
merely hidden. This is by design for PERFORMANCE reasons, and will not be
changed.
2) When you do File->Exit, all editor processes are terminated and settings
are saved at that point.
3) If you "closed" the window using the 'X' and then shut down your
machine, the settings may not be saved as the operating system may
abnormally terminate the editor process, rather than asking it nicely to
close.
4) This behaviour comes to us "free" from the base editor that CODE builds
upon. I have requested that they change this behaviour, they have changed
some settings so that they get remembered, but they refuse to do this for
all settings for performance reasons.
Whether the CODE team will be able to override the base editor behaviour
isn't known right now.
I have heard this complaint before and we have heard your opinions here
again and we see that the general consensus is to save the settings "live"
so that even when the 'X' is pressed, settings are remembered. We will try
our best to get CODE Editor to behave itself.
Thanks,
Violaine Batthish
CODE Project Lead
batthish@ca.ibm.com IBMCA(BATTHISH)
WDT/400 page: http://www.ibm.com/software/ad/wdt400
WDT/400 Support : http://www.ibm.com/software/ad/wdt400/support
"Ric A. LuBell"
<rlubell@iointerna To:
code400-l@midrange.com
tional.com> cc:
Sent by: Subject: RE: Code Extras
code400-l-admin@mi
drange.com
10/21/2002 11:09
AM
Please respond to
code400-l
If you want an escape, then design in a question on exit or a check next to
a "Save on Exit" parameter under the File menu, like Client Access does.
Don't, however, try to sell a flaw as a feature... it diminishes your
credibility!
Sincerely,
Ric LuBell
I/O International, Inc.
-----Original Message-----
From: haklui@ca.ibm.com [mailto:haklui@ca.ibm.com]
Sent: Monday, October 21, 2002 10:21 AM
To: code400-l@midrange.com
Subject: RE: Code Extras
>>>I was hitting the big X button on the top right of windows, but if I use
>>>File -> Exit it saves the settings.
First of all, I do not know if it has been purposely designed this way or
not.
Of course, I cannot make any excuses to say that it cannot be done easily.
However, personally, I would prefer to leave the design as is, since it
provides me an escape, not to save my current session settings sometimes,
in my daily work.
Best regards,
Hak
_______________________
Hak Lui
AS/400 AD, IBM Canada Ltd.
e-mail: haklui@ca.ibm.com
_______________________________________________
This is the CODE/400 Discussion & Support (CODE400-L) mailing list
To post a message email: CODE400-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/code400-l
or email: CODE400-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/code400-l.
NOTE: WDSc for iSeries disucssion has it's own mailing list.
Information can be found at
http://lists.midrange.com/cgi-bin/listinfo/wdsc-l
_______________________________________________
This is the CODE/400 Discussion & Support (CODE400-L) mailing list
To post a message email: CODE400-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/code400-l
or email: CODE400-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/code400-l.
NOTE: WDSc for iSeries disucssion has it's own mailing list.
Information can be found at
http://lists.midrange.com/cgi-bin/listinfo/wdsc-l
_______________________________________________
This is the CODE/400 Discussion & Support (CODE400-L) mailing list
To post a message email: CODE400-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/code400-l
or email: CODE400-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/code400-l.
NOTE: WDSc for iSeries disucssion has it's own mailing list.
Information can be found at
http://lists.midrange.com/cgi-bin/listinfo/wdsc-l
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.
