[progress Communities] [progress Openedge Abl] Forum Post: Re: Associate Product Module To...

  • Thread starter Thread starter Simon de Kraa
  • Start date Start date
Status
Not open for further replies.
S

Simon de Kraa

Guest
At the moment we have products like gui, server, tty and product modules like gui.params, server.params, tty.interface, gui.assembly etc. Total number of standard product modules is ~200. Custom objects are in product modules like abc.server.params for customer ABC. Both product modules server.params and abc.server.params are linked to the same workspace module server.params that is linked to a physical directory ./server/lib/params. Before RTB we already had the custom objects stored in a separate directory like ./gui/cus/params. When RTB was introduced we decided to move everything into the same directory like ./gui/lib/params. That works. But... We also like the idea of being able to distinguish between standard and custom objects on file system level, do diffs, use symbolic links, use the propath to manipulate behavior etc. That is the reason why we would like to introduce new workspace module like cus.server.params that is linked to ./server/cus/params. Product module gui.params will be linked to workspace module gui.params and product module abc.server.params will be linked to workspace module cus.server.params (instead of server.params).

Continue reading...
 
Status
Not open for further replies.
Back
Top