Why don't navigators work over HTTP in Notes 4.6?
Joe
I thought Navigators were supposed to by fully supported in Notes 4.6.
But buttons on navigators don't show up (it looks like "blank hotsots"
where the button is supposed to be are there, but you can't see the
buttons). This is using the latest version of Netscape.
Joe McGinn
===================================================
Author of Inside LotusScript
http://www.manning.com/McGinn/459.html
===================================================
Ed Coakley
Joe,
Check the Navigator Properties. There's an option you need to check to make
it available to the web. I've used it in the last couple of weeks and know
that it works.
Good luck!
Joe wrote in message <3jiQ.18$5f2.1...@newsgate.direct.ca>...
Joe
"Ed Coakley" <e...@touch1.net> wrote:
>Check the Navigator Properties. There's an option you need to check to make
>it available to the web. I've used it in the last couple of weeks and know
>that it works.
Thanks Ed, I checked that option but navigators with multiple buttons
on them are still very flaky. A totally empty navigator with just one
button on it works sort-of Ok, but as soon as yo add more buttons
wierd stuff starts happening (e.g., you get one large "overly scaled"
graphics of a button, with hotspots where the two buttons should be).
I'm just going to have to dump navigators altogether for the web
version of this app, and use forms in HTML frames instead. Buttons
seem to be properly supported in forms.
I REALLY hope Lotus significantly improves the whole web development
side in Notes 5.0, because it's still pretty hokey in many ways. For
example, even if navigators DID work, I still have to use HTML to
manually create web browser frames to get a similar effect to using
navigators in the Notes client. That's totally bogus (especially if
you want web browser AND Notes client access - you have to develop two
seperate user interfaces). There's no reason Domino couldn't do a much
better job of converting these kind of Notes client concepts to the
web automatically.
Ed Coakley
Joe,
The navigators in the app I've worked with have multiple buttons and I've
been able to very closely emulate Notes client functionality in a web
browser. The buttons all use simple actions to open another view or
navigator. To emulate the left navigator in Notes, I created a
$$NavigatorTemplate form for each of the navigators. In R5 these will be
pages instead. Each template has a one row, two column table with an
embedded navigator in one cell and an embedded view in the other.
I wonder what's different with your navigators that's causing them to act
flaky.
Let me know if you want to see the app I'm talking about.
Ed
Joe wrote in message ...
Joe
"Ed Coakley" <e...@touch1.net> wrote:
>The navigators in the app I've worked with have multiple buttons and I've
>been able to very closely emulate Notes client functionality in a web
>browser. The buttons all use simple actions to open another view or
>navigator. To emulate the left navigator in Notes, I created a
>$$NavigatorTemplate form for each of the navigators. In R5 these will be
>pages instead. Each template has a one row, two column table with an
>embedded navigator in one cell and an embedded view in the other.
>I wonder what's different with your navigators that's causing them to act
>flaky.
I don't know, they are as simple as can be. Just some buttons that
open views with "simple actions". I'm really not impressed with the
Domino 4.6a HTTP service. Unless I find out what's causing it to act
so strangely I'm going to have to recommend to my customers to just
use the Notes client, and put off web browser interfaces until at
least Notes 5.0. The amount of effort required to redo the user
interface for a web browser just isn't worth it at this point.
Daniel Juarez
I agree. I think (and hope) they will. After seeing the 5.0 interface, I
don't see why they wouldn't. It looks just like a web browser itself.
In article <Q7DQ.30$em4.1...@newsgate.direct.ca>, mcg...@direct.ca (Joe)
wrote:
David Gordon
hear, hear!
I hear way way too much about using Notes with a web client in
situations where it is unneccessary. Since the Notes client can securely
work over TCP/IP, is technologically about 5 years ahead of the browser
market (and 10 ahead of Java), and the HTTP service is unproven (and not
really on its way), stay away from the web clients whenever you can!
Sure the web client is sexy... if you're a necrophiliac