ChatCrawlersearch across public Telegram Open the app
Q

Qt for Python (PySide/Shiboken)

20 May 2020
2020-05-20×
20 May 2020
J
in qml : import MyType 1.0 and just add your Type as the model of the listview
C
Jim @yossiovcharik do you feel like writing an example or tutorial for the documentation? maybe even submitting some files of an example case would be really good, since many people is using QML
I know it's not so simple to create a Qt account and setup gerrit, but it's difficult to upgrade such process, since it has been around for many years. However, let me know if you need my help in some process or if you have some questions, before doing a step.
C
People manage to do so, so it's not impossible :)
J
and yes it's not an esay thing to contribute 😅
since you didn't add reviewers
C
nobody looked at it :(
J
ah ok, i thought one was added automatically
but I haven't lately
will add that step into the wiki page
Y
@cmaureir 1. What branch should tutorials etc. should be on? 2. Where in the repo they should be? I mean a tutorial like the one I mentioned above, with description etc. Not like these in pyside/examples/tutorial/
1. if you believe you can have it ready these days (say it's submitted before Monday) -> 5.15 since the release will be on the 26th of this month. 2. If you want to write a Tutorial, with text and more, sources/pyside2/doc/tutorials/ inside there you need to create a directory (you can just copy other there and replace the text and stuff), if you want to just submit the code as an example: examples/declarative/
C
ah, I didn't read the whole message and answered :P so if descriptions and more is intended, then sources2/doc/tutorials :)
J
"contributing to doc" with this previous lines should also be added to wiki I think
F
I thought everything should go to dev with a Pick-To: 5.15 footer nowadays?
but PySide has a diff git hierarchy
C
we are always playing catch, so maybe for Qt 6 we try to adopt a new strategy
will qmltyperegistrar and Qml required property be added to pyside2 also in 5.15 ? if so I think I should be taken in account to write new doc about model/view (since it seems to become the recommanded usage)
because we are still figuring out
how to properly doing
the current implementation of qmlRegisterType is a hack around class reflection
and we have been struggling with it since the release in 2018
if you have some ideas, or want to contribute some, please be my guest, but it's something we are quite lost.
So far we just have qmlRegisterTyep, and we can set context properties (which are not recommended!) but still we support them.
C
even the UncreatableType and SingletonType registration as challenging as fuck
J
no knowledge on C++, can't help on it...
And how are you registering types now Jim ?
C
context properties? or qmlRegisterType?
J
both. I use context properties as singleton (for example to interface database/api ) and qmlRegisterType for QAbstractlistModel derived class. It's pretty usable except for testing but it'sanother question :-) I declare all in a main.py file. I also add an instance of context_property to app (QApplication) so I can access it every where without importing (jsut retrieving app via QApplication.instance() and use app.ddb.myslot()
Calendar: May 2020
Archive by month
Open in Telegram Каталог площадок Искать в ChatCrawler

A snapshot of an open public feed from the search index ChatCrawler — “Google for public Telegram”; refreshed as the venue is crawled. Times are UTC.

Public content only, official Telegram API. About · FAQ · What we do not do · Remove a page · Catalog