Hi,

I think the KDE3 branch was called "maint"; I had some errors when I
tried to build it for Trinity a while ago. Right now I don't have a
possibility check the exact point in time when the move to KDE4 was
commited - sorry - you probably have to check it yourself. Please
share your results with us (because version 1.x is useful as reference
for (re)implementing features in 2.x).

Regards,
Gleb

2014-08-09 6:26 GMT+03:00, David C. Rankin <drankina...@suddenlinkmail.com>:
> All,
>
>    Glad to see basket is moving along. I have 2 projects I'm involved with
> that
> are still building with qt3 (for good reason). The Trinity Desktop Project
> (http://www.trinitydesktop.org/) and the openSuSE KDE3 project. Noting the
> 3/12/14 post from Lionel Petit regarding:
>
> - no more use of the Qt3 support classes (full Qt4/Kde4) to prepare a future
>
> upgrade to Qt5,
>
>    I wanted to check with the list to see if the qt3 code classes still
> exist in
> the current master, and if not, what is the latest branch that did contain
> it?
>
>    While ultimately both projects will move forward, they will -- for the
> foreseeable future -- continue relying on the qt3 code classes. For the next
>
> round of Trinity builds, I would like to pull the latest compatible code (if
> it
> exists) and attempt building (or backporting) any fixes it contains to the
> 1.0.3
> versions currently in use by the project. What branch/commit would I look to
> for
> the latest code supporting the qt3 classes?
>
> --
> David C. Rankin, J.D.,P.E.
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Basket-devel mailing list
> Basket-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/basket-devel
>

------------------------------------------------------------------------------
_______________________________________________
Basket-devel mailing list
Basket-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/basket-devel

Reply via email to