The new forums will be named Coin Return (based on the most recent vote)! You can check on the status and timeline of the transition to the new forums here.
The Guiding Principles and New Rules document is now in effect.
Dynamic Webpage Content
blue integer
Registered User regular
Registered User regular
Hello PAers.
I have the desire to create a slightly dynamic web page. I know html and css fairly well. Needless to say, I can design a page that looks ok.
However, I want to do some simple stuff...for instance, create lists that can be organized alphabetically or numerically at the user's discretion.
Would this be best suited for php or sql? How long would it take to learn and implement something like this?
Thanks for your advice.
I have the desire to create a slightly dynamic web page. I know html and css fairly well. Needless to say, I can design a page that looks ok.
However, I want to do some simple stuff...for instance, create lists that can be organized alphabetically or numerically at the user's discretion.
Would this be best suited for php or sql? How long would it take to learn and implement something like this?
Thanks for your advice.
blue integer on
0
Posts
http://www.thelostworlds.net/
Integers, some strings...maybe true/false stuff. Basically, a bit of everything. There might even be some sentences.
Ease of update isn't an end all...I'd rather have a solution that's easier to implement than a solution that's easier to update.
Thanks for the reply.
Well you don't need SQL for that, you have no need for state. If you wanted the list to be stored outside of the web page (this is a good idea) then you will need the database.
Eh, not necessarily.
If it's a simple two-dimensional list it could easily be stored in a text file rather than a full database.
the "no true scotch man" fallacy.
Well, yeah. But I like putting everything in databases; text files worry me
However, though it's possible, actually implementing anything to do with node manipulation will make you want to stab yourself in the balls with a fork.
PHP and a text file would probably be easiest, especially if you're doing the set up yourself and learning from scratch. You'd want a database if you planned to do anything on a large scale.
I'd like to come out of this project with my balls intact (if possible).
Any good resources to read? Or just learn some php?
As for Javascript/nodes, I'd say buy a decent book. I have a particular hatred for complex Javascript solutions because you have to think about the content and it's presentation in weird ways compared to PHP, and they never work quite like you'd expect cross-browser (that's mostly the cause of the fork/balls interaction).