As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
I'm trying to decide between Sencha Architect 2 and Wavemaker. They both seem very similar. Of course Wavemaker is completely open source, and Sencha is only partially open source. For this reason I'm leaning towards Wavemaker, but given the learning curve with either, I'd hate to find myself with less options later on, just because I tried to save some money. Here are my main concerns.
1- I want to be able to sell my application without giving away my source code.
2- Productivity of course is paramount. Are they both about the same?
3- Database development tools.
4- Easy of deployment and hosting options.
Opinions either way are much appreciated.
wavemaker is for me best tool for now..
1.on javascript can use some tools for obfuscate code
2.WYSIWYG..visual tool with cool ajax widgets drag and drop and offcourse all free
3.have is model part for can create your db
4.cloudfoundry
Full disclosure: I work for VMware on WaveMaker.
I felt compelled to correct a few things from Rene’s post. WaveMaker is not strictly a backend framework. WaveMaker is a visual, drag-and-drop development tool. Applications created with WaveMaker contain a backend framework (Java, Spring) and a frontend framework (JavaScript, Dojo). Developers enhance their UI by writing JavaScript code.
The comparison to GWT implies that UI development in WaveMaker is done using Java. Although Java is part of the WaveMaker framework, developers do not use Java code to enhance UI functionality. The back-end code is Java, which is used to access databases and other backend services. In most cases WaveMaker developers do not need to modify the Java code. Since WaveMaker produces standard Java/Spring applications it’s easy for a Java developer to extend the backend functionality.
This question doesn't make much sense to me. Are you comparing just the IDE-s?
Anyway, your options look like very different things. One is primarily a front-end framework and another one a back-end framework. One produces Java apps, another one JavaScript. Maybe you should compare Wavemaker against Ext GWT instead, which is Java-based.
Given your point 3, your choice should be straight-forward as there are no database development tools in any of those Sencha front-end development tools that you seem to be referring to. There might be something in Ext GWT, but I'm not at all familiar with that.
Related
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 9 years ago.
I've read some interesting articles and comparisons on JavaScript MV* frameworks and I do know outline of architecture of most popular ones (Ember, Backbone, Angular) However as a PHP programmer (and Symfony 2 lover) who wants to learn one of those in detail, I am concerned if Meteor (my first choice) is flexible enough to be considered a full stack framework so I can abandon server side (eg. PHP) entirely on most basic apps. Until today I thought that PHP + Angular give more possibilites (although it's more time consuming to maintain both server and client side), however I'd like your opinion on that. From what I've seen in meteor's screencast, it seems pretty awesome.
As many people have mentioned, server-side JS would replace the function of PHP completely. But Meteor is much more than that; it allows you to replace your imperative code with declarative code. Meteor takes care of synchronizing the data and you just decide how to render it. No more passing around messages through AJAX. As one article put it, Meteor has made MVC obsolete.
In my experience with meteor, I'm developing a project and reading the book. What I've been able to do with Meteor in a short time has completely blown my mind. Combined with some excellent frontend frameworks such as bootstrap, I don't really have to do any CSS work either (if I don't want to), and that means I can develop without worrying about styling or AJAX, essentially freeing up my time to create awesome applications with very little legwork.
Besides, as they say, it only takes a weekend to try Meteor out. It's not complicated at all if you have JS experience. However, as it took me a bit to understand, it's not necessary to think with MVC anymore. It only took me a couple of days to build my first meteor app so I suggest you try it out!
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 9 years ago.
I want to develop an Android application with HTML5. Application has some basic UI with data which needs to be fetched from server.
I have only basic knowledge of the HTML5 and CSS; But I am new to JavaScript and JQuery.
Which is essential to learn, JavaScript or JQuery? Or I need to learn both?
Any sample code for mobile application screen and request/response will be really appreciated.
First of all you should decide which framework you want to use. The next step is to setup environment. Let's say you want to code with PhoneGap, than you need Eclipse and Android SDK, etc. The list of software you will find in a description.
Actually in my view it is not necessary to use jQuery or its mobile version for development. Sometimes you only need to create an up to 5-6 pages app with some basic animation which is easy to make with CSS3 Transition3D.
However, when you plan to create a big app with complicated business logic, than you may need to use some framework like Sencha or Angular (it depends on your needs).
Talking about frameworks you must understand that every framework is for certain purpose only. I mean, it is ridiculous to use, for instance, knockoutJS for big apps, because the only thing it has been developed for is data binding between model and view. Moreover, in many cases you don't need a framework at all.
Anyway, first of all you should to learn JavaScript basics. I mean how it works, in which steps a code is being processed, that is a function and what in a prototype and so on. Otherwise, you will never know how to write an effective code or how to optimize your code for better performance. It is critical for a mobile devices as they are not such powerful as a desktops. Also you need to understand how a browser works (rendering, network, etc).
That's my view.
You learn here javascript and jquery by simple way
You can build apps using html, css, javascript with phone gap
You can use cross mobile platform.Sencha touch is also one of the cross platform to start.
http://www.sencha.com/products/touch
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
I had asked a question previously regarding the use of Javascript or Ruby on Rails for the development of web apps and got some very good advice from maerics which basically boiled down to Javascript for Frontend/Smaller apps, RoR for service-side/larger apps (Groupon scope).
After a little digging however, I found out about Node.js and Express.js So my decision is basically back at square one.
I'm looking for a language I can use to take an idea to a functional stage (again, the scope is something like Groupon or Twitter). I am an absolute beginner. I know HTML/CSS and a little jquery, but that's about the extent of my knowledge on web technologies.
I've heard about RoR being very easy to learn, or at least pick up, and has a lot of community/support. But Javascript is everywhere, and can be useful for more than just large scale web apps (and I'd be using it anyway if I used RoR), though is far more complex. Seeing as I have no experience in either, I thought I should pick one now and stick to it for the next ~6 months and see how I go.
But can anyone recommend which one to go for?
When you asked about Javascript and RoR in your previous question, you effectively asked about Node.js and RoR.
If you are building a commercial/enterprise level application, stick with RoR. There are way more resources, bigger communities, relatively stable releases, and you can easily find good developers with RoR experience.
Express.js is like Sinatra for Ruby. Neither is as advanced as Rails, preferring to be more 'basic' and providing a minimal feature set rather than try to be an 'everything at once' framework that Rails is.
Right now, Node.js is rapidly changing its API, still has not hit version 1 and hard to find developers for(you often get people claiming they know node and have 1 year exp with it, when they actually mean they have 1 year exp with client side javascript). Besides, for 99% of the web's purposes, RoR will suffice. Most people only use Node for their pet projects, for testing out the next generation of super dynamic interfaces or websocket integration with Socket.io. If you just want to build an application for commercial purposes, use RoR.
As for difficulty, when you start out, Rails will be a bit magical, it does so many things under the hood, you'll have a little bit of difficulty doing something that doesn't already have a tutorial. But look through the source code of some popular gems or even rails itself, and you'll be up to speed in no time. Ruby is an amazingly simple and beautiful language, and you'll find it simpler and probably more fun than javascript.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
I am .NET (do most of my work in ASP.NET WebForms) developer. But I am not limiting myself to that framework only and read and try to learn new stuff from time to time.
Lately I noticed a lot is happening in Javascript world. I'm familiar with jquery/UI and calling web services from client side. But lately I see a lot of new frameworks written in Javascript. I really don't know why so many are created lately. Can anyone enlighten me why is that happening? What are the differences between different frameworks. When should I use/not use them? For example node.js is something totally weird for me. Writing server side code in JS? Writing HTTP servers in JS (or maybe no one really does it?). Creating client side UI on JS only? I really don't get it. Add to this at least 5 templating frameworks and my head is about to explode :)
Atwood's law:
Any application that can be written in JavaScript, will eventually be written in JavaScript.
The real story is: nodejs (or v8) allows developers to write applications in Javascript that can be executed outside a browser. This makes Javascript as powerful as Python or Ruby. Nodejs was adopted faster than any language in history, because many developers already know Javascript. Suddenly it's possible to write applications in Javascript, so we are in a gold rush of development. Many from the Ruby community (who are early adopters) tried nodejs, so it inherited a culture of sharing libraries under permissive licences.
I don't use the client-side/server-side language because it's confusing and a false dichotomy.
I think all the javascript server side libraries are now coming out because of Google's V8; The highly efficient JS engine that Google made for Chrome. It compiles the JS codes and therefore runs its pretty fast.
It was not too long ago that V8 was released.
It makes it easy to run js without a browser efficiently.
The biggest downside of node.js is probably that a fatal error will crash the entire http daemon. So one visitor can bring the entire site down unless a lot of care has been taken.
I think the biggest advantage of js-server-side like node.js is that you can run the same code on server and on browser. This is particularly useful for form validations, for example.
As compared to PHP, node.js also provides the advantage of being able to make non-blocking calls. In fact with node.js its really hard to make any blocking calls.
I wouldn't call node.js a framework though, I see it more like an essential library for which a framework still has to be made (or does one exist already?).
Linkedin is built on node.js and they seem to be very pleased with it. However their site seems to be quite backward to me.
All the fuss about JS is because of the great UI experience the user can get. Instead of the user waiting for the page to refresh every single time they do something, the results are almost instantaneous. I agree with #Karoly Horvath's comment. JQuery may seem weird at first, but its because of the unknown, it's great to work with once you are used to the syntax. Getting back to the user experience, if your page takes forever to load/reload, the users will rather use another site. Your question is not really fit for Stack Overflow, but im sure you will find some additional answers and opinions in the chat sites available on SO. Good luck.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 11 years ago.
I'm going to be developing a small web application for internal use at my company. What is the best Javascript framework to use with it? I'm not a graphic designer but I do have experience writing desktop applications so I think a library strong on containers and widgets would be good. I'd prefer not to spend money and I don't think my management will go for open sourcing the web application. My web application will be written in Grails so it needs a good plugin. What frameworks do you recommend?
I was leaning towards ExtJS but I'm concerned about the license. Does the FLOSS exception apply?
I also considered Dojo but old answered questions suggested that the quality was poor. Is that still the case?
What about GWT?
jQuery seems too open ended for my use, with only a few widgets and a seemingly difficult to browse widget library. Is that assessment correct?
Others?
Prototype JS (my recommendation) and Mootools
jQuery is the industry standard, used by a lot of companies of varying size worldwide. If you worry about the interface there is jQuery UI, which extends jQuery and provides a number of user interface elements. I would suggest to look at it.
Sproutcore is free and works with grails. It has a good library of default components as well.
Dojo has improved a lot. I used the framework recently and they cover many different aspects (from widget library to data repository abstractions). They are improving documentation with tutorials. In addition, you can follow a declarative approach (using tags on your HTML elements) reducing the amount of javascript code.
However, the choice depends on your specific needs. Frameworks such as jquery or mootools are great for manipulating the DOM easily. Howver, if you are looking for a consistent widget framework maybe Dojo or yahoo YUI can be more suited to your needs.
If it's a small project and you are not already familiar with GWT, you'll find it tough to justify the investment in the time spend on learning. GWT's true potentials starts shining when you are familiar with the toolset and development/debugging/deployment workflow.
ExtJS requires paid license for commercial use. But if you can afford it, it might be the fastest route to a good-looking app with powerful UI.
JQuery is good but as someone already pointed out, you need to pick and choose your plugins and resolve version incompatibility issues on your own. For example, if you need an editable grid, jqGrid is a good option, but you'll need to figure out which version will work with your jquery version and other plugins. Similary things like form-validation, masked input etc. often require third-party plugins (or rolling your own). It can become tedious if you are working solo and on a tight deadline.
In my experience, DOJO has much higher learning curve than most other popular JS libraries.
Summary:
GWT, if the project is large-enough to justify the learning effort (or you can reuse the skills in other projects)
jQuery, if you have time and patience for integrating myriad of plugins on your own.
ExtJS, if you value time and convenience over money
DOJO, probably never ;)