From: Rich Felker <dalias@aerifal.cx>
To: musl@lists.openwall.com
Subject: Re: Wiki for musl?
Date: Wed, 13 Jun 2012 23:46:00 -0400 [thread overview]
Message-ID: <20120614034600.GM163@brightrain.aerifal.cx> (raw)
In-Reply-To: <20120614031006.GB8304@intma.in>
On Wed, Jun 13, 2012 at 11:10:06PM -0400, Kurt H Maier wrote:
> On Wed, Jun 13, 2012 at 08:21:40PM -0400, Rich Felker wrote:
> > I assume you're talking about the live preview. What about submitting
> > changes without reloading the page? To me that makes a big difference
> > in the usability impression - avoiding the discontinuity of the screen
> > disappearing for a second, the scrollbar getting reset, etc.
>
> Since this was never meant to be how http works, this is a non-trivial
> requirement. In fact, it's a general case that the program must be
> written from the ground up to support such behavior. The only wiki
See below...
> > It's not that I want things to "look ajaxy". I don't mind if they look
> > like the first websites from the early 90s with no styling, default
> > fonts, no custom buttons, etc., but I do like having a responsive
> > interface without discontinuities.
>
> This is what I meant by "look ajaxy." http is a fetch/display protocol;
> html is a markup language designed to be rendered once. dynamic
> document alteration and xmlhttprequest are what ajax is all about.
I understand how it works.
> > Graceful fallback to non-AJAX when JS is disabled (or in browsers that
> > don't support JS) is of course a requirement for an accessible site.
>
> That graceful degradation is a unicorn that has never been caught. The
> de facto solution that web people have adopted is in the style of
> google: AJAX wherever possible, with a failover site written in regular
> HTML. The two front ends share no components and will double your
> development and maintenance costs up front. Recently Google has begun
Just because this is the way broken sites are done doesn't mean it has
to be that way. Suppose instead you do something like this. When the
client sends the submission to the server, the server generates the
updated contact then does a DOM-level diff of the old and new
versions, then sends a representation of the diff across to the
client-side js that incorporates it into the DOM there.
No ugly duplication, eh? And the ajax code is nearly 100% generic and
site-generic.
Rich
next prev parent reply other threads:[~2012-06-14 3:46 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-13 18:14 Rich Felker
2012-06-13 18:23 ` Jeremy Huntwork
2012-06-13 18:24 ` Daniel Cegiełka
2012-06-13 18:39 ` Szabolcs Nagy
2012-06-13 18:48 ` Jeremy Huntwork
2012-06-13 18:49 ` Daniel Cegiełka
2012-06-13 18:52 ` Ivan Kanakarakis
2012-06-13 18:51 ` Kurt H Maier
2012-06-13 19:20 ` Jeremy Huntwork
2012-06-13 19:38 ` Rich Felker
2012-06-13 19:54 ` Rich Felker
2012-06-13 20:02 ` Jeremy Huntwork
2012-06-13 20:00 ` Rich Felker
2012-06-13 20:14 ` Jeremy Huntwork
2012-06-13 23:09 ` Kurt H Maier
2012-06-13 23:23 ` Jeremy Huntwork
2012-06-14 0:21 ` Rich Felker
2012-06-14 3:10 ` Kurt H Maier
2012-06-14 3:46 ` Rich Felker [this message]
2012-06-14 7:55 ` Szabolcs Nagy
2012-06-14 10:28 ` Conrad Pankoff
2012-06-14 4:00 ` Conrad Pankoff
2012-06-13 19:46 ` Justin Cormack
2012-06-13 20:23 ` Luca Barbato
2012-06-13 20:38 ` nwmcsween
2012-06-13 21:02 ` Ivan Kanakarakis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120614034600.GM163@brightrain.aerifal.cx \
--to=dalias@aerifal.cx \
--cc=musl@lists.openwall.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).