Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I didn't use Jaxer for very long, but here's some things I found:</p> <p><strong>Pros</strong></p> <ul> <li>Write the frontend and backend in the same code. Especially nice for writing validation logic.</li> <li>"Seamless" AJAX communication back to the server - it's just like calling a JS function.</li> <li>The ability to use JavaScript frameworks like jQuery to manipulate the DOM.</li> <li>The ability to generate or manipulate images using the Canvas API.</li> <li>You get to write your server JavaScript using whizzy new JavaScript 1.8 features like Array extras and getters/setters.</li> </ul> <p><strong>Cons</strong></p> <ul> <li>I found their API to be unstable (they were transitioning to 1.0 when I was trying it so that kinda made sense) and the documentation was confusing, missing, or didn't match with changed functionality. I also found that it was very hard to debug my Jaxer server-side code, and when I got in trouble the error messages weren't very helpful.</li> <li>You don't get real MVC or even MVP (ASP.NET-style) separation between your presentation and your logic.</li> <li>I personally couldn't get E4X (xml in JavaScript) working, which was supposed to be a big draw.</li> <li>There's not a lot of framework built around it for building a whole application. You're starting from some pretty basic building blocks.</li> <li>It's not really providing any help in your view, so forget all the templating or reusable components you might use elsewhere. Not that you can't replicate that, but it's more difficult than having it out of the box.</li> </ul> <p>Overall, I think Jaxer has the most promise as a postprocessor in front of another web framewok. It would be great to use Jaxer to layer all the spiffy AJAX stuff on top of an existing site. It would make it a lot easier to make a dynamic site with validation / page manipulation logic shared between server and client. I don't think I would want to write an application using only Jaxer. Also, it's young (and immature) - I'll be interested to see where it ends up.</p>
    singulars
    1. This table or related slice is empty.
    1. POPros and cons with Jaxer
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USbhollis
    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. COI have installed Jaxer now and the first thing I tested was the E4X functionality. Seems to work great and is a very powerful tool. You do have to keep in mind that E4X code should be kept server-side as Mozilla is the only browser that knows what to do with it.
      singulars
      1. PO
      1. USPrestaul
    2. COYeah, I know that it's a Moz-only. As I said, I was using it right around the transition to 1.0, during the betas, and I had a hard time with E4X. If it works, it's wonderful, if it doesn't, it's totally opaque.
      singulars
      1. PO
      1. USbhollis
 

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