But surely those couple hundred lines would be useful for
more than just the
WYSIWYG editor. Custom spam handlers? Maybe an
rss2email-type tool...there
are a bunch of non-essential features that could be bundled
like that.
Anyway, my point was more that fancy editors simply don't
belong in the
admin interface. The two big problems with the current
interface are that a)
it's monolithic and b) it covers a *lot* of functionality.
I'd almost argue
that the 'settings' page is the only thing that belongs in
the admin
interface. Everything else (categories, articles, feedback)
is more of a
blog-owner interface. When multi-blog Typo happens, this
blog-owner
interface will need to be per-blog, which will underscore
this point.
Plug-ins are good, and might actually help keep Typo lean
and clean.
Uzair
> -----Original Message-----
> From: typo-list-bounces rubyforge.org
[mailto:typo-list-
> bouncesrubyforge.org] On Behalf Of Scott Laird
> Sent: Friday, July 21, 2006 3:57 PM
> To: typo-listrubyforge.org
> Subject: Re: [typo] Admin interface complete rebuild
>
> Here's the thing: adding an interface for plugins for
the admin
> interface would probably take a couple hundred lines of
code, by the
> time we turn the current interface into a plugin, add
an extra sample
> or two, and then test the whole thing. Adding one
rich-text editor as
> a standard option would cost *maybe* 10 lines of code.
In total. One
> admin setting to enable it, and a couple lines that
change the HTML
> generated and load the right .js file.
>
> So, maybe it's a good usability move, maybe it isn't,
but complaining
> that it'd make Typo too complex and it should be a
plugable option is
> almost exactly backwards  .
>
>
> Scott
>
> On 7/21/06, Syed Uzair Aqeel <uzairnairang.org> wrote:
> > A WYSIWYG editor doesn't belong in the admin
interface. The current
> editor
> > is more than adequate for the purpose it should be
used for -- to allow
> the
> > administrator to edit posts as necessary. The
reasons for allowing
> admins to
> > post *new* entries from the admin interface are
arguable.
> >
> > It would make much more sense for themes to offer
a post editor from the
> > front page if the user's session is active (ie,
by checking that the
> log-in
> > cookie exists and hasn't expired) the way many
themes currently offer
> > 'edit'/'nuke' options on comments if the user
is an admin. Maybe that's
> not
> > something that's going to happen right now, but
even in the worst case,
> post
> > editors should be prime candidates for being
broken into plugins (once
> the
> > refactoring work Scott mentioned happens).
> >
> > Anyway, Frederic best of luck to you on this,
it's going to be awesome
> I'm
> > sure. A cleaner admin interface will be great,
regardless of whether it
> > includes WYSIWYG support.
> >
> > (BTW, anyone who hasn't checked out the Firefox
blogging extension from
> > http://www.performancing
.com should -- it's quite nice and unintrusive.
> I'm
> > not as happy with it as I used to be, because
posting with it makes Typo
> > return an error message about not being able to
update the categories
> > table...apparently because the some column is
marked as unique.)
> >
> > Cheers,
> >
> > Syed
> >
> >
> > > -----Original Message-----
> > > From: typo-list-bouncesrubyforge.org
[mailto:typo-list-
> > > bouncesrubyforge.org] On Behalf Of Frederic de
Villamil
> > > Sent: Friday, July 21, 2006 7:43 AM
> > > To: typo-listrubyforge.org
> > > Subject: Re: [typo] Admin interface complete
rebuild
> > >
> > > Scott Laird a écrit :
> > > > On 7/20/06, Wade Menard <wadeezri.org> wrote:
> > > >> On Fri, 2006-07-21 at 10:10 +1000,
Trejkaz wrote:
> > > >>> Can you not use an external
application with WYSIWYG support, to
> post
> > > to the
> > > >>> blog? That's what the API is
for, after all. Might as well throw
> > > away the
> > > >>> API if nobody uses it.
> > > >> A writer is not always at home or at
a place where they can use a
> > > >> desktop client when they want to
post something, but are always
> near a
> > > >> web browser. It is really
frustrating to use the interface as it is
> > > now,
> > > >> having to do <p>'s and
<br>'s or whatever manually. It's not beyond
> my
> > > >> abilities but it's the last thing I
want to deal with when
> composing an
> > > >> article. I might as well be
inserting the entry with phpMyAdmin.
> > > >
> > > > Frankly, if you're inserting <p>
and <br> by hand, then you're using
> > > > the wrong text filter.
> > > >
> > > >
> > > > Scott
> > >
> > > Or maybe the text filters were brocken and no
one was able to use them
> > > don't you think ? 
> > >
> > >
> > > --
> > > Frédéric de Villamil
> > > "Quand tu veux chasser une belle fille,
il vaut mieux commencer par
> > > draguer sa copine moche" -- précepte de
go.
> > > http://t37.net
> > http://fredericdevillam
il.com
> > > neuro7el.net tel: +33
(0)6 62 19 1337
> > >
_______________________________________________
> > > Typo-list mailing list
> > > Typo-listrubyforge.org
> > > http:
//rubyforge.org/mailman/listinfo/typo-list
> >
> > _______________________________________________
> > Typo-list mailing list
> > Typo-listrubyforge.org
> > http:
//rubyforge.org/mailman/listinfo/typo-list
> >
> _______________________________________________
> Typo-list mailing list
> Typo-listrubyforge.org
> http:
//rubyforge.org/mailman/listinfo/typo-list
_______________________________________________
Typo-list mailing list
Typo-listrubyforge.org
http:
//rubyforge.org/mailman/listinfo/typo-list
|