Hello, promised temporary repository for that exporter (compatible with F-Spot 0.8.2) has been created at http://sourceforge.net/projects/f-spotrajcenet/. Provided zip file includes also all common makefiles updated. However, Monodevelop project and solution files are not included, because I was not able to get it working even for the latest f-spot source checked out by git (still problems with invalid references to "nunit", regardless of configuring project with or without --enable-tests option). Best regards Petr
On Tue, Feb 1, 2011 at 10:16 PM, Petr H. <[email protected]> wrote: > Tim, > thank you for responding me. I'm really looking forward to F-Spot Community > Extensions project. > Meanwhile I'll try to create the repository compatible with the latest > F-Spot version (0.8.2.), as you suggested. > Best regards > Petr > > > > On Thu, Jan 27, 2011 at 5:00 PM, Tim Howard <[email protected]>wrote: > >> Petr, >> >> First off, that's excellent. Another popular exporter is fantastic news. I >> can't speak for F-Spot proper since Ruben **Vermeersch is the currrent >> maintainer but at the moment I am actively working on setting up a F-Spot >> Community Extensions project. My idea is to remove the exporters and editors >> from F-Spot and make them part of the community extensions. Then that can be >> released separately and as often as necessary to address necessary updates. >> It would also hopefully dramatically lower the bar for extension creation >> with some much needed automation (for reference the entirety of this idea >> and a lot of the initial set-up comes from the Banshee Community Extensions >> project). So, to me that would be an excellent place for this. >> >> However, I'm sure if you create a patch or put the code in a repository >> that can be pulled from then it could be included in the next release -- >> whenever that is. You would need to create a repository based on the latest >> code from the GNOME git repository and make sure the new exporter is >> integrated at all levels including makefiles and Monodevelop solution. And >> be sure not to introduce any warnings, I'm counting. :) >> >> Additionally, you could check into making your own, online, controlled >> F-Spot repository for add-ins. Users could then add that repository to their >> F-Spot add-in manager and get the add-in directly from you. That gives you >> maximum control if you want to provide updates often. >> >> When I get the F-Spot Community Extensions project ready for developers to >> add extensions I will post here. Hope this helps. >> >> >> >> cheers, >> >> >> Tim >> >> >
_______________________________________________ f-spot-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/f-spot-list
