Skip to content
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

Open
janbrohl opened this issue Jun 1, 2016 · 6 comments
Open

Use .version file to populate fields? #34

janbrohl opened this issue Jun 1, 2016 · 6 comments

Comments

@janbrohl
Copy link
Collaborator

janbrohl commented Jun 1, 2016

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.

@janbrohl janbrohl changed the title Use .version file to populate fields Use .version file to populate fields? Jun 1, 2016
@politas
Copy link
Member

politas commented Jun 1, 2016

That's a good idea

@janbrohl
Copy link
Collaborator Author

janbrohl commented Jun 1, 2016

Not as simple as i thought. Coding should not be hard but how to integrate in the user's workflow?

@politas
Copy link
Member

politas commented Jun 1, 2016

List the discovered details with checkboxes and a "use these" button?

@janbrohl
Copy link
Collaborator Author

janbrohl commented Jun 1, 2016

Where to put the input-area? That's the main problem for me.

@politas
Copy link
Member

politas commented Jun 2, 2016

In a separate pulldown section that only appears after the user selects to use a vref?

@janbrohl
Copy link
Collaborator Author

janbrohl commented Jun 2, 2016

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants