Tag Info

New answers tagged

6

Command Pattern is generally used to decouple WHAT from WHO, and WHAT from WHEN. This is the benefit of having a simple interface as simple as: public abstract class Command { public abstract void execute(); } Lets imagine that you have a class EngineOnCommand. You can pass this Command to other objects which accept instances of Command. So this means ...


2

Most of the benefit of commands is that they make it easy to undo an action, redo an action, perform an action in multiple places (over a network connection), or perform it at a later date, and so on. With that in mind: Probably not. It's hard to imagine any situation where "undoing" a dialog box makes sense, and this is the sort of thing I'd rather put ...


0

You can potentially mix 1 and 2 but create less work in the process. I would initially build your query logic on the assumption that all requests would be of the form "show all documents published on all websites" and then extend it to support filtering by tags (adding parameters to queries is easier than taking them away). You'd achieve this by simply ...


11

I'll give you some tips, regarding CRUD applications, since I don't have much experience in games or graphically intensive apps: Business logic usually involves rules the owner of the business has learned or decided over years of operation, like for example: "reject any new credit if the client hasn't yet finished paying the last one", or "we don't sell ...


4

It sounds like most of your work may be in the UI layer. Changing the display format for business reasons, does not imply any business logic. The change is a change to the view logic. Being able to change the format implies some business logic possibly involving persistence of the preference. Persisting the format to a cookie, could also be implemented ...



Top 50 recent answers are included