On Thursday 22 August 2002 11:43 am, Andre Poenitz wrote:
> On Thu, Aug 22, 2002 at 09:57:17AM +0100, Angus Leeming wrote:
> > I was thinking about this last night.
>
> Looks like you are looking for work.

Not at all. I got included on a bugzilla bug report. Anyway, John and I have 
been saying how we should have a single clean interface to fork() for ages. 
This is just a possible road map to that goal.

> What about moving the interface  dialogs <-> core  to LFUNs?

I'm off to New York tomorrow...

This is what I plan to do on my return.

The LyX Server
=============
1. Learn about pipes and sockets using some stand-alone code to experiment 
with. I have written said stand-alone code (implementing a Controller-View 
split, naturally ;-). It currently uses open(), close(), read() and write() 
for communication.
2. Implement NamedPipeStream and NamedSocketStream using said stand-alone 
code.
3. Slot NamedSocketStream into the LyX Server.

Dialogs and LFUNs
================
1. Implement LFUN_INSET_TO_LYXSERVER
2. Implement LFUN_INSET_CREATE and be able to invoke it from the LyX server.
3. Implement LFUN_INSET_MODIFY and ditto. This still needs some thing about 
(how to find the inset efficiently...)
4. Once this is working, then use LFUN_INSET_CREATE, LFUN_INSET_MODIFY in the 
frontend controllers. At this point I can also strip out many crappy, 
half-baked LFUNs
5. Implement LFUN_INSET_DIALOG_OPEN and LFUN_INSET_DIALOG_CLOSE. Again, this 
needs some thinking about as it's new functionality.
6. Further the Controllers clean-up. This will be much easier once the above 
is realised.

The two problem sets are orthogonal

> I'd be interested in using the tabular dialog for mathed, too.
> Would it be possible to use a  BufferView *  instead of a InsetTabular *?

I know almost nothing about FormTabular other than blanching at the prospect 
of splitting it into a Controller and a View. It's a horrible bloated pile of 
shit.

Angus

Reply via email to