Changes for page Usage for Windows

Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -1,28 +1,0 @@
1		-1) Create the structure:
2		-C:pple
3		-C:ppleocalibraryrameworks (equivalent to /Library/Frameworks on the Mac)
4		-C:ppleibraryrameworks (equivalent to /System/Library/Frameworks on the Mac)
5		-
6		-2) Copy all the frameworks from /System/Library/Frameworks on a Mac that are named Java except for JavaScriptCore and JavaVM to C:ppleibraryrameworks
7		-
8		-3) If you copied a 5.2, you will need to put a Windows License.key in JavaWebObjects.framework/Resources.  If you copied a 5.3, I think it's a universal license key.
9		-
10		-4) Create a wobuild.properties file in C:ocuments and Settingsyour user>ibrary with the contents:
11		-wo.woroot=C:/Apple
12		-wo.wolocalroot=C:/Apple/Local
13		-wo.wosystemroot=C:/Apple
14		-wo.homeroot=C:/Temp
15		-eclipse.home=C:/Programs Files/eclipse
16		-wo.dir.library.frameworks=C:/Apple/Library/Frameworks
17		-
18		-5) Install eclipse 3.3.1.1
19		-
20		-6) Install WOLips nightly from http:~/~/webobjects.mdimension.com/wolips/nightly
21		-
22		-That should be it, I think?  The things that are problematic right now on Windows:
23		-1) The woproject/**.patternset don't work quite right on Windows.  If you don't have subfolders in your Resources/Components/etc, you can work around it by converting Components~/~/**/etc/** to Components/**, same w/ Resources and WebServerResources
24		-2) Couple images have backgrounds that should not
25		-3) Outline view in component editor is not right
26		-4) AutoOpenInBrowser doesn't work unless you override Application.//isSupportedDevelopmentPlatform to return true//
27		-
28		-I THINK that was it, but there might have been a couple other misc items .. I'll have to go back through and doublecheck.