Home › Forums › eaDocX queries › eaXL : issues in importing sub-packages + classes › eaXL : issues in importing sub-packages + classes
Home › Forums › eaDocX queries › eaXL : issues in importing sub-packages + classes › eaXL : issues in importing sub-packages + classes
Hi Guillaume,
Thanks for your suggestion. Either could work as you outline, my personal preference would be the boolean as it minises risk i.e. no data value entered. I’ve also been thinking about some options and favour a rule based solution, for example:
If I am an element then I use the row above as follows to find my owning package:
– if it is an element then I use its parent
– if it is a package then I use it
If I am a package then I use the row above as follows to find my owning package:
– if its an element I find its parent package and then use its parent
– if its a package I use its parent
This would not involve the user entering any data into existing rows and doesn’t complicate the output. The only issue is that it doesn’t produce the same structure as you outline in that there is not a mechanism to produce subpackages.
The challenge, as always, is to make it logical, minimise the risk associated with user data entry (to avoid ending up with a mess!) whilst keeping a usable UI.
We will have a chat here – and see what we come to.
Of course, whatever decision we make will not work for everyone :unsure:
Once again thanks for your input.
Regards
Adrian
Download a free trial
Download eaTeamWorks today for several free for life features, plus no obligation, 30-day trials of all the products: eaDocX, ea Revision Manager, eaSheets, Model Expert and PortfolioManager. Discover for yourself why we sell the world’s best-selling Enterprise Architect extension.
Download