The only thing is that I would like it if we didn't force them to fork for win32 support. Eventually, features could show up in the Win32 port that may be useful, and I don't see a big disadvantage to adding win32 if we are doing BSD as well. Neither of them is Linux, but I don't think we should favour a platform.
A lot of people use windows (or so I've heard :) so it might be good to increase the user base, as long as we set up a seperate mailing list for troubleshooting for windows users since it's a far different beast. On Mon, Oct 13, 2003 at 09:17:28PM -0300, Rob Shortt wrote: > Dirk Meyer wrote: > >Christophe PERINAUD wrote: > > > >>Hi, > > > > > >Hi > > > > > >>I would like to know if it could be possible to integrate the win32 > >>version in the official freevo release. For now i am working on the > >>1.3.4 trunk but as the 1.4 will be release soon i will have to patch > >>again all. > > > > > >Since there is 1.4rc1 out know and the code changed weeks ago, I don't > >think there is another way than redoing the work. But since you've > >done it once, it should be much faster the second time. But please try > >it first with 1.3.4 to see if it's doable. > > I think you should probably checkout freevo cvs and make modifications > to that. Every week or so you can cvs update and it will merge in your > changes with the code from cvs. When a new release comes out you won't > have to change any code at all because you would have your changes > merged incrimentally. You may have to resolve some conflicts every now > and then when you cvs update but I think this would be a good way to > keep current. > > > > > > >>Is it possible to get only one trunk or does it have to be one for > >>linux and one for windows ? > > Personaly, I would rather not see ANY windows code in freevo cvs. From > the web site: "Freevo is an open-source digital video jukebox (PVR, > DVR) based on Linux". Freevo is also intended to run standalone on a > set-top like box connected to your TV. Windows is not made for this and > Linux fits the bill quite perfectly, that is probably one reason Krister > chose the platform in the first place. > > >I thought about it. I guess you have three kinds of patches: the first > >changes some Linux-specific stuff into a more Python way of doing > >it. 1.4 already has some of these patches because of the BSD port. I > >don't see any reason why we should not include this. > > I think that doing things the python way when using python is probably > for the best anyway. > > > The second type > >is a small 'if' around some smaller blocks to do it the windows way > >and not like Linux would do it. I also don't see a reason here. > > I would rather not see much (or any) of "if this, windows" in Freevo. > If it's there then we will end up having to support it. Also you can > bet that when I'm working on something I won't be thinking about windows > in the process. > > >But (there is always a but) I guess you can't port everything to > >windows. E.g. I don't thing you can read the device to check if it's a > >DVD or VCD. I would add 'Play DVD' to the menu and there better should > >be a DVD in the drive. I also would use ZoomPlayer for normal files > >and maybe WinDVD or PowerDVD for DVD/VCD discs. So you need extra > >plugins, maybe you don't need the current once, like xine. > > > >Conclusion: we have the Freevo core and some special plugins (and > >special settings in freevo_config.py). IMHO, it would be the best to > >patch the Freevo core that it works with windows, but we have a > >different repository with win32 stuff: config and plugins. To make a > >new win32 release, take the core (Unix release) and replace some > >plugins and the config. > > > > > >>Is it possible to have an official mailing list here just for win32 > >>dev ? > > > > > >Yes. I don't care about windows. So if there will be a windows version > >of Freevo, the users and developers should use there own list. > > I don't care about windows wither. I think they should use their own > list too, and their own website, and cvs tree. Freevo is open source > after all, if someone wants to start a Freevo for windows project they > have every right to. I know... that sounds harsh! > > > > >This is my point of view, other developers, please comment this. > > There you go. :) > > -Rob > > > > ------------------------------------------------------- > This SF.net email is sponsored by: SF.net Giveback Program. > SourceForge.net hosts over 70,000 Open Source Projects. > See the people who have HELPED US provide better services: > Click here: http://sourceforge.net/supporters.php > _______________________________________________ > Freevo-devel mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/freevo-devel ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php _______________________________________________ Freevo-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/freevo-devel
