> I suggest that "import element" would create a virtual node that references > the external file symbolically. > Then, the import could be "scoped to the subtree", so you might import > "commons" library at the very top, and you could import more specific > "libraries" somewhere inside the tree.
Gotcha, thanks for clarifying - then it might absolutely be an alternative solution. >> a challenge to >> properly resolve a tree assuming the external modules could >> potentially be cross-referenced > Even though it sounds the most challenging task, it does not sound it is > complicated. > It should probably cache the referenced files to avoid reparsing on each > click. Sounds promising, I'll consider both options then. //Lena
