4 ms·
I have something similar I use in Visual Studio - it's a module file full of useful functions, that saves me rewriting the same code over and over again for eac
by Jaruzel 7y ago
I have something similar I use in Visual Studio - it's a module file full of useful functions, that saves me rewriting the same code over and over again for each new app.
For example, I have GetFile() and SaveFile() functions which I use ALL the time, also as I'm on windows, I've wrapped up a bunch of Registry code into nice 'SaveRegValue' and 'GetRegValue' functions.
All in all there's about 50 or so functions in the module. Personally, I thought every coder did this?
Edit: I'm not dissing the OP, just surprised that there's value in sharing these things.
- masklinn 7y agoThat seems to be a very different thing. You’re talking about a utils file / module you’re carrying around, OP is about a ready-made application template (à la cookicutter).
- close04 7y agoConceptually they feel like the same thing. They are a reusable foundation on which to build more.
- tasogare 7y agoDid you read the article? It mentions "Two helper classes that make building a typical macOS source list easy." which is exactly what OP is talking about. So helpers classes, while not being all the project presented here, are an important part of it.
- masklinn 7y ago> Did you read the article? I'm wondering if you did. > It mentions "Two helper classes that make building a typical macOS source list easy." TFA goes much further than that, it's an actual working application in a box. You can copy the template, build it, and it runs. A template can include utilities, not the other way around. > So helpers classes, while not being all the project presented here, are an important part of it. They're an important but relatively minor sub-set of the whole.