Stefano Ghirlanda <[EMAIL PROTECTED]> writes:
| Ok, done. The "int clients" in LyXServer has been replaced by
| "vector clients". The server adds the clients names on
| "hello" messages instead of doing clients++. On "bye" messages, the server
| checks that the client is in the vector, and remov
> "Stefano" == Stefano Ghirlanda <[EMAIL PROTECTED]> writes:
Stefano> Ok, I will use the crude array in the 1.0.x patches, no
Stefano> problem. Is STL "allowed" in the development version?
It is even extensively used there.
JMarc
Hi Jean-Marc,
> I'd rather avoid to use STL stuff in 1.0.x, since it still compiles
> with old compilers which have broken STL and template support. In
> 1.1.x, the situation is different, since by the time we release it,
> the situation should have improved...
>
> Could you use a plain old link
> "Stefano" == Stefano Ghirlanda <[EMAIL PROTECTED]> writes:
Stefano> I add to #include the standard in lyxserver.h and
Stefano> in lyxserver.C, but I do not know how to make the
Stefano> necessary modifications to check for these in the configure
Stefano> stuff, sorry.
I'd rather avoid to
Hi Asger and everyone,
> There is no deadline, except that we just got the first cut at docbook support
> in, and that will need some time to be finished, and polished up before the
> 1.0.4 release.
Ok, then I have time to rewrite the server patches for the stable code.
> In particular, if it's
> Ok, can you give me a deadline? I also saw that 1.1.x uses "string"
> instead of LString and a different syntax for error streams. I have coded
> for 1.1.x, will 1.0.4 be based on that or on the 1.0.3 code?
As Jean-Marc noticed, 1.0.4 will be based on the 1.0.3 code (or specifically,
on the ly
> "Stefano" == Stefano Ghirlanda <[EMAIL PROTECTED]> writes:
Stefano> Hi Asger and everyone,
>> > If you think it's worth it, I will submit the following to this
>> list:
>>
>> Of course it is worth it! The earlier you send this, the better
>> ;-) If the patch looks good, I still think we s
> "Stefano" == Stefano Ghirlanda <[EMAIL PROTECTED]> writes:
Stefano> Hi all,
>> Speaking about lyxserver problems, there is one which bothers me
>> now: it does not work at all on Digital Unix, due to a peculiarity
>> of the select() implementation (excerpt from the man page):
>>
>> [Digita
Hi all,
> Speaking about lyxserver problems, there is one which bothers me now:
> it does not work at all on Digital Unix, due to a peculiarity of the
> select() implementation (excerpt from the man page):
>
> [Digital] Objects ready for the requested operation are those which the
> operati
Hi Asger and everyone,
> > If you think it's worth it, I will submit the following to this list:
>
> Of course it is worth it! The earlier you send this, the better ;-)
> If the patch looks good, I still think we should put it into 1.0.4
Ok, can you give me a deadline? I also saw that 1.1.x us
> "Asger" == Asger Alstrup Nielsen <[EMAIL PROTECTED]> writes:
>> I still have one concern with the LyX server code but I don't want
>> to abuse of your patience any longer. I will speak of this another
>> time.
Asger> I have patience to hear what the problem is now. I see no
Asger> reason
> I am working on a LyX client, and I have suggested a small change in the
> LyX server in order to make client implementation easier.
> If you think it's worth it, I will submit the following to this list:
[Lots of great stuff]
Of course it is worth it! The earlier you send this, the better
Hi,
I am working on a LyX client, and I have suggested a small change in the
LyX server in order to make client implementation easier. The change was
to have LyX return an INFO message even for functions not returning any
data. This means that a client can always fetch a line from the LyX output
p
13 matches
Mail list logo
