Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 6 years ago.
Improve this question
Can you call an Angularjs app a single page angular application if while it's built/setup in angular, but then you might use jQuery for a carousel image or jQuery for fade effects or something like this added to the site that isn't angular. Would it technically be a single page angular application if jQuery or something else is incorporated in the app? I'm asking because of when I see job listings for single page applications, I want to make sure I fully understand the underlying meaning of a single page application
Also wouldn't it technically not be a single page if ng-src routed to another .html file and the page refreshed to do so as opposed to using routeprovider and locationprovider to make it appear without refreshing via ng-view?
That may come as a surprise to you, but Angular have its own jQuery subset implementation called jQLite. As long as you load a single HTML page and dynamically update its contents instead of navigating away, it is an SPA regardless of javascript libraries in use.
That's kind of opinion-based, but I would call it a non-SPA since it causes a refresh (for something other than, say, updating to a newly-deployed version.)
Related
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 months ago.
Improve this question
I am a bit confused...Do companies use HTML/CSS and then add react.js to it or do they just use react + JSX + css only for building Websites?
The html and css with js is almost always the final result. So some companies create first their mock-ups to see how it will be visualized in all the clients they desired to render( mobile desktop etc) and then break it in to components with any behavior they need. Other just take a mock-up and start directly in the frameworks they choose. All depends the money time and resources available.
Normally companies are no longer working with plain HTML/JS/CSS anymore. That means that their use is restricted by the framework/library they are working with. In the case of React and other libraries to build SPA (Single Page Applications), it's a common pattern to use a single HTML file as an entry-point. Regarding JS and CSS they are normally used along with syntax extensions like JSX, libraries like styled-components etc, so they need to be transpiled and bundled to get them to work into the actual browser.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 7 years ago.
Improve this question
I'm using angularjs for my application, which is so secure (similar like banking application),i have another option of using freemarker or velocity ..
whether it is best to go with angularjs or we can use freemarker or velocity. if so could you please explain. the backend service is spring boot .
Freemarker is just a templating engine, it's not a full front-end framework with 2 way data binding like angularjs is. Also, with angular it's very easy to build Single Page Applications which have a very smooth user experience compared to traditional applications where you must reload the page every time the user navigates to another page. If you already know angular, it's the better choice. If you don't know angular, then freemarker is much faster to learn but not quite as powerful/good. Though I do quite like freemarker as a templating engine.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
I was playing with ReactJS for a bit, and given a bit of prior exposure to AngularJS, and the way things are done in the latter, I had a hard time to get used to the syntax and the 'flow' of React.
So I had the above-mentioned question, plus: are there scenarios when ReactJS should be preferred to AngularJS?
Could anyone point out what can be done [easier/better/more efficiently] in React rather than in Angular, and other way around.
It's actually the opposite. Angular has a lot of features, apis, configuration options, etc. React tries to be much simpler and let you choose how your application is structured. Controllers, directives, and templates are reduced to just components. Services are just plain JavaScript, there's nothing React specific about it. Things like $q and $timeout don't exist because there's no digress (use anything you like for those).
You use React in your application, vs making your application in angular.
ReactJS uses the concept of virtual DOM which speeds up the rendering of the app.
Watch Pete Hunt's excellent video on Virtual Dom here:
https://www.youtube.com/watch?v=-DX3vJiqxm4
The syntax might be very unconventional but the same thing can be said about Angular's concept of Directives, services, controllers, etc. It just takes time to get used to, but once you feel comfortable, you'll find that thinking in ReactJS really makes sense.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
Since Backbone's Router only work with "#", it means that it should be all in the same page. Should a BB application be only in one page and have only 1 Router?
One of the many nice things about Backbone is that it is very unopinionated about how you work with it. For example, if you just want to use views, then you can do that, and if you want to just use models, you can do that as well.
A Backbone application can be a single-page application, and it certainly provides a lot of functionality to make that easier if that is your goal, but it doesn't have to be. There is absolutely nothing wrong with explicitly calling your views by hand instead of using a router.
To answer the second part of your question... No, you can have as many routers as you like. However, I'd say a large portion of Backbone apps out there make do with just one. I am working on a Backbone app that has over a hundred different views, and I've never run into an issue where I'd have to introduce a secondary router.
Finally, a bit of a correction on your end; The Router object actually doesn't enforce the "#" anymore as long as your browser has pushState functionality. Older browsers (mainly IE) will fallback to the hashtag approach if necessary.
Hope this helps!
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
EXT JS - which is better to have navigation between pages? To have different html files or single html file and different views considering the fact that all the files reside on the server.
Basically what i want to know is in sencha touch it makes sense to have single page architecture. But how about ext js ?
The second question first:
ExtJS is designed for single page application. Go for it, you then don't need to ask yourself the first question.
First question:
In ExtJs, you don't have to think so much in terms of html files, because you generally only have one.
If you really want to have more than one html file, you would probably choose to use the same js file on both and include in the html a kind of a trigger which defines what part of code is executed. But anyway, I would not recommend you to go that way.