I'm with Jake--it'd just get in my way, but I have nothing against reasonably semantic editors. As long as I can turn it off.
OTOH, any editor that inserts <font> tags needs to die :-). Scott On 7/20/06, Jake Good <[EMAIL PROTECTED]> wrote: > I use Markdown and SmartyPants ... so when I'm writing posts, I'm > already keeping markup in mind. > > SO I'd like the ability to turn it off... but I would venture to guess > that *most* new bloggers would want it. > > Frederic de Villamil wrote: > > Wade Menard a écrit : > > > >> On Thu, 2006-07-20 at 17:14 +0200, Frederic de Villamil wrote: > >> > >>> I've already started to re think the whole stuff from scratch, but I'm > >>> really looking forward your ideas. > >>> > >>> > >> Would a WYSIWYG post editor be out of the question? > >> > >> -Wade > >> > > > > I've been thinking about it for a while actually, and there are lots of > > for and against. > > > > I really don't like wysiwyg editors, but my personnal tates is nothing > > when compaired to the amount of users Typo should gain with a wysiwyg > > interface. > > > > If we decide to enable one, it means we MUST have an alternate editor > > with people being able to choose whether or not they want to use it. I > > come from the Wordpress world where adding a rich text interface by > > default without any alternative really made a fuss for the 2.0 release, > > and they had to make a step back. > > > > There is still an issue : does the rich interface need to be enabled by > > default or not ? I believe it depends on another question : we want to > > make Typo more user friendly, but do we want him to still choose his > > friends or not ? > > > > > > > _______________________________________________ > Typo-list mailing list > [email protected] > http://rubyforge.org/mailman/listinfo/typo-list > _______________________________________________ Typo-list mailing list [email protected] http://rubyforge.org/mailman/listinfo/typo-list
