|
Christmas wishlist: I would like CPO to be essentially like VAJ. Why not? Imagine prompting a subprocedure and getting a list of valid argument signitures. That would be nice. Image the editor telling me right away that an argument is the wrong type. I like how VAJ has the "format source" option, and that it is customizable (to some degree.) Why not do that in codeedit? Phil > -----Original Message----- > From: code400-l-admin@midrange.com > [mailto:code400-l-admin@midrange.com]On Behalf Of mcumming@ca.ibm.com > Sent: Wednesday, October 31, 2001 9:18 AM > To: code400-l@midrange.com > Subject: Re: CODE/400 Development Team "Considerations List" > > > I will speak with the powers that be and see what we can do. Presently I > only have my own > private list which I have started to put together and some items that > Violaine passed on to me. > I'll keep you posted. > > Michele Cummings > > WDT iSeries Development > IBM Toronto Lab > > > "SamL" <lennon_s_j@hotmail.com>@midrange.com on 10/30/2001 08:10:43 PM > > Please respond to code400-l@midrange.com > > Sent by: code400-l-admin@midrange.com > > > To: <code400-l@midrange.com> > cc: > Subject: Re: CODE/400 Development Team "Considerations List" > > > The RPG compiler developers have occasionally posted a list of possible > enhancements with the degree of difficult to implement and allowed us to > prioritize the list by spending $100. I'd like to see something similar > for Code/400. > > Here are some things I'd like to see: > > * Intelligent indenting in /FREE. > > * Improvements on handling embedded SQL. Currently it is only > "tolerated". > > - Get error messages back properly from both the pre-compile and the > compile. > > - In a C/Exec SQL C/End-Exec block put C+ at the beginning of each > inserted line. Maybe this will be superceeded if /FREE in the RPG > compiler can handle free form SQL. > > - A prompting facility would be nice. Re-use something from Ops Nav? > > * Improvements to Alt-J. Trim the statement type leading blanks off > the following line. It the result is too long, split the second line at > a word and leave the remainder on the line. I'm thinking primarily of > something that would make editing comment blocks and SQL easier. > > * Alt-S could have similar improvements. For example, if I have > something like this, which has wandered into the comment field: > c eval ALongNamedVariable=SomeThingBig + > AnotherVariable > and I Alt-S at the + I'd like it to end up like this: > > c eval ALongNamedVariable=SomeThingBig > c + AnotherVariable > not like this: > c eval ALongNamedVariable=SomeThingBig > + AnotherVariable > > OK, it's getting late--I quit for now. > > Sam > > PS: If it carries any weight, I do appreciate Code/400. I can't do > without the editor. Keep up the good work. > > ----- Original Message ----- > From: "Brian D. James" <bjames@isdsolutions.net> > To: <code400-l@midrange.com> > Sent: Tuesday, October 30, 2001 10:21 AM > Subject: CODE/400 Development Team "Considerations List" > > > Hi Michele, > > Is this list publicly available somewhere? Does the CODE/400 development > team ever solicit feedback on what the users think are the most > important > features being considered for implementation? > > Regards, > > Brian > > > -----Original Message----- > From: code400-l-admin@midrange.com > [mailto:code400-l-admin@midrange.com]On Behalf Of mcumming@ca.ibm.com > Sent: Tuesday, October 30, 2001 8:04 AM > To: code400-l@midrange.com > Subject: Re: Intelligent Indenting with /FREE > > > Sam, > I agree that intelligent indenting would be a great thing to have in the > /free blocks. I'll add it to our considerations list. > As far as the View->Indent in the /free block goes, it is working as > designed but I'll give some thought to indenting it as well. > > Thanks for your ideas! > > > Michele Cummings > > WDT iSeries Development > IBM Toronto Lab > > > _______________________________________________ > 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. > > > _______________________________________________ > 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. > > > > > _______________________________________________ > 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. > _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com
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.