[meta] Scope of D7 Edit module

+1 for views integration, here. I'm imagining, in particular, a table view of fields, where editors can easily click in, edit, and save.

I agree that Views integration (being able to choose what field can be edited) seems the most immediately usable, maybe even before fields integration (the Plone experience seems to imply that either you have a Wysiwyg editor, and inline edition is nice, or you have lots of fields, and the user will almost always edit the whole content instead of editing one field after the other (either for consistance of the edit, revision, ...).
Anyway, looking forward to see it working ;-)

@nod_: I know, I just have to find the time ;-)

I didn't know we could try it right now (and not expect something to break horribly). That's great news, but in that case, might it be worth releasing an -alpha6?

I would say the priority should be getting something out. Then panels and views. In our case, we're about to overhaul our D7 site and it would be fantastic to be able to show our writers Edit, and plan to build the revamped site on that. So having something stable enough to show and try out would be a huge help.

What is required to test Edit? Just a clean core install with CKeditor and current Edit dev, and any dependencies eg Entity. Are there any core patches required?

Some decisions have been made in this area.

• With the addition of hook_edit_render_field(), just like in Drupal 8 (see #2083387: Make it possible to use in-place editing on entities rendered by a custom render pipeline (e.g. Views)), #1895526: Add a way to make things that don't use Field API in-place editable was fixed.
• This in turn allows us to have proper integration with Panels: #1889798: Panelizer support (use Panels' render pipeline to re-render edited field panes in Panels). It still needs to be investigated though whether this is something that should be supported by this module (if trivial) or by a separate module (if complex).
• As well as proper integration with Views. That particular integration is already with 100% certainty very complex and has therefor been split off into a separate project: https://drupal.org/project/edit_views. See #2149185: Figure out a way to *start* in-place editing inside a View — on a per-entity basis, just like elsewhere for the first major obstacle in supporting that.
• Overall, D7 Edit now has the same set of features as D8 Edit, albeit with some limitations: it's impossible to support all entities generically in D7 like it's possible in D8 (where you can automatically in-place edit any entity: node, taxonomy term, user, custom block …). It's likely that in-place editing in D7 will remain limited to nodes.