[Kalzium] Fwd: Final Reminder: KDE 4.2 Feature Plan Closing Tonight

[Benoît Jacob]

Here's the latest episode of this comedy...

I realized that our libavogadro snapshot contains fixes (especially by the 
kde-windows guys) that would be lost if we updated it from avo trunk, and 
that can't be easily forwardported to avo trunk anymore since we didn't do it 
in time.

So what I finally did, was to put a eigen1 snapshot inside kalzium's libavo 
snapshot. I then removed eigen1 from /trunk/kdesupport (there is 
now /tags/eigen/1.0.5).

Notice that the size of eigen1 is small anyway compared to the size of libavo.

That allows kalzium 4.2 's molecular editor to work like in 4.1, without 
forcing /trunk/kdesupport to keep eigen1, and without forcing the user to 
grab another dependency.

Of course that's a completely unsustainable thing to do in the long term, and 
the fact that our libavo snapshot contains changes that now are difficult to 
forwardport is another proof that it is more than time to get rid of any 
snapshot, so in 4.3, I really really hope that libavogadro 1.0 is out, 
otherwise we will have to remove the molecular editor from /trunk/KDE 
(playground would then be a good temporary home for it).

Cheers,
Benoit

On Monday 03 November 2008 13:20:54 Benoît Jacob wrote:
> Thanks for your reply, obviously you don't have to tell us in advance when
> you are traveling, but here what made me grow afraid that nobody would take
> care of that is that nobody added that to the KDE 4.2 feature plan until I
> did it the last day before the soft freeze.
>
> It is very helpful to me that you plan to take care of the kalzium 3D
> editor for 4.2, as that lets me focus on finalizing the eigen2 API. I hope
> to do what I have to in this respect in the next few days and adapt
> libavogadro accordingly so that when you take care of kalzium 4.2 this is
> behind us.
>
> Cheers,
> Benoit
>
> On Monday 03 November 2008 12:17:48 Marcus D. Hanwell wrote:
> > On Monday 27 October 2008 13:23:17 Benoît Jacob wrote:
> > > Nobody replied... confirms my fear that Kalzium is seriously lacking
> > > love.
> >
> > I did not reply as I was traveling (left 15 October) - perhaps I should
> > have posted this somewhere? I was only checking my personal email
> > accounts and not really monitoring mailing lists as I had limited
> > Internet connectivity along with a limited amount of time. I only just
> > got back home yesterday and so have been reading through mailing lists
> > etc.
> >
> > > Beware: provocative phrasing below this point.
> > >
> > > Look, we're not going to keep eigen1 alongside eigen2 in kdesupport
> > > forever, just because nobody cares to deal with the old libavogadro
> > > snapshot used by Kalzium.
> >
> > This was certainly on my list and should not take too long. I am still
> > feeling very jet lagged today having just crossed the Atlantic. The
> > changes I have been making to libavogadro are to allow for stabilization
> > of the Avogadro API independent of the OpenBabel API. I am not finished
> > but hope to be soon.
> >
> > I will certainly try to help as I have in the past. These six month
> > cycles seem to be tough to work in and may be working in git branches or
> > similar would be easier? I had talked about the possibility of splitting
> > the viewer/editor off and I think it has many benefits including reducing
> > the impact of the libavogadro changes on Kalzium.
> >
> > I am not sure how long it will take getting over jet lag, catching up at
> > work etc and so don't feel like I can make any promises about this week
> > but will do what I can in the spare time I have. With work, travel plans,
> > sorting out KDE 4.1 in Gentoo and other things I had lost track of the
> > KDE 4.2 schedule a little but was hoping to make some improvements before
> > the freeze.
> >
> > Thanks,
> >
> > Marcus
>
> _______________________________________________
> Kalzium mailing list
> Kalzium at kde.org
> https://mail.kde.org/mailman/listinfo/kalzium