> -----Original Message----- > From: Unmoderated discussion of advanced .NET topics. > [mailto:[EMAIL PROTECTED] On Behalf Of Geoff Taylor > Sent: Mittwoch, 21. April 2004 10:00 > To: [EMAIL PROTECTED] > Subject: Re: [ADVANCED-DOTNET] Using a common form for web > and windows-based application. > > Thomas Tomiczek wrote: > > >>This would speed things a lot, especially for enterprise > development. > >> > >> > > > >Possibly. > > > >But only if you like extremely idiotic surfaces. > > > > > Oh, I think that's a little harsh... You can do a lot in > browser applications these days that was previously only > possible in rich clients. For instance, HTML only provides > dropdown lists, not real combo boxes, but there are real > combo boxes available that take advantage of dynamic HTML to > provide the same user experience. > (Shameless plug: > http://www.opinionatedgeek.com/DotNet/Products/PowerPack/Examp > les/ComboBox.aspx > - or a free alternative by someone else: http://www.coreyhulen.com/ ) > > I agree that trying to come up with a platform that will > allow a rendering to both web forms and win forms will mean > you have to accept the lowest common denominator from both > camps, but I don't think that that lowest common denominator > is as low as you think.
It is. See, the issue is not only about UI capabilities, it is also about WORKFLOW. You can do a LOT in HTML now (though still way less than in winforms), but when I design a Winform app, I do a lot of thigns that aI can not do in the web - I simply use different paradigms. Serving BOTH from one UI will lead to THIS being low. I am not depating that given the right tools you can make a HTML UI that runs locally (We do so for some text editors - IE is a great platform for this), is a winform like app that runs in the browser. But serving both from one codebase will lead to the smallest common factor. And THIS leads to very badly designed apps. Basically the UI will make all people used to winforms apps cringe. Like my text editors are getting spellchecking now - while you type. Dynamic help (while you type), intellisense. Making this from one codebase would mean hundreds of calls back to the server, or some way to translate the mlogic from IL to javascript (to run it from the client). Or taking the functionality out. Which - well - leads to minimalistic surfaces. The approach for a winform app is just different than for a webform app. Thomas Tomiczek THONA Software & Consulting Ltd. (Microsoft MVP C#/.NET) (CTO PowerNodes Ltd.) =================================== This list is hosted by DevelopMentorŪ http://www.develop.com Some .NET courses you may be interested in: NEW! Guerrilla ASP.NET, 17 May 2004, in Los Angeles http://www.develop.com/courses/gaspdotnetls View archives and manage your subscription(s) at http://discuss.develop.com
