Mobiles
opened this issue · comments
Great idea for the hot loading.
Have you tried this on a mobile emulator as a way to develop faster.
If I understand this you run the golang code and the qt process separately ?
Hi,
(I will comment on mobile in a moment)
So my build process tends to go:
- Build a console app and build out all the functionality of the app (see _cuiinterface folder). It doesn't need to be the greatest user experience, just enough so that you can test all the apps features, get everything working, and have 95% of the functional code in place. I do this, because console app compilation is very fast.
- Once I have built out what i think the functionality needs to be, I start work on the qml front end using the hotloader. While designing the front end, I can work out what interaction I need between the front end and the back end, and can start putting the needed signals and slots in place (but not recompile yet). Once the front end is able to do everything the console app can do (visually/functionally), I wire the signals/slots up to the backend functions (this should be very easy as it should be identical to how the console app works).
- Recompile everything and test the front end is doing what the console app did.
Rinse and repeat until the app is complete. Its quite a nice discipline as you build out the functionality in a way totally decoupled to the front ends (and minimal compiles).
So... to your question.
I did try on an Android emulator, however, having my android phone wired to computer, and using adb install -r deploy/android/build-debug.apk I could test the app very quickly (and frankly the compile/build is the slowest part by a long way). So I didn't find it necessary to configure the emulator, although it should be straight forward with the android-emulator docker container
Iphone haven't tried - would love someone to work out this process. The issue is I installed built Qt with brew, but for iphone need proper Qt installation and I haven't got space on laptop at the moment
The golang/qt process is the same process always (I don't bother with Qt creator or anything). However they run on different Go routines.
Can you suggest some examples that would give you more/enough? I'll try and produce some.
Currently working on a project using this repo as a basis, so am slowly moving things I need into this repo.
I think a good first step is to make a Makefile..
Then its very easy for a newbiew like me to see the stesp involved to get things working together.
I find Makefiles with single line for each Task to be way way better than reams of documentation etc.
That will allow me and others to try out your current code easily and understand the steps.
i woudl even include in the Makefile the calls you need to make to get therecipe code installed and the QT code insatlled on MacOS. Forget other OS's for now.
Is that cool ?
Ok, lets see how this goes.
Ive created a branch (makefile) where I have added a make file and instructions on using it: https://github.com/amlwwalker/got-qt/blob/makefile/MAKEFILE.md
So the only thing you will need to do differently is to make sure you checkout the makefile branch before following instructions.
It hopefully will run you through all the setup to have a project running. Let me know if you get stuck. Heading out but back on this tomorrow
A
P.S make install will try and clone this repo, i thought it might be useful if the makefile could be used standalone. If you have already cloned the repo, then it will gracefully just continue
screw it, I've merged this in as I have run it multiple times on my machine. It's tricky to know if the setup/install works as I already have all that configured, but I figure if its in master more people will come across it and more likely to discover a bug....
So its now in master - the makefile I mean