Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Matpol gave a literal solution to the specific information provided. Your edit implies that you are looking for an answer to a more hypothetical question. In other words, you're looking for the "approach".</p> <p>Answering the question in this manner; the single example you gave is a bit of a red herring. It is but a single item in the whole app, and prevents us from "seeing the forest from the trees". So what is the Forest? The question, asked as such, doesn't define it. But I think all programmers will agree when I say it's a nightmare to work on a project that has no definition. So, I'll rephrase your question and answer, "What is the process for defining a project?"</p> <p>Mine is, in fact, asking a series of questions:</p> <ul> <li>What is the core purpose of this application?</li> <li>When do you want it launched? If we had to launch it in 1/4 that time, which features would you keep?</li> <li>Which features are you absolutely certain you're going to need afterwards?</li> </ul> <p>A lot of the time, to get to the bottom of those questions, I need to ask other business questions:</p> <ul> <li>Who is your audience?</li> <li>Why do they care about this site? What's going to keep them coming back?</li> <li>How are you going to generate revenue?</li> <li>What is your call to action? If you could funnel all of your users down a single path, which would it be?</li> </ul> <p>Hopefully, these questions will result in a set of foundational code that you can consider your core. Your core, as you suspected, probably doesn't fit the modular approach. And as you identified, you will want to break that core down into a Model / View / Controller layout.</p> <p>But it's inevitable that you will need to add design fluff. And this brings us back to your code example - its fluff. Fluff belongs in a plugin, separated from the core. This isn't to say that all of your plugins should be delivered to the user in separate js files... but for your development purposes, they should be viewed as modular, and independent from the core code base.</p>
    singulars
    1. This table or related slice is empty.
    1. POHow would you organize a large complex web application (see basic example)?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USMatrym
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    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. VTUpMod
    1. COThanks for the answer. You cover some really good points, but I made the question very specific because it's very difficult to get good answers for very broad and open-ended questions. That said, I wrote the above code specifically for this question ignoring any design or architecture. The functions and logic were written with a fix-as-you-go kind of approach. A crappy solution can be improved in numerous ways, but the same may not apply to a decent solution. So I guess I am looking for innovative ways to handle just the above case and nothing more. Hope that makes sense :)
      singulars
      1. PO
      1. USAnurag
    2. COFor the specific code provided, I think Matpol's answer was good. For a text counter widget, I think a jquery plugin (if you're using jquery) is the prefect solution. But I was led to believe that there was more when you said "...which is going to be problematic when you have 20 such plugins in the application, which is not an absurd number by any means." Was the question more about how do you set it up with configurations? If so, which aspects would you like to have configurable? If its for a single site that you control, that may be less of a concern?
      singulars
      1. PO
      1. USMatrym
    3. COAn encapsulated UI component, call it a widget or a jQuery plugin is indeed the way to go. Regarding the second point, the idea is to make these widgets/plugins configurable using a global configuration. The widgets keep control over the trivial aspects of the plugin and the important aspects are controlled by app or module-wide configurations. I've rewritten the original example partially using MooTools (framework is irrelevant), where the global configuration is supplied to the comment box. With custom application events, things might look a lot better from the original example.
      singulars
      1. PO
      1. USAnurag
 

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