On Fri, 10 Mar 2000, John Levon wrote:
> On Fri, 10 Mar 2000, Angus Leeming wrote:
>
> > FINALLY --- and perhaps most importantly for me --- A
> > QUESTION
> >
> > I haven't done anything in the xforms/forms directory, yet
> > all three pop-ups work. Why is the forms directory needed?
> > A.
> >
>
> This contains files created by "fdesign". They are used with this when
> changing the GUI layout and generate the code you see in build() ...
> you can just move the .fd files from lyx/forms (iirc), add them to the
> Makefile, and add names for each element as described in the README
> in that directory
I don't want every file moved at once and in particular I only want one
dialog per .fd file. When a new form is made gui-indep then its .fd
should be in the xforms/forms. It doesn't necessarily have to be derived
from the old .fd that it may have been in -- ie. you could design a new
one or merge the ideas from the old tree with whatever changes have been
made in the current tree.
This is particularly true for those dialogs like Document and Paragraph
which should become tabbed dialogs. Just like they were in the old tree.
I like Angus' scheme. It sure is a lot smarter and neater than what I
had. All that common looking code had been bugging me for ages(*). I
don't want to have to repeat all the work I did last time however. If
Angus and John want to do it all again from scratch that's fine by me and
I'll help you everyway I can: co-ordination of who's doing what via a web
page at devel.lyx.org for example, maintaining a `dialogs' branch for you
to work against and committing your work for you(%), words of wisdom from
my
experience doing it all last time. That would give me time to work on
things that I have been putting on the backburner for ages: support for
different citation packages (I can do that dialog at same time), fix up
printing support (and that dialog also), look at supporting listings.sty
and hyperref.sty also.
Above all I recommend that you at least reuse the fdesign files from the
lyx cvs module and take a look at how the various dialogs were handled
there. That will also give you a chance to figure out which dialogs looks
similar and can be derived from the same parent.
> unless anyone wants to correct me ;)
Just expanding on you said.
> john
>
> p.s. is there any chance we could have a look at the script that's being
> written to transform lyx gtk-- stuff -> rae ? I know it's not finished but
> maybe it would be instructive
Sure I'll post it sometime this weekend. (I'm at uni and it's at home at
the moment)
Allan. (ARRae)
(*) I have had a fixation on keeping the:
struct FD_xxxx {...};
in the class definition (ie. in the header). This isn't really
necessary and it is only really needed in the FormXXX.C file at file
scope. None of the other files needs to see it. A bit of fresh
blood in a project can make a big difference.
(%) Lars wants to keep the number of developers with cvs access small so
I'm happy to be the conduit through which your code gets into LyX.
