[fossil-users] Some more default settings for a UI user

[Marko Käning]

Hi,

it would be nice to have some default settings definable for a user:

• Timeline view:
- Type of entries (e.g. only check-ins)
- Max.
- With/Without Files

• Files view:
- would be nice to be able to set it e.g. by default to tree-view.

This would be probably ideally configurable via Admin/Configuration.

Greets,
Marko

[Stephan Beal]

You can achieve all of that by changing the appropriate menu entries/links
via the setup page. If

----- stephan
(Sent from a mobile device, possibly from bed. Please excuse brevity,
typos, and top-posting.)

Post by Marko Käning
Hi,
- Type of entries (e.g. only check-ins)
- Max.
- With/Without Files
- would be nice to be able to set it e.g. by default to tree-view.
This would be probably ideally configurable via Admin/Configuration.
Greets,
Marko
_______________________________________________
fossil-users mailing list
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[Stephan Beal]

Ps: see the /help page for the various /timeline options.

----- stephan
(Sent from a mobile device, possibly from bed. Please excuse brevity,
typos, and top-posting.)

Post by Stephan Beal
You can achieve all of that by changing the appropriate menu entries/links
via the setup page. If
----- stephan
(Sent from a mobile device, possibly from bed. Please excuse brevity,
typos, and top-posting.)

Post by Marko Käning
Hi,
- Type of entries (e.g. only check-ins)
- Max.
- With/Without Files
- would be nice to be able to set it e.g. by default to tree-view.
This would be probably ideally configurable via Admin/Configuration.
Greets,
Marko
_______________________________________________
fossil-users mailing list
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[Marko Käning]

Post by Stephan Beal
Ps: see the /help page for the various /timeline options.
- Type of entries (e.g. only check-ins)
- Max.
- With/Without Files
- would be nice to be able to set it e.g. by default to tree-view.

Thanks for the pointer to the /help page. Would be nice to have that link already in
Fossil's vanilla version of the UI, as it is a great overview of all the commands.

[Stephan Beal]

All 3 of those options are there, but i am in bed and won't be up for
(ideally) another 10 hours, so i am hoping someone else will point them out
;). Help is not in the default menu because it is, in practice, rarely
used. Feel free to add it to yours.

----- stephan
(Sent from a mobile device, possibly from bed. Please excuse brevity,
typos, and top-posting.)

Post by Stephan Beal
Ps: see the /help page for the various /timeline options.

Post by Marko Käning
- Type of entries (e.g. only check-ins)
- Max.
- With/Without Files

For the tree view there’s also nothing specific for the menu structure to

Post by Marko Käning
- would be nice to be able to set it e.g. by default to tree-view.

Thanks for the pointer to the /help page. Would be nice to have that link already in
Fossil's vanilla version of the UI, as it is a great overview of all the commands.
_______________________________________________
fossil-users mailing list
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[Marko Käning]

Hi Stephan,

All 3 of those options are there, but i am in bed and won't be up for (ideally) another 10 hours, so i am hoping someone else will point them out ;). Help is not in the default menu because it is, in practice, rarely used. Feel free to add it to yours.

ok, thanks for reassuring. I will search on a bit and thus wish you a good night.

Bye,
Marko

[Marko Käning]

My /setup_timeline page gives me these options:

Allow block-markup in timeline
Plaintext comments on timelines
Use Universal Coordinated Time (UTC)
Per-Item Time Format
Show version differences by default
Max timeline comment length

Post by Marko Käning
- Type of entries (e.g. only check-ins)
- Max.
- With/Without Files

[Marko Käning]

Perhaps it is important to note that I am running the current stable version 1.34,

I’ve installed fossil’s version 1.34 using MacPorts on OSX. The web UI shows
Fossil version [62dcb00e68] 2015-11-02 17:35:44

[ http://www.mail-archive.com/fossil-***@lists.fossil-scm.org/msg22951.html ]

[Stephan Beal]

You need to edit the links in the menus to add parameters for the settings
you want. e.g. max is set using n=123.

----- stephan
(Sent from a mobile device, possibly from bed. Please excuse brevity,
typos, and top-posting.)
On Apr 24, 2016 01:02, "Marko KÀning" <sec001+***@posteo.net> wrote:

My /setup_timeline page gives me these options:

*Allow block-markup in timeline*
*Plaintext comments on timelines*
*Use Universal Coordinated Time (UTC)*
HH:MM HH:MM:SS YYYY-MM-DD HH:MM YYMMDD HH:MM (off) *Per-Item Time Format*
*Show version differences by default*
*Max timeline comment length*

which do not include the 3 additional ones I am seeking for:

• Timeline view:
- Type of entries (e.g. only check-ins)
- Max.
- With/Without Files

[Marko Käning]

You need to edit the links in the menus to add parameters for the settings you want. e.g. max is set using n=123.

I know that I can do that, in principle, BUT next time I click the /timeline menu link I am back to the default settings for all three parameters, i.e. n=50 in this case.

BEDTIME NOW! :-)

[John P. Rouillard]

Post by Marko Käning

Post by Stephan Beal
You need to edit the links in the menus to add parameters for the
settings you want. e.g. max is set using n=123.

I know that I can do that, in principle, BUT next time I click the
/timeline menu link I am back to the default settings for all three
parameters, i.e. n=50 in this case.

You're missing what he is saying. He is saying change the Timeline
(/timeline) link in the menu.

When logged in as an admin, go to:

Admin/Skins

You will see text that says:

A "skin" is a combination of CSS, Header, Footer, and Details

Choose Header.

The html/th1 mix that shows up in the textbox is the top section of
the pages.

Search for Timeline and you should see:

menulink /timeline Timeline

Change
/timeline
to
'/timeline?n=100'

and click Apply changes. Now the default value when clicking Timeline
menu link is to show 100 changes.

I don't think there is an option to allow logged in users to set those
sorts of things on a per user basis. AFAIK there is no user data
stored other than a password. So you would need to figure out how to
create a user table to store user preferences. There are no custom
forms for users (i.e. a user equivalent of the admin/tickets
mechanism), you wouldn't be able to allow the user to edit things
without some changes to the fossil core code.

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.

--
-- rouilj
John Rouillard
===========================================================================
My employers don't acknowledge my existence much less my opinions.

[Marko Käning]

Hi John,

Post by John P. Rouillard
You're missing what he is saying. He is saying change the Timeline
(/timeline) link in the menu.

indeed, not hard to miss it. :)

I couldn’t figure out where I could change exactly those links.

Post by John P. Rouillard
Admin/Skins
A "skin" is a combination of CSS, Header, Footer, and Details
Choose Header.

Well, that’s not really intuitive, is it! ;-)

I would have expected something like “Edit menu” or something along that line.

Post by John P. Rouillard
The html/th1 mix that shows up in the textbox is the top section of
the pages.
menulink /timeline Timeline
Change
/timeline
to
'/timeline?n=100'
and click Apply changes. Now the default value when clicking Timeline
menu link is to show 100 changes.

Yep, got that now.

Post by John P. Rouillard
I don't think there is an option to allow logged in users to set those
sorts of things on a per user basis. AFAIK there is no user data
stored other than a password. So you would need to figure out how to
create a user table to store user preferences. There are no custom
forms for users (i.e. a user equivalent of the admin/tickets
mechanism), you wouldn't be able to allow the user to edit things
without some changes to the fossil core code.

OK.

Post by John P. Rouillard
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.

Thanks for the clarification wrt the "Menu Settings" aka Admin/Skins. :)

Greets,
Marko

[Stephan Beal]

Post by Marko Käning

Post by John P. Rouillard
You're missing what he is saying. He is saying change the Timeline
(/timeline) link in the menu.

indeed, not hard to miss it. :)
I couldn’t figure out where I could change exactly those links.

Indeed, it's not intuitive, and i was too tired to get out of bed and back
to my full keyboard, so was unnecessarily brief ;).

Post by Marko Käning

Post by John P. Rouillard
I don't think there is an option to allow logged in users to set those
sorts of things on a per user basis. AFAIK there is no user data
stored other than a password. So you would need to figure out how to
create a user table to store user preferences. There are no custom
forms for users (i.e. a user equivalent of the admin/tickets
mechanism), you wouldn't be able to allow the user to edit things
without some changes to the fossil core code.

That's essentially correct - only the password hash (not the password),
login name, permissions, and an optional "contact info" field (normally
email address) are stored. There is no other per-user data (and were we to
add it, people would insist that it optionally be syncable with other repo
copies, and then they'd demand that it automatically sync with some repos
(namely, their own) and not with others (everyone else's), and then...). i
did experiment with using a JSON object to store arbitrary user-specific
data (in a single DB field, as a JSON object tree) some years ago, but
never did anything useful with it. The plan, at the time, was to use it to
store drafts of wiki pages/tickets.

[Marko Käning]

Hi Stephan,

Indeed, it's not intuitive, and i was too tired to get out of bed and back to my full
keyboard, so was unnecessarily brief ;).

you still responded even when you were supposed to have already nodded off! ;-)

Thanks for all the insights big time. My Fossil wiki’s menu layout is now exactly the
way I wanted it by default. Great.

Regarding keeping of more user info I see what you mean. It’s complicated enough
already with all those admin passwords spit out when cloning a remote repo and so on…
So, I guess it’s not worth it for now to think in that direction.
Ideally the devs working together find some common decision on the wiki layout
and make the corresponding manipulations once.

Greets,
Marko


P.S.: Any hints for my other two post regarding code blocks and font sizes?

[Stephan Beal]

Post by Marko Käning
P.S.: Any hints for my other two post regarding code blocks and font sizes?

i'm not gonna touch those, in the hope that someone with more fingers in
the wiki code can say something to them.

just fyi: while i'm a long-time contributor to fossil (since 2008),
relatively recent elbow nerve damage caused by too much typing severely
limits how much i can do on a keyboard, so since 16 months it's rare that i
partake in longer/detailed discussions or touch more than a few lines of
code at a time. So please don't misunderstand my general brevity as
annoyance or impatience - it's a physical limitation which forces me to be
very choosy with regards to what i type!

[Marko Käning]

Hi Stephan,

i'm not gonna touch those, in the hope that someone with more fingers in the wiki code can say something to them.

no worries, I am very happy about your immediate feedback!

Greets,
Marko

[Steve Schow]

I’m having trouble changing skins. It works on my local repo, but not on the server repo.

1 - created repo on machine A. setup user foobar with s privs.

2 - created clone of that repo on machine B. also with user foobar with s privs

3 - Working on the local machine B, I can run fossil ui, and i’m able to change the skins all i want.

4 - if I start machine A as a server with “fossil server’ and then connect to that ui from machine B…I’m able to create tickets and everything else I’ve tried has worked but if I try to chose a different skin, it just stays on the default.

what am I missing?

[Richard Hipp]

Post by Steve Schow
I’m having trouble changing skins. It works on my local repo, but not on
the server repo.
1 - created repo on machine A. setup user foobar with s privs.
2 - created clone of that repo on machine B. also with user foobar with s privs
3 - Working on the local machine B, I can run fossil ui, and i’m able to
change the skins all i want.
4 - if I start machine A as a server with “fossil server’ and then connect
to that ui from machine B…I’m able to create tickets and everything else
I’ve tried has worked but if I try to chose a different skin, it just stays
on the default.
what am I missing?

Did you do "fossil config push skin" to move your local changes over
to the server?

[Steve Schow]

haven’t used that command yet at all. i wasn’t trying to copy skins from local to server, I was just trying to login to the webui on the server and use it directly through the webui. Go into admin section and hit the link for skins and then there are install buttons for each of the skins you guys have provided, but they don’t change anything, the skin always just stays on the default one.

I only mentioned the local repo because when I use the webui of the local repo I am able to change the skins just fine. When I try to use the webui of the non local repo…I can’t change the skins.

Post by Richard Hipp

Post by Steve Schow
I’m having trouble changing skins. It works on my local repo, but not on
the server repo.
1 - created repo on machine A. setup user foobar with s privs.
2 - created clone of that repo on machine B. also with user foobar with s privs
3 - Working on the local machine B, I can run fossil ui, and i’m able to
change the skins all i want.
4 - if I start machine A as a server with “fossil server’ and then connect
to that ui from machine B…I’m able to create tickets and everything else
I’ve tried has worked but if I try to chose a different skin, it just stays
on the default.
what am I missing?

Did you do "fossil config push skin" to move your local changes over
to the server?
--
D. Richard Hipp
_______________________________________________
fossil-users mailing list
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[Ross Berteig]

Post by Marko Käning

Post by John P. Rouillard
....
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.

[Marko Käning]

I’ve understood now that

$ fossil config push skin

should actually push the clone’s skin to the central repo. :)

[Marko Käning]

Hi Sephan,

You can achieve all of that by changing the appropriate menu entries/links via the setup page. If

I am puzzled, as I can’t seem to find the correct setup page which makes the wiki’s menu links
available for configuration.

Greets,
Marko


P.S.: Running the web UI via “fossil ui” here, but I guess that shouldn’t make any difference.

[Steve Schow]

Post by Marko Käning
Hi,
- Type of entries (e.g. only check-ins)
- Max.
- With/Without Files
- would be nice to be able to set it e.g. by default to tree-view.

+1

[Fran]

add option to display unified or sidebyside patch by default too

Enviado con Aquamail para Android
http://www.aqua-mail.com


Hi,

it would be nice to have some default settings definable for a user:

• Timeline view:
- Type of entries (e.g. only check-ins)
- Max.
- With/Without Files

• Files view:
- would be nice to be able to set it e.g. by default to tree-view.

This would be probably ideally configurable via Admin/Configuration.

Greets,
Marko

_______________________________________________
fossil-users mailing list
fossil-***@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users