[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kwrite-devel
Subject:    Re: Pate
From:       Dominik Haumann <dhaumann () kde ! org>
Date:       2012-06-17 7:47:49
Message-ID: 1793612.onPVtGfWvk () eriador
[Download RAW message or body]

Hi Shaheed,

the expand plugin uses the smartInterface, which is not implemented anymore by 
Kate Part. So the correct thing would be to not create bindings for it. 
Instead, the smart* classes were replaced by the moving* classes 
(MovingInterface, MovingRange, MovingCursor). But the movingCursor does not 
have an advance function as the SmartCursor one had, afaik. So in the expaned 
plugin, the advance must be implemented differently anways.

Besides, I think it's a good idea to release the pate plugin with KDE 4.9, 
that's after all what I once porposed to Paul years ago, but never happened.

So as soon as KDE 4.9 is branched, the move can be done. So keep it up :-)
It would be awesome, if you blog about the pate plugin a bit on kate-
editor.org. You can have an account, what do you think?

Greetings
Dominik

On Thursday, 14. June 2012 22:37:35 Shaheed Haque wrote:
> I now regard the Pate plugin as essentially done and working. So, once
> the 4.9 release is out, I'd like to get it out of the playground and
> into the main plugins folder. What would be needed to get to that
> point?
> 
> On 10 June 2012 16:29, Dominik Haumann <dhaumann@kde.org> wrote:
> > On Saturday, 9. June 2012 16:27:52 Shaheed Haque wrote:
> >> Hi,
> >> 
> >> On 9 June 2012 13:33, Sune Vuorela <nospam@vuorela.dk> wrote:
> >> > On 2012-06-07, Dominik Haumann <dhaumann@kde.org> wrote:
> >> >> Possible solution in file playground/CMakeLists.txt:
> >> >> 
> >> >> -macro_optional_add_subdirectory(pate)
> >> >>  macro_optional_add_subdirectory(scriptIDE)
> >> >> +
> >> >> +macro_optional_find_package(SIP)
> >> >> +macro_log_feature(SIP_FOUND "SIP" "Support for SIP Python bindings"
> >> >> "")
> >> >> +
> >> >> +macro_optional_find_package(PyQt4)
> >> >> +macro_log_feature(PYQT4_FOUND "PyQt4" "Python bindings for Qt4" "")
> >> >> +
> >> >> +macro_optional_find_package(PyKDE4)
> >> >> +macro_log_feature(PYKDE4_FOUND "PyKDE4" "Python bindings for KDE4"
> >> >> "")
> >> >> +
> >> >> +if (SIP_FOUND AND PYQT4_FOUND AND PYKDE4_FOUND)
> >> >> +  macro_optional_add_subdirectory(pate)
> >> >> +endif (SIP_FOUND AND PYQT4_FOUND AND PYKDE4_FOUND)
> >> > 
> >> > Hi
> >> > 
> >> > Please don't let 'what's being installed' depend on what's being
> >> > available in the build environment.
> >> 
> >> I think the problem here was that a lack of build time dependencies
> >> for Pate caused the entire build to abort when it was included in the
> >> build.
> > 
> > Right, it would be nice if a summary shows up that Pate is being build (or
> > not), depending on whether the required libraries are available.
> > 
> > But breaking the entire build process of Kate is a no-go for obvious
> > reasons> 
> > :)
> > 
> > Greetings,
> > Dominik
_______________________________________________
KWrite-Devel mailing list
KWrite-Devel@kde.org
https://mail.kde.org/mailman/listinfo/kwrite-devel
[prev in list] [next in list] [prev in thread] [next in thread]