Skip to Content

Changes for page XcodeMigration

Last modified by William Sandner on 2011/10/19 21:07
From version 42.1
edited by Pascal Robert
on 2010/01/04 06:20
Change comment: There is no comment for this version
To version 37.1
edited by Pascal Robert
on 2011/03/27 10:24
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -11,7 +11,7 @@
11 11  {{/info}}
12 12  
13 13  {{note}}
14 -XcodeMigration is using the tool _pbprojectdump_ which is no longer present in the Xcode 3 bundle. You need to install Xcode 2.5 to get access to _pbprojectdump_ (you can it over another machine too).
14 +XcodeMigration is using the tool _pbprojectdump_ which is no longer present in the Xcode 3 bundle. You need to install Xcode 2.5 to get access to _pbprojectdump_ (you can copy it from another machine too).
15 15  
16 16  {{/note}}
17 17  
... ... @@ -19,85 +19,144 @@
19 19  
20 20  If you want to convert your Java classes from MacRoman to UTF-8, make sure your Eclipse workspace is in UTF-8 (the default is MacRoman).
21 21  
22 -{{panel align=center}}
22 +{{panel}}
23 23  
24 -!Image 1.png!
25 -{panel}
24 +!Image 1.png|align=center!
26 26  
26 +{{/panel}}
27 +
27 27  Make sure that you are in the WOLips perspective.
28 28  
29 -!Image 6.png!
30 +{{panel}}
30 30  
31 -!Image 7.png!
32 +!Image 6.png|align=center!
33 +!Image 7.png|align=center!
32 32  
33 -[Download the tool|^XcodeMigration.zip] (you don't need to expand the .zip file)
35 +{{/panel}}
34 34  
35 -Import the XcodeMigration tool into Eclipse, by selecting _File_ \-> _Import_.    
37 +[[Download the tool>>^XcodeMigration.zip]] (you don't need to expand the .zip file). You can also get it from a [[GitHub repository>>https://github.com/pascalrobert/XCodeMigration]].
36 36  
37 -!Image 2.png!
39 +Import the XcodeMigration tool into Eclipse, by selecting //File// > //Import//.
38 38  
39 -Select _Existings Projects into Workspace_ and click _Next_.
41 +{{panel}}
40 40  
41 -!Image 3.png!
43 +!Image 2.png|align=center!
42 42  
43 -Select the location of the ZIP file with the tool and click _Finish_.
45 +{{/panel}}
44 44  
45 -!Image 4.png!
47 +Select //Existings Projects into Workspace// and click //Next//.
46 46  
47 -The tool needs two projects templates, one of them is a application template, the other a framework template.  So you need to create a _WebObjects Application_ and a _WebObjects Framework_.
49 +{{panel}}
48 48  
49 -!Image 8.png!
51 +!Image 3.png|align=center!
50 50  
51 -!Image 9.png!
53 +{{/panel}}
52 52  
53 -You should see the tool and the two templates in the _WO Package Explorer_.
55 +Select the location of the ZIP file with the tool and click //Finish//.
54 54  
55 -!Image 10.png!
57 +{{panel}}
56 56  
57 -Open _config.xml_ and change the value of the _<applicationTemplatePath>_ and _<frameworkTemplatePath>_ nodes so that the path points to the templates you created below.
59 +!Image 4.png|align=center!
58 58  
59 -!Image 22.png!
61 +{{/panel}}
60 60  
61 -For each project that you want to import, you need the a _<project>_ node.&nbsp; _<path>_ is the file system path to the Xcode project, _<name>_ is the project name, minus .xcodeproj
63 +The tool needs two projects templates, one of them is a application template, the other a framework template.&nbsp; So you need to create a //WebObjects Application// and a //WebObjects Framework//.
62 62  
63 -Right-click on the _XCodeMigration.java_ class and select _Run As_ \-> _Open Run dialog..._
65 +{{panel}}
64 64  
65 -!Image 12.png!
67 +!Image 8.png|align=center!
66 66  
67 -Double-click on _Java Application_.
69 +{{/panel}}
68 68  
69 -!Image 13.png!
71 +{{panel}}
70 70  
71 -Click on the _Arguments_ tab and enter this value as a _Program arguments_.
72 -{code}
73 +!Image 9.png|align=center!
74 +
75 +{{/panel}}
76 +
77 +You should see the tool and the two templates in the //WO Package Explorer//.
78 +
79 +{{panel}}
80 +
81 +!Image 10.png|align=center!
82 +
83 +{{/panel}}
84 +
85 +Open //config.xml// and change the value of the //<applicationTemplatePath>// and //<frameworkTemplatePath>// nodes so that the path points to the templates you created below.
86 +
87 +{{panel}}
88 +
89 +!Image 22.png|align=center!
90 +
91 +{{/panel}}
92 +
93 +For each project that you want to import, you need the a //<project>// node.&nbsp; //<path>// is the file system path to the Xcode project, //<name>// is the project name, minus .xcodeproj
94 +
95 +Right-click on the //XCodeMigration.java// class and select //Run As// > //Open Run dialog...//
96 +
97 +{{panel}}
98 +
99 +!Image 12.png|align=center!
100 +
101 +{{/panel}}
102 +
103 +Double-click on //Java Application//.
104 +
105 +{{panel}}
106 +
107 +!Image 13.png|align=center!
108 +
109 +{{/panel}}
110 +
111 +Click on the //Arguments// tab and enter this value as a //Program arguments//.
112 +
113 +{{code}}
114 +
73 73  ${project_loc}/config.xml
74 -{code}
75 -!Image 21.png!
76 76  
77 -Click _Apply_ and click _Run_.
117 +{{/code}}
78 78  
119 +{{panel}}
120 +
121 +!Image 21.png|align=center!
122 +
123 +{{/panel}}
124 +
125 +Click //Apply// and click //Run//.
126 +
79 79  When it's running, you should see a output like this:
80 80  
81 -!Image 16.png!
129 +{{panel}}
82 82  
83 -To import the converted projects, open _File_ \-> _Import_ \-> _Existings projects into workspace_.&nbsp; Click _Next_. Select _Select Root Directory_ and browse to _/tmp/migrations_.&nbsp; You should see the list of projects that you converted.
131 +!Image 16.png|align=center!
84 84  
85 -!Image 17.png!
133 +{{/panel}}
86 86  
87 -Your converted projects will appear in the _WO Package Explorer_.
135 +To import the converted projects, open //File// > //Import// > //Existings projects into workspace//.&nbsp; Click //Next//. Select //Select Root Directory// and browse to ///tmp/migrations//.&nbsp; You should see the list of projects that you converted.
88 88  
89 -!Image 18.png!
137 +{{panel}}
90 90  
139 +!Image 17.png|align=center!
140 +
141 +{{/panel}}
142 +
143 +Your converted projects will appear in the //WO Package Explorer//.
144 +
145 +{{panel}}
146 +
147 +!Image 18.png|align=center!
148 +
149 +{{/panel}}
150 +
91 91  Fix all frameworks dependencies and any other build errors.&nbsp; It's done.
92 92  
93 -h1. FAQ
153 += FAQ =
94 94  
95 -*Q.*&nbsp; I can't a _Could not find working dir for project_ error when I launch my converted application.
96 -*A.*&nbsp; Make sure that, in _config.xml_, _<applicationTemplatePath>_ is set to a WO application instead of a WO framework.
155 +**Q.**&nbsp; I can't a //Could not find working dir for project// error when I launch my converted application.
156 +**A.**&nbsp; Make sure that, in //config.xml//, //<applicationTemplatePath>// is set to a WO application instead of a WO framework.
97 97  
98 -*Q.*&nbsp; Some of my resources are missing or in the wrong folder.
99 -*A.*&nbsp; The tool detect files that should be marked as _Resources_ by file extension or name. If a file is not a Java class or one of the file type in the _Resources_ list, the file will be move to the _WebServerResources_ folder instead. You just have to move the files to the Resources folder when needed. If you have file types who should be detected as resources, you can add the needed code in the _copyFiles_ method.
158 +**Q.**&nbsp; Some of my resources are missing or in the wrong folder.
159 +**A.**&nbsp; The tool detect files that should be marked as //Resources// by file extension or name. If a file is not a Java class or one of the file type in the //Resources// list, the file will be move to the //WebServerResources// folder instead. You just have to move the files to the Resources folder when needed. If you have file types who should be detected as resources, you can add the needed code in the //copyFiles// method.
100 100  
101 -*Q.*&nbsp; My application is localized and the content in the components are displaying the wrong caracters.
102 -*A.*&nbsp; If you set the _<convertToUTF8>_ node to true, your Java classes will be converted from MacRoman to UTF-8, but the tool will NOT modify the .woo file so that they use UTF-8. Either you stay in MacRoman and change the value of _<convertToUTF8>_ to _false_, or you will have to modify your components so that they use UTF-8
103 -{{/panel align=center}}
161 +**Q.**&nbsp; My application is localized and the content in the components are displaying the wrong caracters.
162 +**A.**&nbsp; If you set the //<convertToUTF8>// node to true, your Java classes will be converted from MacRoman to UTF-8, but the tool will NOT modify the .woo file so that they use UTF-8. Either you stay in MacRoman and change the value of //<convertToUTF8>// to //false//, or you will have to modify your components so that they use UTF-8.