Any chance that there will be discussions about inline editing?
Sad I won't be able to make it to this conversation, as I'll be presenting at the same time.
Regarding the node preview, I'd like to make a proposal (or perhaps just suggest it here). The CTools object cache needs to go in core for a few reasons (Views and Panels use it, sure, but if we put Form Builder in core it will need it too). But we should explore utilizing it for the node form.
Having an object cache would allow: - AJAX auto-saving of the node form, making it so users wouldn't loose work if they left the page. - Make it possible to temporarily store a node in the cache so we could make a true preview page at a separate URL that looked just like the final output. - Provide a locking mechanism similar to Views that would warn and prevent multiple people from editing a single node at the same time.
Just some interesting thoughts from an architecture perspective. The great thing is we could implement this from the technical standpoint without needing to wait on the UI overhaul that the UX team is putting together.
Comments
Any chance that there will be
Any chance that there will be discussions about inline editing?
Sad I won't be able to make
Sad I won't be able to make it to this conversation, as I'll be presenting at the same time.
Regarding the node preview, I'd like to make a proposal (or perhaps just suggest it here). The CTools object cache needs to go in core for a few reasons (Views and Panels use it, sure, but if we put Form Builder in core it will need it too). But we should explore utilizing it for the node form.
Having an object cache would allow:
- AJAX auto-saving of the node form, making it so users wouldn't loose work if they left the page.
- Make it possible to temporarily store a node in the cache so we could make a true preview page at a separate URL that looked just like the final output.
- Provide a locking mechanism similar to Views that would warn and prevent multiple people from editing a single node at the same time.
Just some interesting thoughts from an architecture perspective. The great thing is we could implement this from the technical standpoint without needing to wait on the UI overhaul that the UX team is putting together.