>- Enter key to split the line the behavior should be like a regular >editor, Aligned, cursor in front of the first character on the new line etc. It is already possible to make the Enter key split a line like a typical editor. Take the following path: Window>Preferences>LPEX Editor>User Key Actions In the "Key" textbox type "enter", and in the "Action" textbox type "splitLine". Kelly -----Original Message----- From: Peter Merikan [mailto:peter.merikan@xxxxxxxxxxxxxx] Sent: Friday, January 30, 2004 4:53 AM To: Websphere Development Studio Client for iSeries Subject: Re: [WDSCI-L] WDSC Wish List Add this to Santa LPEX look at JDT and see how it could be done, at least for free format. - code formatter - code generation, e.g. new member, comments etc. - refactoring, e.g. rename, extract method, change method signature etc. - syntax check in free-format - compare, make it procedure aware - be able to start in insert-mode when editing a member. - Enter key to split the line the behavior should be like a regular editor, Aligned, cursor in front of the first character on the new line etc. - Tab key should indent the line when in insert mode. free-format - skip the usage of /free and /endfree. It shouldn't be to hard make the compiler to understand that it's a free-format statement. - why not make it all-free, not just the C-spec - what's wrong with brackets?, why ENDxx when we can use brackets instead . Then it would look more like java, c# etc. - embedded sql in free-format, of course RSE, a great feature but. Add this features/changes - to be able to use environment variables, that are set on the connection, in user commands. - don't filter files that starts with a dot (.) in ifs (e.g. .profiles) iSeries projects - give us the option to use associated folder as an alternative to associated library. Target library would also be great so we can start to use ant for our builds. why not build a small compiler that can be used on the desktop to give us the possibility to really work off line. /Peter Chris_Bougher@xxxxxxxxxxxxx wrote: > I'm not sure if anyone from IBM sees this list or not but here are some > things I would like to see in the lpex editor. > > Auto-indent - automagically indent after certain words or symbols in free > format code. Maybe even a way to define which keywords-symbols. > > ie - after if;, dow;, for; etc. > > Auto-unindent - ditto for previous except unindent > > ie - after enddo;, endif;, endfor, etc. > > keyword auto correction - it would change enif; to endif; etc. > > saved macros - basically be able to save a portion of code for later > retrieval and insertion into your source file. The source should be saved > on the local system. not on the as400. > > Thats all I have so far. > > Some of these functions may be already there. If so please let me know so I > can start using them. > > Thanks > > P.S. > One other useful item would be a plug-in that would allow you to > telnet to a host system like Client access. > > Chris Bougher > > > > _______________________________________________ > This is the Websphere Development Studio Client for 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. _______________________________________________ This is the Websphere Development Studio Client for 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.
This mailing list archive is Copyright 1997-2013 by MIDRANGE dot 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 here. If you have questions about this, please contact