presentation-layer

Presentation Design Patterns

可紊 提交于 2020-01-07 04:37:22
问题 I've been studying and working with presentation design patterns for a while, and i have successfully impleneted design patterns like FrontController , MVP etc. for WebApps , and of course the MVC pattern and the ASP.NET MVC framework which is a great choice. however, i was wondering if using a presentation pattern like MVP would be a good choice for WinForms applications. if the answer is yes then great, if not and/or there are pitfalls to be aware of it would be great if you could explain

drawbacks for implementing presentation layer inside data layer

夙愿已清 提交于 2019-12-25 02:09:49
问题 whats the drawback in implementing the presentation layer inside data layer. i guess that would be much dynamic and performance oriented way to go for, for example if i compile to code (i mean full compile where even aspx is compiled) and after that i need to make some design changes, i dont need to update of compiled library i can make the changes directly here. Please correct me if i am wrong. Here's the link where someone posted it as a drawback. 回答1: haven't logged-in for a while or i'd

How best to implement support for multiple devices in a web application

荒凉一梦 提交于 2019-12-11 17:52:32
问题 My client would like a business application to support 'every possible device'. The application in question is essentially a web application and 'every possible device', I believe encompasses mobile phones, netbooks, ipad, other browser supporting devices, etc. The application is somewhat complex w.r.t. the data it captures and other functions it performs (reporting). If I continue to honor increasing complexity in the application, I guess there are more chances of it not working on other

Presentation technology for multiple devices

会有一股神秘感。 提交于 2019-12-07 13:20:21
问题 Our application is supposed to serve multiple devices, from simple to smart-phones, IPhones, touch-screens to normal browsers. Application is layered, so we can reuse the business and persistence layer. However, we would like to program single presentation layer as well. I know for example that ASP .NET generates different html output based on the browser type. http://msdn.microsoft.com/en-us/library/ms178620.aspx There are even some sites that promise to transform your site to mobile: http:/

Pros and Cons of Various Java Web Presentation Layer Technologies

前提是你 提交于 2019-11-28 05:59:13
I'm currently working on a web app that makes heavy use of JSF and IceFaces. We've had some discussions of moving to another presentation layer, and I thought I'd take the discussion out into SO and see what the experts think. I'm curious if anyone could weigh in on the pros and cons of the various Java presentation layer technologies. If you've only worked with one, say why you love it or hate it. If you've worked with several, give your impressions of how they stack up against each other. Our technologies under consideration are: IceFaces JSF (without IceFaces) GWT (Google Web Toolkit)

Why should I isolate my domain entities from my presentation layer?

牧云@^-^@ 提交于 2019-11-27 10:02:06
One part of domain-driven design that there doesn't seem to be a lot of detail on, is how and why you should isolate your domain model from your interface. I'm trying to convince my colleagues that this is a good practice, but I don't seem to be making much headway... They use domain entities where ever they please in the presentation and interface layers. When I argue to them that they should be using display models or DTOs to insulate the Domain layer from the interface layer, they counter that they don't see the business value in doing something like that, because now you have a UI object

Pros and Cons of Various Java Web Presentation Layer Technologies

人盡茶涼 提交于 2019-11-27 01:13:04
问题 I'm currently working on a web app that makes heavy use of JSF and IceFaces. We've had some discussions of moving to another presentation layer, and I thought I'd take the discussion out into SO and see what the experts think. I'm curious if anyone could weigh in on the pros and cons of the various Java presentation layer technologies. If you've only worked with one, say why you love it or hate it. If you've worked with several, give your impressions of how they stack up against each other.

Why should I isolate my domain entities from my presentation layer?

寵の児 提交于 2019-11-26 14:59:49
问题 One part of domain-driven design that there doesn't seem to be a lot of detail on, is how and why you should isolate your domain model from your interface. I'm trying to convince my colleagues that this is a good practice, but I don't seem to be making much headway... They use domain entities where ever they please in the presentation and interface layers. When I argue to them that they should be using display models or DTOs to insulate the Domain layer from the interface layer, they counter