Re: [editing] Responsive Input Terminology

At a frist glance I almost agreed with you, Björn.

Note though that, in terms of output, these events we’re talking about are adapted to the input method used to generate them. We’re not any more talking about device specific events, like “mouse click” or “key press”. One of these events could be “insert character” and the way it is triggered vary depending on device, platform, ATs, etc.

This makes me agree that Responsive Input Events is a great choice for it.  

Frederico Knabben
CKEditor Project Lead and CKSource Owner
CKSource -
Follow us on: Twitter ( | Facebook ( | Google+ ( | LinkedIn (

On Friday, 12 December 2014 at 01:17, Bjoern Hoehrmann wrote:

> * Ben Peters wrote:
> > There has been a lot of debate [1][2] about the correct name for device  
> > independent events [3] as a concept*. We have considered Intention  
> > Events, Command Events, and Action Events among others. I believe we now  
> > have a good name for them- Responsive Input Events. The reason for this  
> > name is that it is the corollary to Responsive Layout: for input instead  
> > of output. Together these two concepts can help form the basis of  
> > Responsive Design going forward.  
> >  
> "Responsive Layout" responds to geometric changes in the environment or,
> if you will, adapts to different geometric environments. I do not really
> see how device independent events respond or adapt. They are independent
> of their environment already. Instead of "Responsive (Input Events)", it
> is possible that some people read it as "(Responsive Input) Events", but
> I do not really see how the input responds or adapts either. The input
> is what it is, and does not really interact with anything on its own.
> --  
> Björn Höhrmann · ·
> D-10243 Berlin · PGP Pub. KeyID: 0xA4357E78 ·
> Available for hire in Berlin (early 2015) ·  

Received on Friday, 12 December 2014 08:39:16 UTC