× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.





Hello everybody
You hopefully have seen that some gooodies are coming your way soon.
We did invest in iProjects in making it easy to submit builds and get error
feedback from within the editor via shortcut keys, so your fingers never
have to leave the keyboard.
Another request was to be aple to set the associated connection and library
for a selection of multiple iProjects. This is very handy when extracting
projects from a source control system like RTC or Git.

In general when managing iProjects with source control, it is a much safer
practice to strip off sequence numbers. While this is currently available
as a preference ( Preferences>i Projects "Remove sequence number and date
fields on download"),
it is not the default. The presence of sequence numbers in source control
complicate many operations including compare. We are doing our best to
manage sequence numbers automatically in this coming release, but there are
still cases beyond our power.
I would like to make it the default to strip these sequence numbers, since
the source control system provides a much richer traceability of who
changed what, when and for what reason, than the current sequence numbers
provide.

Are there strong objections?

Thanks
Edmund


|
|
|Edmund Reinhardt
|
|Rational Developer for i
|Architect
|
|IBM
|p:
| 905 413 3125
|w:
| ibm.biz/rdi_hub e:
| edmund.reinhardt@xxxxxxxxxx
|




As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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

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.