Re: [Synaptic-devel] KDE Frontend

[Henrique Pinto]

On Sunday 12 October 2003 19:58, Sviatoslav Sviridov wrote:
> On Sun, 12 Oct 2003 14:44:14 +0200
>
> Michael Vogt <address@hidden> wrote:
> > On Sun, Oct 12, 2003 at 12:33:44AM -0300, Henrique Pinto wrote:
> > > > > I really miss a KDE frontend for synaptic, since the GTK version
> > > > > won't obbey my settings for having menubars on top of screen.
> > > > > Before I start writing one: is there anyone working on that? Is
> > > > > that wanted?
> > > >
> > > > Personnally I would certainly use a KDE frontend!
> > > >
> > > > But I just hope that this frontend will not add too much burden on
> > > > the developpers, since it would require updating the KDE frontend
> > > > each time the Glade UI is updated...
> > >
> > > I have never built synaptic from sources, but I think there is an
> > > option to build it using WINGS instead of GTK. If that is possible,
> > > that's also possible with KDE.
> >
> > There is a seperation between the ui-independend part of synaptic and
> > the ui-part. We have right now:
> > common/ - all classes that are not gui
> > gtk/    - the gtk gui
> > wings/  - the wings gui (not maintained any more)
> >
> > so adding a qt (or kde) interface is not a big deal.
> >
> > > I can mantain the KDE interface myself, so the main developers won't
> > > have to care about it. Right now I'm reading the code, and I don't
> > > think it will be difficult to port it. If there's no objection I'll
> > > start the port soon, and once it is ported I'll take responsibility for
> > > updating it according to the GTK version, if the port is accepted as
> > > part of the source tree.
> >
> > Just go ahead :) Feel free to send patches to me or the list once you
> > have a working version. I don't know a lot about Qt development, but
> > may I suggest to use something like qt-designer to make the gui?
> >
> > I think this can also have the benefit to check how good the common/
> > classes really are. All of the recent development was against the gtk
> > version. This could have blurred the line between common/ and gtk/
> > (e.g. adding feature to the gtk classes that really should be in
> > common/). If you discover stuff like that, tell us about it, so we can
> > improve the code :)
> >
> > The same goes for the interfaces in common/. Some of them are not
> > optimal and we could use this new frontend to check and improve them.
>
> Isn't it a time for creating shared library libsynaptic? :)
> if there will be more than one choice of UI, than it will be useful for
> packaging synaptic.

I second that. Making a shared library should be very simple, since all
 common code is already in a separate subdirectory, and a libsynaptic.a is
 already generated. It's just a matter of changing it into a shared library.

--
        Henrique Pinto
        address@hidden