Andre Poenitz <[EMAIL PROTECTED]> writes: > > The string conversion orgies are nothing to do with a controller/view > > separation of the dialog. They're all to do with getting data between > > the dialog and the frontend. > > Not (entirely) true. It's also because frontends/* and > frontends/controllers/* are not supposed to know of actual frontend > implementations, so they have to use "kernel style strings". This in > turn means that anything in frontends/concretefrontend/* has to convert > its strings to "controller strings" as soon as it accesses the > controller or gets string data out of it.
Ah, OK. But that's not an orgy ;-) The orgy is the Mailer interface to serialize chunks of the kernel data structure to/from strings. And anyway, user interaction with the dialogs is *not* a perf bottleneck so your "kernel strings" to/from "qt strings" argument is your own "agenda" rather than any "user cries of woe". > > Given that there was a hard requirement to post data to the kernel > > from the dialog as a string, I made the interface symmetric so that > > getting data into the dialog from the kernel used a string too. > > Come on. You were already a big boy at that time, so I'd guess you > had some influence on the discussion. Actually, I'm quite happy that we serialize data in and out of the core and have a single point of access to the core. I understand that others are "less happy". What I really don't want to see is a return to the old days where kernel and gui were hopelessly intertwined. I'm sure you don't want to see that either, but I suspect that you don't give two hoots for the GUI-I thing and are turning LyX into a Qt only app. Sigh. Anyway, you're doing the work and you have to convince the other active developers that what you envision is something they want too. The views of retired devs matter only in that they can illuminate the discussion and help some opinion-forming process. Angus
