× 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.



> At one point we were considering making "IFS
projects" separate from "Library based projects"
> but it sounds like you really want a merged project.

I think I'm in terminology overload. <grin> When I say 'project' I mean all of the objects I need to inspect or modify in order to deploy an end user request. A single project can easily cross platforms, operating systems, programming languages and file systems. Imagine deploying a new web service. I need to change Apache's httpd.conf (on Windows), a CL program, some DDS and RPG, a PASE ksh script, several PASE C files (it's an ASN.1 project), some Java source and some entries in a database setup file.

Nirvana would be to have all that stuff appear under one navigational item, preferably named the same as my trouble ticket number so I can track the source and object code by my internal references. To be able to click an icon to build all the objects from source would be magical indeed!

Or would two, somehow related, projects be
worthwhile? I ask because in building WDSC
> we typically have several interdependent projects
> in our workspaces. Some of these are different
project types. Having things separate like this
> is an advantage when building from components.

For a complex project it can be difficult to execute the builds in the proper order, that's for sure. We simple RPG guys have the same problem: we have to create the file before we create the program or externally defined fields don't work. :-)

I don't know what the right answer is, but the discussion is very interesting!
  --buck

As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.