The Forum has been Updated
The code has been upgraded to the latest .NET core version. Please check instructions in the Community Announcements about migrating your account.
Hello,
I want to learn just one thing
.how to make one of the options work without refreshing the page
For instance, when adding a quick reply, it appears directly when
.I am in the subject without refreshing the page
I want to learn this because I want to make many options work without
refreshing the page such as fixing the subjest and locking it, and locking
the form and opening it as well as many many things
DO NOT POST LINKS WHICH HAVE NO RELEVANCE TO THE FORUM OR YOUR QUESTION
I want to learn just one thing
.how to make one of the options work without refreshing the page
For instance, when adding a quick reply, it appears directly when
.I am in the subject without refreshing the page
I want to learn this because I want to make many options work without
refreshing the page such as fixing the subjest and locking it, and locking
the form and opening it as well as many many things
DO NOT POST LINKS WHICH HAVE NO RELEVANCE TO THE FORUM OR YOUR QUESTION
Posted
What you are describing is commonly done with AJAX. There are some ASP AJAX libraries out there to make the learning curve a little easier (Google/Bing/whatever and you will find several options). The forum is not set up with this in mind, and I'm not the biggest AJAX fan in the world.
For starters, you are still depending on the client having JavaScript turned on (which it usually is, but not always - NoScript is rather popular these days). So you'll need to make sure you either have a fallback option or decide that they are not worth the traffic. Only you can decide which applies to you.
That's not even getting into what versions of what browsers will run a given chunk of code...
Also, many of the libraries break the back button - a huge disadvantage. A lot of people will assume your site is broken and leave if the back button doesn't work.
For me, adding the "cool factor" has not been worth the extra work. At my job, the people that remote in can't run JavaScript - kills the whole option for a sizable percentage of the people that need to run the site.
On my side projects, I still get enough traffic from older browsers and browsers with JavaScript turned off that it's not a good value propisition. It will take too much time for me to make it work right.
For you, only you can decide if it is worth your time and effort.
For starters, you are still depending on the client having JavaScript turned on (which it usually is, but not always - NoScript is rather popular these days). So you'll need to make sure you either have a fallback option or decide that they are not worth the traffic. Only you can decide which applies to you.
That's not even getting into what versions of what browsers will run a given chunk of code...
Also, many of the libraries break the back button - a huge disadvantage. A lot of people will assume your site is broken and leave if the back button doesn't work.
For me, adding the "cool factor" has not been worth the extra work. At my job, the people that remote in can't run JavaScript - kills the whole option for a sizable percentage of the people that need to run the site.
On my side projects, I still get enough traffic from older browsers and browsers with JavaScript turned off that it's not a good value propisition. It will take too much time for me to make it work right.
For you, only you can decide if it is worth your time and effort.
Posted
yes you're right it takes a lot of time to learn and i do not have enough time for the time being, maybe