Changes for page WOLips-Eclipse beginner mistakes and questions
Last modified by Ray Kiddy on 2010/02/27 14:51
From version 48.1
edited by Pascal Robert
on 2007/12/20 08:52
on 2007/12/20 08:52
Change comment:
There is no comment for this version
To version 45.1
edited by Gavin Eadie
on 2009/02/18 00:12
on 2009/02/18 00:12
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. probert1 +XWiki.gavineadie - Content
-
... ... @@ -2,8 +2,10 @@ 2 2 3 3 {{toc}}{{/toc}} 4 4 5 -= ==The first most common error:===5 += Common errors = 6 6 7 +== The first most common error: == 8 + 7 7 Eclipse/WOLips does not run properly in java 1.4.2. 8 8 9 9 Run it using **JavaVM1.5**. ... ... @@ -12,47 +12,53 @@ 12 12 13 13 **One more time: 1.5** 14 14 15 - ====How to get eclipse running with Java1.5?====17 +How to get eclipse running with Java1.5? 16 16 17 17 go to /Applications/Utilities/Java/J2SE 5.0/Java Preferences. Select J2SE5.0 18 18 19 19 [[image:JavaRunTimeApplicationSettings.png]] 20 20 21 -== =The second most common error ===23 +== The second most common error == 22 22 23 -=== =I can not get help to start in my browser, things work flakey ====25 +=== I can not get help to start in my browser, things work flakey === 24 24 27 +{{tip}} 28 +The following is somewhat out of date -- in general terms it is still true but (as of mid-Feb 2009) Eclipse 3.4(.1) is the required version for (nightly and stable) WOLips, and WOLips nightly is around build number (3.4.)5676. 29 +{{/tip}} 30 + 25 25 Eclipse 3.3 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. 26 26 27 27 This should actually fixed in Eclipse 3.3 (Eclipse reads first it's own paths, and then the system paths), but WOLips supports Eclipse3.3 only in the nightly builds. For 3.2.2 you should use the stable build. 28 28 29 -== =The third most common error ===35 +== The third most common error == 30 30 31 -=== =WOLips does not behave like you describe. (Use nightly only on 3.3) ====37 +=== WOLips does not behave like you describe. (Use nightly only on 3.3) === 32 32 33 33 WOLips updates often. There is a stable version, (4118) that should be used on Eclipse 3.2.2, the nightly version is where it's at now for 3.3 (Officially released 29th of june 2007). 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. 34 34 35 35 [[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 36 36 37 -== =The fourth most common error ===43 +== The fourth most common error == 38 38 39 -=== =I can not install the projects I built, the WOLips install does not work, strange things happen. (be admin) ====45 +=== I can not install the projects I built, the WOLips install does not work, strange things happen. (be admin) === 40 40 41 41 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. 42 42 43 - ====More admin problems====49 +If you are working on a Mac where multiple users will need to use Eclipse, you have to change Eclipse's permissions because it will not allow other people to install features, even if they are in the admin group. 44 44 45 - If installing yourframeworksdoes not work, than it might be that you are running as a plain user, not adminuser. The WOLips ant install by default tries toinstall in /Library/Frameworks, and Apps in /Library/WebObjects/JavaApplications. As a plain user you should not have permission to write there.51 +More admin problems 46 46 47 - ===Userquestions===53 +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/Applications. As a plain user you should not have permission to write there. 48 48 49 -= ===I createda component but I don't see itn the Componentsfolder====55 += User questions = 50 50 57 +== I created a component but I don't see it in the Components folder == 58 + 51 51 When you create a new component, it will put the component into the highlighted folder in the Package Explorer. For example, if the current highlighted folder is the project name, the component will be created in the top-level folder of the project. So you will find your component there and you can move it to the Components folder. 52 52 53 53 So when you create a new component, make sure that you highlight the Components folder, or right-click on the Components folder and select New->Component, it will be created into the good folder. 54 54 55 -== ==Why don't I see all my files? ====63 +== Why don't I see all my files? == 56 56 57 57 Not all the files are presented, some are filtered away. In Package Explorer (In WOLips pespective, the upper left window), go to the right corner of that window, there is a caret. Under this caret, there is a Filter option.Click on it to see what get's filtered away. 58 58 ... ... @@ -62,7 +62,7 @@ 62 62 63 63 [[image:FilterProperties.png]] 64 64 65 -== ==Where did all my code go? ====73 +== Where did all my code go? == 66 66 67 67 Suppose you suddenly ended up with something like this: 68 68 ... ... @@ -78,19 +78,19 @@ 78 78 79 79 [[image:chooseperspective.png]] 80 80 81 -== ==I have the right perspective, but it is all screwed up. ====89 +== I have the right perspective, but it is all screwed up. == 82 82 83 83 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. 84 84 85 85 Do not worry: there is a menu button, Windown->Reset Perspective that will give you the original settings back. 86 86 87 -== ==Which file from which project am I editing? ====95 +== Which file from which project am I editing? == 88 88 89 89 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. 90 90 91 91 [[image:SeeFileinProject.png]] 92 92 93 -== ==Another app is running than I expected: ====101 +== Another app is running than I expected: == 94 94 95 95 Running an app works a bit different from running an app in XCode. 96 96 ... ... @@ -98,11 +98,11 @@ 98 98 99 99 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. 100 100 101 -== =I want to run my app with some other arguments. ===109 +== I want to run my app with some other arguments. == 102 102 103 103 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. 104 104 105 -== ==Changing the Launch arguments: ====113 +== Changing the Launch arguments: == 106 106 107 107 Select Project in Package Explorer, from menu choose Run->Run... , from contextual menu choose Run As->Run 108 108 ... ... @@ -116,22 +116,29 @@ 116 116 117 117 [[image:Launchsaving.png]] 118 118 119 -== ==I want to open EntityModeler in a new window, so it does not get in the way of WOLips ====127 +== I want to open EntityModeler in a new window, so it does not get in the way of WOLips == 120 120 121 121 There is a setting in the WOLips preferences, which will get your EOModel started in a separate EntityModelere window: 122 122 123 123 [[image:OpenEntityModelerInNewWindowAnnot.png]] 124 124 125 -== ==I see all that magic typing with code completion going on. How do you do that? ====133 +== I see all that magic typing with code completion going on. How do you do that? == 126 126 127 -The shortcut is C MD-space on the Mac, by default. It is also known as contextual assist.135 +The shortcut is Control-space on the Mac, by default. It is also known as contextual assist. 128 128 129 -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 C MD-Space, and you will get the possible endings.137 +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 Control-Space, and you will get the possible endings. 130 130 131 131 [[image:ContextualContentAssist.png]] 132 132 133 - ==== Which shortcutsare available? ====141 +{{warning}} 134 134 143 +Please note that Control-Space is also the key combo for Spotlight. You need to either change the key combo for Eclipse (Preferences->General->Keys) or for Spotlight (System Prefences->Spotlight). 144 + 145 + 146 +{{/warning}} 147 + 148 +== Which shortcuts are available? == 149 + 135 135 I don't know. It depends on the plugins you are running. Fortunately, there is a shortcut to end all shortcuts: 136 136 137 137 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. ... ... @@ -158,17 +158,17 @@ 158 158 159 159 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. 160 160 161 -== ==I have the choice of doing a WOApplication or a WOnderApplication, which one should I use ? ====176 +== I have the choice of doing a WOApplication or a WOnderApplication, which one should I use ? == 162 162 163 163 If you use WOLips/Eclipse 3.2, or if you use a WOLips 3.3 from before December 2007, the layout for the WOApplication and for the WOnder Application was quite different. Starting in recent (December 2007 and later) builds of WOLips, the layout is the same ("WebObjects Application" use the "Wonder" layout), the only difference between them is that the Wonder-type application and framework will link to the Wonder frameworks (ERJars and ERExtensions), Application.java will extend from ERXApplication and Session.java will extend from ERXSession. 164 164 165 165 If you are using a old build of WOLips, you should use the Wonder layout, you just need to remove the references to ER if you don't use Wonder. 166 166 167 -== ==If I right-click on an folder and select "New", I don't see "EOModel" or "WOComponent" as options. ====182 +== If I right-click on an folder and select "New", I don't see "EOModel" or "WOComponent" as options. == 168 168 169 169 Make sure that your current perpective is "WOLips", if you are in the "Java" or "J2EE" perpective, all WebObjects-related file types are not available. 170 170 171 -== ==Component Bindings are Showing Errors, but No Error Is Present ====186 +== Component Bindings are Showing Errors, but No Error Is Present == 172 172 173 173 This can occur for example where you are overriding ##valueForKey(..)## and so the component editor is not able to know that a keypath is valid. In this case add ##~/~/VALID## at the end the association and Eclipse will stop taking this to be a bad binding. An example follows; 174 174 ... ... @@ -180,10 +180,10 @@ 180 180 181 181 {{/noformat}} 182 182 183 -== ==Classpath Order ====198 +== Classpath Order == 184 184 185 - [[App]]186 - [[Non-App-Projects]]187 - [[Non-Apple-Framework jars]]188 - [[Apple-Framework jars]]189 - [[normal jars (everything not named Foo.framework.Foo.jar)]]200 +App 201 +Non-App-Projects 202 +Non-Apple-Framework jars 203 +Apple-Framework jars 204 +normal jars (everything not named Foo.framework/../Foo.jar)