Changes for page Browser as a Development Tool
Last modified by Kieran Kelleher on 2010/01/27 13:26
From version 6.1
edited by Kieran Kelleher
on 2008/09/03 11:21
on 2008/09/03 11:21
Change comment:
There is no comment for this version
To version 5.1
edited by Kieran Kelleher
on 2010/01/27 13:26
on 2010/01/27 13:26
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -1,3 +1,9 @@ 1 +{{note}} 2 + 3 +This use of the WOOpenURL file to open a different browser than your default for development will not work in WO 5.4.X+ since WOOpenURL is no longer used for WO 5.4.X+. Auto open in browser logic is now determined by com.webobjects._ideservices._WOLaunchServices#_openURL() which calls /usr/bin/open directly 4 + 5 +{{/note}} 6 + 1 1 == Introduction == 2 2 3 3 Yes, in this modern day of CSS and JavaScript, you will be productive when you choose a good browser with excellent integrated developer tools. Remember your WebObjects application responds to requests from the browser and delivers back the responses. The browser ultimately interprets your response and displays it and interacts with it. So, it is critical that you fully embrace learning when it comes to basic http protocol, http headers, the DOM, semantic HTML, CSS, javascript, etc. Unbelievably there are WebObjects developers who think they can get by knowing just java and the WebObjects Dynamic Elements and Extension WOComponents! Read on for how to get the most development productivity out of the popular browsers. ... ... @@ -16,7 +16,7 @@ 16 16 #!/bin/bash 17 17 18 18 # Open argument with firefox 19 -/usr/bin/open -a Firefox $1 25 +/usr/bin/open -a /Applications/Firefox.app $1 20 20 21 21 {{/code}} 22 22