> 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 Signup for the Fusion Authority news alert and keep up with the latest news in ColdFusion and related topics. http://www.fusionauthority.com/signup.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
