From: Stephen W. <wa...@ue...> - 2003-08-27 08:37:44
|
In message <200...@in...> Geoff Youngs <g...@in...> scribbled: > On Tue, Aug 26, 2003 at 08:16:16PM +0200, Vincent Lefevre wrote: > > On Tue, Aug 26, 2003 at 19:59:44 +0200, Guido Schimmels wrote: > > > Example gThumb: > > > > <?xml version="1.0"> > > > <AppInfo> > > > <mime_types>x-directory/normal,image/jpeg,image/gif,image/png, > > > image/tiff,image/x-bmp,image/x-png,image/xpm,image/x-tga</mime_types> > > (That would be inode/directory, but I get your point). > > > The following may be better: > > > <mime_types> > > <item>x-directory/normal</item> > > <item>image/jpeg</item> > > <item>image/gif</item> > > ... > > </mime_types> > > I would ask that a few things be considered: > > 1/ The annoying need to Filer_Boot any application before you used a > file associated with it on RISC OS. This is a Bad Thing(TM). > Particularly given that automatic installation of Mime handlers, while > sometimes usefull, can lead to confusion. I think that this is meant as an install-time thing. You would need a small program which would scan the AppInfo file and add SentTo entries according to the <mime_types> elements. I'm against it being automatic, because you would have any random app you installed for a quick look muscling in on a user's setup. [snip] > > 4/ I don't know at what point the Filer reads the AppInfo.xml file - a) for the Summary element when doing tooltips b) the About element when doing Info > whether it is read on demand or when the Filer sees the application > directory (I know it is *re-read* on demand, but I'm not sure about the > other). Big AppInfo.xml files /could/ slow the Filer down when scanning > directories containing many applications. > > > None of which actually preclues using the AppInfo.xml file. > > But it would be better (IMHO) if the focus was on working towards a > shared library for ROX applications with bindings for the various > languages. So that all ROX applications are singing from the same hymn > sheet, so to speak. > > And the best start for that would be ROX-CLib (again, IMHO). There > should really be mime-type support in the library, rather than invoking > the filer via the soap interface. That is part of my plans for ROX-CLib, probably by lifting the code from the filer. ROX-Lib2 already has its own interface to the share mime database. > I have a library (which I need to > release the latest version of - it fixes a rather major bug) which is > the fullest implementation of the shared-mime-info specification that I > am aware of (Yes, it does support contents recognition and trying to > guess whether a file is binary or text). And it should have IPC > support, where DBUS would probably come in - but there should be well > defined protocols for common tasks, like loading a file, launching a > URI, so that existing processes get the information directly rather > than having to start a new process. And the library should provide an > interface for finding out other important information, such as prefered > web browser - (it's *not* my text/html handler). Binding it to text/x-uri seems like a better idea. > And there should also > be some common widgets, like a program about box InfoWin is now in ROX-CLib and ROX-Lib2. > and shared > key-bindings. That gets complicated. -- Stephen Watson Physicist Ultra Electronics Ltd - Signature Management Systems (UESMS) Tel: +44 (0)1543 878888 (switchboard) Fax: +44 (0)1543 878249 Email: wa...@ue... |