▲ ▼ Visual generator for repetitive code structures
What so you think about the current way of starting new code projects?
The current way would be the use of the different framework-CLIs and copy-pasting everything together or starting with a GitHub Starter.
But instead of doing so and then adjusting everything for your current problems domain, what so you think of a visual configuration of data structures and simple ui-wireframes, which will be translated into real code files by adjustable templates. The results must be syncable.
Would you like to use something Like this?
Register to comment or vote on this problem
Voted!
Need karma! Please check contributor guidelines.
>The current way would be the use of the different framework-CLIs and copy-pasting everything together or starting with a GitHub Starter.
Can you tell me what is problem you face because of it?
It's so rarely project contexted. I am thinking about creating an app which does the same, as the clis, but puts a level of project specific code on that, e.g. interfaces, services, tables or whatsonot
Sorry, still unable to understand what you mean by 'rarely project contexted'.
I understand that you want to create a visual tool to create projects, may be it will create some boilerplate code inside with it? But, unless you are able define what problem it solves clearly it could be a tough sell.
Sorry, with "rarely project-contextet", I mean these cli boilerplates usually don't habe that much "inner content" for the current project, and I think it might be possible to change that
Surely, it saves development time, spares nerves, secures clean code and solves the miscommunication of project requirements.
But I wanted to know if developers would want to use something like this in their dev cycle
I guess you're telling about a combination of GUI Git clients like Git Tower (Which does everything a CLI SVN does visually) + IDE like features to generate project files with boilerplate code. SVN like Git are by design project agnostic i.e. if there was a 'context' like you mentioned, then behaviours needs to changed depending upon type of files, programming language, framework etc.
You might be interested in checking out this need gap - https://needgap.com/problems/84-simple-cli-for-cloud-deployments.-cloud-devops, that user wants kind of opposite to what's being discussed here.