HTML

[Wim Van den Wyngaert]

I'm looking for a WORD like editor (even better : compatible) running on VMS that produces HTML files.

Anyone seen something I can use ?

[Lokesh_2]

Hi Wim,

You can use Mozilla browser or CSWB on VMS for creating HTML files. This is similar to microsoft front page on Windows.

Thanks & regards,
Lokesh Jain

[Lokesh_2]

sorry for my incomplete earlier post...

open the mozilla web browser ---> windows ---> composer .

This will open the composer window, which is similar to microsoft's front page.

HTH,
Best regards,
Lokesh Jain

[Antoniov.]

You could find something here
http://h71000.www7.hp.com/ebusiness/technology.html

Bye
Antoniov

[Wim Van den Wyngaert]

Thanks Lokesh. It works. But it is VERY slow.
Will do some testing with it.

[Ian Miller.]

you will need lots of memory for SWB :-(
If you have lots then ensure your working set is big enough.

[Wim Van den Wyngaert]

Indeed.

When started : 50 MB
After opening 90K HTML file : 55 MB
After opening the document in the composer : 65 MB
After clicking spell check : 75 MB
After clicking HTML source : almost 80MB.

A real PC program !

Btw : it is not compatible with IE. It doesn't know to resize images and ignores them. It also interpretes HTML differently (I think that faulty code reacts differently).

[Willem Grooters]

Wim:

>>A real PC program !

No: Unix.

It's something you see with "open source" software more often, since "OSS" normally means "Linux based" - with all limitations in error handling, security (buffer overflows), locking, file-IO (delivers and requires STREAM-LF files), memory usage....

[Wim Van den Wyngaert]

I tried the DOM inspector and had to stop it with stop/id. 150 MB and 13 minutes of cpu.

My window manager starts behaving strangly and mon io reports high "logical translation" rates.

Nice program for a small demo. But for the real work ...

[Antoniov.]

Hello Wim,
composer it's very slowly; you can edit a HTML file locally and you can work in same time; I tryed with Netscape V4.6 and Front Page Express; Front Page is quicker but opening a real complex page can crash.
If I understand, you are using a web server based on VMS and client PC: I think there are a few choice to edit a real complex page (next week I have to install Macromedia).

Bye
Antoniov

[Lokesh_2]

Hi,

What I do generally is make my HTML page on Microsoft's front page. Then I copy the corresponding HTML text page ( code ) to my composer and save it. Or I simply copy the HTML code in notepad and ftp to my VMS machine. For small editing stuff, i do use composer..

best regards,
Lokesh Jain

[Martin P.J. Zinser]

Hello,

if you insist on a "Word" like interface I fear you really need Mozilla. This does need considerable resources, but it <> very standard compliant in my experience (as in W3C standard compliance, acting the same as IE is not a standard).If you do not insist on a GUI any texteditor is fine to create HTML, pick your favorite one! Standards verification can be done with tidy (http://zinser.no-ip.info/vms/sw/tidy.htmlx).
If your documents are based on Ascii texts you might also want to check asctohtm (http://zinser.no-ip.info/vms/sw/asctohtm.htmlx).

Greetings, Martin

[Wim Van den Wyngaert]

For who is interested.

I used mozilla against a SANswitch, output of mozilla directed via TCPIP to a workstation.

I used every page of the SANswitch for a few moments.
As a result I got some alarms :
1) the network interface was overloaded (3 Giga in about 45 minutes.
2) continuous buffered IO at a rate of 400 per sec by mozilla and java vm
3) 40% cpu load on the server node, esp for java VM.

Conclusion : don't use it on your production servers !!!

[Uwe Zessin]

Yes, the browser is doing a lot of data exchange with the switch. It does even reflect the port LEDs state from the real hardware.

[Wim Van den Wyngaert]

Uwe,

At least 50% of the traffic was between mozilla and the workstation.
I used it via 10 Mbit and it was VERY slow.

Don't use this at home (unless the wife forces you to).

Wim

[Willem Grooters]

I double Lokesh. However, you should be aware of some latent problems when your webserver is Apache 1.3.
Some facilities of Frontpage (themes with navigation buttons, for instance) create filenames with mutiple dots in it and these are referenced from within the HTML pages.
It's not within the EDIT phase, but when publishing!
The final result is that these files cannot be located. Renaming them is not enough, you'll need to change the references as well.
I don't know for OSU, WASD or Apache 2.0 (the latter would be able to cope with multiple dots, but requires the files to be STREAM_LF. I don't know what's worse...)