Using CEED-Migrate - Revision history

Ident: /* Migrating multiple files */

2015-07-10T10:44:47Z

‎Migrating multiple files

2015-07-08T08:50:29Z

2015-07-07T17:51:17Z

‎Migrating multiple files

2015-07-07T17:51:04Z

‎Migrating multiple files

2015-07-07T17:43:52Z

‎Migrating multiple files

2015-07-07T17:43:27Z

2015-04-18T09:22:37Z

‎Python ceed-migrate examples

2014-06-12T05:36:43Z

2014-06-12T05:34:16Z

2014-06-12T05:31:59Z

@@ Line 29: / Line 29: @@
 <code>for /R %f in (*.font) do echo %f </code>
-If you see that only the file paths you want to migrate are written to console you may proceed to use the migrate command
+If you see that only the file paths you want to migrate are written to console you may proceed to use the migrate command (watch out, this will not work if there are spaces in the path)
 <code>for /R %f in (*.font) do python C:\CEED\bin\ceed-migrate font %f %fcopy</code>

@@ Line 21: / Line 21: @@
 === Migrating multiple files ===
-If you use the Windows command line (cmd) you may run "bin/runwrapper.bat" after removing the "python ceed-gui" line at the end. This will give you a CMD with all paths set that you need. You may now change to the directory with your files, e.g.:
+If you use the Windows command line (cmd) and you got CEED from the repository, you may run "bin/runwrapper.bat" after removing the "python ceed-gui" line at the end. This will give you a CMD with all paths set that you need. You may now change to the directory with your files, e.g.:
 <code> cd C:/CEGUI/datafiles/fonts </code>
@@ Line 33: / Line 33: @@
 <code>for /R %f in (*.font) do python C:\CEED\bin\ceed-migrate font %f %fcopy</code>
-Check if the .fontcopy files are fine providing the migrated version of the file as expected. If this is the case, then we can go on to delete the original files and rename the copies to the original names:
+Check if the .fontcopy files are providing the migrated version of the file as expected. If this is the case, then we can go on to delete the original files and rename the copies to the original names:
 <code>del *.font
 ren *.fontcopy *.font
 </code>

@@ Line 36: / Line 36: @@
 <code>del *.font
-ren *.fontcopy* *.font
+ren *.fontcopy *.font
 </code>

@@ Line 33: / Line 33: @@
 <code>for /R %f in (*.font) do python C:\CEED\bin\ceed-migrate font %f %fcopy</code>
-Check if the .fontcopy files are fine, if they are then delete the originals and rename the copies to the original name:
+Check if the .fontcopy files are fine providing the migrated version of the file as expected. If this is the case, then we can go on to delete the original files and rename the copies to the original names:
-<code>for /R %f in (*.font) do python C:\CEED\bin\ceed-migrate font %f %f</code>
+<code>del *.font

@@ Line 22: / Line 22: @@
 If you use the Windows command line (cmd) you may run "bin/runwrapper.bat" after removing the "python ceed-gui" line at the end. This will give you a CMD with all paths set that you need. You may now change to the directory with your files, e.g.:
 <code> cd C:/CEGUI/datafiles/fonts </code>
 and then run a command to check if you can do a for loop fetching all files, e.g.:
 <code>for /R %f in (*.font) do echo %f </code>
 If you see that only the file paths you want to migrate are written to console you may proceed to use the migrate command
 <code>for /R %f in (*.font) do python C:\CEED\bin\ceed-migrate font %f %fcopy</code>
 Check if the .fontcopy files are fine, if they are then delete the originals and rename the copies to the original name:
 <code>for /R %f in (*.font) do python C:\CEED\bin\ceed-migrate font %f %f</code>

← Older revision		Revision as of 17:43, 7 July 2015
Line 17:		Line 17:

	If you use a pre-built version such as the 0.8.0 CEED Release then you have to call the commands without the "python" at the beginning.		If you use a pre-built version such as the 0.8.0 CEED Release then you have to call the commands without the "python" at the beginning.
		+
		+
		+	=== Migrating multiple files ===
		+
		+	If you use the Windows command line (cmd) you may run "bin/runwrapper.bat" after removing the "python ceed-gui" line at the end. This will give you a CMD with all paths set that you need. You may now change to the directory with your files, e.g.:
		+	<code> cd C:/CEGUI/datafiles/fonts </code>
		+	and then run a command to check if you can do a for loop fetching all files, e.g.:
		+	<code>for /R %f in (*.font) do echo %f </code>
		+	If you see that only the file paths you want to migrate are written to console you may proceed to use the migrate command
		+	<code>for /R %f in (*.font) do python C:\CEED\bin\ceed-migrate font %f %fcopy</code>
		+	Check if the .fontcopy files are fine, if they are then delete the originals and rename the copies to the original name:
		+	<code>for /R %f in (*.font) do python C:\CEED\bin\ceed-migrate font %f %f</code>

← Older revision		Revision as of 09:22, 18 April 2015
Line 15:		Line 15:
	python ceed-migrate looknfeel TaharezLook.looknfeel TaharezLook_0_8.looknfeel		python ceed-migrate looknfeel TaharezLook.looknfeel TaharezLook_0_8.looknfeel
	python ceed-migrate font TimesNewRoman_12.font TimesNewRoman_12___V_0_8.font		python ceed-migrate font TimesNewRoman_12.font TimesNewRoman_12___V_0_8.font
		+
		+	If you use a pre-built version such as the 0.8.0 CEED Release then you have to call the commands without the "python" at the beginning.

@@ Line 8: / Line 8: @@
 === NOTE ===
-The version of ceed-migrate that comes with 'CEED-Snapshot11' has known bugs and is very likely to fail when converting your data. So it is currently recommended that you build CEED yourself to get the latest bug-fixes. Follow the above mentioned guides for building your own fresh copy CEED.
+The version of ceed-migrate that comes with 'CEED-Snapshot11' has known bugs and is very likely to fail when converting your data. So it is currently recommended that you build CEED yourself to get the latest bug-fixes. Follow the above mentioned guides for building your own fresh install of CEED.
 === Python ceed-migrate examples ===

@@ Line 7: / Line 7: @@
 Then you can migrate your old CEGUI_0.7.x data files to be compatible with CEGUI_0_8 by running "python ceed-migrate [params]" or by creating a batch file similar to the runwrapper.bat file in your CEED\bin folder to process all of your old data files into the new format.
 (Note: The version of ceed-migrate that comes with 'CEED-Snapshot11' has known bugs and very is likely to fail when converting your data. So it is currently recommended that you build CEED yourself by following the above mentioned guides.)
 === Python ceed-migrate examples ===