Sunday, January 25, 2009, 1:42:27 PM, Hussein Shafie wrote: > Daniel Dekany wrote: >> Just in case it's missing from your TODO list... XXE should be in the >> context menu for *.xml in Windows Explorer (and thus automatically in >> other file managers). > > OK, we'll try to do that for the next release. > This already works on the Mac. We'll see how we can do it for Windows.
Great. >> If I add it manually, it still doesn't work >> properly if XXE is already running, because then it will open a new >> XXE instance instead of in a new tab. (I didn't try XXE under other >> OS-es.) > > This feature, which is not directly related to associating XXE to a > number of file types, has been implemented several years ago. Ops, sorry. But I guess the reason why you expect the user to look for it and turn it on manually is that it's not entirely reliable (as it's a dirty trick really... maybe would be better with a lock file that stores an automatically chosen port). I mean, this thing used to be, and should be always on, no option is need for this at all. If it's reliable. > Please use Options|Preferences, General section and check "Use a unique > instance of XMLmind XML Editor". This option works on all OS-es. > > See > http://www.xmlmind.com/xmleditor/_distrib/doc/help/com.xmlmind.guiutil.PreferencesEditorDialog.html#generalOptions > > [[[ > I personally use this feature all the time from the command-line (of my > Linux box). Examples: > > --- > ~$ xxe docsrc/bar/foo.xml > --- > > or > > --- > ~$ xxe -last > --- > ]]] > > >> >> (I know, incredibly enough, Java still doesn't support these. But your >> Windows distribution comes with a native launcher, xxe.exe. If that's >> home gown stuff, then there you can do the correct solution, just like >> a native Windows application. > > xxe.exe is a very simple, generic, Java launcher we use in several other > projects (after renaming the .exe and editing its associated .jstart > file, of course). Its main job is to find and use the ``right'' Java > runtime installed on a machine. > >> To cut a long story short, if the time >> comes, you may peek into the source code of WinRun4J. It calls a Java >> method with JNI to pass the file name received with Windows DDE. No >> dirty socket or lock file tricks.) >> > > Sorry, but we want XXE to remain a 100% Java[tm] application. Having a better launcher wouldn't change that... (That JNI call is just in the already native launcher program, there is no Java class around with native implementation.) -- Best regards, Daniel Dekany
