On Fri, Mar 6, 2015 at 9:11 AM, Tontyna <tont...@ultrareal.de> wrote:
> Maybe me and my co-workers aren't exemplars of The Average Fossil User > (current and future) but typing commands in a shell is not our common > approach to move or delete files. > Reference point are files on a harddrive actually belonging to a specific > software project which are managed and altered via IDE and file browser and > afterwards confirmed (not performed) in fossil. > > Fossil should not interfere with that worklflow. > > BTW: As soon as I started exploring Fossil I startet developing a GUI > application to comfortably operate Fossil. My GUI is much alike Paul's > `fcommit`. I am curious which IDE you and your team are using. Also, why you chose to write a stand-alone GUI application for Fossil rather than configure your IDE to interact with Fossil. Curiously, I've found that the open source IDEs I've tried actually make it harder to integrate "new" VCSs. Up until recently, my team and I used the SlickEdit IDE. It has very easy to configure support for any command line VCS. (Sadly, when the company decided to not renew the support contract, a manager in IT decided that meant we no longer had a license to use it - despite the fact that the license itself stated it is a perpetual license for the specified version.)
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
