Lars Gullik Bj�nnes wrote: > | The problem is that we use this stuff all over the place. Do we > | want to make these changes before or after 1.4.x is released? > > probably not, ... even if I have a tree largely changed to use > boost::filesystem... > > but I have a feeling that boost::filesystem might be too strict.
It can't handle kpsewhich magic or any other stuff that uses environment variables to set the path to be searched. Nonetheless, I think that this is the sort of stuff that should be hidden internal to some File class. I think that the class should do whatever needs to be done to find the file and then make this available to the rest of LyX through an accessor function that returns a boost::path. The insets, graphics cache, frontend code etc would store an instance of the File class. I think that the various free functions (MakeDisplayPath etc) could be passed either a File const & or a boost::path const &; it doesn't really matter so long as File has a member function returning a boost::path. I have been thinking quite hard about this. It is what has stalled my clean-up of the InsetBibtex code :-( -- Angus
