What layer generates commands for dependent services?
Our business works with truck drivers making pickups/deliveries of containers. The location of containers needs to be tracked.
Does Separation of Concerns applies to GUI components?
In an application I developed with C#, I use a webbrowser control, it should navigate to some websites, then I would like to extract some contents from the webpages. I do it by manipulation of DOM and removing some nodes. It can be done automatically or manually with the help of user.
Does Separation of Concerns applies to GUI components?
In an application I developed with C#, I use a webbrowser control, it should navigate to some websites, then I would like to extract some contents from the webpages. I do it by manipulation of DOM and removing some nodes. It can be done automatically or manually with the help of user.
Does Separation of Concerns applies to GUI components?
In an application I developed with C#, I use a webbrowser control, it should navigate to some websites, then I would like to extract some contents from the webpages. I do it by manipulation of DOM and removing some nodes. It can be done automatically or manually with the help of user.
How can I create a model to efficiently answer the question of – where to place my db-interaction code I am about to write?
I am seeking the right model for storing and retrieving data, when working with any specific class, while keeping in mind the bigger picture.
Sense user-agent to determine HTML – Keep HTML and Logic separate?
I am of-the-understanding that you should try to keep HTML out of your logic, and keep logic out of your HTML. E.G.: You don’t write HTML in (C# strings or Javascript Services) and pass them into the View or DOM. Likewise, you don’t write classic ASP anymore (and I personally limit/nill Razor). HTML is for HTML, Services are for Logic. My question is based on this best-practice. Of course there are small rare one-off’s. Counter E.G.: Razor fans use the HTML Extensions class. But Razor is its own beast.
Refactoring long methods with a lot of cyclomatic complexity
I’m attempting to refactor what is becoming a very large method — currently 350 or so lines — that contains a high degree of cyclomatic complexity.
Refactoring Processor classes
I am writing some python 3 bioinformatics software and was wondering about the best way to write it in an OOP format. I am pretty sure a lot of my classes are violating the SRP principle, but I’m not entirely sure of how to refactor them (partly because they are quite small).
How to do “Separation of concerns”
I understood(edit: I assume) the importance of seperation of concerns and benifits in an application, But struggling to identify what are considered to be a concern (developer, feature, consumer or what ?).