Support #4999
pre-converted Possenet
0%
History
#1 Updated by Greg Shah over 3 years ago
We use Possenet in many applications. Each time we use it, it brings a large number of problems. For example, there is a certain amount of extra configuration needed to add this and maintain it over time. We try to limit the problems by only including the minimum procedure files from Possenet. But this in itself brings problems because when we hit missing programs, we have to pull in more of Possenet in the conversion list to satisfy whatever additional part of the call graph is being accessed. This is error prone, must be figured out by testing and then causes many extra iterations of conversion to get it right.
On the other hand, we have a number of working ADM/ADM2 applications at this point all using the same Possenet version. It seems like we could take the superset of all the needed code and convert that as a separate project that is shared/used by multiple applications. This would require some changes in FWD to allow this kind of multi-project server. For example, the name mapping and environment configuration for Possenet would be outside of the customer application.
This approach would have several benefits:
- It would be more stable since it will be better tested.
- Improvements from one customer would help others.
- There would be less work to convert GUI applications.
- There would be less code to convert making each customer application conversion run a little faster.
One thing we must consider is if there are any implications for customers that customize the ADM/ADM2 template files. We would need to support that.