Monday, September 22, 2003, 5:12:33 PM, Dirk wrote: > Hi,
> I take this posting as a mail I want to write for a long time > now. It's not personally :-) Thought about it for a long time if i should reply or not. But don't take it personally ;) >> I'd like the dvd menu support that xine is supposed to use, but I'm >> getting sick of 'fixing' each component that is necessary for freevo >> (already worked alot to make mplayer work right). > A second common problem: Freevo has good support for the hardware the > developers have, they take care of it. But since I don't have more > than one graphic card (and don't need to), users have to help > users. You fixed each component. Good, than share your results with > the rest. _Everyone_ has write access to the WiKi on the homepage. If > each user shares the resultions they have, it would much easier for > new users, Freevo could integrate this knowledge. Good point whenever i can or able to i do this always. But from a user standpoint some things in freevo are complicated. In fact when 1.3.4 released i was truly amazed by the plugins i found in the plugins dirs. Lot of them weren't documented in the wiki. For a user it's very hard to go to the sources and understand it all. Luckily since then plugins are know documented by developers and users. > In the future, I like to have some sort of auto detection. Freevo > knows what cards you have and will setup correctly, no need to change > the deatils. But right now, I get nearly no feedback for help > requests. Here some examples: > o I developed a way to detect if a disc is a DVD, VCD or SVCD. I send > a mail: please test and send results. I only got 1 (!!!) > answer. Lucky for you all, this answer helped to solve a bad bug. Hmm keep in mind that testing new cvs code isn't that easy for a user who want to give some feedback at this moment. Anoncvs is behind in fact a week ago i found out it was more then 6 days behind. But found my way to a snapshot but even that is 24 hours behind and sometimes missing important updates in the last 24 hours. But i understand your point. > o A asked for all to write a small doc for plugins. Even if you don't > know much about Python, you can document the plugins you use. I got > 0 (!!!) answers. Yeah, i added and updated some of your plugins in the wiki. ;-) But you are probably referring to additional info in the plugins. Again not sure how some of the plugins supposed to work. > o A asked for a slashscreen. OK, I got one answer, but a little bit > more would be great. Well i find the s(p)lashscreen awesome so that makes two. ;-) > o And skins, this has nothing to do with Python. Help us here, we are > no designers. err me either. > Someone wrote a howto for Freevo. He asked for help to make it > better. I guess the answers are below 10. Make it available on the freevo site don't see a direct link somewhere maybe in the users section. > I (and the other developers) write some code. Documenting is a pain in > the ass, I know, that's why most features aren't documented. We know. >> (Hope that doesn't sound ungrateful, but frustration is setting >> in--sorry) > Same here. not here ;-) /Robert ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Freevo-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freevo-users
