"Asger K. Alstrup Nielsen" <[EMAIL PROTECTED]> writes:
| Rename SpaceLess to MakeLaTeXFilename, because it should *only*
| be used for the LaTeX filenames. Let's not end up in the same
| situation again.
Yes. This is the point that I have been waiting for.
Lgb
"Asger K. Alstrup Nielsen" <[EMAIL PROTECTED]> writes:
| The real difference compared to the last time is that we have realized
| that we can not just pull out a huge chunk and redo that, and then pull
| out another huge chunk, redo that all at the same time. We *have* to move
| slowly. It's te
> I agree with Asger that we need a combination of the two. Welcome aboard
> looks like you volunteered yourself for the canvas side of things ;-)
Regarding the canvas side of things: We already did this work with
the painter from the defunct branch. It was very clean work, and the
result was
Thanks very much for your prompt and surprizingly thorough discussion
Andre' (given your very brief skim of the documents and code involved).
On Tue, 16 Nov 1999, Andre' Poenitz wrote:
[...]
> > I think we should do both. The first, we should do for
> > the canvas area. This is already what is
> Andr=E9 suggests to let each front-end be a dumb terminal
> which is feeded with detailed drawing instructions from
> the kernel.
Well, not from the kernel, but from the painter. The kernel
does not know about frontends. Anyway, I think we understand
each other here...
> ...
> I think we sh
[How should UI-independence be handled?]
André suggests to let each front-end be a dumb terminal
which is feeded with detailed drawing instructions from
the kernel. Thus, the frontend is ignorant of
state.
Allan suggests that each front-end is told carefully about
state through signals, but each
> Since it is monday now, I'll try to be *really* constructive.
Ahh, you know *really* constructive is coding ;-)
> Asger> 3) LaTeX, xdvi, ghostview, DocBook, OS/2, SGMLtools, the shell
> Asger> all have different sets of problematic characters, and escaping
> Asger> rules.
>
> What programs ha
On 15 Nov 1999 12:15:17 +0100, Jean-Marc Lasgouttes wrote:
>What problems have problems other than LaTeX?
OS/2 and Win9* file systems are localized (charsets!), this means all
kind of trouble, but you cannot foresee what will happen. E.g. as SMi
said here, you cannot even think of running X/2 on
On Mon, 15 Nov 1999 12:11:49 MET, Andre' Poenitz wrote:
>Depends. It makes the executable slimmer if only one frontend is linked
>in at a time and it does not create dependencies on libraries you do not
>need/want/have. Personally I am in favour of having a 'kernel library'
>that contains all rea
> "Asger" == Asger K Alstrup Nielsen <[EMAIL PROTECTED]> writes:
Asger> Now, let's be a little productive instead, huh? These are the
Asger> issues:
Since it is monday now, I'll try to be *really* constructive.
Asger> 1) The conversion is needed, because I want to be able to use
Asger> spac
> If you haven't already, and your comments
> seem to indicate you haven't, I'd certainly like you to take a look at
> the signal/slot approach I developed.
Indeed I had not. But I just got the 'lyx' branch from CVS and had
a really quick look. I mean 'really' quick, so please forgive me if I
On Sat, 13 Nov 1999, Andre' Poenitz wrote:
> > Check the roadmap on the web site, and grab a task. Choose a small
> > one, like backport the new menu-code from the old development branch.
> > This menu-code is modelled after the Model-View-Control design pattern,
> > and it's a help in the plan f
> Check the roadmap on the web site, and grab a task. Choose a small
> one, like backport the new menu-code from the old development branch.
> This menu-code is modelled after the Model-View-Control design pattern,
> and it's a help in the plan for better structured code.
I don't have much experi
[About applying the design pattern Model-View-Control to LyX]
> >Any opinions?
>
> For me this sounds just great, it is a major step to the right
> direction:
Yes, all of this sounds just great. However, it's too ambitious.
The LyX team is too small to handle such a large task. Therefore,
let'
On Fri, 12 Nov 1999 10:55:08 +0100 (MET), Asger K. Alstrup Nielsen
wrote:
>Now, where do we go from here?
>
>Can we handle this very extremely hyper-super-difficult problem that
>is completely and utterly impossible to solve?
>
>Of course we can not, so let's just keep arguing that ; should be
>c
On Fri, 12 Nov 1999 12:59:03 MET, Andre' Poenitz wrote:
>The commandline interface does exactly the same, of course the painter
>is much simpler in this case, it just produces some text describing the
>current state. But this is a way to achieve GUI
>independence: Everything up to and including t
> I think this patch should go in! This is something that I wanted to
> do a long time ago, but never had the time for. Also, hopefully
> that will keep Andr=E9 morale up to send in lots of other pathces ;-)
Well, I don't think you know what you are saying ;-}
*grin* erm...
Since it is Friday
> The attached patch adds a new 'command' called
>
> 'command-sequence'
>
> This allows a key sequence to be bound to a seqeunce of other lyx-commands
>
> Example:
> \bind "F12" "command-sequence math-insert alpha; math-insert beta;"
>
> Every single command in the sequence has to be terminat
18 matches
Mail list logo
