Context Navigation

Changes between Initial Version and Version 1 of Ticket #4583, comment 4

initial	v1
5	5	It is sub-optimal in other cases, when you work with more limited packages:
6	6	- when you want to use the same txt files for several packages, for instance containing efficiency maps of components, or physical trajectories to be followed, and you don't like replicating them (for maintenance reasons)
7		- when you play around with packages, e.g. for teaching, and therefore you don't like to hard code the package name in the package code (~~the URI~~ must always contain the package name, AFAIK).
	7	- when you play around with packages, e.g. for teaching, and therefore you don't like to hard code the package name in the package code (modelica URIs must always contain the package name, AFAIK).
8	8
9	9	So I still believe that, in addition to loadResource, having a generic place where to put files to be just loaded (as it is with Dymola and used to be with OM) is not a bad idea. It allows avoiding to hard code absolute paths in the packages, even though the connection with resources remains a bit loose (which would be bad for libraries but is acceptable in other cases)