[M O D E R N]

Looking for the right direction to material for AV scanning. Currently been working on my UI



Ideally I wanted to replicate features that JRT has since that is getting discontinued (https://www.malwarebytes.com/junkwareremovaltool/)

[gigajew]

I like the idea and the icon

[EZLib]

Hey this is a cool idea!

I'm kinda doing the same, but in a different way.
https://github.com/developer-variety/Anti-Logger

[cocaine_monkey]

I wonder how does it detect adware? hardcoded database?

[chrizator]

That looks like an interesting project. UI is nice so far. I wonder if you acutally want to dig into heuristic analysis. Would be very interesting! 👍

[Zephyros]

Dont write a GUI for a desktop app, write a webservice.

[Washi]

Don't bother with the UI for now. The engine is way more important. Do you have any plans for that already?

[Ninja]

Don't bother with the UI for now. The engine is way more important. Do you have any plans for that already?

You should know that on any skid infested 'hacking' forums the UI makes the program 10x better and more expensive, right?

[M O D E R N]

This more of a personal project for my own use. I have a thing for UIs so that is why I started there.

The plan is for it to do the following:
-Portable
-Automatic PUP cleanup
-Automatic cleanup of adware (like conduit, coupon, etc.. type shit)
-Get rid of unwanted toolbars
-Check and cleanup browser extensions/addons
-Behavior monitor (like cyber reason's ransomfree)
-Sig Verification (like how process explorer does)
-Heuristic scans (need to figure out database stuff for this)

[0xDEAD10CC]

Don't bother with the UI for now. The engine is way more important. Do you have any plans for that already?

Exactly, a lot of people don't understand that you build a UI around the functionality that you are providing. If you try to use a UI to match functionality that you haven't even built yet it doesn't work that way. I always build my class libraries first and write basic form stuff or console applications to test it out.

So I really don't see much point for this thread quite yet. There's really nothing built yet and this isn't a GDI or WPF theme thread.

[Ninja]

Exactly, a lot of people don't understand that you build a UI around the functionality that you are providing. If you try to use a UI to match functionality that you haven't even built yet it doesn't work that way.

If it is a small application and you wrote down your requirements then it is fine. Especially for a beginner.

---

I always build my class libraries first and write basic form stuff or console applications to test it out.

No unit tests? :(

[0xDEAD10CC]

If it is a small application and you wrote down your requirements then it is fine. Especially for a beginner.

---

No unit tests? :(

Unit testing is usually for portions of code that needs to fit a certain requirement. I just use a console application from a higher level perspective sometimes to just test out functionality as a whole when I'm not testing code units to see if they are fit for production. Either way, GUI is last priority. Unless he enjoys doing things differently for example, people don't start by building a car from the looks, they usually have the engine engineered first because the design of the car itself needs to accommodate this core piece. This thread seems like a ploy for the coolness factor and perhaps to gain some hype about a product that isn't going to be released anytime soon anyways, and the only thing likely to stay in that GUI are probably exactly what is seen in the image and not much more.

[Cecilia]

Unit testing is usually for portions of code that needs to fit a certain requirement. I just use a console application from a higher level perspective sometimes to just test out functionality as a whole when I'm not testing code units to see if they are fit for production. Either way, GUI is last priority. Unless he enjoys doing things differently for example, people don't start by building a car from the looks, they usually have the engine engineered first because the design of the car itself needs to accommodate this core piece. This thread seems like a ploy for the coolness factor and perhaps to gain some hype about a product that isn't going to be released anytime soon anyways, and the only thing likely to stay in that GUI are probably exactly what is seen in the image and not much more.

I agree with this statement.
I always build the backend as a console app and then either add the ui, or turn the console app into a dll.

[Ninja]

Unit testing is usually for portions of code that needs to fit a certain requirement. I just use a console application from a higher level perspective sometimes to just test out functionality as a whole when I'm not testing code units to see if they are fit for production. Either way, GUI is last priority. Unless he enjoys doing things differently for example, people don't start by building a car from the looks, they usually have the engine engineered first because the design of the car itself needs to accommodate this core piece. This thread seems like a ploy for the coolness factor and perhaps to gain some hype about a product that isn't going to be released anytime soon anyways, and the only thing likely to stay in that GUI are probably exactly what is seen in the image and not much more.

Agreed, but for a beginner who learns on his own it is fine. He will understand eventually if he gets more proficient.

---

Unit testing is usually for portions of code that needs to fit a certain requirement.

Unit testing is just to test your code. It is a nice way to check it even. I prefer unit testing over a console app any time. With a console app you have to edit the code a bit every time, catch exceptions, etc. With unit tests you write the test and you can select the test(s) you want to run, set up initialization, run the tests, exceptions are caught for you and displayed, and you can assert multiple conditions easily. You can even make a test expect a certain exception to be thrown. It is just easier than a console application, and more convenient.

But I partially agree, for somethings like the database handling and client-server connections you don't write unit tests or you use mock classes/data.

[M O D E R N]

Everyone is missing that I have said this is for my personal use, nothing is going to be sold...