jjpetrucelli
Programmer
i have a system now that is viewable to the public but you can also login, for simplicity lets say the public (non login) can view info and if you login you can update. the system currently has the pages coded twice, once for view and once for update. This can cause problems if you were to change the design, add or drop a column from the website. If you change the graphic or add something to one page you have to go into the other page and change there also. people can forget, there could be a bug on one page and not the other, its not the best for consistency.
Now what would the downfalls of creating one page be? I would guess that you could set variables for things like an update button, or textarea etc, based on your login. This could keep the amount of code down.
Whats the best practice here?
Now what would the downfalls of creating one page be? I would guess that you could set variables for things like an update button, or textarea etc, based on your login. This could keep the amount of code down.
Whats the best practice here?