On 27 Jan 2000, Lars Gullik Bj�nnes wrote:
> Allan Rae <[EMAIL PROTECTED]> writes:
>
> [I dropped the sigc++ list]
It was just Karl's private mail address not the list.
> So you are not letting the included sigc++ use its own ./configure?
My first draft does but its a pain -- 12 hours yesterday but I got it
working.
> Ok that seems like the best way. Some work needed to the the correct
> autoconf macros in place then.
I took a look at gettext.m4 and the intl/Makefile and saw how we get
around not building internal stuff. I had started writing a LYX_WITH_SIGC
that was very rapidly growing. The problems mostly stem from the need to
either run sigc++/configure _before_ running the testing of
with-included-sigc in configure so that a sigc-config script is created --
this script is used in Karl's supplied sigc++.m4 for testing library
versions etc. It's a real chicken-and-egg thing and I haven't tried it
yet but we might get away with an AC_SUBDIRS(sigc++) just before the
LYX_WITH_SIGC test. It'd also need a few other mods to
sigc++/configure.in to setup for not building the library if we're going
to use an externally supplied one. This was going to be my second stage
of integration but I ran out of blinks last night.
> There are also some other very important things that is closely
> releated to gui-indep that needs to get done before the ball can begin
> to roll: the lyx painter, new menucode, new toolbar code.
> Also the gui initialization needs to get cleaned up.
I was aiming for gui-init + dialogs. The painter, toolbar etc are
independent of the dialogs so we can get people working on the dialogs
and then branch out from there. As you know from previous discussions I
see toolbars as just another form of dialog (stackable, embeddable ones
perhaps) so they will eventually be added to the Popups lineup (or should
that be Dialogs).
> | As I said before I want to filter the popup work and am trying to get a
> | base where we can have popups from different toolkits co-existing although
> | I don't want to allow a new popup to replace a hardcoded one until the
> | hardcoded one has been made gui-indep.
>
> One other approach is to just not show the popups that has not been
> implemented yet for the given tk.
We can cover that on a tk by tk basis. If we can get a workable version
why not?
> | It's also a question of just how extravegant we are willing to allow our
> | signals/slots to get -- how many parameters we're willing to pass.
>
> There is the possiblity of passing objects.
Exactly. BufferParams and PrinterParams spring to mind although I'm
thinking we should try to just stick to a std::string parameter list.
> | Oh and the popup will get its info from a LyXFunc. We used to use a
> | separate class called Communicator but I've since decided that was a dumb
> | idea as a LyXFunc will be available to scripts and the outside world via
> | the LyXServer.
>
> It is possible that when setting paramters we will do that using
> lyxfunc too.
More than just possible -- preferably mandatory.
> | Yes, you get the idea!
> | Although I'm thinking about adding another member and also something very
> | naughty: a data member,
>
> Hey! forget that.
Ouch! Yes Boss!
;-)
> Hmmm a fulltime LyX developer would be nice :-)
Well at least 3 or 4 full days a week.
> I have been planning to begin the gui-indep work for some time, but so
> far there have been other task that has been crying to get done. As I
> see it [I] have no[w] finished a lot of the cleanup that was needed, and
> we can begin to focues (slowly) on different matters.
> So my simplistic plan is now: [snipped]
SO you want gui-indep started before 1.2.0 then. Okay. I was thinking
we'd solidify what we've got and call that 1.2.0 then get the gui-indep
foundations built (at least for dialogs) and solidify them, then release
1.3.0 and so on.
> Hmm I seem to one task I really would have liked to have done:
> - get rid of current_view.
> (I think I will work on this too before 1.1.5)
Ahh... I remember back in the old days Lars used to load up his truck
(Emacs) and head out into the wild blue yonder (lyx repository) and
go shoot anything that moved (current_view etc.). Ahh yeahh bring on the
old times! ;-)
Allan. (ARRae)
