windows vs web UI
-
I'm working on an intranet based app for mid-sized businesses and was wondering what everyone's thoughts were about building a web UI vs. a Traditional Windows UI. I actually prefer Windows based UI since the client can be much richer, however there are some definite advantages to building web based UI. Specifically the ease of deployment issues (i.e. no client code needed). In looking at the market, many of the companies building solutions for this market are using web based UI. Are there any advantages going with web based other than deployment issues. I find web based UI limiting in some respects. Any insight would be great.
-
I'm working on an intranet based app for mid-sized businesses and was wondering what everyone's thoughts were about building a web UI vs. a Traditional Windows UI. I actually prefer Windows based UI since the client can be much richer, however there are some definite advantages to building web based UI. Specifically the ease of deployment issues (i.e. no client code needed). In looking at the market, many of the companies building solutions for this market are using web based UI. Are there any advantages going with web based other than deployment issues. I find web based UI limiting in some respects. Any insight would be great.
I'm in the same boat right now and I'm exploring a three tiered approach where I have the business logic inside of web services. In theory, I can now do an ultra thin web AND Windows Forms based application without having to actually write two applications ... rather, just two different UIs. Obviously, when you're at the office, you can use the pretty application with the better features (I'm tired of the word 'richer') and then on the road you can fire up a web browser and use the web based version. It seems like with .NET, Microsoft is getting pretty close to making web apps behave more like real apps. Of course, you're still missing things like right click menu options and intercepting keystrokes and things that a sophisticated UI provides. For a fairly traditional client/server data driven application, I think you'll find that web apps are going to give you 90% of what you want, which may be good enough. I'm still experimenting myself so perhaps we could trade notes. Give me one more medicated peaceful moment
-
I'm working on an intranet based app for mid-sized businesses and was wondering what everyone's thoughts were about building a web UI vs. a Traditional Windows UI. I actually prefer Windows based UI since the client can be much richer, however there are some definite advantages to building web based UI. Specifically the ease of deployment issues (i.e. no client code needed). In looking at the market, many of the companies building solutions for this market are using web based UI. Are there any advantages going with web based other than deployment issues. I find web based UI limiting in some respects. Any insight would be great.
Web UI. Virtually anything that can be done with a Windows UI can be done with a Web UI. Yes, there are limitiations. However, it depends on the apps requirments. If it's data entry and reporting, then there is no question to use a Web UI. You can create very, very rich Web Interfaces, it just takes skill. Jason Gerard
-
I'm working on an intranet based app for mid-sized businesses and was wondering what everyone's thoughts were about building a web UI vs. a Traditional Windows UI. I actually prefer Windows based UI since the client can be much richer, however there are some definite advantages to building web based UI. Specifically the ease of deployment issues (i.e. no client code needed). In looking at the market, many of the companies building solutions for this market are using web based UI. Are there any advantages going with web based other than deployment issues. I find web based UI limiting in some respects. Any insight would be great.
I haven't actually worked on commercial web UI programs, but there is only reason I would really want to -- easier distribution. (The for-fun work I did like this just seemed to be a lot of extra work to get the web interface to do some of the simple things that a Windows UI can do easily.) Anybody with a web browser can use the Web UI software from anywhere (of course, you might need specific browser versions...) And updating the site is all that is required for software updates, requiring no special install distributions or programming to handle updates, etc. After saying that, I'd really like to look into the new .NET auto-update stuff. I've read one quick article about it, and it intrigued me. However, I don't know quite how it works yet. John
-
Web UI. Virtually anything that can be done with a Windows UI can be done with a Web UI. Yes, there are limitiations. However, it depends on the apps requirments. If it's data entry and reporting, then there is no question to use a Web UI. You can create very, very rich Web Interfaces, it just takes skill. Jason Gerard
Is there a way to implement auto-completing combos and edits without resorting to ActiveX? Tomasz Sowinski -- http://www.shooltz.com
-
I'm working on an intranet based app for mid-sized businesses and was wondering what everyone's thoughts were about building a web UI vs. a Traditional Windows UI. I actually prefer Windows based UI since the client can be much richer, however there are some definite advantages to building web based UI. Specifically the ease of deployment issues (i.e. no client code needed). In looking at the market, many of the companies building solutions for this market are using web based UI. Are there any advantages going with web based other than deployment issues. I find web based UI limiting in some respects. Any insight would be great.
If your clients will be able to install the .NET runtime, Windows Forms may be just what you are looking for. You can build a rich Windows UI that can be easily deployed over the internet. Check this out: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnadvnet/html/Vbnet10142001.asp Regards, Suresh
-
Is there a way to implement auto-completing combos and edits without resorting to ActiveX? Tomasz Sowinski -- http://www.shooltz.com
Tomasz Sowinski wrote: Is there a way to implement auto-completing combos and edits without resorting to ActiveX? Yes there is, construct your own controls using DHTML. I won't say it's easy, but it is certainly possible. Oh, and needless to say, the approach I have in mind is IE specific. ________________ David Wulff http://www.davidwulff.co.uk Sonork ID: 100.9977 Dave …
-
I'm in the same boat right now and I'm exploring a three tiered approach where I have the business logic inside of web services. In theory, I can now do an ultra thin web AND Windows Forms based application without having to actually write two applications ... rather, just two different UIs. Obviously, when you're at the office, you can use the pretty application with the better features (I'm tired of the word 'richer') and then on the road you can fire up a web browser and use the web based version. It seems like with .NET, Microsoft is getting pretty close to making web apps behave more like real apps. Of course, you're still missing things like right click menu options and intercepting keystrokes and things that a sophisticated UI provides. For a fairly traditional client/server data driven application, I think you'll find that web apps are going to give you 90% of what you want, which may be good enough. I'm still experimenting myself so perhaps we could trade notes. Give me one more medicated peaceful moment
Glad to see someone else is in the same boat. :) I'm following the same path, three tier architecture with the possibility to do either windows or web based forms. The one thing I also need is disconnected user support. In other words, users will be able to take data with them when working in offline mode. Not sure what is the best way to handle this (via windows or web forms) Have you at all looked into a mixture of both. I've been playing with the .net stuff and the new windows forms can do some pretty cool stuff over the web. I'm thinking web based for general UI but Windows forms for dialog boxes and things of the nature. The thing I don't knwo is how will it work if someone is accessing the app from a machine outside the firewall where .net may not be installed. I don't know, still doing research as well. X|
-
If your clients will be able to install the .NET runtime, Windows Forms may be just what you are looking for. You can build a rich Windows UI that can be easily deployed over the internet. Check this out: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnadvnet/html/Vbnet10142001.asp Regards, Suresh
Yeah, I saw that article a while ago and it's pretty sweet what you can do. The only problem is that .net is required on the client machine (I believe). This works well for an intranet app, but I believe others will be accessing the app from outside the intranet, there I'm not sure this will work until .net becomes apart of the OS. Also, there are definately some security issues as well. I remember using c# to access the dll from the server and I would get a security notice everytime I tried to run the app.
-
I'm working on an intranet based app for mid-sized businesses and was wondering what everyone's thoughts were about building a web UI vs. a Traditional Windows UI. I actually prefer Windows based UI since the client can be much richer, however there are some definite advantages to building web based UI. Specifically the ease of deployment issues (i.e. no client code needed). In looking at the market, many of the companies building solutions for this market are using web based UI. Are there any advantages going with web based other than deployment issues. I find web based UI limiting in some respects. Any insight would be great.
ez2 wrote: I'm working on an intranet based app for mid-sized businesses I think that says it all. Web UI. The "formula" I use is : all "forms" type applications including data entry, reporting, CRM, HR apps, should probably be web based. All productivity applications like word processing, CAD, 3D design, Sound/Video editing, IDEs, etc; should be windows based. In some cases, you may want to have a "console" where you have a rich windows GUI, in addition to a web GUI for the rank and file users. However, I am not sure economics can justify this double work in some cases. HTH :-)
-
Web UI. Virtually anything that can be done with a Windows UI can be done with a Web UI. Yes, there are limitiations. However, it depends on the apps requirments. If it's data entry and reporting, then there is no question to use a Web UI. You can create very, very rich Web Interfaces, it just takes skill. Jason Gerard
That is probably true, with a lot of time and work spent. But there is a speed issue which plagues Web solutions. For example it takes almost 30 seconds on my machine to load 4000+ nodes XML tree structure (from the local disk) to IE6. Same task is accomplished in less than a second with Windows Forms and tree control. I just can't see Web UI as a real life solution. Regards, Dejan Petrovic
-
I'm working on an intranet based app for mid-sized businesses and was wondering what everyone's thoughts were about building a web UI vs. a Traditional Windows UI. I actually prefer Windows based UI since the client can be much richer, however there are some definite advantages to building web based UI. Specifically the ease of deployment issues (i.e. no client code needed). In looking at the market, many of the companies building solutions for this market are using web based UI. Are there any advantages going with web based other than deployment issues. I find web based UI limiting in some respects. Any insight would be great.
[ I hope this reply makes it to the main thread. I'm so burned out, I've been making stupid mistakes continuously for the past 10 minutes. I hope I don't drive into a tree on the way home...] An important thing to keep in mind is that web clients are inherently stateless. You have *much* less control over a web client than a standard desktop app. Of course, there are other pros and cons, but be aware of the statelessness, as it has bearing on how you write your backend code. /ravi "There is always one more bug..." http://www.ravib.com ravib@ravib.com
-
I'm in the same boat right now and I'm exploring a three tiered approach where I have the business logic inside of web services. In theory, I can now do an ultra thin web AND Windows Forms based application without having to actually write two applications ... rather, just two different UIs. Obviously, when you're at the office, you can use the pretty application with the better features (I'm tired of the word 'richer') and then on the road you can fire up a web browser and use the web based version. It seems like with .NET, Microsoft is getting pretty close to making web apps behave more like real apps. Of course, you're still missing things like right click menu options and intercepting keystrokes and things that a sophisticated UI provides. For a fairly traditional client/server data driven application, I think you'll find that web apps are going to give you 90% of what you want, which may be good enough. I'm still experimenting myself so perhaps we could trade notes. Give me one more medicated peaceful moment
An important thing to keep in mind is that web clients are inherently stateless. You have *much* less control over a web client than a standard desktop app. Of course, there are other pros and cons, but be aware of the statelessness, as it has bearing on how you write your backend code. /ravi "There is always one more bug..." http://www.ravib.com ravib@ravib.com
-
Glad to see someone else is in the same boat. :) I'm following the same path, three tier architecture with the possibility to do either windows or web based forms. The one thing I also need is disconnected user support. In other words, users will be able to take data with them when working in offline mode. Not sure what is the best way to handle this (via windows or web forms) Have you at all looked into a mixture of both. I've been playing with the .net stuff and the new windows forms can do some pretty cool stuff over the web. I'm thinking web based for general UI but Windows forms for dialog boxes and things of the nature. The thing I don't knwo is how will it work if someone is accessing the app from a machine outside the firewall where .net may not be installed. I don't know, still doing research as well. X|
Sorry, I meant to reply to the main thread. /ravi "There is always one more bug..." http://www.ravib.com ravib@ravib.com
-
Glad to see someone else is in the same boat. :) I'm following the same path, three tier architecture with the possibility to do either windows or web based forms. The one thing I also need is disconnected user support. In other words, users will be able to take data with them when working in offline mode. Not sure what is the best way to handle this (via windows or web forms) Have you at all looked into a mixture of both. I've been playing with the .net stuff and the new windows forms can do some pretty cool stuff over the web. I'm thinking web based for general UI but Windows forms for dialog boxes and things of the nature. The thing I don't knwo is how will it work if someone is accessing the app from a machine outside the firewall where .net may not be installed. I don't know, still doing research as well. X|
AAAAAAAARGH! :mad: Sorry. (Again) /ravi "There is always one more bug..." http://www.ravib.com ravib@ravib.com
-
I'm in the same boat right now and I'm exploring a three tiered approach where I have the business logic inside of web services. In theory, I can now do an ultra thin web AND Windows Forms based application without having to actually write two applications ... rather, just two different UIs. Obviously, when you're at the office, you can use the pretty application with the better features (I'm tired of the word 'richer') and then on the road you can fire up a web browser and use the web based version. It seems like with .NET, Microsoft is getting pretty close to making web apps behave more like real apps. Of course, you're still missing things like right click menu options and intercepting keystrokes and things that a sophisticated UI provides. For a fairly traditional client/server data driven application, I think you'll find that web apps are going to give you 90% of what you want, which may be good enough. I'm still experimenting myself so perhaps we could trade notes. Give me one more medicated peaceful moment
Sorry Bill, I meant to reply to the main thread. /ravi "There is always one more bug..." http://www.ravib.com ravib@ravib.com
-
I'm working on an intranet based app for mid-sized businesses and was wondering what everyone's thoughts were about building a web UI vs. a Traditional Windows UI. I actually prefer Windows based UI since the client can be much richer, however there are some definite advantages to building web based UI. Specifically the ease of deployment issues (i.e. no client code needed). In looking at the market, many of the companies building solutions for this market are using web based UI. Are there any advantages going with web based other than deployment issues. I find web based UI limiting in some respects. Any insight would be great.
Here's my analysis on the two possible approaches: The Web-based approach Pros: - It's kind of cool (newer technology). - It's easy to deploy and keep up-to-date. Cons: - The UI is not great for complex forms. - It sucks if you have to support multiple browsers, which is not typically the case for an intranet. The Windows-based approach Pros: - It allows for a great UI. - It's usually more responsive since a lot of processing is done client-side. - It can be made easy to deploy if users run it from a common network folder. Cons: - It's not as cool (older technology). - It can be a pain to deploy if every client has to copy/install it to their local machines. This can be avoided by putting it all on one central network folder, and installing an icon (shortcut) that points to it. - It eliminates the ability to one day (maybe) use the application from outside the intranet.
Personally, if I was 100% sure the app would never need to be used outside the intranet, I'd go with the Windows-based approach. The improved UI and overall better performance would make it worthwhile. Regards, Alvaro A priest, a minister and a rabbi walk into a bar. The bartender says, "What is this, a joke?"
-
[ I hope this reply makes it to the main thread. I'm so burned out, I've been making stupid mistakes continuously for the past 10 minutes. I hope I don't drive into a tree on the way home...] An important thing to keep in mind is that web clients are inherently stateless. You have *much* less control over a web client than a standard desktop app. Of course, there are other pros and cons, but be aware of the statelessness, as it has bearing on how you write your backend code. /ravi "There is always one more bug..." http://www.ravib.com ravib@ravib.com
Ravi Bhavnani wrote: An important thing to keep in mind is that web clients are inherently stateless. Is this true anymore ? I am not an expert of web UI (or windows UI for that matter :-) ) Cant we use cookies to achieve stateful behavior ?
-
That is probably true, with a lot of time and work spent. But there is a speed issue which plagues Web solutions. For example it takes almost 30 seconds on my machine to load 4000+ nodes XML tree structure (from the local disk) to IE6. Same task is accomplished in less than a second with Windows Forms and tree control. I just can't see Web UI as a real life solution. Regards, Dejan Petrovic
Dejan - Something is wrong, 30 seconds is toooo much. Are u using the IE to directly open an XML document or do you have some VBScript ? Vivek
-
[ I hope this reply makes it to the main thread. I'm so burned out, I've been making stupid mistakes continuously for the past 10 minutes. I hope I don't drive into a tree on the way home...] An important thing to keep in mind is that web clients are inherently stateless. You have *much* less control over a web client than a standard desktop app. Of course, there are other pros and cons, but be aware of the statelessness, as it has bearing on how you write your backend code. /ravi "There is always one more bug..." http://www.ravib.com ravib@ravib.com
Ravi Bhavnani wrote: [ I hope this reply makes it to the main thread. I'm so burned out, I've been making stupid mistakes continuously for the past 10 minutes. I hope I don't drive into a tree on the way home...] I really thought the creator of the great Spell-O-Matic would not have problems like this. :-) Maybe you could create a Post-A-Matic Regardz Colin J Davies
Sonork ID 100.9197:Colin Logic merely enables one to be wrong with authority. -- Doctor Who 28 th Law of Computing: Anything that can go wr# Segmentation violation -- Core dumped