China DOS Union

Is it necessary to make a batch processing interface?

[ Last edited by czl1378 on 2009-7-10 at 09:52 ]

I am a selfish and stingy person, and what I chose is not right

I think the interface is always empty. Just write a script to complete the core functions you want. Considering the interface is just a waste of time and energy.

As for what the landlord wants to do, it is whatever, there is nothing right or wrong
HOHO

I see that YISHANJU has been paying more attention to my post. Thanks for your vote. There's no such thing as self - ish or not. When I made a vote, I definitely wanted to see the real result. If those who choose "shouldn't" are considered selfish, then it's meaningless, right? To be honest, I'm in an uncertain state now.

Misunderstanding, misunderstanding. I've been hanging out on the forum recently with nothing to do. I reply to new posts when I have nothing to do. The choice shouldn't be only for oneself, choosing only for oneself.
Phew

Could it be that one should still choose for others? Well, does it mean that?

[Uncertain]
Of course, the more beautiful the better, but if too many resources or time are spent for a better interface, it should not be.
If the batch processing done is for personal use, it depends on personal preference!

Not sure. Practical is fine, the interface is good-looking, but it will occupy system resources, and instead it is not worth the cost.

When your batch processing level can solve most of the problems in this section, then consider the so-called interface.

Obviously a CLI, it's better to stay away from GUI...

A practical attitude: should not be too fancy, spend more time to make the functions stronger and bigger
For the sake of showing off: want to have as many PLs as possible, in fact, making a good interface also has quite a lot of technical content

Those who can use search and lurk are not bad.

As for if you really want to touch the essence of cmd to modify the interface, technology is very important.

The third option is better changed to "depending on the situation". Generally, the batch scripts I write are all without an interface, and they run and complete when double-clicked. Because batch scripts generally don't need interaction, at most files or directories are dragged and dropped onto the batch icon, and even then, an interface isn't needed. For example, batch - made games that need an interface, of course, the more beautiful the better. If interaction is really unavoidable, then we need to consider the readability and maintainability of the interface - related code. The beauty of the interface is secondary, as long as it is neat enough to understand.

CMD is a free world, you can do what you want to do