Edit and delete options for slush-marklogic

[Scapadiver]

Great new framework for creating apps in place of app builder.

Is it possible to add the the default configuration the ability edit and delete documents?

Would greatly help in creating sample applications.

[dmcassel]

The generator is based on an app that has that ability. I'll see about bringing that in.

[grtjn]

I really liked the DLS approach, shown internally recently. Leveraging the optimistic locking features of the rest api would also be nice..

[dmcassel]

I while ago I added some sample data (not yet included in what you get from
npm), and my intention has been to set up a detail page to allow editing
that data as an example. Personally, I like a view that allows field-level
edits over a DLS-style checkout/checkin, as done in Demo Cat
https://github.com/marklogic/demo-cat/blob/master/ui/app/views/demo.html.

[grtjn]

Field-level edits and DLS don't have to contradict each other.. ;-)

I do like the idea of not immediately pushing each change to the server, but 'caching' them first, and explicitly asking the user to apply or cancel. That is more realistic, and would allow showcasing more of the capabilities.

I'm also thinking of data validation, both client-side (immediately while typing, like in XForms), and server-side (Schema driven?)..

[grtjn]

Should be pretty straight-forward to reuse the create for edit (like we did in demo-cat). Won't make it in 0.2.0 though..

[grtjn]

Still on the list, PR's welcome!

[grtjn]

I think we best start with a relatively simple implementation that reuses create page to allow editing as well, alike demo-cat. There is a bit of client-side validation in there as well which is nice to have.

[grtjn]

@divino Try to build on top of ui-themes branch. Feel free to open a PR with work in progress, so all can give suggestions along the way..

[grtjn]

In meantime we merged ui-themes branch, so you can work against master for this..

[divino]

Currently, the details page contains an option to view it either as JSON or XML. We can support both file types if we allow on create to explicitly select what file type to save the data. Right now, we are only saving it as JSON.

[grtjn]

Sounds great. I'm thinking of a radio toggle between last input field and submit button. You can also show that at edit, disabled to the format it already has..

[grtjn]

Fixed in master..