Quote:
Originally Posted by frabjous
I never said that decent WYSIWYG editors exist. If that was your claim, then I agree. My point was that the lack of them is not the fault of CSS.
|
Oh? A standard so arcane major browsers can't do it properly? A standard which killed off WYSIWYG editors which were coming along nicely before? No, CSS is most certainly to blame.
Quote:
You think that's brain surgery? What are you talking about? WYSIWYM is much easier to use than WYSIWYG.
|
Absolute and total nonsense. There is a good reason basically every single program out there for the mass market is WYSIWYG, whereas WYSIWYM programs are for highly technical specialists in narrow markets.
Quote:
I have already given reasons for the necessity of separating form and content.
|
There is good reason to separate them in terms of files, yes. But not in the UI presented to the user of the program: that simply needs to be managed such that you generate form and function files by using, for example, stylesets.
Quote:
I think most ordinary people aren't interested in creating style, just content.
|
So basically you want to disenfranchise people from making websites, keeping it to the realm of the specialists. Lovely! It's precisely that attitude which I
intensely dislike.
Quote:
And even if they did care about style, as I noted, it is entirely possible to create a very intuitive interface for creating CSS.
|
LINK!
(And "intuitive" means it cannot contain ANY visible scripting, let alone coding ofc...)