Skip to content

Latest commit

 

History

History
44 lines (37 loc) · 2.83 KB

ROADMAP.md

File metadata and controls

44 lines (37 loc) · 2.83 KB

ROADMAP

This is an attempt to a high-level "roadmap" (or wishlist :-)) for IrScrutinizer. The "low-level" issues are kept as issues.

Vocabulary

  • IrScrutinizer denotes the interactive program, and the source packages org.harctoolbox.irscrutinizer and subordinate packages,
  • IrpTransmogrifier is this project, that has replaced IrpMaster, DecodeIR, Analyzer, and much more,
  • HarcHardware denotes a collection of "drivers" and other software that accesses hardware more or less directly, source package org.harctoolbox.harchardware and subordinate packages,

Demarkation (what not to do (here!))

IrScrutinizer is a program for the interactive collection, analysis, editing and transformations of IR data, and the sending of test signals. It should stay that way (cf. Zawinski's law of software envelopment). It should not be turned into a daemon or a production program for sending or receiving IR signals. (This is not to say that I do not care about these use cases, see Girs, and the projects JGirs, AGirs, dispatcher. Also note that HarcHardware is intended to be useful for those use cases.)

2. An advanced "abstract remote" editor.

(By "abstract remote" I mean a collection of IR commands with (unique) names, but with no assignment of the commands to buttons on a physical remote.) This covers the issues #89, #88, #87, #86, #85, #73, #72, #71, #52, #48.

6. Documentation system

See #15. The article on the web site should be a "cool" article, not a "dry" reference manual.

-1. Internationalization

This is not at all an important issue for me, at least not for the moment. (Despite being Swedish native speaker, and speaking German at work.) Sometimes, however, that day may come. For the immediate future, no internationalization is planned.