Notice the Properties window when you select any object in the Designer. These are the parameters corresponding to the code that comes with that object and which you do not have to write. These parameters could be changed manually and also programmatically. ASP.NET Forms use event-based model, which means that every object on the page, and even a seemingly blank page itself, have programmed sensitivity to various user and software induced events (like button click, mouse over, etc.) and respond to it instead of working as simple programs that have a start and finish points of execution. This means that the user will see a page with some elements on it that will be “waiting” for user’s actions instead of asking questions in a menu of what else you want to do.
Tuesday
Objects and Events in Frameworks
It is important to
understand that you are dealing with the Framework, which includes a bunch of objects
(see the book and may be do the Google search if the book is not enough to get
the idea of a software object)) with already written code and properties. See,
for example, how simple actions in the Design view add lots of lines of code in
the source view (which in the open-source tools often have to be written by you
manually). The main work in this course will be in learning some basic important
objects (controls) that could be just dropped on the page, learn how to adjust
their parameters, and, ultimately, how to make them do whatever else is needed
by additional programming tweaking. Another goal is to learn more general
approach, methods, and design patterns of Web development when using frameworks
with ready-made code.
Notice the Properties window when you select any object in the Designer. These are the parameters corresponding to the code that comes with that object and which you do not have to write. These parameters could be changed manually and also programmatically. ASP.NET Forms use event-based model, which means that every object on the page, and even a seemingly blank page itself, have programmed sensitivity to various user and software induced events (like button click, mouse over, etc.) and respond to it instead of working as simple programs that have a start and finish points of execution. This means that the user will see a page with some elements on it that will be “waiting” for user’s actions instead of asking questions in a menu of what else you want to do.
Notice the Properties window when you select any object in the Designer. These are the parameters corresponding to the code that comes with that object and which you do not have to write. These parameters could be changed manually and also programmatically. ASP.NET Forms use event-based model, which means that every object on the page, and even a seemingly blank page itself, have programmed sensitivity to various user and software induced events (like button click, mouse over, etc.) and respond to it instead of working as simple programs that have a start and finish points of execution. This means that the user will see a page with some elements on it that will be “waiting” for user’s actions instead of asking questions in a menu of what else you want to do.
