Re: Access to running WO app via network
Re: Access to running WO app via network
- Subject: Re: Access to running WO app via network
- From: Kieran Kelleher <email@hidden>
- Date: Sun, 20 Nov 2005 07:59:10 -0500
Hello Hans,
I make changes too in WOBuilder, etc. and reload the pages on the Mac
and the PC. Simply make the port fixed for the app in development mode
.... like this ....
http://homepage.mac.com/kelleherk/iblog/C1216817469/E1577869113/
index.html
So on the local dev machine your shortcut will look something like this
if you fix the DWOPort as 52040 for example....
http://127.0.0.1/cgi-bin/WebObjects/myApp.woa/-52040
.... and in your Windows PC the browser shortcuts will look something
like this....
http://kieranmac/cgi-bin/WebObjects/myApp.woa/-52040
.... and, then create a permanent shortcut in the bookmarks bar of all
browsers on both your Mac and Windows machine .... then you can click
and load simultaneous sessions in FireFox, IE, etc on your Windows
machine and FireFox, Safari, etc. on your Mac .... and you can change
something in WOBuilder, CSS stylesheets and justsave & refresh
everywhere. When you rebuild, you just click the shortcut in all the
browsers.
This is the setup I use .... I have my Mac dev machine and a Windows
machine on my desk and I use the Windows machine for both testing all
browsers and for API doc browsing. On the mac I have two screens ....
one has the debug log window and the other big screen has the browser
windows where I test the app and the XCode project windows
I also have a launch arg to turn off auto opening in browser since I
don't want to keep opening and closing browser windows ..... I simply
watch the debug log while the app is launching and as soon as I see
debug log statements whizz by, then click the shortcut(s) in whichever
browser I feel like using and I am into the app. Personally I prefer to
use FireFox for development testing on my Mac since the FireFox dev
toolbar is great for debugging html and CSS.
If your app requires login, you can create a direct action that logs
you in and use that to save you time each time you Build and Run. For
security, the direct action can check that the request came from the
localhost or the Windows PC IP address..... so the shortcut might be
something like this.....
https://127.0.0.1/cgi-bin/WebObjects/myApp.woa/-52040/wa/login?
userName=myUserId&password=myPassword , or this ....
https://127.0.0.1/cgi-bin/WebObjects/myApp.woa/-52040/wa/
backDoorDevelopmentLogin?userName=myUserId
On the topic of rendering problems using development mode, you will
find if you check the archives that people get bitten when they try
deployment after they have spent weeks or months doing development
using direct connect. Why would you want to develop using direct
connect when direct connect _does_ _not_ simulate the real deployment
environment? Why would you not want to change a couple of launch args
and life goes on with no extra work and you get so much more for free
such as
1) assurance that the mechanism for page delivery during your
debelopment is exactly the ame as the mechanism that will be used for
deployment
2) the ability to set up HTTPS and develop using a mix of HTTP and
HTTPS pages (you cannot do this with Direct Connect)
3) the ability to test you app on multiple platforms and web browers
depending on how many different computers platforms you can fit on your
desk! (this has the added advantage of making your desk look like the
bridge of Star Treks' Starship Enterprise so that your wife, friends or
co-workers are in impressed of your development set-up ;-) )
Anyway, HTH,
-Kieran
________________________________________________________________
Blog: http://webobjects.webhop.org/
On Nov 20, 2005, at 7:11 AM, email@hidden wrote:
I understand this is an easy way to set this up and I would use it to
do some final testing before installing the app on the server. But I
lose an important feature when using deployment mode: Every time I
change something I have to do a new build to see the results.
When working on the layout I have to do a lot of small changes in HTML
or CSS files. In development mode I just change the file, save it,
switch to my browser and reload the page, all without stopping the
application. This is a very fast development environment and I can now
use it even from another machine: test several browser/OS combinations
imediately.
BTW I never recognized any problems with rendering when using direct
connect.
On 19.11.2005, at 23:26, Kieran Kelleher wrote:
Just develop in "deployment mode" by turning off direct connect and
then you can use the URL in your PC but using the mac ip address
instead of localhost.....
http://homepage.mac.com/kelleherk/iblog/C1216817469/E1192290575/
index.html
On Nov 18, 2005, at 3:59 AM, email@hidden wrote:
Hi to all!
For testing purposes I need to access my running WO application (in
development mode, started from Xcode) from another machine (Windows
PC) inside our LAN. But I can't use the URL I have on my local
browser (which is something like
"http://localhost:54342/cgi-bin/WebObjects/SkillPortal.woa";). Of
course I replaced localhost with the IP address.
Is there a way to do it? The firewall on my Mac is on, but Personal
Web Sharing is enabled as well.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
email@hidden
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
email@hidden
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
email@hidden
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden