On Wednesday 09 October 2002 10:12 am, Rob Lahaye wrote: > Angus Leeming wrote: > > On Wednesday 09 October 2002 9:28 am, Jean-Marc Lasgouttes wrote: > >>Unfortunately, there is a lot of hardcoded stuff in > >> dvips/xdvi support. It would be nice to get rid of it, but > >> I am not sure how to do it. > > > > Well the obvious way to accommodate this is to drop direct > > support for dvips/xdvi completely. > > > > Instead support an external LyX script that can interpret > > these hard-coded options in the source code for whichever > > dvi converter/viewer the user desires. > > Does that also mean to forget about Allan's "comma/-" direct > input to From/To fields:
No, it was a recommendation that you should not worry too much about what happens to the data after "Apply" is pressed. You are implementing a user interface to a print dialog, so make it logical and intuitive and powerful. If commas and dashes add to the power, then use them. What we do with these PrinterParams is no business of the View. It's the Controller's business. You have mentioned that the controller is effectively assuming that this data is to be used by dvips. So be it, for the time being. If subsequently, the controller decides to abrograte some of its controlling responsibility and pass the data to an external script that can act as a common interface to any dvi viewer/converter, then so be it. I like scripts simply because they can be changed without a recompilation of the source code and are readily modifiable by a user. That doesn't mean, however, that we have to use them. It was just an idea. Angus
