The original keyjnote developer was threatened with legal action from Apple, Inc. over trademark infringement. Since then, the Sourceforge page has been removed and the original package is nowhere to be found. Taking the code from the Gentoo ebuild, I implemented some patches to implement LIRC remote support and fade-to-black after last page. I sent these patches to the developer, but I haven't heard anything from him for weeks. He said he would bring the page back up at some point, but it's been about 3 months, and I'm starting to think the project is fairly dead. In the meantime, I made my patched version available under the name Accentuate. I filed this bug in case someone was interested in making an ebuild from my version, maybe under the same ebuild as keyjnote. Check it out here: www.cs.rit.edu/~jrm8005/accentuate.html Reproducible: Always Steps to Reproduce: 1. Try to download keyjnote from outside the gentoo repos 2. ??? 3. No profit.
Created attachment 164212 [details] new ebuild initial ebuild for accentuate
There are some unfortunate things with this 1. The splash screen still says keyjnote... not good 2. There should be a possibility to run this without having to install pylirc and related tools something like try: import pylirc pylirc_enabled = true except: pylirc_enabled = false because there are some really nasty errors when lirc is not running on the machine!
> 1. The splash screen still says keyjnote... not good Oh definitely not. I just haven't been able to get the right PNG file converted to a string (can't be interlaced) I tried all day yesterday, but I must not have the tools I need. I'm not good at graphics editing :-\ > 2. There should be a possibility to run this without having to install pylirc I can definitely do this. That was my initial patch and just scratched an itch for me. Now that I'm maintaining it for real, I'll give it some polish I'll get back in a couple hours with the 2nd change. As for the first, I'm not sure if I can get it done today. If anyone can make a patch that changes the "keyjnote" string to "Accentuate" in the PNG file, I'll gladly take it. Thanks!
I've updated the version on my website; it should no longer barf when LIRC support is missing.
Nice, I can see that you have updated so its not nessesary to have pylirc to run. But could you create versioned releases of accentuate ?? like accentuate-0.99.0 accentuate-0.99.1 and so on.... Secondly the image is easy to create!! actually... LOGO = '\x89PNG\r\n\x1a\n\x00\x00\x00\rIHDR\x00\x00\x01\x00\x00\x00\x00@\x08\x00\x00\x00\x00\xd06\xf6b\x00\x00\x00\x01sRGB\x00\xae\xce\x1c\xe9\x00\x00\x00\tpHYs\x00\x00\x0b\x13\x00\x00\x0b\x13\x01\x00\x9a\x9c\x18\x00\x00\x00\x07tIME\x07\xd8\t\x01\x0e/"J\xf7eu\x00\x00\x00\x19tEXtComment\x00Created with GIMPW\x81\x0e\x17\x00\x00\x05TIDATx\xda\xedXkL\\E\x18=\xfb\xa0\xbc\x16\x02\x94W\xdd"4\x88\x8d\x85\xb6P\x8b\xa9\xa6\xb5)-\x11\xaa\xa8\xa4\xc4TcR\x1a\xb1\xb1j4b\x8dFS\x03\xd6\x1a\xa3&Jl\xac\xb1\xc1\xbe\xb4\xbe\xfda1\xd1\xa8\xd8\x07M\x9a`\x81D\xc4\x18\x0cH\x1f\xb6\xa6\xa5\xd8\x07\xec\x02\xdd\xbd\xfe\xf8\x06v\xe6\xee\x9d\xb9+\x90\xf4\xc7\xce\xf9\xb3\xf3\x9do\xeew\xcf=\xf7\xee\xbc\x00\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\r\x8d(\xc6rc\x02\xcb\xa3\xe6\x99\x9d|\xb0q\xb2U{]\xc40\xf7\xaf[\xa5\xc4+\x93_\xc0\xe5\x84h1\x80\xff\x02j<\x93\xcd\xa4\x9ah\x1c\x02~6Bh\x8d\xc2\xbf\xc0\xbc g@0/J\x0cp\x87\x9a\xb5\x0e\x00\x80/\x1e\x00\x1c\xb5\r\xa6\x9eq\x95\xe5\xc5\xb9i\xb3\xfc\x83\xa7\xba\xdb[\xfb\xec\xf9\x8c\xeaU\x0b\xbd\x9e\xe0`\xef\xb1/:\xad\xee\xec}\xac\xf2\xe6\x84\xa1\x9eov]\x9e\xfas\xban[\xb3t~\xb6\xc7\x18\xb9\xd0\xd7\xf9Ck\xc0\xb6\xbfR\x93\xa3\x9f\\\xdbL?}\x0e!\x9b\xd0p\x91\xfb>\x0c[>c\xa7\x9f\xfb?-\x0c\x7f5[|\xacyn\xa5\x90\x11k\x99\xca\x8a\xe1\x92\xf7\x84{\x9f\xdc\x08E%\x85&\x862J\xf4\xa2\x87\x1a\xab\xf8\xe4\xa2?-KJ\xf9\x95\xff\x08\xb4\x7f\x83\xe9\x11\x9c{C\xc9\x91[\xa7h@\xd8\x15\xfb\x9c*\x03\xa4\x9a\x18\xf6\x13\xdf\x80\x17Y5.Wz\xc9\xdaS\x19_\xe67k\xd8 \x8a\xde\xc1\xe7\xba\x1c3d\x80\xb1Ua\x80\\\x13\x9b\xf8\x86\x89\xbd\ty4\x18\x0e\'\x85\xbe\xe7\xbf\xad=\x95\xf1\xde\xc10\r\xfe"\x99h\xc30*f\xca\x00_\x96\xb4\x92B\x13\xa1\x8e\xc8\xe3\x00\xda\xa8\xf9\xc8d\xae\x99]qakq\xb2\xcb{\xffG\xa3\x86\x9a?\xc0\xbe\xed\xc6[b\x93\xd7vP\xf0\x93I\xf4\x9e\xe2\xb8\xdcwX\xfb}\x1b\x03\x822\x03\xba\xb7\xdf\x9d\x9f\xe8\x8c\xf5\xae\xde9N\x99zi%\x85&\xc21\xe2\x9e\x04\xc0\x86\xc1\xb6\x89\xd4\\V\xbd#\x9b\x119_*\xf9\xbc\x00\x19\xbc\x0c\x00\x10\xdfN\xbd\x8a\x05\x03\x1ay\x07OH\'/"\xaeY\x1b\xf0\xdd\xed\xdc*\x9e2\xdf\xca*\xa94\x01\x00\n\x88\x19\xcf\x000{\x8c\x82\x02\x96\xab\xa7\xf0\xdf\xb9\xa6QC\xc6?G\xfc\x1b,,\xa7\xf0U^Y\x8f\x0b\x00\xb0\x82\xa2A\x1b\x03\xc6\xed\xa7\xf78\xca\xf4\xcb:\xaa4\x01\x00^\xe3\x1d<H\xc1v\x96c\xe1\xeb\xe6\x9b\xca\xf8\x16\xe2K&\xb6\x18\x14\x1e\xe2\x95\xd5Sj\x8e\xf8\x86e\x06\x8c\xc9\x0c\xc8~t\xf7\xf13\xc3\x01nF\x91URi\x02\x00\xe7ib\x1e\x04\x00\xac\xa7\xe0\x14\xdb(\xf4Qx\x87\xf9Ae|\xbf\xe5Hw\x86W\xb6T\xd0a\xd8\x18\xe0\xb76\xc0\xfb\xf15\xf3M\x82\xb2J*M\x00P!l\x02\x13\xd8\xb6\xf0.J\x8eP\x94j~P\x1b\xde<\xe6\xf2\xcaR\xd8:t:\x06\x14\x9f\xb7\xb8\x8b\xac\x92J\x13\x00|J\xc4^\x16\xee\xa3\xf0\x13\x8a\xd8\x1e\xc1m~P\x1b\xdeR\x1bk\xbb\xd8\xeas\x1a\x06$\x0e\x18\xff\xc3\x00\x95&\x00\xa9~\xcb\xb4/e\x06\xbf\x00\x03\x91N\xec\xd2A\xd0\xc3wx\x86\xda\x81\xa6\xd2\xa4\x08*\x8d\xa8\rx\xdc:ml\x9e\xce\x18\x90\x11\xc16-2\x03\x0c6\x18\xcd\xe7;\x1c\x16\x86\xd3d\x9bJRMN\xe5\t\x18\xf1\xbfQPe\xce\xca\xf8\xdf\xd9\t\xe3Llk\xe9\x87\r\x19\x82\xd5l\x19\xf7!\x1b\x10l\n\xa95\x15\x1a2,\x00\x80g\xa9=t\x83\xe92\x19\xff\xbc\xc5\x99J\xc1\xc1\x08\xbe\x80\x80\xf0\xbe\x01\x80\x8d\xc6\xa5\x14\xb5\xf1\xddY\xe7Da\xf1)\xad\xa4\xd2\x04\xbc%5\xe0M~\xc5\xd7\x9e\xc9\xfag}\x0e\x15?\x8f\xdd\xfe\x95\xd0\xdbj\x1e7"0\x80m\xad\xf2C\x1a\xd9\xce\xf4m\x00\xc0\x13\xc2?\xf7*\xb5\x1f\x02\x00<l\xd8TRi\x82\xfb\x1c%\xeb\xf8\x8f\x9f\xa8\xb3.\x00\xd8\xcd\xaa\x9f\x7fi\xb1\xc7\x95]\xf1\xc1\x08\xbbR\xc6\x7f\xc6\xf8#\xebsf\xc5xW\xbf\xdc\x1e\x92\xa64\xe0\x0f\x8aZ\x8ab!NG\xc1m\xde\xd8\xc2w\x03\xc2S\x9e\xa0\xf6\xa5M\xe91\x0b\x9a\x02\x86]%\x85&T\xb1\xf14\x933 \x9d\xad1\xee\x01\x80\xcc\xb3\xd6\xa3\xa7\x8c\xcf\xb9(\x1dp\x95\x06\x1c\x08\xbb\xa0F>v7\xaa\x86\xf5\xf0J\nM\xf8\xda\xb4\xf9\x01\x00\x1c!\xf2+\x00\xc0\xb2+\xd6W\xca\xf8r\xff\x94\x0cx \xec\x02\xb7p\xe0\xb2\x83\xef\x9e%\x9cE\xec\xb1\xab\xa4\xd0\x94\xce\xf6>[\xacv:\xa3\xb3\x01\x00%}\xd6\xf3\xa7\x8c\xbf\xd3\xfcmtWF`@LgX\xad\x15c!b\xbfK\xe8\xbe\x8e\xdb\x03\x1c\x8a\xb3\xad$\xd7\xf4\xb41q\x14\xc2#\x9f\xb1O\xb1U\xfb\xb6!\xcb\xb3?\x19\x9f\xd64\xcc\xad\xd0\x0f\xafsF\xb2\x0e@nGX\xad\x8a\x89\x05\xaf\xff\x05\x87\xa9\xfb}\x93g\x1c\xcdq\x11T\xb2\xd6\xe4\x00\xba\x16\xd3\xac^$Nf\xdd\x85\x00\x80\xae\x89\rT\xfc\xda5%\xb9i\xee\xd1\xc1\x93=\xed?r\xa7\xbf2>\xf9\xde\xb2E7\xa6\xb8\xae\x9e\xfe\xf5h\xcb\x80ybwX\x87pWW/\x99\xe3q\xf2dj]Ua\x8a\xaf\xf7\xfb\x9d\x03a\xddS7U\x15&\xfb\xfe:\xda\xfcKD\x95d\x9a4444444444444444\xa2\x0b\xff\x01?\xcc\xad7\x02?\x98z\x00\x00\x00\x00IEND\xaeB`\x82' This is a very fast version..... to create this. Make a png image in gimp or so... 256x64 pixels and greyscale. Save the file to temp.png now in a console run python from the command line fp = open("temp.png","r+") fp.read() this will give the above string or similar :) ....
I don't consider these intermediate changes to be a version bump. When we sort out all these bugs, I'll just turn it to 1.0, tag it, and then move from there. I use git, so version numbers are kind of pointless for me, anyway. I tried to insert the image lines you gave, but I can't get it to work, and I'm not too keen on installing all the dependencies for GIMP or Inkscape... could you format a patch for me with a better logo?
The revisions good for the ebuilds! If the filename to download is always the same, then the ebuilds cant tell different versions appart! I have created a logo patch
Created attachment 164265 [details] logo patch
Thanks for the patch. The updated version is up on my website, and is now version 1.0 (woohoo!) As for versioning, I'll keep something consistent from now on. I didn't really want an ebuild made from .99, I just wanted to get a dialog going.
Ahh great :) But could I get you to create a version tar.gz or something! Because if I create a new ebuild for 1.0 (can use the same but just do a rename) then I would not download the new version, because there would already be a file with that name in my distfiles!!!! Again, I ask you, please create versioned releases. It could that you have a tar.gz file that just onpacks to that one file... as long as there is a distinct downloadable file for each release :)
Ok, I've put a link to a tarball with the version number in the name on the page. Hopefully that's what you wanted.
Comment on attachment 164212 [details] new ebuild path has changes ...
Created attachment 164275 [details] accentuate v1.0
Comment on attachment 164275 [details] accentuate v1.0 WRONG
Created attachment 164276 [details] new lovely version 1.0 ebuild for accentuate
Thanks for the ebuild!
any reason for the RESTRICT="nomirror" in the ebuild? @tove: are you interested in helping maintaining this package?
Hello, I've cut a new release for Accentuate (v1.1) due to a very important fix being added that fixes a bug many many users experienced. Tarball is here: http://www.cs.rit.edu/~jrm8005/accentuate/accentuate-1.1.tar.gz
(In reply to comment #17) > any reason for the RESTRICT="nomirror" in the ebuild? Only that no gentoo devs had said anything about this ticket, so I put it in to not seach all gentoo mirrors each time for the file. I can remove it for the 1.1 release ebuild. > @tove: are you interested in helping maintaining this package? @tove?? If it is me you are addressing, then yes, I could maintain this ebuild, that would be an easy task :D Jorden: one comment, before I create the 1.1 release could you update the version number in the source file as well ? It states 1.0 :D When you have created the new tar ball I will create the new ebuild for it.
(In reply to comment #19) > (In reply to comment #17) > > any reason for the RESTRICT="nomirror" in the ebuild? > > Only that no gentoo devs had said anything about this ticket, so I put it in to > not seach all gentoo mirrors each time for the file. I can remove it for the > 1.1 release ebuild. > > > @tove: are you interested in helping maintaining this package? > > @tove?? If it is me you are addressing, then yes, I could maintain this ebuild, > that would be an easy task :D > > Jorden: one comment, before I create the 1.1 release could you update the > version number in the source file as well ? It states 1.0 :D When you have > created the new tar ball I will create the new ebuild for it. > Oh, how embarassing! Should be fixed now!
(In reply to comment #20) Hehe... now I dont have permissions to get the file :D
(In reply to comment #21) > (In reply to comment #20) > Hehe... now I dont have permissions to get the file :D > Argh! Today has been such a mess... should be working for real now :-\
Created attachment 170649 [details] accentuate-1.1.ebuild
(In reply to comment #0) > The original keyjnote developer was threatened with legal action from Apple, > Inc. over trademark infringement. Since then, the Sourceforge page has been > removed and the original package is nowhere to be found. The keyjnote project is alive again, under the name of impressive: http://impressive.sourceforge.net/ I haven't tested the old keyjnote ebuild with the new software, but I think it will not need many changes.
Are accentuate and impressive going to merge or not?
(In reply to comment #25) > Are accentuate and impressive going to merge or not? > I don't know, but I doubt it. Any time I've tried to send the author patches or communicate, I didn't get a response.
Why does accentuate block keyjnote? I guess for a non-technical reason ...
http://www.cs.rit.edu/~jrm8005/accentuate/accentuate-1.1.tar.gz link is dead.
Created attachment 237907 [details] Ebuild pointing to new SRC_URI SRC_URI was dead, this -r1 points to a new mirror at my uni.
Do we still need this?
app-office/impressive has an active upstream. Don't know what happened to the patches that went into the accentuate fork, may be worth saving/porting to some, but I guess we could say the disappearance of k*yjnote is now "solved upstream".
OK, I suggest you use app-office/impressive, since it is still under development.
