Is there any better way to publish a "read-only" panel on the web

[zach DDS]

Hi

I am new user in Labview. I am trying to publish some of our test result on the web. However. the current methods all have their disadvantages in my application

.monitor: I like this, but it is only supported by Netscape, which is not do popular anymore. I dont want push our customer to install it just for our demonstration.

.snap+refresh: Our application requires fairly fast refresh, 1 fresh/sec. the blank in during the refresh does not look nice.

Embed: I want to demonstration to be read-only, I dont want the custome gain any control over that. Also scroll bar shows in the embed mode is also something I dont want.

I am using LabView 6.1, if the problem has been solve in new version, I am glad to upgrade. Also is there is other better to meet my requirement, please help me.

Thanks

Message Edited by zach DDS on 10-05-2005 12:23 PM

[altenbach]

---

@zach DDS wrote:

Is there any better way to publish a "read-only" panel on the web

---

Better than what?

[zach DDS]

better than the ways I tried, :monitor, .snapshot, embeded, because they all have their disadvantages as I mentioned.

[altenbach]

Sorry, you must have edited your message. When I saw it, only the title showed ;).

Embedded is what you want. You can change the windows apperance (e.g. hide the scroll bars) by changing the VI properties.

Uncheck "request control" in the web publishing wizard, and it will be read only.

Works fine here in LabVIEW 7.1. I don't remember if 6.1 had any limitations.

[altenbach]

Actually, to make it read-only, you need to got to tools...options..Web server:Browser access.

Here you can selelct between

• Allow vieweing and controlling
• Allow viewing                                  <---- that's what you want.
• Deny access

[zach DDS]

Thank you for your help. I tried to change the window appearance, but it will be effetive only after the program starts running. So if you didnt start the vi, they are still there.  What makes it worse is that if the customer roll the scroll bars before I start the program, he will be stuck there after I start because the scroll bars will disappear. Sorry for my nitpicking. Please let me know if there is a better to make the demonstration more presentable.

[altenbach]

The VI should be always running, you can set it e.g. to "run when opened".

Starting and stopping is more usful while developing the VI. A finished VI should be designed to always run.

[zach DDS]

Thank you very much for the advices. I appreciated it.