• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Ron McLeod
  • Paul Clapham
  • Bear Bibeault
  • Junilu Lacar
Sheriffs:
  • Jeanne Boyarsky
  • Tim Cooke
  • Henry Wong
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • salvin francis
  • Frits Walraven
Bartenders:
  • Scott Selikoff
  • Piet Souris
  • Carey Brown

Using only javascript/ Jquery to generate UI content

 
Ranch Hand
Posts: 1400
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Friends,

I'm in the middle of evaluating technologies for my next assignment. Evaluating if we can use javascript (JQuery) to generate UI content and JAX-RS at server side. I've created a mock page with few artifacts and played around.
I noticed that to create some of the things such as a grid, I have to look around for plugins developed by developers. For e.g. for grid creation I found that jqgrid is pretty useful. Question I have here is suppose if I decide to use jqgrid, would I have to rely upon the developer of jqgrid for future support. For e.g. if a new browser/ or version of it comes up and by that time suppose the support isn't around - what options would I have other than asking developers to go and make changes in jqgrid? Ours is a basically team of java developers, so I'm little bit apprehensive if it would be that easy. Other option that we are evaluating is GWT. I haven't much looked into it yet, but assume chances of getting support in future could be bit high since it has a backing of a bigger organization.

Would like hear opinions from people on how they planing for such scenarios and what recommendations do they have.

Thanks
Varun
 
author
Posts: 15385
6
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
That is how any 3rd party library works, you hope the people developing them keep on updating them. If not, you either are stuck with a bug OR you have to fix it yourself.

Eric
 
Marshal
Posts: 67451
173
Mac Mac OS X IntelliJ IDE jQuery Java
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
While I'm a big proponent of jQuery, if no one in your organization wants to take the time to learn something other than Java, it sounds like GWT might be the better way to go for your organization. I find GWT way too limiting, but for people who can't learn JavaScript, it may be useful.
 
Varun Khanna
Ranch Hand
Posts: 1400
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thanks Eric and Bear.

I have another question. I have realized those who are using JQuery, they are mostly using & recommending a single html approach where-in the contents are dynamically changed in the page by javascript. I googled a bit and seems like this is called as SPA (Single Page Architecture). Is this a recommended or preferred design? If I use separate HTML pages, just I liked used to have during "JSP days", will that be considered a bad design? At this point I'm not sure if I do that, what all will I miss. What I can think of is, having separate HTML pages will allow me to write lesser javascript, also with team of many developers - lesser chances of people working on same file. Am I missing something?

Thanks much.
 
Bear Bibeault
Marshal
Posts: 67451
173
Mac Mac OS X IntelliJ IDE jQuery Java
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

Varun Khanna wrote:
I have realized those who are using JQuery, they are mostly using & recommending a single html approach where-in the contents are dynamically changed in the page by javascript.


That is one approach. It is hardly what I'd called "the recommended" approach.

If I use separate HTML pages, just I liked used to have during "JSP days", will that be considered a bad design?


No.
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
    Bookmark Topic Watch Topic
  • New Topic