On Wednesday 04 December 2002 1:47 pm, Jean-Marc Lasgouttes wrote: > >>>>> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes: > > Angus> o the xforms image loader should fail gracefully if it fails to > Angus> load a weird xpm file. > > BTW, angus, why don't we use the native pnm handler with xforms image > loader? We could disable xpm support in flimage and give image->pnm > converters. > > It seems that ppm files are larger than xpm ones (+60%), but is this > such a big problem? The gains would be faster conversion, and maybe a > more robust parser in xforms part.
The only reason I haven't disabled the xpm loader already is, believe it or not, the splash screen and the fact that we currently support xforms versions with and without flimage. If we disable xpm loading and leave the splash screen as an xpm file then most people will start off LyX with a conversion process. Ditto, if we change to a ppm file, then those 0.88 users would start off with a conversion. Assuming that xforms 1.0 /does/ come out on Friday, will we continue to support xforms < 1.0 or force people to upgrade? It'd be really nice to remove all that #ifdef mess... > Another xforms bug to add to the list: the problem with clicking on > Edit menu when File is open. I reported it in this thread > http://bob.usuf2.usuhs.mil/mailserv/list-archives/xforms-archive.2000/0529. >html and the reason for the problem is analyzed here: > http://bob.usuf2.usuhs.mil/mailserv/list-archives/xforms-archive.2000/0643. >html > > However, I guess the offending code is here for some reason, so I did > not try to remove it (which would be the easiest solution). Thanks, JMarc, I'll add it to my list. Angus
