mark at the-howards.net
Mon Feb 16 17:39:17 EST 2009
Couldn't resist jumping in here ...
There are obviously a lot of things that can be done on the 'client side'
1) Populating dynamic content based upon input (dynamic selects)
2) Asynchronous lookup, such as populating/auto-completion based upon
3) Field validation, or modification, such as inline
Not necessary 'flashy' stuff, although that can be fun too (and what's wrong
with that) ... ;^)
From: geeklog-devel-bounces at lists.geeklog.net
[mailto:geeklog-devel-bounces at lists.geeklog.net] On Behalf Of Dirk Haun
Sent: Monday, February 16, 2009 4:41 PM
richardsw at nc.rr.com wrote:
Well, interactivity ;-)
So far the only really useful application would be an auto-save for the
editors. You can't really do that any other way.
>From the visitors perspective,
>much of the content is static to them. Its the editor that is editing
>content - so in the long run, does using these libraries save you or
>them any time, or is it there just to be flashy?
I'm with you on this one - adding flashy things just to be able to say
"we're flashy now" shouldn't be the reason.
Somebody mentioned editors that open up right on the page where you are.
Not sure I see any real advantage in that over getting redirected to the
editor when you click on an "edit" link. It may be a solution for the
problem of not being able to see a story when you're commenting on it,
>I hope that actual
I wouldn't want the either. It does make sense for widgets or something
like that (I'm thinking of the rating plugin, for example). But it
shouldn't be necessary to display actual content.
geeklog-devel mailing list
geeklog-devel at lists.geeklog.net
More information about the geeklog-devel