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

Component-specific fields are not available #35

Open
DarkmatterVale opened this issue Apr 4, 2016 · 3 comments
Open

Component-specific fields are not available #35

DarkmatterVale opened this issue Apr 4, 2016 · 3 comments

Comments

@DarkmatterVale
Copy link
Owner

For example, if a component test is a graphics card, a section for "Display information" will be needed.

@DarkmatterVale
Copy link
Owner Author

To solve this, without javascript, I think we have 2 possible solutions:

  1. Create a page for every kind of accessory/component...this is a lot of work and I don't want to do this but if it is required then I will do it
  2. Add a text area which contains other details that the author can provide information in

@humdingerb what do you think?

@humdingerb
Copy link

I don't think 2) is a good solution. It lacks any guiding structure and will make analysing the data difficult.
Generally, I can imagine that building the "System test" from items of the "Component test" would be rather elegant. Users could even be able to add/remove certain components specific to their system. Of course, I have no idea how to implement that... :) Maybe you'd need JS after all. I don't see the problem with using JS for a web service.

@DarkmatterVale
Copy link
Owner Author

That could definitely be done (and sounds like a great idea). I will look into doing that and add some more information here when I have a more specific answer.

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