On 4/23/2016 5:06 PM, Marko Käning wrote:
On 24 Apr 2016, at 01:45 , John P. Rouillard <rouilj+fos...@cs.umb.edu> wrote:
....
However once you had that info in the database, IIRC you can use th1 to
find out who the current user is. Then you can make sql calls into the
database. So I think in theory you could change/create a user schema
that holds personalized settings and use th1 to customize the menu
item.
I see.
Well, I’ve reconfigured the repo’s header now to my linking.
Having just skimmed this thread, I think we're all missing an elephant
in the room here.
A very common usage model for fossil is for each dev to have their own
clone. That clone has (by nature) complete copies of the tickets and
timeline, assuming that autosync is on, or that sync has been happening
regularly. (I don't think that ticket updates in a local copy trigger
autosync. I vaguely recall some discussion about that in the past.)
But skins are not autosync'ed. You get a copy of some skin on clone, but
without some effort by an authorized user of the main repo, no changes
made to a skin in a clone will propagate back.
So if you have personal preferences for timeline defaults, repo home
page, cosmetic features in the CSS, or similar, you can just change
those in your clone and use "fossil ui" to play with the repo with those
defaults.
If it is important that multiple users of the web UI on a single server
see different or personalized settings, that would be trickier. But a
way to do that would be to serve different clones to each user, and use
a cron job to keep them all synced. Probably not worth the effort unless
the value added to the user's convenience is significant.
--
Ross Berteig r...@cheshireeng.com
Cheshire Engineering Corp. http://www.CheshireEng.com/
+1 626 303 1602
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
