Re: [Phpwebsite-developers] More phpWS and OOP

[Eloi G. <el...@re...>]

> I always thought blank lines between blocks of text was the best way 
> of indicating they are a separate block of text. Some people call them 
> paragraphs. Not sure it'll catch on though. ;-)


Wow.  There's an actual *name* for them?!?!
Note: For those who aren't sure if we're joking or not, I was more 
referring to those instances where you wanted your users to be able to 
make a sidebar that sticks to the right side with a company logo 
background/watermark and an image rollover as the title.  All they'd 
have to do is select that template and enter the text.

> It's a pity to have to make a section of users 'second class' by 
> implementing a solution that works for the majority of users but the 
> simple answer is
>
> a) switch javascript on
> b) Use Firefox


Naw, we're still back at square one because a lot of corporations 
prohibit the use of javascript on the company-mandated browser (usually 
IE).  My sitelogs show that most browsing is being done between 9-4 on 
Mondays through Fridays on the bosses' high-bandwidth line.  It's 
weird.  You can actually set your watch by looking at where users are 
logging in from.


> Then you're down to just the special cases of providing access for the 
> disabled and I can't imagine that a wysiwyg tool is any worse than the 
> textarea/buttons we have now.


I think it would be worse in the sense that the exsistence of a wysiwyg 
tool encourages people to use more markup, making a text version more 
unreadable.  Take a look at 
http://www.interactivetools.com/products/htmlarea/index.html#demo using 
FireFox.  Takes you a while to understand where to edit what.  A blind 
editor would be dealing with that all day long.