tde-devs@chat.jabb.im < 2021/12/07 >
[01:29]michelec2 has joined
[03:33]michelec2 has left
[03:33]michelec2 has joined
[04:34]michelec2 has left
[04:34]michelec2 has joined
[04:37]michelec2 has left
[07:52]michelec2 has joined
[09:59]michelec2 has left
[09:59]michelec2 has joined
[10:05]blu.256 has left
[10:33]blu.256 has joined
[11:17]cethyel has joined
[12:24]cethyel: @Slávek, in tdeedu you suggest to drop the search for libartskde to look for the CMake target artskde-shared instead but I can't get this solution to work, have you tried your solution?
[13:16]michelec2: Hi Greg
[13:16]michelec2: in case you missed that, I post some comment a couple of days ago about the sip/tqscintilla/python conversion stuff here in this chat
[13:17]michelec2: have a look :-)
[13:22]blu.256 has left
[13:31]cethyel: Hello Michele, sorry can you copy/paste here (or reexplain), I don't know what comments you refer to :-[
[14:14]blu.256 has joined
[14:18]michelec2: ok
[14:18]michelec2: let me get them
[14:19]michelec2: https://www.trinitydesktop.org/irc/logs/tde-devs@chat.jabb.im/2021/12/04/
[14:19]tde-bot: Page title: tde-devs@chat.jabb.im logs
[14:19]michelec2: you can read the log here. it's pretty much all the comments in that day, so very few
[14:20]michelec2: [10:27] michelec2: @Greg: regarding sip/python-tqt and others, I think we should go in stage.1) First do the sip4-tqt cmake conversion, without thinking about renaming or moving stuff. To check if it works, python-tqt and other packages should be able to build and the result should be the same2) convert tqscintilla in a similar way3) convert python-tqt in a similar way4) same for remaining module (python-trinity, pykdeextensions, libtqt-perl...)[10:28] michelec2: once all cmake conversions are done, focus on dropping admin module if present in any of those modules[10:28] michelec2: then finally we can discuss about renaming things and move stuff around[10:29] michelec2: I feel we tried to do too many things at once recently, the result being lot of discussions, no real progress and perhaps some frustration[10:29] michelec2: better to go back to the basic and take small steps, once at a time[10:29] michelec2: what do you think?
[14:20]michelec2: ```[10:27] michelec2: @Greg: regarding sip/python-tqt and others, I think we should go in stage.1) First do the sip4-tqt cmake conversion, without thinking about renaming or moving stuff. To check if it works, python-tqt and other packages should be able to build and the result should be the same2) convert tqscintilla in a similar way3) convert python-tqt in a similar way4) same for remaining module (python-trinity, pykdeextensions, libtqt-perl...)[10:28] michelec2: once all cmake conversions are done, focus on dropping admin module if present in any of those modules[10:28] michelec2: then finally we can discuss about renaming things and move stuff around[10:29] michelec2: I feel we tried to do too many things at once recently, the result being lot of discussions, no real progress and perhaps some frustration[10:29] michelec2: better to go back to the basic and take small steps, once at a time[10:29] michelec2: what do you think?```
[14:20]michelec2: aiuch, the formatting is bad
[14:21]michelec2: [10:27] michelec2: @Greg: regarding sip/python-tqt and others, I think we should go in stage.
1) First do the sip4-tqt cmake conversion, without thinking about renaming or moving stuff. To check if it works, python-tqt and other packages should be able to build and the result should be the same
2) convert tqscintilla in a similar way
3) convert python-tqt in a similar way
4) same for remaining module (python-trinity, pykdeextensions, libtqt-perl...)
[10:28] michelec2: once all cmake conversions are done, focus on dropping admin module if present in any of those modules
[10:28] michelec2: then finally we can discuss about renaming things and move stuff around
[10:29] michelec2: I feel we tried to do too many things at once recently, the result being lot of discussions, no real progress and perhaps some frustration
[10:29] michelec2: better to go back to the basic and take small steps, once at a time
[10:29] michelec2: what do you think?
[14:21]cethyel: to fix the formatting, copy and paste in a editor, start with a new line
[14:21]michelec2: thanks (y)
[14:21]cethyel: yes blank line (new line) then you copy and paste
[14:22]michelec2: let me test it out
[14:22]michelec2: [10:27] michelec2: @Greg: regarding sip/python-tqt and others, I think we should go in stage.1) First do the sip4-tqt cmake conversion, without thinking about renaming or moving stuff. To check if it works, python-tqt and other packages should be able to build and the result should be the same2) convert tqscintilla in a similar way3) convert python-tqt in a similar way4) same for remaining module (python-trinity, pykdeextensions, libtqt-perl...)[10:28] michelec2: once all cmake conversions are done, focus on dropping admin module if present in any of those modules[10:28] michelec2: then finally we can discuss about renaming things and move stuff around[10:29] michelec2: I feel we tried to do too many things at once recently, the result being lot of discussions, no real progress and perhaps some frustration[10:29] michelec2: better to go back to the basic and take small steps, once at a time[10:29] michelec2: what do you think?
[14:22]michelec2: seems to be the same
[14:23]michelec2: although it is possible to delete the new line and add new line hee in kopete, but needsto be done for every line, which is tedious
[14:24]cethyel: in your editor (i use geany), the first line is blank ( type entry to make a new line) then you copy your stuff, then you copy the whole here
[14:24]cethyel: i think It works with kate as well
[14:26]michelec2: I tried kate but it seems still wrong, let me do a second test, maybe I did something wrong
[14:26]michelec2: [10:27] michelec2: @Greg: regarding sip/python-tqt and others, I think we should go in stage.1) First do the sip4-tqt cmake conversion, without thinking about renaming or moving stuff. To check if it works, python-tqt and other packages should be able to build and the result should be the same2) convert tqscintilla in a similar way3) convert python-tqt in a similar way4) same for remaining module (python-trinity, pykdeextensions, libtqt-perl...)[10:28] michelec2: once all cmake conversions are done, focus on dropping admin module if present in any of those modules[10:28] michelec2: then finally we can discuss about renaming things and move stuff around[10:29] michelec2: I feel we tried to do too many things at once recently, the result being lot of discussions, no real progress and perhaps some frustration[10:29] michelec2: better to go back to the basic and take small steps, once at a time[10:29] michelec2: what do you think?
[14:26]michelec2: same
[14:26]michelec2: nevermind anyway
[14:27]michelec2: if you scroll back I posted a formatted copy a bit earlier
[14:27]michelec2: or you can read from the link I posted before
[14:27]michelec2: it's about doing the conversion a bit at a time instead of trying to do too many things at once
[14:28]cethyel: anyhow to answer your proposition, I can't convert a step at a time because python-tqt and python-trinity relies on Python module from sip4-tqt (EG sipconfig), but I couldn't reproduce sipconfig behaviour with cmake so the three (sip4-tqt, python-tqt, python-trinity) had to be done in one shot
[14:32]michelec2: so it is not possible to make a cmake conversion of sip4 which gives identical results ?
[14:34]cethyel: the sip4-tqt cmake conversion was done, minus where Slavek wanted the install location and the Python modules (eg sipconfig) but as I said those Python modules aren't needed for python-tqt and python-trinity, they only used at build time
[14:36]michelec2: but would potentially be possible to do a first cmake migration as-is, and then later when all other modules are also on cmake, work on improving things?
[14:36]cethyel: python-tqt and python-trinity use the Python module sipconfig to configure, sipconfig gather data and set data for python-tqt, but I'm convinced that once this is done, sipconfig is not needed anymore
[14:36]michelec2: I feel it would split the troubles in smaller chucks this way
[14:37]michelec2: @sipconfig: I don't know the details, but I think it is imported in the code, based on a comment from Slavek in a PR
[14:37]cethyel: no I don't think the cmake conversion can be done one module after an other without sipconfig
[14:38]cethyel: but if you convert the three at the same time you shunt sipconfig
[14:39]michelec2: yes, but it's a bigger job ==> more likely we miss something IMO.
[14:39]michelec2: is it possible to add sipconfing to cmake conversion of sip-tqt? or does it require a lot of extra work?
[14:41]cethyel: maybe from you or Slavek, but I can't, It is too difficult for me, first I'm not proficient in Python then I'm not sure cmake can cope with a Python module, Python is a programming language, cmake is not
[14:42]michelec2: how is sipconfig created in current non-cmake code?
[14:43]cethyel: read configure.py, sipdistutils.py and siputils.py from sip4-tqt, you will understand how It works, I got the big picture
[14:43]michelec2: ah, so it is based on python code.
[14:43]michelec2: I will see if I can have a look sometime tomorrow
[14:44]michelec2: then we can discuss more
[14:44]cethyel: I got the big picture after a couple of hours of Python reading, should be easy for you
[14:44]michelec2: but I think sipconfig it is something still required :-)
[14:45]cethyel: yes if you convert a step at a time
[14:46]michelec2: I could be wrong, but probably sipconfig is holding some sort of config required when building the other modules. so even if we migrate all together, we may either use the same sipconfig or will have to replace it with equivalent cmake code in all modules
[14:47]cethyel: you start to get it
[14:48]michelec2: (y)
[14:48]cethyel: one way to avoid sipconfig, is too make a macro in cmake-trinity which mimics It's behaviour
[14:49]michelec2: yes, that could be a way to go.
[14:50]cethyel: I don't think that macro have to mimic everything sipconfig does, because the most important is a macro to use sip (the executable)
[14:51]michelec2: ok, I can't comment much without checking the code
[14:51]cethyel: if you look at python-tqt for EG, the sip files are processed by sip into *.cpp files
[14:51]cethyel: that is important
[14:52]michelec2: yes, that's the main part of creating the binding
[14:52]cethyel: sipconfig is secondary because I'm convinced it is only useful to set things in python-tqt for build time
[14:53]cethyel: once those *.cpp file have been processed they become qt.so, qtui.so, etc
[14:53]michelec2: ok
[14:56]cethyel: so when you have those library (there are libraries even if we call them modules in Python vocab) you don't need the Python modules from sip4-tqt anymore (I think...)
[14:57]michelec2: ok, understood. I will have a look once I fix an issue I have on polkit-tqt with dbus startup
[14:57]michelec2: so possibly sometime tomorrow
[14:58]cethyel: that why I make the difference between library and module, I call libraries == *.so and Python modules == *.py
[14:58]cethyel: but in Python vocab they are both Modules
[14:58]michelec2: well, they are very different things actually.
[14:59]michelec2: but similar concept of providing some library functions
[14:59]cethyel: yes one is an extension i believe, the other a true module
[15:00]cethyel: anyhow If I'm right, to write code with the binding, you only need sip.so, qt.so, qtui.so, not sipconfig.py
[15:02]michelec2: .so are shared library that can be loaded at runtime by any program. .py files are python source code and when they refer to them as a module it means it is a file providing some sort of functionaly. .py files are interpreted (or precompiled in .pyc files) but they are not share objects
[15:03]cethyel: from what I get sipconfig.py gathers data and set data in python-tqt/configure.py which is used to build python-tqt libs, EG some data are parsed from Makespecs files
[15:04]cethyel: sipconfig holds data on where to find sip.h and sip.so, etc
[15:06]cethyel: It's a quite shitty way of setting things in my view
[15:06]michelec2: ok I get it
[15:08]cethyel: but It was written by a master Python user, so he used Python for everything, the binding itself and he wrote modules to find sip.h, sip.so to set the building env for python-tqt
[15:09]michelec2: yeah, not surprised
[15:09]michelec2: python is actually a very easy and powerful language for quick things
[15:09]cethyel: I digress but did any of you had a look at mgb bug report in Amarok?
[15:10]michelec2: I saw the bug report, but I didn't have a look yet
[15:10]michelec2: are you able to reproduce the same bug?
[15:12]cethyel: Python is not so easy, from what I get, the grammar is quite similar to c++ (abstract the syntax) with few keywords but the the difficulty is hidden in the modules provided with, the stock library is huge
[15:13]cethyel: @Amarok, no I didn't give It a go
[15:14]michelec2: Python is way way easier than c++ :-)
[15:14]michelec2: @Amarok: me neither, because I switch off my pc every night
[15:15]cethyel: maybe, just saying that to be proficient in Python you have to know the stock library
[15:16]michelec2: like every language, the more you know the better :-)
[15:21]michelec2: well, time to go for me
[15:21]cethyel: Michele my man, I'll be going for now, have a good night, and see you guys some other time, bye!
[15:21]michelec2: have a godd evening
[15:22]michelec2: see you
[15:22]cethyel has left
[15:22]michelec2 has left
[15:22]Slávek-pine has joined
[17:35]blu.256 has left
[18:33]Slávek-pine has left
[18:38]Slávek-pine has joined
[20:01]blu.256 has joined
[20:02]blu.256 has left
[21:03]blu.256 has joined
[21:11]blu.256 has left
[21:17]blu.256 has joined
[22:37]Slávek-pine has left

tde-devs@chat.jabb.im < 2021/12/07 >