64bit/Help - Revision history

Dave at 22:10, 19 August 2020

2020-08-19T22:10:53Z

← Older revision		Revision as of 22:10, 19 August 2020
Line 17:		Line 17:

	When you run it will stop at the main() so you can poke around. Stepping into the constructor of CApp will enlighten you as to the startup process of the business logic of the application. feel free to remove this breakpoint.		When you run it will stop at the main() so you can poke around. Stepping into the constructor of CApp will enlighten you as to the startup process of the business logic of the application. feel free to remove this breakpoint.

	~~==Qt / Project Settings==~~
	~~[[64bit/Help/Qt Prefs\|separate page]] for that~~

	==Qt Kit Updates==		==Qt Kit Updates==
	[[64bit/Help/Qt Update\|separate page]] for that too		[[64bit/Help/Qt Update\|separate page]] for that too

			==Project Settings==
			[[64bit/Help/Qt Prefs\|separate page]] for that

	==Perforce==		==Perforce==

Dave: /* Qt Kit Updates */

2020-08-18T22:53:27Z

Qt Kit Updates

← Older revision		Revision as of 22:53, 18 August 2020
Line 17:		Line 17:

	When you run it will stop at the main() so you can poke around. Stepping into the constructor of CApp will enlighten you as to the startup process of the business logic of the application. feel free to remove this breakpoint.		When you run it will stop at the main() so you can poke around. Stepping into the constructor of CApp will enlighten you as to the startup process of the business logic of the application. feel free to remove this breakpoint.

			==Qt / Project Settings==
			[[64bit/Help/Qt Prefs\|separate page]] for that

	==Qt Kit Updates==		==Qt Kit Updates==
	[[64bit/Help/Qt Update\|separate page]] for that		[[64bit/Help/Qt Update\|separate page]] for that too

	==Perforce==		==Perforce==

Dave: /* Dock / Taskbar */

2020-05-21T17:17:01Z

Dock / Taskbar

← Older revision		Revision as of 17:17, 21 May 2020
Line 1:		Line 1:
	==Dock / Taskbar==		==Dock / Taskbar==
	You will find a reference app, '''kJams ~~Pro~~'''. Run that and you'll see what we're trying to re-create in Qt. You'll also see Qt Creator, Perforce (P4V), and the command line (terminal or cmd.exe). I've also included the Qt Maintanance Tool, just in case an important update comes out during the time you're working on the project. Also preinstalled is the TeamViewer app so we can do screen sharing in case i need to poke around on your VM or show you how to do something.		You will find a reference app, '''kJams 2''' (32bit). Run that and you'll see what we're trying to re-create in Qt. You'll also see Qt Creator, Perforce (P4V), and the command line (terminal or cmd.exe). I've also included the Qt Maintanance Tool, just in case an important update comes out during the time you're working on the project. Also preinstalled is the TeamViewer app so we can do screen sharing in case i need to poke around on your VM or show you how to do something.

	==General==		==General==

Dave: /* Dock / Taskbar */

2020-05-17T02:22:17Z

Dock / Taskbar

← Older revision		Revision as of 02:22, 17 May 2020
Line 1:		Line 1:
	==Dock / Taskbar==		==Dock / Taskbar==
	You will find a reference app, '''kJams Pro'''. Run that and you'll see what we're trying to re-create in Qt. Qt Creator, ~~and~~ Perforce (P4V), and the command line (terminal or cmd.exe). I've also included the Qt Maintanance Tool, just in case an important update comes out during the time you're working on the project. Also preinstalled is the TeamViewer app so we can do screen sharing in case i need to poke around on your VM or show you how to do something.		You will find a reference app, '''kJams Pro'''. Run that and you'll see what we're trying to re-create in Qt. You'll also see Qt Creator, Perforce (P4V), and the command line (terminal or cmd.exe). I've also included the Qt Maintanance Tool, just in case an important update comes out during the time you're working on the project. Also preinstalled is the TeamViewer app so we can do screen sharing in case i need to poke around on your VM or show you how to do something.

	==General==		==General==

Dave: /* Qt Kit Updates */

2020-04-15T17:07:59Z

Qt Kit Updates

@@ Line 19: / Line 19: @@
 ==Qt Kit Updates==
-When there is a Kit version update, follow these steps:
+[[64bit/Help/Qt Update|separate page]] for that
 ==Perforce==

Dave: /* kJams Code Hints */

2020-03-31T19:30:40Z

kJams Code Hints

← Older revision		Revision as of 19:30, 31 March 2020
Line 34:		Line 34:
	# run Qt Maintenance Tool, select "add or remove components"		# run Qt Maintenance Tool, select "add or remove components"
	# now deselect (uncheck) the old kit, and uninstall it		# now deselect (uncheck) the old kit, and uninstall it

	~~==kJams Code Hints==~~
	Open the file "kj_main.cpp" and look for "main(". Step through that, especially the construction of the CApp object, to see all the initialization that kJams does, including loading the existing (non-sql) database.

	==Perforce==		==Perforce==

Dave: /* Qt Creator */

2020-03-31T19:26:57Z

Qt Creator

← Older revision		Revision as of 19:26, 31 March 2020
Line 15:		Line 15:

	Second is "kJams" itself. kJams can build three editions: Lite, Pro, and 2, in increasing order of "more features", ie: 2 has more features than Pro, which has more features than Lite. Each edition comes in debug and release configs. You'll be working on "2 debug". You should be able to immediately "press play" to run the app.		Second is "kJams" itself. kJams can build three editions: Lite, Pro, and 2, in increasing order of "more features", ie: 2 has more features than Pro, which has more features than Lite. Each edition comes in debug and release configs. You'll be working on "2 debug". You should be able to immediately "press play" to run the app.

			When you run it will stop at the main() so you can poke around. Stepping into the constructor of CApp will enlighten you as to the startup process of the business logic of the application. feel free to remove this breakpoint.

	==Qt Kit Updates==		==Qt Kit Updates==
	When there is a Kit version update, follow these steps:		When there is a Kit version update, follow these steps:

Dave: /* Mac */

2020-03-31T19:26:42Z

Mac

← Older revision		Revision as of 19:26, 31 March 2020
Line 55:		Line 55:
	==Mac==		==Mac==
	DO NOT UPDATE to Catalina! The "Software Update" will urge you to update. RESIST!		DO NOT UPDATE to Catalina! The "Software Update" will urge you to update. RESIST!

			Please DO do any security or Mojave-related updates.

			There is no password to the user. If the OS asks for a password to do something, just press enter.

	In the Dock, the kJams app on the far right is the reference (32bit) app. The one just to its left is the app you're building (it can run but only shows a shell).		In the Dock, the kJams app on the far right is the reference (32bit) app. The one just to its left is the app you're building (it can run but only shows a shell).
	On the left next to Finder is an app called PathFinder, which is a "power user's version of Finder", i find it useful for chmod'ing using a GUI.		On the left next to Finder is an app called PathFinder, which is a "power user's version of Finder", i find it useful for chmod'ing using a GUI.

			Qt compiler will say it requires at least version 10.14 of the platform SDK, but please ignore that, do not switch SDKs

	==Parallels==		==Parallels==
	Before opening the VM for the first time, configure the "Hardware->CPU & Memory" to your computer. Use the maximum CPU & memory you can for your particular computer (stay in the green however)		Before opening the VM for the first time, configure the "Hardware->CPU & Memory" to your computer. Use the maximum CPU & memory you can for your particular computer (stay in the green however)

Dave: /* General */

2020-03-31T19:06:26Z

General

← Older revision		Revision as of 19:06, 31 March 2020
Line 7:		Line 7:
	After you have gotten preliminary database working, you'll want to turn on Music Stores. To do this, go to kJams->preferences->stores, and check the box above the three music stores, then quit and re-run the app. It will then ask to download the music stores. Note these may or may NOT be shown in the Library playlist. Even if they are, they should not be stored within the Library database, or if they are, then they should auto-purge if you run kJams and the corresponding music store's xml file is gone (ie: the user should be free to delete the xml file between runs, and have that reflect when they next run). Also, when a music store gets an update, it must be done in such a way that new meta data for an existing song updates the '''existing''' song, that no NEW song (with a new ID) is generated (code already exists, must be checked and thoroughly tested). It is okay to lose song IDs if the user manually turns off stores, or throws out store xmls. A song who's ID is in a music store that is turned off is expected to "just disappear" from all playlists. It's fine to require a restart of the app for this.		After you have gotten preliminary database working, you'll want to turn on Music Stores. To do this, go to kJams->preferences->stores, and check the box above the three music stores, then quit and re-run the app. It will then ask to download the music stores. Note these may or may NOT be shown in the Library playlist. Even if they are, they should not be stored within the Library database, or if they are, then they should auto-purge if you run kJams and the corresponding music store's xml file is gone (ie: the user should be free to delete the xml file between runs, and have that reflect when they next run). Also, when a music store gets an update, it must be done in such a way that new meta data for an existing song updates the '''existing''' song, that no NEW song (with a new ID) is generated (code already exists, must be checked and thoroughly tested). It is okay to lose song IDs if the user manually turns off stores, or throws out store xmls. A song who's ID is in a music store that is turned off is expected to "just disappear" from all playlists. It's fine to require a restart of the app for this.

	In the file system, in your user's Music folder, is the kJams folder. Inside that you'll see "kJams Library" which is a shortcut / alias (henceforth called "alias"). The existing alias points to "kJams Library (~~current~~)". This is a small library (of real songs that you can play ~~in the reference app~~) to get you started with some data. Later when you're ready to test importing a very large library, delete this alias, and make a new alias from "kJams Library (monster)". Rename the alias to be only "kJams Library", then launch kJams, which should now pick up the monster library.		In the file system, in your user's Music folder, is the kJams folder. Inside that you'll see "kJams Library" which is a shortcut / alias (henceforth called "alias"). The existing alias points to "kJams Library (small)". This is a small library (of real songs that you can play) to get you started with some data. Later when you're ready to test importing a very large library, delete this alias, and make a new alias from "kJams Library (monster)". Rename the alias to be only "kJams Library", then launch kJams, which should now pick up the monster library.

	==Qt Creator==		==Qt Creator==

Dave: /* Mac */

2020-03-31T19:05:50Z

Mac

← Older revision		Revision as of 19:05, 31 March 2020
Line 54:		Line 54:

	==Mac==		==Mac==
			DO NOT UPDATE to Catalina! The "Software Update" will urge you to update. RESIST!

	In the Dock, the kJams app on the far right is the reference (32bit) app. The one just to its left is the app you're building (it can run but only shows a shell).		In the Dock, the kJams app on the far right is the reference (32bit) app. The one just to its left is the app you're building (it can run but only shows a shell).
	On the left next to Finder is an app called PathFinder, which is a "power user's version of Finder", i find it useful for chmod'ing using a GUI.		On the left next to Finder is an app called PathFinder, which is a "power user's version of Finder", i find it useful for chmod'ing using a GUI.
			==Parallels==
			Before opening the VM for the first time, configure the "Hardware->CPU & Memory" to your computer. Use the maximum CPU & memory you can for your particular computer (stay in the green however)