Events are used for more than just GUI functionality. You can, for instance create an event listener. Then, on your web page, create an event that the listener picks up and acts upon.
The nice thing is, the event can originate from anywhere, not just your web page. Maybe you have another app somewhere else that also creates those events. Anyhow, in terms of ASP.NET and presentation, the event model exists to make web development closer to traditional client/server development. The fact that VS.NET works well with it is a nicety. The event model came first; it does not exist for an IDE's sake. ----- Original Message ----- From: Dave Watts <[EMAIL PROTECTED]> Date: Friday, July 18, 2003 11:34 am Subject: RE: MSDN on CF -> ASP.net > > You don't need VS.NET for the event model. You can write it > > yourself. > > > > Wiring an event handler is extremely easy - it's one line of > > code for each event. The extra code you alluded to earlier > > is for VS.NET's benefit - it allows the IDE to know exactly > > what methods are called for any given event. I myself don't > > really bother to use this functionality. > > But if you're not using VS.NET, why bother with an event model at > all? It > seems to me that the goal of the event model is to let developers > use GUI > concepts and tools to build web applications. > > Dave Watts, CTO, Fig Leaf Software > http://www.figleaf.com/ > voice: (202) 797-5496 > fax: (202) 797-5444 > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4 Subscription: http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4 FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Get the mailserver that powers this list at http://www.coolfusion.com Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
