Changes for page Click to Open

Last modified by Kieran Kelleher on 2012/07/21 20:41

From 54.1 to 55.1 From 58.1 to 59.1

From version 55.1

edited by Marc Guenther
on 2010/01/25 12:44

Change comment: fix wrong method call: getBoolean() -> parseBoolean()

To version 58.1

edited by Pascal Robert
on 2012/07/21 20:41

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (2 modified, 0 added, 0 removed)

Details

Page properties

Author

@@ -1,1 +1,1 @@
--XWiki.marc
++XWiki.probert

Content

@@ -1,36 +1,52 @@
  == What It Is ==
--Click to Open (C2O) allows you to open components in Eclipse directly from the running application in your browser  Click to Open appears in the lower left corner of browser as part of the pages of your running application.  Clicking on this component, and then on an object in the browser window, opens the relevant WOComponent in Eclipse.   This makes life easier for UI designers and for developers getting familiar with new projects.  It also provides some other very slick debugging tools.
++Click to Open (C2O) allows you to open components in Eclipse directly from the running application in your browser! Click to Open appears in the lower left corner of browser as part of the pages of your running application. Clicking on this component, and then on an object in the browser window, opens the relevant WOComponent in Eclipse. This makes life easier for UI designers and for developers getting familiar with new projects. It also provides some other very slick debugging tools.
--Check out the [[screencast at the mDimension build site>>http://webobjects.mdimension.com/wolips/support/screencasts/WOLipsFramework.m4v]]
++Check out the [[screencast at the mDimension build site>>url:http://webobjects.mdimension.com/wolips/support/screencasts/WOLipsFramework.m4v||shape="rect"]]
--Click to Open is a browser based extension to WOLips found in [[Project Wonder>>WONDER:Home]].  All of the Wonder ERD2W components support Click to Open.
++Click to Open is a browser based extension to WOLips found in [[Project Wonder>>doc:WONDER.Home]]. All of the Wonder ERD2W components support Click to Open.
  **Note that click-to-open support is expensive, because it has to dig around your component HTML quite a bit, so you will take a performance hit in development to have it enabled.**
++*Also note that if you use ERExcelLook or ERPDFGeneration that you will want to disable Click to Open in development. The former you can do in a rule:
++
++{{code}}
++*10 : pageConfiguration like '*Excel' => clickToOpenEnabled = "false" [com.webobjects.directtoweb.BooleanAssignment]
++{{/code}}
++
++The latter in your component:
++
++{{code}}
++
++public boolean clickToOpenEnabled(WOResponse response, WOContext context) {
++     return false;
++ }
++
++{{/code}}
++
  == What You Need ==
--You need the **WOLips** framework that is part of Project Wonder.  You also need the **ERExtensions** framework that is part of Project Wonder on the class path at runtime.   If you already use Project Wonder, you are almost done.
++You need the **WOLips** framework that is part of Project Wonder. You also need the **ERExtensions** framework that is part of Project Wonder on the class path at runtime. If you already use Project Wonder, you are almost done.
--If you are not using Project Wonder, you can download it from [[mDimension's site>>http://webobjects.mdimension.com/wonder/]], untar the frameworks, and copy just the WOLips.framework and ERExtensions.framework to where you have the rest of your frameworks (usually /Library/Frameworks or /Library/Frameworks).
++If you are not using Project Wonder, you can download it from [[mDimension's site>>url:http://webobjects.mdimension.com/wonder/||shape="rect"]], untar the frameworks, and copy just the WOLips.framework and ERExtensions.framework to where you have the rest of your frameworks (usually /Library/Frameworks or ~~/Library/Frameworks).
  == Getting Set Up ==
  === Add the WOLips.framework ===
--Follow the [[tutorial>>Add a Framework Dependency]] on adding a framework to add WOLips.framework and ERXExtentions.framework to your application.
++Follow the [[tutorial>>doc:Add a Framework Dependency]] on adding a framework to add WOLips.framework and ERXExtentions.framework to your application.
  === Add Support to Component Base Class ===
--If your components extend Wonder's ERXComponent, you can skip this step.  Once again, using Wonder makes your life easier.
++If your components extend Wonder's ERXComponent, you can skip this step. Once again, using Wonder makes your life easier.
--If you don't have a custom component base class, you really should.  Using com.webobjects.appserver.WOComponent as the super-class for your pages and components is just going to leave you doing the same things over and over.  If you don't have one, you might want to start using the ClickToOpenComponent below.
++If you don't have a custom component base class, you really should. Using com.webobjects.appserver.WOComponent as the super-class for your pages and components is just going to leave you doing the same things over and over. If you don't have one, you might want to start using the ClickToOpenComponent below.
  You will need to add the appendToResponse(WOResponse, WOContext) method below to your component base class, or add this code to your appendToResponse method if you already have one.
  Here is an example implementation of a component base class and of Click to Open support:
--{{code value="java"}}
++{{code 0="java"}}
  package net.com.foo.bar;
@@ -63,7 +63,7 @@
  For components that can't sub-class ClickToOpenComponent (directly or indirectly), you can enable Click to Open by adding this method to your component:
--{{code value="java"}}
++{{code 0="java"}}
  public void appendToResponse(WOResponse response, WOContext context)
  {
@@ -78,9 +78,9 @@
  === Add Support to Application ===
--If your Application.java class extends Wonder's ERXApplication, you can skip this step too.  Otherwise, add a developmentMode() method like this:
++If your Application.java class extends Wonder's ERXApplication, you can skip this step too. Otherwise, add a developmentMode() method like this:
--{{code value="java"}}
++{{code 0="java"}}
  private Boolean isDevelopmentMode;
  public boolean developmentMode() {
@@ -113,7 +113,7 @@
  === Provide prototype.js ===
--WOLips.framework needs a prototype.js.  If you are using Ajax framework, you don't need to do anything, because it will default to use Ajax.framework's prototype.js.  However, if you are not, add this to your application's Properties file (as an example, change the values as appropriate):
++WOLips.framework needs a prototype.js. If you are using Ajax framework, you don't need to do anything, because it will default to use Ajax.framework's prototype.js. However, if you are not, add this to your application's Properties file (as an example, change the values as appropriate):
  {{code}}
@@ -126,17 +126,17 @@
  In your page wrapper's HTML template, add
--{{code value="html"}}
++{{code 0="html"}}
  <wo:WOLToolBar/>
  {{/code}}
--and you're done.  If you don't have a [[page wrapper>>WO:Web Applications-Development-Examples-Page Layout]], you will have to add this to every page.  Hint: page wrappers make your life easier.
++and you're done. If you don't have a [[page wrapper>>doc:Development-Examples-Page Layout]], you will have to add this to every page. Hint: page wrappers make your life easier.
  If you are using the old WO template syntax, add this to the .html file:
--{{code value="html"}}
++{{code 0="html"}}
  <webobject name="WOLToolBar" />
@@ -144,7 +144,7 @@
  And add this to the .wod file:
--{{code value="html"}}
++{{code 0="html"}}
  WOLToolBar: WOLToolBar{
  }
@@ -153,13 +153,13 @@
  === Configure WOLips Server ===
--You must be using a recent version of WOLips that supports the **WOLips Server**.  In your WOLips preferences, you must enable the WOLips Server and set the communication password.  This password must match the ##wolips.password## in the **Set Application Properties** section above.
++You must be using a recent version of WOLips that supports the **WOLips Server**. In your WOLips preferences, you must enable the WOLips Server and set the communication password. This password must match the {{code language="none"}}wolips.password{{/code}} in the **Set Application Properties** section above.
  **Turning on the WOLips Server requires Eclipse to be restarted.**
--[[image:WOLipsServerPreferences.png]]
++[[image:attach:WOLipsServerPreferences.png]]
--You can optionally change the port number.  If you do change the port number, see ##wolips.port## in the **Set Application Properties** section above.
++You can optionally change the port number. If you do change the port number, see {{code language="none"}}wolips.port{{/code}} in the **Set Application Properties** section above.
  === Enable Click to Open ===
@@ -170,33 +170,32 @@
  If you are not using Wonder, add the Launch parameters as follows:
--* Parameter = **Der.component.clickToOpen=true**, Argument = **true**
--* Parameter = **Der.extensions.ERXApplication.developmentMode=true** Argument = **true**
--     (needing to have "true" twice is a [[minor bug>>http://issues.objectstyle.org/jira/browse/WOL-787]]. The really important one is the first one)
++* Parameter = **-Der.component.clickToOpen=true**, Argument = **true**
++* Parameter = **-Der.extensions.ERXApplication.developmentMode=true** Argument = **true**
--[[image:EnableClickToOpen.png]]
++[[image:attach:EnableClickToOpen.png]]
  == Using Click to Open ==
--Run your application and look in the lower, left hand corner.  You should see a link like this:
++Run your application and look in the lower, left hand corner. You should see a link like this:
--[[image:ClickToOpenLink.png]]
++[[image:attach:ClickToOpenLink.png]]
--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.
++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.
  \\
  Click on this component to open the Click to Open UI:
--[[image:WOLipsToolbar.png]]
++[[image:attach:WOLipsToolbar.png]]
--**EditDisplayAd** is the page in the browser.  Click on this link to open this page in Eclipse.
++**EditDisplayAd** is the page in the browser. Click on this link to open this page in Eclipse.
  \\
--If you are looking for a sub-component of this page, click on the **Click to Open** 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 open the component under the mouse in Eclipse.  It is that easy
++If you are looking for a sub-component of this page, click on the **Click to Open** 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 open the component under the mouse in Eclipse. It is that easy!
--[[image:ClickToOpenInAction.png]]
++[[image:attach:ClickToOpenInAction.png]]
  \\
@@ -205,5 +205,5 @@
  * Esc is a shortcut for getting out of click-to-open mode
  * hold down the Cmd key while you move the mouse around and it will highlight the component
  * Cmd-click it will popup the stack of components and you can pick from the stack:
--[[image:ComponentStack.png]]
--* you can set the binding ##expanded=true;## on WOLToolBar so it's open by default, instead of closed
++[[image:attach:ComponentStack.png]]
++* you can set the binding {{code language="none"}}expanded=true;{{/code}} on WOLToolBar so it's open by default, instead of closed

Changes for page Click to Open

Summary

Details

Applications

Navigation

My Recent Modifications

Need help?