Hi Luca,
On 5 September 2017 at 23:12, Luca Beltrame wrote:
> Il giorno Tue, 5 Sep 2017 22:12:26 +0100
> Shaheed Haque ha scritto:
>
> Hello Shaheed,
>
> first of all, thanks for continuing work on the bindings!
>
>> https://github.com/ShaheedHaque/extra-cmake-modules/tree/shaheed_master/find-mo
[ Copying in kde-frameworks-devel as suggested ]
On 5 September 2017 at 22:12, Shaheed Haque wrote:
> A lot of progress has been made in the last 18 months or so:
>
> THE TOOLING
> ===
>
> We have:
>
> - A pretty powerful KDE-independent automatic binding generation capability.
>
> - Supp
El dimarts, 5 de setembre de 2017, a les 22:12:26 CEST, Shaheed Haque va
escriure:
> A lot of progress has been made in the last 18 months or so:
Looks great :)
You may want to email kde-frameworks-de...@kde.org though since that list is
the one where specific KF5 things (like this one seems to
A lot of progress has been made in the last 18 months or so:
THE TOOLING
===
We have:
- A pretty powerful KDE-independent automatic binding generation capability.
- Supplemented by a powerful/fine-grained manual override "rule" capability.
- Comprehensive (rule-based) support for the m
El divendres, 8 d’abril de 2016, a les 1:29:38 CEST, Stephen Kelly va
escriure:
> Albert Astals Cid wrote:
> > El divendres, 8 d’abril de 2016, a les 0:29:57 CEST, Stephen Kelly va
> >
> > escriure:
> >> Albert Astals Cid wrote:
> >> > So my suggestion would be renaming pykde5.git to pykf5.git, a
Albert Astals Cid wrote:
> El divendres, 8 d’abril de 2016, a les 0:29:57 CEST, Stephen Kelly va
> escriure:
>> Albert Astals Cid wrote:
>> > So my suggestion would be renaming pykde5.git to pykf5.git, and that
>> > means *only* KDE Frameworks 5 bindings would go in there, any other
>> > repo that
El divendres, 8 d’abril de 2016, a les 0:29:57 CEST, Stephen Kelly va
escriure:
> Albert Astals Cid wrote:
> > So my suggestion would be renaming pykde5.git to pykf5.git, and that means
> > *only* KDE Frameworks 5 bindings would go in there, any other repo that
> > wants to provide python bindings
Albert Astals Cid wrote:
> So my suggestion would be renaming pykde5.git to pykf5.git, and that means
> *only* KDE Frameworks 5 bindings would go in there, any other repo that
> wants to provide python bindings (say okular, marble or krita) should do
> somewhere else, ideally their own repo so the
I'm fine with this. The non-KF5 project (okular, marble, whatever)
would in any case have a dependency on KF5/Tier1 and so the fact that
the tooling lives there is probably fine. (And this essentially means
no change from how I am currently working, plus-or-minus a change of
repo name at some point
Il giorno Thu, 07 Apr 2016 00:16:58 +0200
Albert Astals Cid ha scritto:
> But personally I would not suggest having a "kde-wide" pykde5 repo
> given how many different release schedules we have now it would be
> close to unmanageable having a single repo that has kf5+marble+krita
> python binding
On Thursday, April 07, 2016 12:16:58 AM Albert Astals Cid wrote:
> So my suggestion would be renaming pykde5.git to pykf5.git, and that means
> *only* KDE Frameworks 5 bindings would go in there, any other repo that
> wants to provide python bindings (say okular, marble or krita) should do
> some
El dilluns, 4 d’abril de 2016, a les 18:36:16 CEST, Shaheed Haque va escriure:
> Those build dependency and packaging questions are exactly why I keep
> making remarks about needing CMake help from folks who are familiar
> with current KDE build setups (and, maybe, packaging).
>
> So, to provide s
super cool!
replacing the current PyKF5 repo (and naming it PyKF5 surely is a
possibility?
Shaheed Haque schrieb am So., 3. Apr. 2016 um
14:32 Uhr:
> On 1 April 2016 at 23:18, Albert Astals Cid wrote:
> > El dijous, 31 de març de 2016, a les 23:04:07 CEST, Shaheed Haque va
> escriure:
> >> Tha
Those build dependency and packaging questions are exactly why I keep
making remarks about needing CMake help from folks who are familiar
with current KDE build setups (and, maybe, packaging).
So, to provide some food for thought...
1. The way the tool works is that there is a driver.py program w
El diumenge, 3 d’abril de 2016, a les 23:04:48 CEST, Ingo Klöcker va escriure:
> On Sunday 03 April 2016 20:27:27 Shaheed Haque wrote:
> > What seems to be causing ripples is my suggestion that I call the
> > *tool* to create the SIP files something relating to PyKDE5. That made
> > sense to me sin
On Sunday 03 April 2016 20:27:27 Shaheed Haque wrote:
> What seems to be causing ripples is my suggestion that I call the
> *tool* to create the SIP files something relating to PyKDE5. That made
> sense to me since the tools is all about making SIP wrappers for all
> of KDE(5) that wants them. Simi
On 3 April 2016 at 17:58, Philipp A. wrote:
> super cool!
>
> replacing the current PyKF5 repo (and naming it PyKF5 surely is a
> possibility?
Calling the python version of KF5 PyKF5 is not the question; we are
all agreed that is the right thing.
What seems to be causing ripples is my suggestion
On 1 April 2016 at 23:18, Albert Astals Cid wrote:
> El dijous, 31 de març de 2016, a les 23:04:07 CEST, Shaheed Haque va escriure:
>> Thanks for all the feedback. Here is what I am thinking:
>>
>> - The basic tooling might as well keep the PyKDE5 name because the
>> tool is intended to be used KD
El dijous, 31 de març de 2016, a les 23:04:07 CEST, Shaheed Haque va escriure:
> Thanks for all the feedback. Here is what I am thinking:
>
> - The basic tooling might as well keep the PyKDE5 name because the
> tool is intended to be used KDE-wide. And the repo name for the tool
> is pykde5. This
Thanks for all the feedback. Here is what I am thinking:
- The basic tooling might as well keep the PyKDE5 name because the
tool is intended to be used KDE-wide. And the repo name for the tool
is pykde5. This should not be a problem because nobody outside dev
should see this tool. (Plus, I have li
Il Sat, 26 Mar 2016 22:30:18 +, Shaheed Haque ha scritto:
Hey Shaheed,
> about 800 lines of Python code [2] which can already create 684 .sip
> files [3].
As someone who occasionally worked on PyKDE4 I can say this is nothing
short of awesome!
> whatever. If anybody can actually explain, t
On Saturday, March 26, 2016 10:30:18 PM Shaheed Haque wrote:
> Hi all,
>
> I've given up on trying to get the twine2 PyKDE bindings generator
> working [1] because not only is the code there broken, but it seems a
> Sysiphusian task to maintain a C++ parser. Instead, a few evenings
> with clang 3.
Yes. Generally, The core generator.py can handle anything clang can
parse and the idea is that where needed, you'd just add a few rules to
the database for any krita-specific hacks needed.
In due course, the rules.py could easily be made more separable to
separate out what different projects need
On Sat, 26 Mar 2016, Shaheed Haque wrote:
Hi all,
I've given up on trying to get the twine2 PyKDE bindings generator
working [1] because not only is the code there broken, but it seems a
Sysiphusian task to maintain a C++ parser. Instead, a few evenings
with clang 3.9 have yielded what I hope i
Hi,
exciting work! Just the other day I was hoping someone would pick
up work on PyKDE5 ...
Cheers,
Eike
Hi,
exciting work! Just the other day I was hoping for someone
to take up PyKDE5 ...
Cheers,
Eike
Hi all,
I've given up on trying to get the twine2 PyKDE bindings generator
working [1] because not only is the code there broken, but it seems a
Sysiphusian task to maintain a C++ parser. Instead, a few evenings
with clang 3.9 have yielded what I hope is the basis of a way forward:
about 800 lines
27 matches
Mail list logo
