Skip to Content
Last modified by Ray Kiddy on 2010/02/27 14:51
From version 128.1
edited by Johan Henselmans
on 2007/06/19 22:57
Change comment: There is no comment for this version
To version 130.1
edited by Pascal Robert
on 2007/06/20 04:21
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.johanhenselmans
1 +XWiki.probert
Content
... ... @@ -2,17 +2,17 @@
2 2  
3 3  === The first most common error: ===
4 4  
5 -Eclipse/WOLips does not run properly in java 1.4.2.
5 +Eclipse/WOLips does not run properly in java 1.4.2.
6 6  
7 -Run it using **JavaVM1.5**.
7 +Run it using **JavaVM1.5**.
8 8  
9 -Only Way: **1.5**.
9 +Only Way: **1.5**.
10 10  
11 11  **One more time: 1.5**
12 12  
13 13  ==== How to get eclipse running with Java1.5? ====
14 14  
15 - go to /Applications/Utilities/Java/J2SE 5.0/Java Preferences. Select J2SE5.0
15 +go to /Applications/Utilities/Java/J2SE 5.0/Java Preferences. Select J2SE5.0
16 16  
17 17  [[image:JavaRunTimeApplicationSettings.png]]
18 18  
... ... @@ -20,27 +20,27 @@
20 20  
21 21  ==== I can not get help to start in my browser, things work flakey ====
22 22  
23 -Eclipse 3.2.2 is a big, big project. It uses lots of frameworks. Sometimes these frameworks are already in some way available in your environment, but they are old versions, that do not do the expected thing in Eclipse. I had the experience that the help did not start in the browser. If that happens to you, remove all the jars of which you are not sure why they are there in /Library/Java/Extensions. You do not have to remove things like frontbase.jar, postgresql.jar etc.
23 +Eclipse 3.2.2 is a big, big project. It uses lots of frameworks. Sometimes these frameworks are already in some way available in your environment, but they are old versions, that do not do the expected thing in Eclipse. I had the experience that the help did not start in the browser. If that happens to you, remove all the jars of which you are not sure why they are there in /Library/Java/Extensions. You do not have to remove things like frontbase.jar, postgresql.jar etc.
24 24  
25 -This is actually fixed in Eclipse 3.3 (Eclipse reads first it's own paths, and then the system paths), but WOLips does not support Eclipse3.3 yet.
25 +This is actually fixed in Eclipse 3.3 (Eclipse reads first it's own paths, and then the system paths), but WOLips does not support Eclipse3.3 yet.
26 26  
27 27  === The third most common error ===
28 28  
29 29  ==== WOLips does not behave like you describe. (Use nightly) ====
30 30  
31 -WOLips updates often. And although there is a stable version, the nightly version is where it's at. It is used in production by the wonderful people from MDimension and other WebObjects developers. If something brakes there, it gets fixed immediately.
31 +WOLips updates often. And although there is a stable version, the nightly version is where it's at. It is used in production by the wonderful people from MDimension who develop WOLips and other WebObjects developers. If something breaks in nightly, it gets fixed immediately. They depend on it themselves.
32 32  
33 -http:~/~/webobjects.mdimension.com/wolips/nightly/ should be in your Eclipse update site, under Help->Software Update->Find and install->Search for new features to install
33 +[[http://webobjects.mdimension.com/wolips/nightly/]] should be in your Eclipse update site, under Help->Software Update->Find and install->Search for new features to install
34 34  
35 35  === The fourth most common error ===
36 36  
37 37  ==== I can not install the projects I built, the WOLips install does not work, strange things happen. (be admin) ====
38 38  
39 -Allthough we all know that we should not run as admin, for installing Eclipse you'd better be. If you have installed Eclipse on one of the common places, or it has been installed for you, than the permission from the Eclipse folder will prevent you to install WOLips and other plugins. Make sure that, if you are installing plugins, You are allowed to do so.
39 +Allthough we all know that we should not run as admin, for installing Eclipse you'd better be. If you have installed Eclipse on one of the common places, or it has been installed for you, than the permission from the Eclipse folder will prevent you to install WOLips and other plugins. Make sure that, if you are installing plugins, You are allowed to do so.
40 40  
41 41  ==== More admin problems ====
42 42  
43 -If installing your frameworks does not work, than it might be that you are running as a plain user, not admin user. The WOLips ant install by default tries to install in /Library/Frameworks, and Apps in /Library/WebObjects/JavaApplications. As a plain user you should not have permission to write there.
43 +If installing your frameworks does not work, than it might be that you are running as a plain user, not admin user. The WOLips ant install by default tries to install in /Library/Frameworks, and Apps in /Library/WebObjects/JavaApplications. As a plain user you should not have permission to write there.
44 44  
45 45  === User questions ===
46 46  
... ... @@ -54,7 +54,7 @@
54 54  
55 55  [[image:FilterProperties.png]]
56 56  
57 -==== Where did all my code go? ====
57 +==== Where did all my code go? ====
58 58  
59 59  Suppose you suddenly ended up with something like this:
60 60  
... ... @@ -70,41 +70,41 @@
70 70  
71 71  [[image:chooseperspective.png]]
72 72  
73 -==== I have the right perspective, but it is all screwed up. ====
73 +==== I have the right perspective, but it is all screwed up. ====
74 74  
75 -That happens. A lot, if you are inexperienced. And even if you are experienced. Eclipse does some things inadvertently, and as it does not conform to the Apple Interface guidelines, you might press something that has an other effect in Eclipse.
75 +That happens. A lot, if you are inexperienced. And even if you are experienced. Eclipse does some things inadvertently, and as it does not conform to the Apple Interface guidelines, you might press something that has an other effect in Eclipse.
76 76  
77 -Do not worry: there is a menu button, Windown->Reset Perspective that will give you the original settings back.
77 +Do not worry: there is a menu button, Windown->Reset Perspective that will give you the original settings back.
78 78  
79 79  ==== Which file from which project am I editing? ====
80 80  
81 -If you open a lot of projects at the same time, you'll sometime find yourself editing a few Session.java or localizable.strings files at the same time. How can you see which file from what project you are editing? There is a simple trick for that: in the Package Explorer window, click on the icon with the two arrows on it. From now on, if you select another file in the editor window, you'll be directed to that file in the project in Package Explorer.
81 +If you open a lot of projects at the same time, you'll sometime find yourself editing a few Session.java or localizable.strings files at the same time. How can you see which file from what project you are editing? There is a simple trick for that: in the Package Explorer window, click on the icon with the two arrows on it. From now on, if you select another file in the editor window, you'll be directed to that file in the project in Package Explorer.
82 82  
83 83  [[image:SeeFileinProject.png]]
84 84  
85 85  ==== Another app is running than I expected: ====
86 86  
87 -Running an app works a bit different from running an app in XCode.
87 +Running an app works a bit different from running an app in XCode.
88 88  
89 -Normally you select the project in the Package Explorer, goto to the contextual menu (via right click), then click Run WOApplication. you can also go to the Run menu. Or to the Run icon.
89 +Normally you select the project in the Package Explorer, goto to the contextual menu (via right click), then click Run WOApplication. you can also go to the Run menu. Or to the Run icon.
90 90  
91 91  Don't suppose you are running the app you are running because you selected the project and pressed the run button in the toolbar. It will run the last application you have run, no matter what you have selected in the package explorer. You have to do a "run as", select your program and then you might get your app.
92 92  
93 -=== I want to run my app with some other arguments. ===
93 +=== I want to run my app with some other arguments. ===
94 94  
95 -The way eclipse works, it saves a set of arguments in which your app has run. This set of arguments have some default settings, depending on which type of application you are running. You can save these arguments in your project, for later use.
95 +The way eclipse works, it saves a set of arguments in which your app has run. This set of arguments have some default settings, depending on which type of application you are running. You can save these arguments in your project, for later use.
96 96  
97 97  ==== Changing the Launch arguments: ====
98 98  
99 -Select Project in Package Explorer, from menu choose Run->Run... , from contextual menu choose Run As->Run
99 +Select Project in Package Explorer, from menu choose Run->Run... , from contextual menu choose Run As->Run
100 100  
101 101  [[image:LaunchArgs1.png]]
102 102  
103 -You'll get into the create,manage and run configurations window. If there are any launch configurations available in your projects, you will already see them here. If there aren't any, a new one will be created.
103 +You'll get into the create,manage and run configurations window. If there are any launch configurations available in your projects, you will already see them here. If there aren't any, a new one will be created.
104 104  
105 -Normally the proper settings for a WOApplication are all in place, if you have created the application from the contextual menu. See the tutorials.
105 +Normally the proper settings for a WOApplication are all in place, if you have created the application from the contextual menu. See the tutorials.
106 106  
107 -By default these settings are stored in the workspace, not in the project. If you want to store them in the project, you have to change the settings under the "Common" tab, from "local" file to "shared file", and you can save it then in your project for future use.
107 +By default these settings are stored in the workspace, not in the project. If you want to store them in the project, you have to change the settings under the "Common" tab, from "local" file to "shared file", and you can save it then in your project for future use.
108 108  
109 109  [[image:Launchsaving.png]]
110 110  
... ... @@ -116,9 +116,9 @@
116 116  
117 117  ==== I see all that magic typing with code completion going on. How do you do that? ====
118 118  
119 -The shortcut is CMD-space on the Mac, by default. It is also known as contextual assist.
119 +The shortcut is CMD-space on the Mac, by default. It is also known as contextual assist.
120 120  
121 -Actually, it is real magic. The trick is that it works in a contextual way. So the program knows what kind code can be expected where. For instance, if you are inside the bindings of a WOComponent, it will know which bindings are there. Just press CMD-Space, and you will get the possible endings.
121 +Actually, it is real magic. The trick is that it works in a contextual way. So the program knows what kind code can be expected where. For instance, if you are inside the bindings of a WOComponent, it will know which bindings are there. Just press CMD-Space, and you will get the possible endings.
122 122  
123 123  [[image:ContextualContentAssist.png]]
124 124  
... ... @@ -126,13 +126,13 @@
126 126  
127 127  I don't know. It depends on the plugins you are running. Fortunately, there is a shortcut to end all shortcuts:
128 128  
129 -cmd-shift-l= show the shortcuts in a popup-window. Pressing cmd-shift-l one more time will show you all the shortcuts via the preferences.
129 +cmd-shift-l= show the shortcuts in a popup-window. Pressing cmd-shift-l one more time will show you all the shortcuts via the preferences.
130 130  
131 131  Some general Eclipse shortcuts:
132 132  
133 -cmd-1= Quickfix: suggest you a fix for your errror
134 -cmd-e= quick switch to other open documents
135 -cmd-space= completion, also known as content assist. This one screws up with the standard settings for Spotlight, which are also cmd-space. Some have tried to move cmd-space to something else in Eclipse, but that does not seems to be picked up everywhere. Better replace Spotlight to something else.
133 +cmd-1 = Quickfix: suggest you a fix for your errror
134 +cmd-e = quick switch to other open documents
135 +cmd-space = completion, also known as content assist. This one screws up with the standard settings for Spotlight, which are also cmd-space. Some have tried to move cmd-space to something else in Eclipse, but that does not seems to be picked up everywhere. Better replace Spotlight to something else.
136 136  
137 137  Some shortcuts that are available from WOLips (gracefully donated by Mike Schrag):
138 138  
... ... @@ -147,3 +147,9 @@
147 147  cmd-o o = include superclass
148 148  cmd-shift-g = show references
149 149  F3 = go to declaration
150 +
151 +Another nice overview of shortcuts that Edgar Klein sent me can be found here: [[http://eclipse-tools.sourceforge.net/Keyboard_shortcuts_(3.0).pdf]]. It can be even printed out on one double page, so you can put it above your bed.
152 +
153 +==== I have the choice of doing a WOApplication or a WOnderApplication, which one should I use ? ====
154 +
155 +Even if it's got "Wonder" in it's name, "WOnderApplication" and "WOnderFramework" don't include any Wonder related stuff in the project, it's just a different project layout than the other two. The Wonder layouts will become the only layout in the future, so use those.