I am looking for a WYSIWYG html editor to maintain our schools website, we are currently using windows and Dreamweaver, but I would like to start using LTSP and need to find a simple web page editor, we don`t use a fraction of the features in Dreamweaver most of the time so I was wondering if anyone had any recomendations? Rob Keeling Network Manager Queen Elizabeth`s Grammar School
There are a few nice Linux Programs: Quanta and Bluefish I both like.
(for our schools website it has been a combination of notepad/pure html,
Adobe Pagemaker Mac, and Frontpage).
David.
----- Original Message -----
From: "Rob Keeling"
I am looking for a WYSIWYG html editor to maintain our schools website, we are currently using windows and Dreamweaver, but I would like to start using LTSP and need to find a simple web page editor, we don`t use a fraction of the features in Dreamweaver most of the time so I was wondering if anyone had any recomendations?
Rob Keeling Network Manager Queen Elizabeth`s Grammar School
-- To unsubscribe, e-mail: suse-linux-uk-schools-unsubscribe@suse.com For additional commands, e-mail: suse-linux-uk-schools-help@suse.com
At 19:51 03/04/02 +0100, you wrote:
I am looking for a WYSIWYG html editor to maintain our schools website, we are currently using windows and Dreamweaver, but I would like to start using LTSP and need to find a simple web page editor, we don`t use a fraction of the features in Dreamweaver most of the time so I was wondering if anyone had any recomendations?
Hi Rob, My advice would be to avoid all WYSINWYG web editors like the plague, unless you are what seems to me to be unbelievably expert - or all systems used to view the page are identical. Each browser/version/screen-resolution/colour-depth/OS/etc. combination will render any given page in a slightly different way - even before you consider different user settings. What YOU See Is NOT What Anyone Else Will Get! Keep the code simple enough to handle in a standard text editor and you are likely to end up with HTML that renders sensibly on any system, while if you use a so-called WYSYWYG editor, you end up with code so complicated that you need a grade 1 guru to de-bug it (mind you, I'm only grade 3 ;^) Good networking, Roger Beaumont
Roger,
Whilst I fully agree with your sentiment of clean HTML, and keeping it
simple,
my problem is that I want to change operating system on 90 or so staff, some
of which
can just about change their departments intranet pages by point and click in
dreamweaver,
the thoughts of them trying to learn HTML if frightening to say the least!
Perhaps instead of WYSIWYG I should have said Graphical?
Anybody else done anything similar?
Rob keeling
Network Manager
Queen Elizabeth`s Grammar School
Ashbourne
----- Original Message -----
From: "Roger Beaumont"
At 19:51 03/04/02 +0100, you wrote:
I am looking for a WYSIWYG html editor to maintain our schools website, we are currently using windows and Dreamweaver, but I would like to start using LTSP and need to find a simple web page editor, we don`t use a fraction of the features in Dreamweaver most of the time so I was wondering if anyone had any recomendations?
Hi Rob,
My advice would be to avoid all WYSINWYG web editors like the plague, unless you are what seems to me to be unbelievably expert - or all systems used to view the page are identical. Each browser/version/screen-resolution/colour-depth/OS/etc. combination will render any given page in a slightly different way - even before you consider different user settings. What YOU See Is NOT What Anyone Else Will Get!
Keep the code simple enough to handle in a standard text editor and you are likely to end up with HTML that renders sensibly on any system, while if you use a so-called WYSYWYG editor, you end up with code so complicated that you need a grade 1 guru to de-bug it (mind you, I'm only grade 3 ;^)
Good networking,
Roger Beaumont
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Friday 05 April 2002 9:33 am, Rob Keeling wrote:
Perhaps instead of WYSIWYG I should have said Graphical?
There's two KDE applications. Quanta (quanta.sf.net) which is being worked on for KDE 3.x (I haven't seen any activity from the author for a while). There's also Jono's Kafak, which currently lives in the kdenonbeta module of KDE CVS. I have no idea what its status is. - -- Cheers, Chris Howells -- chris@chrishowells.co.uk, howells@kde.org Web: http://chrishowells.co.uk, PGP key: http://chrishowells.co.uk/pgp.txt KDE: http://www.koffice.org, http://edu.kde.org, http://usability.kde.org -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE8rXdnF8Iu1zN5WiwRAqM0AJoDZwhUjYSC4XKzvkZ5Qdhj6gn5PgCeOQEO 0T3Q1ks9osF5H8ky8vSp/wA= =u2OZ -----END PGP SIGNATURE-----
On Fri, Apr 05, 2002 at 09:33:40AM +0100, Rob Keeling wrote:
Roger,
Whilst I fully agree with your sentiment of clean HTML, and keeping it simple, my problem is that I want to change operating system on 90 or so staff, some of which can just about change their departments intranet pages by point and click in dreamweaver, the thoughts of them trying to learn HTML if frightening to say the least!
Perhaps instead of WYSIWYG I should have said Graphical?
The problem with using a specific application such as a graphical html application is that the skills learnt in finding your way around the application are not transferable and almost certainly not across platforms. You say that the staff are barely able to use Dreamweaver and hence suppose that them marking up html by hand is a non-starter. I think that supposition is false. Whilst I don't know Dreamweaver I do know that most of all the graphical applications that I've used are opaque and difficult to use. On the contrary, html documents are structured, logical and if you write compliant html will adhere to a DTD. So for anybody with half a brain cell (and I'll rashly include teachers in that category ;), marking-up html by hand is more logical because the structure of your document and how the tags work becomes apparent to you as you build up and write your document. In fact, it will make more sense to them than to grovel around the menus of some graphical html application. So my advice would be to put some pages up on your intranet on how to use a syntax highlighting editor (vim - cross-platform) and then some pages about how to go about using it to write html. Provide them with a template document in html that makes use of a cascading style sheet. By doing that you will impose a style on the html pages that are common across the school ie. bold text, code etc. will appear in one way only. Produce a document(s) that make use of all the defined tags and show them how to use the `view as source' facility on their browser. Show them how to cut and paste from there into their text editor. Drill into them the advantages of using the css and the consistent structure it will impose on their work. Help yourself to my stylesheet if you like & hack it to suit your own needs: http://www.esperance-linux.co.uk/style/default.css & an example of it in action: http://www.esperance-linux.co.uk/misc/zetnet.html Show them how to use htmltidy to parse their html and clean it up: http://www.w3.org/People/Raggett/tidy/ Provide links to the various tutorials at w3c with regards writing html. Provide a couple of books in the school library on html and using the text editor. This might all seem like a lot of work and it probably is in the short term but the long term advantages are considerable: They will have learnt a mark-up language so they will be able to write other mark-up languages without too much difficulty XML, LaTeX -> pdf etc. because once you're familiar with how one works you're pretty familiar with how they all work. They will have learnt how to use a (decent) text editor which they can then use whether they're sending email, writing programs, editing configuration files etc. They can use the text editor on any platform that they choose to work on. They'll then be in a position to start learning the more advanced features of that editor such as search and replace. They have then learnt about regular expressions and are in a position to go on to learn about using grep, sed, perl etc. All of a sudden they find that learning bespoke GUI applications was a complete waste of time and they're indoctrinated into the unix philosophy and that is now their platform of choice. What's more they've got a true understanding of how some very important computing technologies work. They can then go onto teach their pupils how to produce standards compliant html rather than showing them how to navigate through some braindead, non-sensical menu system of a GUI application. They can show them the advantages of structured documentation: structured documentation = structured ideas. The school can then boast that all it's staff and pupils are able to write html. This is a considerable boast as the layman thinks that writing html involves heavy wizardry/rocket science. The fact is it doesn't, it's trained monkey stuff (but keep that quiet). What's even better is that when the MS salesman comes calling next you can sling him out of the door without him clutching a huge cheque in his sweaty palm and you can invest the money into something more worthwhile than crappy software. -- Frank *-*-*-*-*-*-*-*-*-*-* Boroughbridge. Tel: 01423 323019 --------- PGP keyID: 0xC0B341A3 *-*-*-*-*-*-*-*-*-*-* http://www.esperance-linux.co.uk/ How many seconds are there in a year? If I tell you there are 3.155 x 10^7, you won't even try to remember it. On the other hand, who could forget that, to within half a percent, pi seconds is a nanocentury. -- Tom Duff, Bell Labs
Whilst I fully agree with your sentiment of clean HTML, and keeping it simple, my problem is that I want to change operating system on 90 or so staff, some of which can just about change their departments intranet pages by point and click in dreamweaver, the thoughts of them trying to learn HTML if frightening to say the least!
You could struggle to fill 2 sides of A4 with the relevent information on how to use HTML. It wouldn't suprise me if there are primary school kids who can understand it... -- Mark Evans St. Peter's CofE High School Phone: +44 1392 204764 X109 Fax: +44 1392 204763
If you can produce a web page in a text editor then USE Frontpage (2000 onwards) or Dreamweaver. They will produce good code if used for the basics (ie don't use them to produce a page like you would in a graphical word processor) James Carter South Lee School
At 13:20 05/04/02 +0100, James Carter wrote:
If you can produce a web page in a text editor then USE Frontpage (2000 onwards) or Dreamweaver. They will produce good code if used for the basics (ie don't use them to produce a page like you would in a graphical word processor)
That last sentence says it all. In my experience, sit a novice down with a WYSIWIG editor and it is almost impossible to stop them going way beyond the basics, because they don't know - and can't see - what is basic and what isn't: it's all just click-and-drag... I should own up though. My experience isn't in a school, but teaching with the OU (and in FE). One OU course I taught (T171) required students to submit assignment work using HTML as the medium. Since both staff and students provide their own machines, there is no uniformity whatever between the kit of author & reader. That's an unusually demanding situation. However, I found that there were 3 classes of work: - a very few students were experienced HTML authors - they're not really relevant to this discussion; - next, and since I plugged the point to my utmost, the largest class, were those I'd persuaded to ignore the tool provided by the OU (AOLPress) and use Notepad to modify some very basic templates I provided myself - I could read all of them perfectly; - finally, the smallest class of all, work produced using a clever tool - not one of those pages rendered well on my kit and some were so bad that I could only read them by opening the source in a text editor! I found that persuading the students to use a simple tool was the only way I could ensure that they produced HTML that was simple enough to work reliably... I accept that schools are facing different problems and different contraints, but unless you are fortunate enough to have everyone using the same browser on the same specification of display (as a minimum level of compatibility), then I think my observation is still relevant as the fastest way to solve compatibility problems. But that's just my opinion! Good networking, Roger Beaumont
I am looking for a WYSIWYG html editor to maintain our schools website,
WYSIWYG and HTML are mutually exclusive concepts. Since the browser has substantial control over how it renders.
we are currently using windows and Dreamweaver, but I would like to start using LTSP and need to find a simple web page editor, we don`t use a
There are plenty of HTML editing programs, as well as regular text editors.
fraction of the features in Dreamweaver most of the time so I was wondering if anyone had any recomendations?
It might help if said which features you need. -- Mark Evans St. Peter's CofE High School Phone: +44 1392 204764 X109 Fax: +44 1392 204763
participants (7)
-
Chris Howells
-
David J Nelson
-
Frank Shute
-
James & Cybèle
-
Mark Evans
-
Rob Keeling
-
Roger Beaumont