It could, of course.could it automatically open an ARexx port as well, using BaseName?
I initially thought the Application Class should do various stuff like this, including automating certain common operations like iconification. However, during implementation it's becoming increasingly clear that this may not be such a good idea. For example, if the class automates iconification/uniconification, how will you handle situations when you need to do something specific and important before the operation takes place? For example, in applications that need to drop certain resources or pointers before going to iconified state: how will you go about it if the iconification/uniconification is handled automatically and internally by the class? It'd need something like an iconification hook, which would add complexity instead of making things more straightforward.And maybe respond to some default commands like QUIT, or anything application.library supports could be handled exactly as if it had come from there?
Another thing in question is handling various input sources (incl. ARexx) by the class' own HANDLEINPUT method. This would require coalescing message port event streams like Window Class does it (merging IDCMP and Workbench AppMessages), which is something Steven Solie seems to be strongly against. And I certainly don't want to implement a kludge.
But I'm all ears for any suggestions.