Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>The big thing you need to do is make the workflow separate from the views themselves. That is, you should have an object that coordinates the work flow between the views, holds on to the data that was entered in to the views, and uses the results of the views (through events or other means) to figure out where to go next.</p> <p>I've blogged about this in more detail, with a very simple example of a wizard-style interface, here:</p> <p><a href="http://lostechies.com/derickbailey/2012/05/10/modeling-explicit-workflow-with-code-in-javascript-and-backbone-apps/">http://lostechies.com/derickbailey/2012/05/10/modeling-explicit-workflow-with-code-in-javascript-and-backbone-apps/</a></p> <p>and here:</p> <p><a href="http://lostechies.com/derickbailey/2012/05/15/workflow-in-backbone-apps-triggering-view-events-from-dom-events/">http://lostechies.com/derickbailey/2012/05/15/workflow-in-backbone-apps-triggering-view-events-from-dom-events/</a></p> <p>Here's the basic code from that first post, which shows the workflow object and how it coordinates the views:</p> <pre><code> orgChart = { addNewEmployee: function(){ var that = this; var employeeDetail = this.getEmployeeDetail(); employeeDetail.on("complete", function(employee){ var managerSelector = that.selectManager(employee); managerSelector.on("save", function(employee){ employee.save(); }); }); }, getEmployeeDetail: function(){ var form = new EmployeeDetailForm(); form.render(); $("#wizard").html(form.el); return form; }, selectManager: function(employee){ var form = new SelectManagerForm({ model: employee }); form.render(); $("#wizard").html(form.el); return form; } } // implementation details for EmployeeDetailForm go here // implementation details for SelectManagerForm go here // implementation details for Employee model go here </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POCreating a wizard process in backbone.js
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USDerick Bailey
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POCreating a wizard process in backbone.js
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. CO+1, thanks for the response. I've read the blog posts and I unfortunately don't think this will be a good fit for what I'm doing (assuming I understand it). The wizard I'm doing only exists to create a blob of data that will be used to automate filling out an existing very-large-and-not-well-structured PDF file that I'm tightly coupled to, so I can't tease out all the pieces into nice models; it's actually easier to just have an array of generic "screens" as I have to end up mapping back into the PDF structure anyway. Definitely finding it challenging to fit this into an MVC-like structure.
      singulars
      1. PO
      1. USAbe Voelker
    2. CO+1 for the time you spent in answering that... from an addicted backbone user :)
      singulars
      1. PO
      1. USDaniele B
    3. COHow would you put the back and forth logic for those views? I have problems to understand to extend the callbacks with a "previous/next" logic without having a lot of redundant code.
      singulars
      1. PO
      1. USGambo
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload