Hi all,
being new to fossil, there is a big chance that I'm doing something wrong. ;-) May be you can help me: I've set up a repository for a project that beside the source files has a lot of binary files like pdf or doc files. What I see when I click on the corresponding link in the files view is a hex dump of the file. That's pretty useless for me and rather time consuming if you have big binary files. I could avoid this by just not clicking on those file links. But: I've attached one of the documents to a wiki page to access the doc from the wiki documentation pages. The result was a new section on the wiki page called Attachments with something which looked like a link to the document. Clicking on the link teleported me to the page of the artifact I've checked in before. Again I see the hex dump of the file, which still is useless for me and I guess for anyone else too. Meanwhile I've managed how to embedd links to the stored binaries on the wiki pages so that I'm offered to download or open them, but the hex dump on the artifact pages still bothers me. Question: Is there anything I can do to prevent the display of the hex dump for binary files? An other question directed to the maintainer: Is there any chance that fossil will be split into a frontend like fossil.exe and a library fossil.dll which has a well defined API so that other applications could use fossil without calling fossil.exe and parsing the output to see what happened? The reason I'm asking is that (after years of using CVS and now Subversion) I really like the DVCS approach and fossil with the integrated bug tracking and wiki is what I missed for so long. I'd like to introduce it in the company I'm working for, but those who got access to a test project griped about the lack of support for their favorite development environment. Especially the windows developers are not amused if they have to switch to the command line to do anything related to version control. They want to do a right click on the file or project and select commit from a menu. They want to enter the commit message in a dialog box instead of providing it on the command line. You can imagine ... I thought about writing a C# wrapper to do all the tasks by calling the fossil.exe and provide an interface to implement a SccProvider for Visual Studio, but that's quite difficult due to the variety of possible answers from fossil which have to be parsed. A well defined API like the one for SQLite would make things a lot easier. I think that fossil could be even more attractive for developers if there would be an easier way to integrate it into other applications. Nevertheless, thanks for fossil. It's a great peace of software. Ingo
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
