[prev in list] [next in list] [prev in thread] [next in thread]
List: kwrite-devel
Subject: Re: Pate
From: Alex Turbov <i.zaufi () gmail ! com>
Date: 2012-06-17 16:54:11
Message-ID: CANktQtvdDENAAMS_8fwF63Yu0aNPeByG=En5jrJ-E78PzruJpg () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
On Sun, Jun 17, 2012 at 11:47 AM, Dominik Haumann <dhaumann@kde.org> wrote:
> 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.
if I understand correctly it can be done w/ move() member... but
MovingInterface isn't available from Python nowadays (at least in my KDE
4.8.3)
> So in the expaned
> plugin, the advance must be implemented differently anways.
>
done in commit
http://quickgit.kde.org/?p=kate.git&a=commit&h=67fc1d31fb04055bd581d85192ff5d805de82f4a
move cursor manually.
>
> 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.
>
> +1
> 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
>
[Attachment #5 (text/html)]
<br><br><div class="gmail_quote">On Sun, Jun 17, 2012 at 11:47 AM, Dominik Haumann \
<span dir="ltr"><<a href="mailto:dhaumann@kde.org" \
target="_blank">dhaumann@kde.org</a>></span> wrote:<br><blockquote \
class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc \
solid;padding-left:1ex"> Hi Shaheed,<br>
<br>
the expand plugin uses the smartInterface, which is not implemented anymore by<br>
Kate Part. So the correct thing would be to not create bindings for it.<br>
Instead, the smart* classes were replaced by the moving* classes<br>
(MovingInterface, MovingRange, MovingCursor). But the movingCursor does not<br>
have an advance function as the SmartCursor one had, afaik. </blockquote><div><br>if \
I understand correctly it can be done w/ move() member... but MovingInterface \
isn't available from Python nowadays (at least in my KDE 4.8.3)<br> \
</div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px \
solid rgb(204,204,204);padding-left:1ex">So in the expaned<br> plugin, the advance \
must be implemented differently anways.<br></blockquote><div><br>done in commit <a \
href="http://quickgit.kde.org/?p=kate.git&a=commit&h=67fc1d31fb04055bd581d8519 \
2ff5d805de82f4a">http://quickgit.kde.org/?p=kate.git&a=commit&h=67fc1d31fb04055bd581d85192ff5d805de82f4a</a><br>
move cursor manually.<br> </div><blockquote class="gmail_quote" style="margin:0px \
0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"> <br>
Besides, I think it's a good idea to release the pate plugin with KDE 4.9,<br>
that's after all what I once porposed to Paul years ago, but never happened.<br>
<br></blockquote><div>+1<br> <br></div><blockquote class="gmail_quote" \
style="margin:0px 0px 0px 0.8ex;border-left:1px solid \
rgb(204,204,204);padding-left:1ex"> So as soon as KDE 4.9 is branched, the move can \
be done. So keep it up :-)<br> It would be awesome, if you blog about the pate plugin \
a bit on kate-<br> <a href="http://editor.org" target="_blank">editor.org</a>. You \
can have an account, what do you think?<br> <br>
Greetings<br>
<span class="HOEnZb"><font color="#888888">Dominik<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
On Thursday, 14. June 2012 22:37:35 Shaheed Haque wrote:<br>
> I now regard the Pate plugin as essentially done and working. So, once<br>
> the 4.9 release is out, I'd like to get it out of the playground and<br>
> into the main plugins folder. What would be needed to get to that<br>
> point?<br>
><br>
> On 10 June 2012 16:29, Dominik Haumann <<a \
href="mailto:dhaumann@kde.org">dhaumann@kde.org</a>> wrote:<br> > > On \
Saturday, 9. June 2012 16:27:52 Shaheed Haque wrote:<br> > >> Hi,<br>
> >><br>
> >> On 9 June 2012 13:33, Sune Vuorela <<a \
href="mailto:nospam@vuorela.dk">nospam@vuorela.dk</a>> wrote:<br> > >> \
> On 2012-06-07, Dominik Haumann <<a \
href="mailto:dhaumann@kde.org">dhaumann@kde.org</a>> wrote:<br> > >> \
>> Possible solution in file playground/CMakeLists.txt:<br> > >> \
>><br> > >> >> -macro_optional_add_subdirectory(pate)<br>
> >> >> macro_optional_add_subdirectory(scriptIDE)<br>
> >> >> +<br>
> >> >> +macro_optional_find_package(SIP)<br>
> >> >> +macro_log_feature(SIP_FOUND "SIP" "Support for \
SIP Python bindings"<br> > >> >> "")<br>
> >> >> +<br>
> >> >> +macro_optional_find_package(PyQt4)<br>
> >> >> +macro_log_feature(PYQT4_FOUND "PyQt4" "Python \
bindings for Qt4" "")<br> > >> >> +<br>
> >> >> +macro_optional_find_package(PyKDE4)<br>
> >> >> +macro_log_feature(PYKDE4_FOUND "PyKDE4" \
"Python bindings for KDE4"<br> > >> >> "")<br>
> >> >> +<br>
> >> >> +if (SIP_FOUND AND PYQT4_FOUND AND PYKDE4_FOUND)<br>
> >> >> + macro_optional_add_subdirectory(pate)<br>
> >> >> +endif (SIP_FOUND AND PYQT4_FOUND AND PYKDE4_FOUND)<br>
> >> ><br>
> >> > Hi<br>
> >> ><br>
> >> > Please don't let 'what's being installed' depend \
on what's being<br> > >> > available in the build environment.<br>
> >><br>
> >> I think the problem here was that a lack of build time dependencies<br>
> >> for Pate caused the entire build to abort when it was included in \
the<br> > >> build.<br>
> ><br>
> > Right, it would be nice if a summary shows up that Pate is being build \
(or<br> > > not), depending on whether the required libraries are \
available.<br> > ><br>
> > But breaking the entire build process of Kate is a no-go for obvious<br>
> > reasons><br>
> > :)<br>
> ><br>
> > Greetings,<br>
> > Dominik<br>
_______________________________________________<br>
KWrite-Devel mailing list<br>
<a href="mailto:KWrite-Devel@kde.org">KWrite-Devel@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/kwrite-devel" \
target="_blank">https://mail.kde.org/mailman/listinfo/kwrite-devel</a><br> \
</div></div></blockquote></div><br>
_______________________________________________
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]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic