Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
I've taught myself HTML and CSS and I'm in the process of going into Javascript. I see a lot of things written about web apps (guessing they are the type of thing you get on the Chrome store etc.) but I can't find a definitive guide as to what language they are written in. I know extensions are written in javascript, but what about web apps?
A web application is any application that uses a web browser as a client. The application can be as simple as a message board or a guest sign-in book on a website, or as complex as a word processor or a spreadsheet.
The 'client' is used in client-server environment to refer to the program the person uses to run the application. A client-server environment is one in which multiple computers share information such as entering information into a database. The 'client' is the application used to enter the information, and the 'server' is the application used to store the information,
Web applications commonly use a combination of server-side script (ASP, PHP, etc) and client-side script (HTML, Javascript, etc.) to develop the application.
Server-side web apps can be written in any language which can output text. All that's required is that there is some way for a web server (as in the server software, e.g. Apache) to run the script so that it can send the output to the requesting browser. If that output is valid HTML then brilliant, a web page can be rendered
Web app consists of a server and a client side. Server side can be written in a any programming language. It would be convenient if the language and the libraries support web development. On the client side the norm is web standards like JavaScript, html and css.
A web app is an app coded in any or many of the laguanges of the web, i.e. html, css, javascript, php, asp.net etc. Web apps can be run in a regular browser, in a mobile browser or can be wrapped as apps to be downloaded from Android Market, AppStore etc.
Related
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 2 years ago.
Improve this question
I am new in js and nodejs. I am studing about nodejs in different web sites like w3schools. I learned that nodejs is a kind of server that can run js in the backend of a website . but my mentor told me it is not a server . it is just an engine in the server that can run js. now I am a little confused. I hope someone tell me what exactly nodejs is or tell me a good reference to learn about nodejs.
thank you
Your mentor is wrong, but still kind of right.
Node.js is an open source server environment.
Originally, it came into existence when the developers of JavaScript extended it from something you could only run in the browser to something you could run on your machine as a standalone application.
Nowadays, it's a JavaScript runtime built on Chrome’s V8 JavaScript engine.
Now, this is as you can see indeed a server as it serves your javascript files. However, in difference to a php server, Node.js is designed without threads.
But that doesn't mean you can't take advantage of multiple cores in your environment, and is something I believe your mentor aren't aware of.
Conclusion
Node. js is an application runtime environment that allows you to write server-side applications in JavaScript. Thanks to its unique I/O model, it excels at the sort of scalable and real-time situations we are increasingly demanding of our servers.
It`s an engine that give you possibility to run js scripts in standalone mode. Instead of browser mode.
I agree with #Sergey that node js is engine firstly.
Node.js allows the creation of Web servers and networking tools using JavaScript and a collection of "modules" that handle various core functionalities.Modules are provided for file system I/O, networking (DNS, HTTP, TCP, TLS/SSL, or UDP), binary data (buffers), cryptography functions, data streams, and other core functions. Node.js's modules use an API designed to reduce the complexity of writing server applications.
you can learn about node.js from w3Schools
and Tutorials point are best sites for node.js learning
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 2 years ago.
Improve this question
I've been working on a "web app" which is actually a web site at the moment, completely vanilla, made with HTML, CSS and JavaScript; absolutely no external libraries or frameworks like JQuery, React or AngularJS.
My goal is to one day deploy the site as a webapp for mobile devices (iOS and Android), and desktops (Windows and Mac).
What is the best way to do this? What path should I follow?
Thanks in advance!
EDIT: I guess the site could be considered an app as it is SPA due to the use of JS and almost completely responsive thanks to media queries in CSS.
The main question here is: how do I get from a website app hosted on a remote server accessed via a domain, to an installable app for mobiles and desktops (.ipa, .apk, .exe, .app, etc)?
I suppose there are a few layers to this question. Let's start with some terms:
Responsive web page: A web page that works on multiple different screen resolutions (doesn't require anything more than CSS that uses media queries)
SPA: Single Page Application, this is how you get web "apps" rather than web pages. Tools like React and Angular help a lot with this, since you now need to manage things like state and routing (since you're not longer actually changing which page you are on).
PWA: Progressive Web App, this is the most modern type of web application, which tries to act very much like a native app by being capable of working without a internet connection and more.
A good way to get started down this path is to use React and their excellent tools Create React App https://reactjs.org/docs/create-a-new-react-app.html#create-react-app
This is a suite of tools that are already configured to create a SPA which is a PWA and with all the other modern tools you need to create a great web app. You'll need to read up on how to create Responsive web pages but there is plenty of resources for this, my tips are to start with media queries https://www.w3schools.com/css/css_rwd_mediaqueries.asp as well as learning Flexbox https://css-tricks.com/snippets/css/a-guide-to-flexbox/
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 3 years ago.
Improve this question
I developed a Node.js Application that I would to like to sell to my clients on monthly charges.
I'm looking for solutions to:
Keep my source code safe
Easy client installation
Serial code solution for activation
Application update method
Any advise will be appreciated.
Similar Question: Secure distribution of NodeJS applications
Your goals
Keep my source code safe
The only way you can do it is by making it a Web application that is used as a service instead of being distributed to the client. Don't trust anyone who tells you about code obfuscation or encryption as this is inherently impossible.
Easy client installation
Nothing easier than a Web application.
Serial code solution for activation
For a Web application you don't even need that. And for any application that you distribute to the client it will be trivial to circumvent and there is no way around it.
Application update method
Web application is always up to date. For a distributed application you can take a look at the Electron auto updater.
Any advise will be appreciated.
General advice
My general advice would be to keep in mind that any Node application that is distributed to the client will be very easy to analyze the source code and to circumvent any activation features that you implement. The only thing you can rely on in that case is law, not technology. Make sure that the licence is enforceable and the terms are clear. Distributing the source code doesn't mean that it has to be open source. The license is what's important, not the visibility of the code.
Your options
Depending on what the application does and how the interface looks like, something that you said nothing about in your question, you have few options:
Distribute the application as is and rely on the license to protect you but understand that anyone could be able to analyze your source code no matter what you do. Here you need to manage updates for every change. People will be able to circumvent your activation code feature.
Make it a web application and keep its inner workings completely to yourself. Here you have no updates problems or source code visibility. No need for activation code, you can give access only to paying customers.
Make it a service and keep all the important logic in your backend API and distribute only a thin client that uses that API. You only need to manage auto updates of the client, the backend code is always up to date. You don't need to implement activation codes, people can just log in to the account on your system in the client program and your backend will know who is a paying customer and who's not. The only source coude visible to the client is the client side code which can be minimal and doesn't have to include any critical logic.
Of course it all depends on the nature of your application which you said nothing about.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 8 years ago.
Improve this question
I'm trying to catch up with modern Web application design approaches. With the latest technologies, is it still appropriate or necessary to tie a web application to a specific backend language like PHP, ASP.NET or J2EE?
I've been thinking of HTML5, JavaScript and asynchronous queries. An application could potentially consist of a series of simple, empty HTML document templates where the data components are filled in after the page load event using JQuery/XMLHttpRequest calls to a web service.
In this context, the backend web service could be implemented using any arbitrary framework and the serving of HTML pages could be handle by any web server. The application's web component would then be purely HTML5 and JavaScript with all other business logic hidden behind a web service interface.
But is this an effective design for complex applications which rely on session management and page transitions? Does anyone code this way or are traditional backend languages always used to generate the HTML documents?
Thanks.
Interesting question, I view it as this way. HTML5 is no longer HTML5.. but "HTML". We'll never see an HTML6, the new HTML5 model will continue to be improved upon and have features added to it. Some day, the days of needing third party plugins for video, audio and drawing, all devices will share the same front end presentation model.
When you think of it, frameworks like PHP just make dynamic HTML, and marry business logic with presentation logic. For the forseeable future, couldn't we always have a need for something like that? That being said, I can certainly see numerous applications in the future that leverage open data and rich client side controls. I don't think this threatens the extinction of ASP.NET, PHP or J2EE.. I think it enhances them, as now we all have a more fuller toolbox to develop with.
Scott Hanselman gave an awesome presentation 2 years ago at Microsoft's Build conference (http://channel9.msdn.com/Events/Build/2012/3-027), it's a great discussion on how JavaScript makes the web browser an incredible emulator, and that you can now front load logic and programming onto the end user... similar to what you are thinking. In the end, I think options like this just allow us to make sure that we use the tools for the appropriate reasons, just like in the ASP.NET world we now have Web Forms and MVC.. Web Forms aren't dead, they're just not the only game in town anymore, but now we can use Web Forms when appropriate, and MVC when appropriate.
Great question!
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 9 years ago.
Improve this question
I have read this article (Uses of Javascript), while it is right I know there are other uses of javascript, modern javascript nowadays. I haven't read about node.js and how this one works but I have heard that this one makes js do server-side stuffs?
The question is, what are other uses of javascript, can this replace php and ruby? I know this might not be a good idea for enterprise applications but will work well with medium-size applications, am I right?
What are the other uses of javascript other than the one given in the article?
Javascript can very well be used server side. If you're on an IIS server, you can for example use JScript, nodejs, v8cgi (currently known as TeaJS), or a combination of these. On *nix servers nodejs is a popular framework. Nodejs can even be used to program your own webserver (e.g. using the expressjs framework).
Dive in the given links and see what's possible.
There is TESSEL and Espruino javascript inside microcontroller.
I use Node.js for web application for few years, few projects and really happy so far.
The Express.js + MongoDB makes a perfect match (exactly as PHP + MySQL, 5 years ago). You can find reference on MEAN stack.
It works good no only for small applications. We have medium-size app that could be easily scaled up.
Node.js is not to about substitute PHP or Ruby, but what's happening now is indeed, it's more and more used for web applications nowaday. The reason is simple, Node.js has "web-oriented" core, meaning it's originally created to aim highly productive tcp/http applications. With some progress beautiful web development frameworks appeared on top of Node.js that makes web application development even more easy and fun.
For me, programming Node.js on server makes a lot of sense, since JavaScript is main client-side language (almost without alternatives), so context-switching between client/server programming is less. With practice you get use to some initial JavaScript weirdness and things goes smooth and nice.