Opportunity to leave features for expansions #8

Closed
opened 2025-04-09 15:00:05 +00:00 by tcsenpai · 0 comments
Owner

Originally created by @JanNeuendorf on 12/27/2024

Now that the expansion mechanism has been fixed and implemented, there is an opportunity to remove features from the spec. Those could then be restored using expansions if needed.

There are not many candidates for that.

The screen is too essential. Without any output, the system is useless.

That leaves one of the two inputs. Removing the button-input would leave only the mouse (without clicking).
This is probably not usable on its own and I want the system to be usable without the use of expansions.

The remaining option would be to leave only the NES inputs as core functionality with the idea that a mouse could be added as an expansion. This would, of course, be a drastic change. It would remove functionality that is already documented and implemented and it would break the demo-programs. There would be three benefits to that

  1. It makes everything a little bit simpler to explain.
  2. It solves the awkward problem that we can not say if there is an external cursor or not.
  3. There would be a single default input-scheme
*Originally created by @JanNeuendorf on 12/27/2024* Now that the _expansion mechanism_ has been fixed and implemented, there is an opportunity to remove features from the spec. Those could then be restored using expansions if needed. There are not many candidates for that. The screen is too essential. Without any output, the system is useless. That leaves one of the two inputs. Removing the button-input would leave only the mouse (without clicking). This is probably not usable on its own and I want the system to be usable without the use of expansions. The remaining option would be to leave only the NES inputs as core functionality with the idea that a mouse could be added as an expansion. This would, of course, be a drastic change. It would remove functionality that is already documented and implemented and it would break the demo-programs. There would be three benefits to that 1. It makes everything a little bit simpler to explain. 2. It solves the awkward problem that we can not say if there is an external cursor or not. 3. There would be a single default input-scheme
Sign in to join this conversation.
No Label
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github/SVC16#8
No description provided.