On Sun, Apr 06, 2003 at 10:02:04AM +0200, Alfredo Braunstein wrote:
> > If we do it async, then even the status bar is wrong. Unless we have a
> > splitter and devote a portion of the status bar to this progress bar.
> > Which I'm not sure is a grweat idea ...
>
> How would be a good solution in
John Levon wrote:
> If we do it async, then even the status bar is wrong. Unless we have a
> splitter and devote a portion of the status bar to this progress bar.
> Which I'm not sure is a grweat idea ...
How would be a good solution in such a case? A modal dialog would certainly
no be it IMHO.
On Sun, Apr 06, 2003 at 12:22:46AM +0200, Lars Gullik Bj?nnes wrote:
> | We so do not need threads.
>
> Would simplify things...
No it wouldn't, it would significantly complicate things. As Angus has
already pointed out, we already have asynchronous notification
architecture, and all that is rea
John Levon <[EMAIL PROTECTED]> writes:
| On Sat, Apr 05, 2003 at 11:22:15AM +0200, Lars Gullik Bj?nnes wrote:
|
| > I'd rather introduce some threads to lyx, and just say that all
| > platforms that does not have treading just gets the sync behaviour
| > instead.
|
| We so do not need threads.
Angus Leeming <[EMAIL PROTECTED]> writes:
| Maybe. But we already have a mechanism for non-blocking forking of processes
| which will tell us when the process has finished. So we could
| for (;;) {
| fork latex run and subsequently
| receive notification of its finish
| p
On Sat, Apr 05, 2003 at 11:22:15AM +0200, Lars Gullik Bj?nnes wrote:
> I'd rather introduce some threads to lyx, and just say that all
> platforms that does not have treading just gets the sync behaviour
> instead.
We so do not need threads.
regards
john
On Sat, Apr 05, 2003 at 11:19:49AM +0200, Lars Gullik Bj?nnes wrote:
> | > And talking about error boxes, what about nuking them and implementing
> | > instead an error log window doubly linked with the document (i.e. cliking
> | > on a log line puts the cursor within problem in the document, nav
Lars Gullik Bjønnes wrote:
> Angus Leeming <[EMAIL PROTECTED]> writes:
>
> | I suspect that you'll be able to use it as-is meaning that all you
> | really have to do is:
> | 1. Rename it to something sensible ;-)
> | 2. Move the latex parsing stuff in Dekel's Converter into a separate
> | functio
Angus Leeming <[EMAIL PROTECTED]> writes:
| I suspect that you'll be able to use it as-is meaning that all you really
| have to do is:
| 1. Rename it to something sensible ;-)
| 2. Move the latex parsing stuff in Dekel's Converter into a separate
| function.
I do not think that latex running sh
John Levon <[EMAIL PROTECTED]> writes:
| On Fri, Apr 04, 2003 at 08:21:37PM +0200, Alfredo Braunstein wrote:
|
| > And talking about error boxes, what about nuking them and implementing
| > instead an error log window doubly linked with the document (i.e. cliking
| > on a log line puts the curso
On Fri, Apr 04, 2003 at 08:21:37PM +0200, Alfredo Braunstein wrote:
> And talking about error boxes, what about nuking them and implementing
> instead an error log window doubly linked with the document (i.e. cliking
> on a log line puts the cursor within problem in the document, navigating on
>
On Fri, 4 Apr 2003, Alfredo Braunstein wrote:
> Alfredo Braunstein wrote:
>
> And talking about error boxes, what about nuking them and implementing
> instead an error log window doubly linked with the document (i.e. cliking
> on a log line puts the cursor within problem in the document, navigat
Alfredo Braunstein wrote:
> There is the problem of the insertion of the latex error boxes. (that's
> one of the reasons why the code is so ugly... there are a lot of bv's
> flying around and so)
And talking about error boxes, what about nuking them and implementing
instead an error log window d
Angus Leeming wrote:
> Alfredo Braunstein wrote:
>
>> John Levon wrote:
>>
>>> Not on the status bar. Have a cenetered modal progress dialog by all
>>> means. Feel free to do so.
>>
>> Do you think that there's no hope in asyncroneous latexing/export?
>>
>> Alfredo
>
> Why not?
>
> The latex
Angus Leeming wrote:
> Why not?
>
> The latex export is complicated by the need to parse the latex log file in
> order to ascertain whether latex needs to be run again. It seems to me
> that you have two possible strategies:
>
> You have two choices.
> 1 (simple to implement): keep this control
On Fri, Apr 04, 2003 at 07:29:12PM +0200, Alfredo Braunstein wrote:
> No, no, you got me all wrong ;) (and yes, I took once a look at the latex
> export code in export.C and it scared the hell out of me). I mean, wont it
> better to have the progress bar on the status bar for asyncroneous (or
> a
Alfredo Braunstein wrote:
> John Levon wrote:
>
>> Not on the status bar. Have a cenetered modal progress dialog by all
>> means. Feel free to do so.
>
> Do you think that there's no hope in asyncroneous latexing/export?
>
> Alfredo
Why not?
The latex export is complicated by the need to par
John Levon wrote:
>> Do you think that there's no hope in asyncroneous latexing/export?
>
> You look like just the right candidate to do it !!
No, no, you got me all wrong ;) (and yes, I took once a look at the latex
export code in export.C and it scared the hell out of me). I mean, wont it
bet
On Fri, Apr 04, 2003 at 06:49:12PM +0200, Alfredo Braunstein wrote:
> > Not on the status bar. Have a cenetered modal progress dialog by all
> > means. Feel free to do so.
>
> Do you think that there's no hope in asyncroneous latexing/export?
You look like just the right candidate to do it !!
John Levon wrote:
> Not on the status bar. Have a cenetered modal progress dialog by all
> means. Feel free to do so.
Do you think that there's no hope in asyncroneous latexing/export?
Alfredo
wild idea... would it make sense to have a progressbar on the statusbar
showing the status of loading, texing, exporting...?
Alfredo
On Fri, Apr 04, 2003 at 06:44:35PM +0200, Alfredo Braunstein wrote:
> wild idea... would it make sense to have a progressbar on the statusbar
> showing the status of loading, texing, exporting...?
Not on the status bar. Have a cenetered modal progress dialog by all
means. Feel free to
22 matches
Mail list logo
