On Wed, Jul 4, 2012 at 10:00 AM, Ramon Ribó <[email protected]> wrote:
> That it allowed to have more than one tickets list, with different > tables and reports in every list. That's an interesting idea. i don't know if the current architecture would play well with that (maybe it can), but i've just written it down on my v2 list. i know the current code lets one add his own fields, and those fields could theoretically be used for grouping purposes. The permissions would span groups, but fossil's permissions system isn't granular enough for us to say "user X has access to ticket group A, but not groups B and C." Maybe the permissions is something we could/should revisit for v2 (but so far the current system has been granular enough for what we've wanted to to). 2- Use fossil as a tool or library for other apps in order to access a > dabatase with tables with full history and with easy syncronization. > This is something that sqlite does not offer by itself > Unfortunately, fossil's architecture does not allow it to be easily refactored as a library/application combination. The effort required to do so would be relatively large - several full-time person-weeks, at least, i suspect (and all of us have day jobs), and that's not accounting for some of the new issues that would bring with it (e.g. multi-threading and how it changes db error handling). During that time other development would need to stop and we would probably introduce all kinds of new bugs along the way. That said: when we get around to writing v2, i think there is no (or little) disagreement that a library is the proper thing to do (for many reasons discussed at length on the list late last year or early this year). For v1, by the time the "librification momentum" was there, the project was too big to just refactor as a weekend project. -- ----- stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
