May be the right way to consider STARTUP is a integration of modules and
The existence of multiple xmls with STARTUP tag is really problem. The
possible way to solve problem is symlinks. Directory with symlinked
modules and STARTUP's xml.
XML-files within CLISH_PATH is good enough.
The default "main" VIEW solves nothing. Because modules doesn't know
exactly how they will be used. In my opinion the right way to use
modules are NAMESPACEs. It's not good for modules to use predefined VIEW
Consider the C programms and C libs for example. C lib has no main()
function but executable binary has. It integrates all libs. Why is it so
May be the right way is to create special klish 'profile' that list all
needed XMLs, starting VIEW and so on. User executes klish with link to
this profile. Profile can be the same as a main() for C. Or may be
profile is XML file too. But it has all needed information internally.
# clish --main=router.xml
Profile define the whole functionality of klish session.
20.11.2020 19:15, Ingo Albrecht пишет: