_camm

Hi, creator here. Some of the issues I had with other sites were bad/old data, slow interface, and difficulty with search/filtering. I'm still working on improving the search/filtering process - I'm currently prototyping whether I can do this with a small parameter LLM or classifier.

I also don't like that many sites require logins to view openings. I made this one login-free, plus you can export any jobs you're interested in to CSV.

It's just because I hadn't heard of it at the time. I will take a look at it though, others have also mentioned it to me after this post.

It looks like the iOS support is in alpha though, and I'm curious if it uses native components on iOS?

I'll try GammaRay. Thank you for the recommendation. I've tried the QML profiler before but I always have difficulty getting it to work on Android.

It's possible to implement custom QQuickItems that you render in C++, and are displayed within your QML somewhere.

https://doc.qt.io/qt-6/qquickitem.html

QTextDocument is a class in Qt::Gui that many of the other text classes/components use. I was thinking you may have implemented your own text handling widget/item, but using delegates of text areas makes sense too.

I will try reuseItems again. It's something I tried before briefly but thought it may have been causing some rendering glitches and removed it. Maybe because I didn't implement onResused or onPooled properly. Thanks!

I haven't seen any performance issues on desktop, but on mobile they really stand out. I have separated logic into QML, and even experimented with implementing custom QQuickItems in some places.

Here are some issues I've seen related to performance on mobile:

1) Opening a larger app is really slow (maybe 3-5 seconds), but works okay for smaller apps. I'm not sure what's going on behind the scenes and haven't had time to dive deep there yet, so this could be specific to me.

2) Rendering full pages is quite slower than native, as is QML rendering in general, even when using the QML compiler (which compiles your QML to C++)

3) Qt text rendering is a bit slow too, but you may not need i.e QTextDocument if you're implementing a text editor of some sort.

You're right, I will update my post. However, it's quite difficult to get this right on all devices as compared to i.e native where it just works. Plus, there are performance issues like those you mentioned that further impact scrolling and rendering responsiveness.

Your framework looks cool! I like that you have some flex support.