I imagine it having a template something like this:ĪRexxProxy PortName=Port/A,ARexxMessage=Msg/A,ShellCommand=Cmd/F/K The solution to both these problems is to provide an extra Shell program with URLOpen, which will handle the ARexx stuff. Multi-platform programs, where OpenURL is the only way on those other platforms, and the developer either doesn't want to introduce additional code just for OS4, or else simply doesn't understand that OS4 must be handled differently. Old programs, which won't get updated to work correctly for some reason (e.g. BUT I humbly suggest your solution is still incomplete regarding two situations:ġ. I am inclined to say that you chose the right trade-off. a web browser), a second trade-off is that it needs a second small program acting as a proxy, so as to avoid a large loading delay when opening a second URL. support being run more than once from the Shell, without the caller having to specifically check for an ARexx port). The trade-off is a slight increase in complexity of programs used by URLOpen, but this is really just making such programs work correctly (i.e. Specifically, you want to keep URLOpen as simple as possible (both implementation AND user configuration), such that there is only a single command for each program. This is all that is required for an application to successfully use the supplied launch-handler and URLOpen seems that you are advocating a different trade-off for URLOpen than what OpenURL chose. Similar to other software of its type to avoid confusion. URL configuration, the format used is up to the author of the software, however, it would be wise to use formats As each application has its own setup line in the launch-handler Normal IDOS->ReadArgs() function template. The commandline format used for such applications should be declared in the help prompt using the When the main application takes longer than two full seconds for the GUI to appear and must renderĪ splash window indicating the loading status of the main application so the user receives adequate feedback. Such a small "loader" style executable should also be used ![]() This requirement may be best implimented by using a small "loader" executable that messages/runsĪn existing instance of the application. Such action for example, using a web browser, would be to not start another GUI instance of theĪpplication, but instead open a new window or tab on the existing instance and display the supplied URL. ![]() Must support all required features within the commandline arguments, this must also include beingĪble to detect multiple instances of the same application being launched, if this were to cause issues,Īnd therefore it should take appropriate action if this situation were to occur. ![]() must also be able to operate properly via the shell commandline interface and they With the licence, whether this situation has changed in recent history, is unknown by me.Īlso, just like any other application running on AmigaOS, applications such as web browsers andĮmail clients, etc. That way, as far as I understand, it is not possible to do anything about this due to some sort of issue Arexx support will not be added to l:launch-handler or c:URLOpen, at least not by me.Īrexx is basically legacy software and parts of it are still in 68K assembly language and will have to stay
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |