-
Notifications
You must be signed in to change notification settings - Fork 43
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
Support irplus codefile Import #321
Comments
This a reasonable request, and it is the right place! I have been planning to add extensible import formats for a long time. (Still to write the issue...) This should be basically a pre-processor -- an XSLT transformation -- that on the fly makes a Girr file out of the user's file. Recall, the export format are basically just XSLT transformations that makes a Girr file (in memory, as DOM, not on disk) into the user's format. So what I would recommend you to do is to write an XSLT script that makes a Girr file from an irplus file with raw or Pronto signals. In the first step, you can then use that to convert your irplus files to Girr, and then import them. If/when I implement the preprocessor import, I will be happy to include your script. (You can also write an XSLT scipt that makes Lirc files out of the example above. But I am less inclined to incorporate a Lirc preprocessor.) XSLT is reasonably easy to learn, and there are tons of books and support on the internet. For examples, see the export formats of IrScrutinizer. (Please use XSLT version 1 if you intend to later have it run within IrScrutinizer.) |
Sorry, I will not accept a fix like that. There are already too much clutter on the import pane. The proposed solution #322 has several advantages, one of them is that a discussion over the importance of a format is not necessary any more. |
recieve.txt @bengtmartensson What is the recommended way to import unsupported file types now in 2023? Is it still to use the text/CSV import? Thanks!
|
@sdaly31: What format is this? format="UEI_LG_LEARNED" is not something that is generally understood, and thus not suitable as an export format. Please try to use pronto hex.
Try to write an input filer that transforms the input format to Girr. Either as an XSLT script (see earlier in this thread) or as a shell script that reads stdin and writes stdout. That way you can easily transform your input to Girr, which is the native format of IrScrutinizer. A later version may support involing the transformer automatically, see #322. |
EDIT: SORRY i wanted to post this in irscrutinizer - Oh not so wrong after all? i thought "harctoolboxbundle" was something else :P
Hey, could you help me to implement import for irplus file? This would help me a lot with database maintenance. Currently i do it manually using the txt import.
What needs to be done to add a new Tab within "Import" like LIRC ?
Basically what needs to be done is:
NOTE: I've created this issue for when you have time to help, so i'm just asking kindly that one day in future it might be supported ;-) I'd like to help out as well, but i have not been able to build irScrutinizer myself.. Its seems so complicated to get it built. I had a lot of maven errors
Just one file for reference:
The text was updated successfully, but these errors were encountered: