felipefar

This is a great use in the short-term. In the long term, you also need situations where you will apply directly the contents of your note. You can explain the subject to your friends or co-workers, use it as the basis for research that you are yourself doing, or synthesize what you've written down with knowledge coming from other books. This will keep you coming back to your notes, and you'll feel that your knowledge is increasing and getting sharper each time.

There is a very clear distinction between details and main point. If you assume that there is no main point in a text, you negate all that the writer is trying to communicate.

Qt Design Studio is buggy and heavyweight. It lacks integration with Visual Studio, has a bad integration with Qt Creator. It doesn't produce clean .qml files. Qt Designer (the one used for Qt Widgets) is better in those regards.

Anyhow, this might be a controversial opinion, but the best experience I've had with WYSIWYG UI designers was with Netbeans Swing Editor and VS Windows Forms Editor. The IDE integration was seamless.

If you create a sample project with a list view, you can scroll that widget by clicking the mouse on the background and dragging it (a reminiscence from touch based interfaces). The example projects don't look native but look like a mobile app inside your desktop. Windows themed button sizes don't follow Windows 7 desktop guidelines out of the box.

Sure that if you put the extra effort you can make QML look native, but it makes you wonder if desktop is in fact a goal for the framework.

I'm favorably disposed to QML, but for it to actually replace Qt Widgets it'd have to provide: better out of the box desktop integration, a public C++ API and a better WYSIWYG UI designer.

I've been enjoying working with Qt as well. I'll start publishing more about Cahier in some weeks. I wish all the best for your project!

Hi! I'm glad you found Cahier interesting. I use it on a daily basis.

I've been developing the tool for 10 months, and still haven't gone full public. There's still some things to iron out before that. But I hope to publish more about it in the coming weeks.

The more commitments you have in life, the more pressure there is to align your learning projects with money earning activities.

You can't justify to your family, kids and other "stakeholders" that you spent thousands of hours developing apps just for learning new subjects. In the least, you need some kind of successful activity to grow out of it.

Besides, some parts of a software development project do involve learning, but a huge portion is drudgery. Solving edge cases, doing customer support for repetitive issues, solving that last pixel that is not quite right.

Making apps is great, and it's a sign of maturity to have a concern for how well received it will be.

Do you offer US visa or allow engineers to work from Canada?

What's the difference between a "problem" and a "research area"?

Research areas are made of problems to solve.

I believe pattern matching works best when solving problems with little variation from previous ones.

Novel problems requires a lot more maturing and thinking, which is when slower, longer term thinking like Polya suggests goes a long way.

New kinds of widgets, composition of classic widgets, view models, event handling (selection state, drag and drop, user inputs), visuals, shortcuts and accessibility.

Nice post!

I'm not sure if the same result is applicable to most software projects. A console emulator doesn't need several types of GUI objects, while most other projects need to display and handle input for several different types of data.

In most projects I've worked on, the proportion of GUI code to business code was different: I saw apprx. 70% GUI code to 30% business code.

So a cross platform GUI layer saves a lot more development time.

I don't use it, it returns mostly incorrect code that makes me realize it's not worth it. I'm more productive and write better code ignoring ChatGPT 95% of the time.

Do you think methodology in general isn't useful or just empirical software research?

Methodology learns from the experience of the experts, and tries to teach the techniques they know to beginners. It's very different from statistics.