I'm just starting to learn web development, but I'm confused about how to invest. I've heard that the server side code translates into client-side code, so if you have an .aspx file, it will be converted to HTML / CSS / JavaScript. I have an experience with the following three technologies which have been inserted into a sluggish text file and provided by the web browser. My question is, how much HTML / CSS / JavaScript coding do I have to do when doing server-side programming? In other words, can a person use the ASP.NET program purely on the server side and can not bother to write for the client side? Of course, I do not care to translate the server-side to the client side, but I'm wondering if the client-side programming should clearly and at what degree.
You will want learn to do your own client-side programming, A framework that's worth your client-side programming to "do for you" or maybe not a good job, but at some point, you have to debug it, find out what it's doing and this is a bug or No misconceptions, etc. Instead of stumbling in the dark, invest some time in learning client-side technologies and techniques, so that you understand what frameworks are creating for you and you exactly on the client, on the server And what they want in the interface between them. For example: About I, how does a button browser on the client side "save the file" dialog box when the user clicks it, then the file is custom-generated in that question, without tearing that page The key is inside the button. This is not necessarily a major issue of edge, so that the user is not uncommon on the custom generation generation (say) all, and can be useful to increase user experience. Without the need of flash or similar, you are hard to do that from beauty , with high quality user experience, what is happening on the client, what is happening on the server To get the experience you want to create, and to get the two parts to exchange related information.
Comments
Post a Comment