Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I have used jQuery extensively and love it. I have reviewed ExtJS on several occasions and would love to have the chance to use this library at some point. This is my take.</p> <p><strong>jQuery</strong></p> <p>The junk drawer of javascript programming. They got everything you need in there, if you're willing to dig, use some duct tape and super glue, and in general have a group of developers able and willing to hammer code. jQuery is great!</p> <p>It's used in way more places than you think. However, like Drupal and other community-supported frameworks/libraries, when you get free support, you get what you pay for. You can get it all done with jQuery, but sometimes you need a shovel, flashlight and perseverance. </p> <p>Additionally, very good documentation (on par with PHP's online docs), and tons, literally tons, of example code and blog entries out there.</p> <p>Will appeal to tinkerers and "advanced scripters" who are not shy to Google a phrase to find an example that can be used to scaffold a problem and speed development.</p> <p><strong>ExtJS</strong></p> <p>Professionally developed by a for-profit company, these are more akin to controls (in the context of Visual Studios) than widgets or plugins. Intentionally complete and robust, with an eye for detail and a higher-level organizational structure than I think exists in the wilds of jQuery, ExtJS is a get what you pay for: A professionally-developed and supported product that lives and dies by it's ability to return value.</p> <p>Will appeal to professionally-trained "programmers" expecting extensive testing and a higher-order or rigorousness in the development of the controls.</p> <p><strong>Final Recommendation</strong></p> <p>It really has to do with your shop and customers. If your group is more DIY and likes to glue together things and get it out the door, go with jQuery. It's robust for any situation. If you have a very ordered and professional shop, ExtJS might be a good choice, but jQuery will also be viable. I don't see the need to split your knowledgebase and use both, but really, if you do, use ExtJS for the client-facing portion and jQuery for the admin consoles. I don't see the benefit the other way around.</p> <p>Also, for you admin consoles, look into <a href="http://developer.tibco.com/default.jsp" rel="noreferrer">TIBCO</a>. Possibly overkill, but very interesting.</p>
    singulars
    1. This table or related slice is empty.
    1. POJQuery vs ExtJS
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USJared Farrish
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POJQuery vs ExtJS
      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. VTUpMod
    1. CONice write up on both.. Funnily enough I came to the opposite conclusion re: client VS admin :)
      singulars
      1. PO
      1. USBen
    2. COI guess the decision has to do with what the clients are seeing and what the admin console is tasked with (adjusting user accounts versus SCADA). My thoughts are that the client should see the money, and that admin consoles should be just what's necessary, but that's not hard in stone. Honestly, I would have a hard time really backing a code split unless it was legacy. Why rewrite code you already have in jQuery? That sounds like wasted $$ unless ExtJS gives you practical and predictable improvements in time-to-ship and/or client support metrics.
      singulars
      1. PO
      1. USJared Farrish
    3. COBy the way, TIBCO General Interface is the best entry point if you are interested in it. http://developer.tibco.com/gi/default.jsp
      singulars
      1. PO
      1. USJared Farrish
 

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