Hi, I will split my answer into serveral post. Details for kaa.popcorn and kaa.candy only to the devel list.
On 21.07.2011 03:57, Jason Tackaberry wrote: > On 11-07-17 05:47 AM, Dirk Meyer wrote: >> I tried XBMC some days ago and while it looks very nice, it forces me to >> organize my media collection in a way I don't want to and has some >> usability issues (IMHO). Therefore, I still need Freevo. :) > > You know it's funny you say that, because after finally upgrading the OS > on my HTPC -- I had an uptime of 380+ days and I was reluctant to reboot > :) -- I also decided to try XBMC. :) > Someone else complained that configuring it was difficult, but I didn't > find that at all. It ran immediately after installation and > configuration was fairly straightforward via the GUI (modulo lirc). Same here -- modulo lcd. > It's certainly overall better than the mishmash of half-baked prototypes > I was using before. But yes, I did have some usability issues (e.g. > library required way too much handholding, requiring manual library > scanning after adding or deleting content) Yes, IMHO kaa.beacon is much better here. >> The main problem with Freevo 2.0 is my and Jason's lack of time the last >> year. Development was not only slow, it wasn't existant. > > Yes, this is the fate of many small open source projects: developers > eventually get carriers and/or lives and progress atrophies. I wish I > had the motivation and energy I had when I was 20. :) Yes. But I think one Freevo hacking evening a week is possible. I'm very motivated after the XBMC test. > Especially an M2TS parser. This is one of the bigger gaps in > kaa.metadata right now. This would be a great, focused little project > for someone looking to contribute. Adding parsers to kaa.metadata is > quite simple and you're not required to figure out how kaa.base or other > big chunks of code works. > > All you need to do is read the ISO 13818-1 spec. *cough* :) That is something we need, but it is not on my TODO list right now. >> 5. kaa.candy has the basics, but may need some nice effects like >> mirror-effect, better animations, etc. It has everything we need to make >> Freevo 2.0 work but it could be nicer. If you know C (Python not needed) >> and want to play with clutter or if you now Python and want to dive into >> kaa.candy, drop me a note. You only need to know kaa.base and clutter as >> dependency. > > I think we should seriously revisit kaa.candy now. clutter has come a > long way since we looked at it last, and it now includes containers and > layout managers, and lots of new effects and animations, which is a lot > of what kaa.candy aimed to add. We should gut what's no longer > necessary in kaa.candy and stay as tight to clutter as possible. Agreed. I will start a new posting here about changes in kaa.candy. But this won't delay Freevo 2.0 plugin development. If you do not need the idlebar, Freevo 2.0 is ready. And the GUI code is separented, it is not much work to replace it. >> 6. XBMC looks soooo cool. The big background images, the animations. >> Nice! We do have the code in Freevo 2.0 to do the same (even support to >> grab TV show or movie specific wallpapers and images). > > Yeah, but a lot of the credit there really goes to the awesome > contributors of thetvdb.com and themoviedb.org. I'm still amazed at the > quality of the fan art. Yes. And we could just reuse this. > My biggest use-case is that I do most of my file management on my NAS, > and the HTPC just has an NFS mount to consume the media. My HTPC is > where beacon would run, but because INotify doesn't work through NFS, > beacon doesn't see the changes. > > We had some neat ideas about distributed beacon instances, but there are > a couple simpler-to-implement options that I'm more likely to get to first: > > 1. An INotify reflector: a small process that just passes INotify > events over RPC back to the beacon server > 2. Have an option to periodically scan NFS mounts in addition to > INotify. Currently (IIRC), polling is disabled if INotify is > supported. > > > #2 is easiest to implement by a long shot. It's not as elegant as it > won't catch file moves, though. Again, not on my list right now. If someone wants to help, this is a good part. [kaa.popcorn stuff see other post] >> 11. There is not webserver for Freevo 2.0. Anyone willing to take over >> this part? You have complete control what you want to do. I guess you >> have to know your HTML/CSS/JS-fu. > > I'm also lately of the opinion that we need a web services API. RESTful > is trendy, and it's usually very easy to work with, lowering the barrier > to entry. But this is something we should not worry about until we have > a stable and complete core. yes Dischi -- Bad spellers of the world Untie! ------------------------------------------------------------------------------ Storage Efficiency Calculator This modeling tool is based on patent-pending intellectual property that has been used successfully in hundreds of IBM storage optimization engage- ments, worldwide. Store less, Store more with what you own, Move data to the right place. Try It Now! http://www.accelacomm.com/jaw/sfnl/114/51427378/ _______________________________________________ Freevo-users mailing list Freevo-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freevo-users
