Brian,
That would be useful but I am not sure if we can use var() as its a
function. Changing $:/themes/tiddlywiki/vanilla/metrics/sidebarwidth is
sufficient.
Regards
Tones
On Thursday, 17 June 2021 at 10:55:08 UTC+10 Brian Radspinner wrote:
> @Tones, I don't know if you can make a tool out of it but you can use CSS
> variables to get a start with one element's width effecting another's...
>
> *body.tc-body* {
> --sidebarWidth: 33.33%;
> }
>
> *.tc-sidebar-scrollable* {
> width: var(--sidebarWidth);
> }
>
> *.tc-story-river* {
> width: calc(100% - var(--sidebarWidth) - 10px);
> }
>
>
> Adjusting the *--sidebarWidth* variable will cause both the sidebar and
> story river widths to change.
> On Wednesday, June 16, 2021 at 5:01:15 PM UTC-7 TW Tones wrote:
>
>> Some thoughts;
>>
>> In a related need I created a sidebar width tool - attached. If you look
>> at how it works I have to concatenate the N with px wide. This value
>> permits one number to change the relationship using fluid story and fixed
>> sidebar. I would like to see the number and units stored separately to
>> allow such manipulation. There should be css values that the user can set
>> and save including in a layout, to manipulate the whole layout. This would
>> include locations for a left sidebar, or settings centred story etc ...
>>
>> As we present custom layouts we should be incorporating hidden elements
>> that can be made active by the wiki designer.
>>
>> I am a strong believer that the layout should be a layer which can be
>> replaced. Kind of making tiddlywiki and engine layer, a layout layer and a
>> customised UI elements layer.
>>
>> Regards
>> Tones
>>
>> Regards
>> Tones
>>
>> On Thursday, 17 June 2021 at 05:56:42 UTC+10 [email protected] wrote:
>>
>>> Hello everybody,
>>>
>>> I think a "simple tool" like TiddlyTweeter wants is already there. It is
>>> the basic settings. The community shows that for people who play a bit with
>>> it (and know CSS), many different designs are possible even without such a
>>> tool.
>>> You can still wish for it, of course :-)
>>>
>>> But perhaps a different presentation of the setting options would be
>>> useful. For example, instead of the typical table (property on the left,
>>> input field on the right), a simplified representation of the boxes and
>>> margins, as used in TiddlyWikki, might be useful. This might also save
>>> translation texts, because it would then be largely self-explanatory.
>>>
>>> ... and because it is used so often here... Just thoughts ;-)
>>>
>>> » FBB
>>> TiddlyTweeter schrieb am Mittwoch, 16. Juni 2021 um 18:00:36 UTC+2:
>>>
>>>> PMario wrote ...
>>>>
>>>>> ... "simple tool" ... I think you meant "simple to use tool" ... The
>>>>> backend side of this tool imo is complex and will need a lot of thought.
>>>>> As
>>>>> I wrote in my last post.
>>>>>
>>>>
>>>> HaHa! I love your semantic appreciation of English!
>>>>
>>>> Right! I did not really mean making it is easy. I am not a programmer
>>>> by either craft or orientation.
>>>> WHAT am I saying? Merely that interactive tools for CSS WILL WORK in TW
>>>> since it is a full-on dynamic system.
>>>> AND I do suspect that we might be able to make a much better job of
>>>> providing simple "CSS use tools" than is currently the case.
>>>>
>>>> Just thoughts
>>>> TT
>>>>
>>>
--
You received this message because you are subscribed to the Google Groups
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/tiddlywiki/5ce3765c-2218-42a5-8d7f-cd1e39d1d9d9n%40googlegroups.com.
