On 02/11/2020 07.07, David C. Rankin wrote:
On 10/31/20 5:13 AM, Carlos E. R. wrote:
It appears that I used it in the past, it has memory (recent files) of an html file I edited on 2007, but complains of something (DTD not known to me or similar).
Ok, I open the current file. Not bad, but can't cope with utf-8 chars.
shows "Baden-W�rttemberg", "What�s Next"...
Anymore,
All I care about is a multi-document interface (like kate), so I can have the .html, .php, .js and any other needed files open at once. I like kate just as well as Quanta (the syntax highlighting is just as good), the only thing missing is tag-completion, and similar type addons. But honestly, I don't find that I miss it. Indentation will keep your tag-nesting straight.
The only reason I harp on kate so much is that it saves sessions with as many documents as your project has (when I was building TDE for Arch I had a session with 128 build file). And, kate will open them remotely over ssh (though now you have to tweak your sshd config to allow opening more than then default 15? or so files simultaneously)
Vim is also fine as an html editor. The only reason I don't use it on my projects is I'm more comfortable with kate's document list in the left pane than cycling through all the open buffers in vim (I tend to have to work at that)
Let us know what you find if you like it a lot. Like I said (it's been a while) but I tried all the latest WYSIWYG tools and I always found them far more trouble than they were worth, or I would have to spend more time cleaning up the awkward, non-conforming, way they would render tables, etc.. to html with the jumbled .css style information. Far cleaner to spend an hour at w3schools and write a style-sheet that you can apply as classes to your tags.
The only thing I find I have to spend time on is what a WYSIWYG editor wouldn't help with to begin with, like how to write the more in-depth routines like your post-redirect-get with form to prevent double-submit problems, or actually using PHP classes instead of writing strictly procedural code, etc... That's just the stuff you will have to spend time learning no matter what you use.
And whatever you have to do that is backend related, do it in PHP. Remember anyone smart enough to know that Firefox is bundled with developer tools can see (and change) every bit of javascript or html you write....
I only do a single html file. I know nothing about tags, styles, I don't want to, and I don't need to. I just want to write a document (that happens to have links to youtube videos), same as I do in *office, only that the document is not .doc but .html and the browser can render it. Or apache. -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)