With Visualforce, I had used
I’m about to invest in coding custom object views and I’m trying to wrap my head around Lightning Components and how to build stuff that looks like LEX. My org is still classic now, but I’d be happy making LEX / SLDS looking things in my org over using the classic styles.
As an aside, I don’t really care to get too deep into Salesforce specific stuff. If there’s no magic convenience like
apex:inlineEditSupport, building with React or something seems more appealing.
I contacted Salesforce developer support, who after many weeks and escalations, finally said there was no supported way to build out this native behavior.
Instead, you can just use the Salesforce Lightning Design System’s CSS to create the right styles, then add in the interactivity and switching between active editing and read only on your own.
You can do this with the framework of your choice such as React, Angular, Lightning Component, or plain JS. Personally, I’ve built this out on Backbone Marionette with backbone.stickit for two-way data binding and Dust.js for templating, but anything will do.
If you build out the components on your own, I highly recommend creating partials for each component – with the necessary parameters. This hides the huge amount of markup to make each component. I’ve done this via Dust, but choose whatever templating language you want.
Alternatively, check out http://aljs.appiphony.com/ or https://lightningdart.com/ for ready to use libraries. Between their flexibility, completeness, and licenses, I found it easier to go out on my own.