MensBeam/Arsse

More driver metadata #34

New issue

Closed

opened 2017-02-10 07:28:43 -05:00 by jking · 1 comment

jking commented

2017-02-10 07:28:43 -05:00

Owner

Drivers (be they for databases, user management, or some future function) should have a getInfo method which not only returns a human-readable name, but also a long-form description and possibly machine-readable data suitable for constructing a configuration form.

This way any driver (including third-party ones) could participate equally in installation and reconfiguration without any need to edit the process.

Drivers (be they for databases, user management, or some future function) should have a getInfo method which not only returns a human-readable name, but also a long-form description and possibly machine-readable data suitable for constructing a configuration form. This way any driver (including third-party ones) could participate equally in installation and reconfiguration without any need to edit the process.

jking added the

label

2019-12-02 07:28:52 -05:00

jking commented

2019-12-02 07:29:55 -05:00

Author

Owner

At this point the trend is toward less metadata, and a Web-based installer is unlikely to ever happen.

At this point the trend is toward less metadata, and a Web-based installer is unlikely to ever happen.

jking closed this issue

2019-12-02 07:29:55 -05:00

Sign in to join this conversation.

No labels

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: MensBeam/Arsse#34

No description provided.