-
-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use .version file to populate fields? #34
Comments
That's a good idea |
Not as simple as i thought. Coding should not be hard but how to integrate in the user's workflow? |
List the discovered details with checkboxes and a "use these" button? |
Where to put the input-area? That's the main problem for me. |
In a separate pulldown section that only appears after the user selects to use a vref? |
After thinking about layouting for a while and seein what can be auto-generated i think a solution with multiple seperate pages would be the best solution. See #35 |
As said in KSP-CKAN/CKAN/issues/1765 there are some fields in .version files that are not extracted by netkan. It would be simple to do this in the form.
From an input field the user copies the file's contents into would be the simplest solution.
Analyzing a zip and letting the user decide which .version file to use would also be an option, too.
The text was updated successfully, but these errors were encountered: