How can I keep a value for a variable in Javascript, even when the webpage reloads?

Sorry to tell you this, but to have a centralized storage like you intend to have, you need a server. JavaScript was/still is client side so having it work for multiple people at the same time will be impossible.

Sorry to tell you this, but to have a centralized storage like you intend to have, you need a server. JavaScript was/still is client side so having it work for multiple people at the same time will be impossible. For this to work you need a server.

A local storage won't work because then not all people will have the same data.

Currently I am using Abyss Web Server for the server. But as far as server side scripting goes, I have zilch experience. Any good ideas for where to begin?

– Jacob A. Bridges 2 days ago Look up AJAX for the client side and for the server side PHP will suffice. AWS even supports it: aprelium.com/abyssws/php.html – vanneto 2 days ago.

From my viewpoint, the main problem I have is modifying a variable in Javascript on a webpage, then somehow saving that variable to a document in ONE location. This way every computer connected to that network can access the variables and modify them as needed. That, my friend, is a database.

Yes, a database is the solution. What you need to understand first about web development is that there are two kinds: client side and server side. Javascript is client side development, meaning it works on the user's browser.

You have a variable on the client side, but only that client can see it. Server side is different. It exists on the server alone.

Your server "serves" your page (and any content from a database or whatever) to the client. Therefore any changes on the server will be visible to all the clients (what you want). To program server side, you have to use another language other than javascript (you can use node.

Js but that's entirely different than client side javascript). Other languages include PHP, Java, C#, etc. Therefore, you need to look up server side scripting.

Sigh Oh well. A database it is. Thank you for your answer!

I did forget to mention that I am using Abyss Web Server as the broadcasting server for the inventory page. But when it comes to server side scripting I know close to nothing. Do you have any recommendations on where to begin?

And from what I have seen, databases have issues when being edited by more than one user. – Jacob A. Bridges 2 days ago @JacobA.

Bridges I feel your pain :P but it's definitely worth learning, and necessary for any serious web development. Good luck! Oh!

And if you do run into any problems, don't hesitate to ask for help on here :) – Joseph Marikle 2 days ago Thank you for your comment, and the encouragement. I edited my comment above, for it was posted prematurely lol. – Jacob A.

Bridges 2 days ago @JacobA. Bridges You're welcome. :) Unfortunately, I am a complete noob when it comes to client side development (I only just recently started learning it), but PHP would probably be the easiest to start learning with.It's cross-platform, has excellent documentation, and is easy to get set up.

You can google for LAMP (for Linux) or WAMP (for Windows) to get a server running on your personal computer. From there, have fun with it and you'll learn it quickly. :) – Joseph Marikle 2 days ago.

You will need a backend language, such as php, asp, . Net, java, etc. Using this backend language you will be able to make queries to a database, for example a mysql database, I would recommend you to take a look at php and mysql as they are both free: http://php.net, mysql.com to get you an environment working quickly to debug NOT for production, try WAMP: wampserver.com/en.

Or XAMPP. These "pre-built" stacks will get you a webserver capable of hosting PHP (and MySQL and more! ) very quickly.

Install, run, visit localhost and start playing. – TRedman 2 days ago.

You can avoid having your own database and store inventory data in some cloud storage like Google Spreadsheet. But of course that will also require some learning. If you have a Google account simplest thing to do is to create a spreadsheet fit for storing your inventory and then generate a web form from that spreadsheet.

Finally just embed that generated form in your html and you're good to go. All the changes in inventory will be reflected in the Google doc's spreadsheet.

There are multiple parts to implementing a shared inventory app. At the highest level, you can break this down to transferring data between the browsers and the server (client-server communication, which will be based on HTTP and includes technologies such as AJAX) and sharing data between requests. The former has been directly covered many, many times before on SO (see linked questions in the "Linked" section on the right of the page).

The latter has also been covered, but perhaps not as directly, so the information is scattered. The exact design and implementation for both depends on what server-side technologies you have available. An ASP.Net approach will be quiet different from a PHP approach, which will differ from a JSP approach.

Each has different way of persisting data in ways that can be accessed by multiple users. Some basic ways are shared memory, files and (as you've already mentioned) databases. Before shying away from databases, keep in mind that there are many tricky data related tasks that must be performed.

If you don't use a database, you'll need to implement these yourself. In the end, you'll wind up implementing a database of some sort, one that likely has fewer features, more bugs, performs worse and will require other developers who may work on the project (an projects can live longer than you expect) to first learn your data storage system.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.