Skip to Content

Changes for page Click to Debug

Last modified by Kieran Kelleher on 2009/08/12 14:33
From version 17.1
edited by Pascal Robert
on 2008/12/21 20:23
Change comment: There is no comment for this version
To version 18.1
edited by David Holt
on 2009/08/12 14:33
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.probert
1 +XWiki.dholt
Content
... ... @@ -1,16 +1,16 @@
1 1  == What It Is ==
2 2  
3 -Click to Debug is a [[Click to Open]] extension that allows you to toggle binding debugging from the UI while your applicaiton is running.
3 +Click to Debug is a [[doc:Click to Open]] extension that allows you to toggle binding debugging from the UI while your application is running.
4 4  
5 5  == What You Need ==
6 6  
7 -See the [[What You Need>>Click to Open||anchor="What You Need"]] section of the Click to Open documentation if you are not already using Click to to Open.
7 +See the [[What You Need>>doc:Click to Open||anchor="What You Need"]] section of the Click to Open documentation if you are not already using Click to to Open.
8 8  
9 9  == Getting Set Up ==
10 10  
11 -See the [[Getting Set Up>>Click to Open||anchor="Getting Set Up"]] section of the Click to Open documentation if you are not already using Click to to Open.
11 +See the [[Getting Set Up>>doc:Click to Open||anchor="Getting Set Up"]] section of the Click to Open documentation if you are not already using Click to to Open.
12 12  
13 -Add this line to the ##Properties## file in your application:
13 +Add this line to the {{code language="none"}}Properties{{/code}} file in your application:
14 14  
15 15  {{code}}
16 16  
... ... @@ -20,9 +20,9 @@
20 20  
21 21  === Add Support to Application ===
22 22  
23 -If your Application.java class extends (directly or indirectly) Wonder's ERXApplication, you can skip this step. Otherwise, add this to your Application() constructor, or a method that runs before requests are processed::
23 +If your Application.java class extends (directly or indirectly) Wonder's ERXApplication, you can skip this step. Otherwise, add this to your Application() constructor, or a method that runs before requests are processed::
24 24  
25 -{{code value="java"}}
25 +{{code 0="java"}}
26 26  
27 27  NSNotificationCenter.defaultCenter().addObserver(this,
28 28   ERXSelectorUtilities.notificationSelector("applicationDidHandleRequest"),
... ... @@ -32,7 +32,7 @@
32 32  
33 33  Then add this method to handle this notification:
34 34  
35 -{{code value="java"}}
35 +{{code 0="java"}}
36 36  
37 37  /**
38 38   * When request is finished, we remove the context from thread local storage.
... ... @@ -49,7 +49,7 @@
49 49  
50 50  The next part is a method that sets ERXWOContext.currentContext() when a request is dispatched:
51 51  
52 -{{code value="java"}}
52 +{{code 0="java"}}
53 53  
54 54  /**
55 55   * When a context is created we push it into thread local storage.
... ... @@ -73,7 +73,7 @@
73 73  
74 74  And finally, add this code to support Click to Debug:
75 75  
76 -{{code value="java"}}
76 +{{code 0="java"}}
77 77  
78 78  protected void _debugValueForDeclarationNamed(WOComponent component, String verb, String aDeclarationName,
79 79   String aDeclarationType, String aBindingName,
... ... @@ -193,25 +193,25 @@
193 193  
194 194  == Using Click to Debug ==
195 195  
196 -Run your application and look in the lower, left hand corner. You should see a link like this:
196 +Run your application and look in the lower, left hand corner. You should see a link like this:
197 197  
198 -[[image:Click to Open^ClickToOpenLink.png]]
198 +[[image:attach:Click to Open@ClickToOpenLink.png]]
199 199  
200 -If you don't, check that the page has the WOLToolBar on it and that the ##er.component.clickToOpen## property is set to true and the ##er.extensions.ERXApplication.developmentMode## property is set to true.
200 +If you don't, check that the page has the WOLToolBar on it and that the {{code language="none"}}er.component.clickToOpen{{/code}} property is set to true and the {{code language="none"}}er.extensions.ERXApplication.developmentMode{{/code}} property is set to true.
201 201  
202 202  \\
203 203  
204 204  Click on this component to open the Click to Open UI:
205 205  
206 -[[image:Click to Open^WOLipsToolbar.png]]
206 +[[image:attach:Click to Open@WOLipsToolbar.png]]
207 207  
208 -**EditDisplayAd** is the page in the browser. Click on this link to open this page in Eclipse.
208 +**EditDisplayAd** is the page in the browser. Click on this link to open this page in Eclipse.
209 209  
210 210  \\
211 211  
212 -If you are looking for a sub-component of this page, click on the **Click to Debug** link. As you move your mouse over the page, the bread crumb of components will change to show you where you are. Just click to turn binding debug on (or off if it is on) for the component under the mouse in Eclipse. It is that easy
212 +If you are looking for a sub-component of this page, click on the **Click to Debug** link. As you move your mouse over the page, the bread crumb of components will change to show you where you are. Just click to turn binding debug on (or off if it is on) for the component under the mouse in Eclipse. It is that easy!
213 213  
214 -[[image:ClickToDebugInAction.png]]
214 +[[image:attach:ClickToDebugInAction.png]]
215 215  
216 216  \\
217 217  
... ... @@ -230,7 +230,7 @@
230 230  
231 231  {{/code}}
232 232  
233 -**Note**: A prefix like ##Dec 13 11:00:29 MDTask62934 (ERXNSLogLog4jBridge.java:46)## was removed from each line above to make this easier to read.
233 +**Note**: A prefix like {{code language="none"}}Dec 13 11:00:29 MDTask[WOL:62934] (ERXNSLogLog4jBridge.java:46){{/code}} was removed from each line above to make this easier to read.
234 234  
235 -So what that's showing is HatchViewTaskPage component is pushing the task binding into the HatchEditTask component with the value Task
236 -1027787, then HatchEditTask component is pushing the binding back up. So you can see here that 6th line, HatchEditTask component is pushing a null binding back out (which, in this case, was causing a problem I was trying to find).
235 +So what that's showing is HatchViewTaskPage component is pushing the task binding into the HatchEditTask component with the value Task
236 +1027787, then HatchEditTask component is pushing the binding back up. So you can see here that 6th line, HatchEditTask component is pushing a null binding back out (which, in this case, was causing a problem I was trying to find).