1
0
mirror of https://github.com/Jermolene/TiddlyWiki5 synced 2024-09-27 14:48:19 +00:00

Merge branch 'master' into multi-wiki-support

This commit is contained in:
Jeremy Ruston 2024-06-08 14:59:17 +01:00
commit 2b2fd4bdb7
106 changed files with 677 additions and 196 deletions

View File

@ -29,7 +29,11 @@ var THROTTLE_REFRESH_TIMEOUT = 400;
exports.startup = function() {
// Set up the title
$tw.titleWidgetNode = $tw.wiki.makeTranscludeWidget(PAGE_TITLE_TITLE,{document: $tw.fakeDocument, parseAsInline: true});
$tw.titleWidgetNode = $tw.wiki.makeTranscludeWidget(PAGE_TITLE_TITLE, {
document: $tw.fakeDocument,
parseAsInline: true,
importPageMacros: true,
});
$tw.titleContainer = $tw.fakeDocument.createElement("div");
$tw.titleWidgetNode.render($tw.titleContainer,null);
document.title = $tw.titleContainer.textContent;

View File

@ -48,7 +48,11 @@ exports.startup = function() {
headers: getPropertiesWithPrefix(params,"header-"),
passwordHeaders: getPropertiesWithPrefix(params,"password-header-"),
queryStrings: getPropertiesWithPrefix(params,"query-"),
passwordQueryStrings: getPropertiesWithPrefix(params,"password-query-")
passwordQueryStrings: getPropertiesWithPrefix(params,"password-query-"),
basicAuthUsername: params["basic-auth-username"],
basicAuthUsernameFromStore: params["basic-auth-username-from-store"],
basicAuthPassword: params["basic-auth-password"],
basicAuthPasswordFromStore: params["basic-auth-password-from-store"]
});
});
$tw.rootWidget.addEventListener("tm-http-cancel-all-requests",function(event) {

View File

@ -100,6 +100,10 @@ headers: hashmap of header name to header value to be sent with the request
passwordHeaders: hashmap of header name to password store name to be sent with the request
queryStrings: hashmap of query string parameter name to parameter value to be sent with the request
passwordQueryStrings: hashmap of query string parameter name to password store name to be sent with the request
basicAuthUsername: plain username for basic authentication
basicAuthUsernameFromStore: name of password store entry containing username
basicAuthPassword: plain password for basic authentication
basicAuthPasswordFromStore: name of password store entry containing password
*/
function HttpClientRequest(options) {
var self = this;
@ -129,6 +133,11 @@ function HttpClientRequest(options) {
$tw.utils.each(options.passwordHeaders,function(value,name) {
self.requestHeaders[name] = $tw.utils.getPassword(value) || "";
});
this.basicAuthUsername = options.basicAuthUsername || (options.basicAuthUsernameFromStore && $tw.utils.getPassword(options.basicAuthUsernameFromStore)) || "";
this.basicAuthPassword = options.basicAuthPassword || (options.basicAuthPasswordFromStore && $tw.utils.getPassword(options.basicAuthPasswordFromStore)) || "";
if(this.basicAuthUsername && this.basicAuthPassword) {
this.requestHeaders.Authorization = "Basic " + $tw.utils.base64Encode(this.basicAuthUsername + ":" + this.basicAuthPassword);
}
}
HttpClientRequest.prototype.send = function(callback) {

View File

@ -74,6 +74,18 @@ ParametersWidget.prototype.execute = function() {
self.setVariable(variableName,getValue(name));
}
});
} else {
// There is no parent transclude. i.e. direct rendering.
// We use default values only.
$tw.utils.each($tw.utils.getOrderedAttributesFromParseTreeNode(self.parseTreeNode),function(attr,index) {
var name = attr.name;
// If the attribute name starts with $$ then reduce to a single dollar
if(name.substr(0,2) === "$$") {
name = name.substr(1);
}
var value = self.getAttribute(attr.name,"");
self.setVariable(name,value);
});
}
// Construct the child widgets
this.makeChildWidgets();

View File

@ -316,7 +316,8 @@ Widget.prototype.getStateQualifier = function(name) {
Make a fake widget with specified variables, suitable for variable lookup in filters
*/
Widget.prototype.makeFakeWidgetWithVariables = function(variables) {
var self = this;
var self = this,
variables = variables || {};
return {
getVariable: function(name,opts) {
if($tw.utils.hop(variables,name)) {
@ -334,7 +335,7 @@ Widget.prototype.makeFakeWidgetWithVariables = function(variables) {
};
} else {
opts = opts || {};
opts.variables = variables;
opts.variables = $tw.utils.extend(variables,opts.variables);
return self.getVariableInfo(name,opts);
};
},

View File

@ -1,10 +1,24 @@
title: $:/core/macros/lingo
tags: $:/tags/Macro
tags: $:/tags/Global
\define lingo-base()
<!-- Note that lingo-base should end with a trailing slash character -->
\procedure lingo-base()
$:/language/
\end
\end lingo-base
\define lingo(title)
{{$(lingo-base)$$title$}}
\end
\procedure lingo(title,override-lingo-base)
<!-- Lingo procedure -->
<!-- Get the parse mode used to invoke this procedure -->
<$parameters $parseMode="parseMode">
<!-- Compute the lingo-base-->
<$let active-lingo-base={{{ [<override-lingo-base>!match[]else<lingo-base>] }}}>
<!-- First try the old school <active-lingo-base><title> format -->
<$transclude $tiddler={{{ [<active-lingo-base>addsuffix<title>] }}} $mode=<<parseMode>>>
<!-- If that didn't work, try the new <lingo-base><langcode>/<title> format -->
<$let language-code={{{ [[$:/language]get[text]get[name]else[en-GB]] }}}>
<$transclude $tiddler={{{ [<active-lingo-base>addsuffix<language-code>addsuffix[/]addsuffix<title>] }}} $mode=<<parseMode>>/>
</$let>
</$transclude>
</$let>
</$parameters>
\end lingo

View File

@ -55,6 +55,7 @@ The easiest way to use the <<.wlink TestCaseWidget>> is by creating TestCaseTidd
Improvements to the following translations:
* Chinese
* French
* Macedonian
* Polish
@ -77,14 +78,17 @@ Improvements to the following translations:
! Hackability Improvements
* <<.link-badge-extended "https://github.com/Jermolene/TiddlyWiki5/pull/8109">> [[WidgetMessage: tm-http-request]] to be able to use Basic Authentication
* <<.link-badge-improved "https://github.com/Jermolene/TiddlyWiki5/pull/7882">> infinite recursion handling using a custom exception
* <<.link-badge-added "https://github.com/Jermolene/TiddlyWiki5/pull/7966">> button to the JavaScript error popup allowing tiddlers to be saved to a local JSON file
* <<.link-badge-updated "https://github.com/Jermolene/TiddlyWiki5/issues/8120">> to latest version of modern-normalize 2.0.0
* <<.link-badge-improved "https://github.com/Jermolene/TiddlyWiki5/pull/8211">> [[tm-permalink|WidgetMessage: tm-permalink]], [[tm-permaview|WidgetMessage: tm-permaview]] and [[tm-copy-to-clipboard|WidgetMessage: tm-copy-to-clipboard]] messages to allow the notification text to be customised
* <<.link-badge-improved "https://github.com/Jermolene/TiddlyWiki5/pull/8225">> [[WidgetMessage: tm-http-request]] to allow the default headers to be suppressed
* <<.link-badge-improved "https://github.com/Jermolene/TiddlyWiki5/pull/8097">> window title rendering to automatically include global definitions
! Bug Fixes
* <<.link-badge-fixed "https://github.com/Jermolene/TiddlyWiki5/pull/8233">> nested functions not resolving variables created in filter runs
* <<.link-badge-fixed "https://github.com/Jermolene/TiddlyWiki5/pull/8186">> nested [[Block Quotes in WikiText]]
* <<.link-badge-fixed "https://github.com/Jermolene/TiddlyWiki5/pull/7933">> TiddlyWikiClassic build process
* <<.link-badge-fixed "https://github.com/Jermolene/TiddlyWiki5/pull/7935">> LinkWidget not refreshing when the `to` attribute changes
@ -103,6 +107,7 @@ Improvements to the following translations:
* <<.link-badge-fixed "https://github.com/Jermolene/TiddlyWiki5/issues/8095">> proper DOCTYPE for the open window template
* <<.link-badge-fixed "https://github.com/Jermolene/TiddlyWiki5/issues/7945">> theme font size settings to open in new window CSS
* <<.link-badge-fixed "https://github.com/Jermolene/TiddlyWiki5/pull/8098">> backlink parser to prevent it parsing binary tiddlers
* <<.link-badge-fixed "https://github.com/Jermolene/TiddlyWiki5/pull/8203">> issue where default parameters were not applied when a ParametersWidget did not find a parent TranscludeWidget
! Node.js Improvements
@ -154,5 +159,6 @@ saqimtiaz
sarna
Telumire
twMat
xcazin
yaisog
""">>

View File

@ -0,0 +1,21 @@
title: Functions/FunctionFilterrunVariables3
description: Nested functions in filter runs that set variables
type: text/vnd.tiddlywiki-multiple
tags: [[$:/tags/wiki-test-spec]]
title: Output
\whitespace trim
\define currentTiddler() old-current
\function .inner() [<currentTiddler>]
\function .outer() [<currentTiddler>match[intermediate2]then[new-current]] :map[function[.inner]]
\function .wrappertwo() [<currentTiddler>match[intermediate]addsuffix[2]] :map[function[.outer]]
\function .wrapper() intermediate :map[.wrappertwo[]]
<$text text={{{ [.wrapper[]] }}}/>
+
title: ExpectedResult
new-current

View File

@ -816,6 +816,26 @@ describe("Widget module", function() {
expect(wrapper.innerHTML).toBe("<p>Bval</p>");
});
it("should use default $parameters if directly rendered", function() {
var wiki = new $tw.Wiki();
var text = "<$parameters bee=default $$dollar=bill nothing empty=''>bee=<<bee>>, $dollar=<<$dollar>>, nothing=<<nothing>>, empty=<<empty>></$parameters>";
var widgetNode = createWidgetNode(parseText(text,wiki),wiki);
// Render the widget node to the DOM
var wrapper = renderWidgetNode(widgetNode);
// nothing = true in this attribute form because valueless attributes always equal true.
expect(wrapper.innerHTML).toBe("<p>bee=default, $dollar=bill, nothing=true, empty=</p>");
});
it("should use default \\parameters if directly rendered", function() {
var wiki = new $tw.Wiki();
var text = "\\parameters(bee:default $$dollar:bill nothing)\nbee=<<bee>>, $$dollar=<<$$dollar>>, nothing=<<nothing>>";
var widgetNode = createWidgetNode(parseText(text,wiki),wiki);
// Render the widget node to the DOM
var wrapper = renderWidgetNode(widgetNode);
// nothing = true in this attribute form because valueless attributes always equal true.
expect(wrapper.innerHTML).toBe("<p>bee=default, $$dollar=bill, nothing=</p>");
});
it("can have more than one macroDef variable imported", function() {
var wiki = new $tw.Wiki();
wiki.addTiddlers([

View File

@ -0,0 +1,8 @@
created: 20230803054456864
modified: 20230803054957952
tags: Filters [[Filter Operators]]
title: String Operators
String operators are [[filter operators|Filter Operators]] that interact with strings.
<<list-links "[tag[String Operators]]" class:"multi-columns">>

View File

@ -0,0 +1,8 @@
created: 20230803055001751
modified: 20230803055210839
tags: Filters [[Filter Operators]]
title: Tag Operators
Tag operators are [[filter operators|Filter Operators]] that interact with strings.
<<list-links "[tag[Tag Operators]]">>

View File

@ -1,5 +1,5 @@
created: 20140908114400000
modified: 20140923141919329
modified: 20230803053808167
tags: About
title: History of TiddlyWiki
type: text/vnd.tiddlywiki
@ -32,17 +32,17 @@ Much of the early feedback was that TiddlyWiki was neat, but that it would be mo
Within a few months I saw an experimental Firefox extension that enabled TiddlyWiki to save changes in the browser. Examining the code, I realised that the APIs that it used to write to the file system were actually available in ordinary HTML files - as long as they were loaded via a `file://` URI.
I adapted the Firefox code into the core of TiddlyWiki, and soon added a similar ability for Internet Explorer (making use of an old ActiveX control that Microsoft distributed with Internet Explorer).
I adapted the Firefox code into the core of TiddlyWiki, and soon added a similar ability for Internet Explorer (making use of an old [[ActiveX|https://en.wikipedia.org/wiki/ActiveX]] control that Microsoft distributed with Internet Explorer).
! Growth of TiddlyWiki
A major milestone in the growth of TiddlyWiki was the creation of "GTDTiddlyWiki" by Nathan Bowers. He took the vanilla TiddlyWiki product and adapted it for the specific application of keeping track of tasks using the popular Getting Things Done methodology. GTDTiddlyWiki was an immediate hit, being enthusiastically greeted on websites like LifeHacker.
A major milestone in the growth of TiddlyWiki was the creation of "GTDTiddlyWiki" by Nathan Bowers. He took the vanilla TiddlyWiki product and adapted it for the specific application of keeping track of tasks using the popular Getting Things Done methodology. GTDTiddlyWiki was an immediate hit, being enthusiastically greeted on websites like [[LifeHacker|https://lifehacker.com/]].
Over the next couple of years TiddlyWiki continued to grow in popularity, and gained new features and capabilities. Within a year I was able to support myself by performing bespoke development work on TiddlyWiki, notably working with wiki pioneer SocialText on the ability to synchronise changes with an online server
Over the next couple of years TiddlyWiki continued to grow in popularity, and gained new features and capabilities. Within a year I was able to support myself by performing bespoke development work on TiddlyWiki, notably working with wiki pioneer [[SocialText|https://en.wikipedia.org/wiki/Socialtext]] on the ability to synchronise changes with an online server
! BT Acquisition
In May 2007, [[BT]] acquired [[Osmosoft]], my consultancy company. It was an unusual decision to acquire a company with a single employee and a tiny trickle of revenue - [[Osmosoft]] didn't even own the intellectual property in TiddlyWiki since I had handed it over to UnaMesa to assure its future for the community.
In May 2007, [[BT]] acquired [[Osmosoft]], my consultancy company. It was an unusual decision to acquire a company with a single employee and a tiny trickle of revenue - [[Osmosoft]] didn't even own the intellectual property in TiddlyWiki since I had handed it over to [[UnaMesa]] to assure its future for the community.
[[BT]]'s motivation was to help them understand community-based ecosystems. I joined the organisation as "Head of Open Source Innovation", taking responsibility for open source governance, and providing advice and expertise on how to participate in open soure communities.

View File

@ -1,9 +1,9 @@
created: 20210101150806938
modified: 20210101151808491
modified: 20230803053451496
tags: Community
title: Community Editions
These are prepackaged editions created by the ~TiddlyWiki [[Community]]. These are TiddlyWikis with added plugins and configurations to facilitate a certain use-case. These are great starting points if you want to quickly jump into TiddlyWiki and start using it without spending too much time configuring yourself.
These are prepackaged editions created by the ~TiddlyWiki [[Community]]. These are ~TiddlyWikis with added plugins and configurations to facilitate a certain use-case. These are great starting points if you want to quickly jump into TiddlyWiki and start using it without spending too much time configuring yourself.
<div class="tc-link-info">

View File

@ -1,10 +1,10 @@
created: 20150630205511173
modified: 20220226175543038
modified: 20230803053548871
tags:
title: Contributor License Agreement
type: text/vnd.tiddlywiki
Like other OpenSource projects, TiddlyWiki5 needs a signed contributor license agreement from individual contributors. This is a legal agreement that allows contributors to assert that they own the copyright of their contribution, and that they agree to license it to the UnaMesa Association (the legal entity that owns TiddlyWiki on behalf of the community).
Like other OpenSource projects, TiddlyWiki5 needs a signed contributor license agreement from individual contributors. This is a legal agreement that allows contributors to assert that they own the copyright of their contribution, and that they agree to license it to the [[UnaMesa]] Association (the legal entity that owns TiddlyWiki on behalf of the community).
* For individuals use: [[licenses/CLA-individual|https://github.com/Jermolene/TiddlyWiki5/tree/tiddlywiki-com/licenses/cla-individual.md]]
* For entities use: [[licenses/CLA-entity|https://github.com/Jermolene/TiddlyWiki5/tree/tiddlywiki-com/licenses/cla-entity.md]]

View File

@ -1,10 +1,10 @@
created: 20140216102454178
modified: 20160617101212889
modified: 20230803045407958
tags: Concepts
title: ColourPalettes
type: text/vnd.tiddlywiki
A colour palette is a [[data tiddler|DataTiddlers]] that supplies a [[CSS]] colour value, such as ''yellow'' or ''#fe0'', for each of several colour names, like this:
A colour palette is a [[data tiddler|DataTiddlers]] that supplies a [[CSS|Cascading Style Sheets]] colour value, such as ''yellow'' or ''#fe0'', for each of several colour names, like this:
```
page-background: #fe0

View File

@ -1,5 +1,7 @@
title: ShadowTiddlers
created: 20230803052544962
modified: 20230803052604957
tags: Concepts
title: ShadowTiddlers
\define actions()
<$action-setfield $tiddler="$:/state/tab/moresidebar-1850697562" $field="text" $value="$:/core/ui/MoreSideBar/Shadows"/>
@ -13,7 +15,7 @@ ShadowTiddlers are tiddlers that are loaded from [[Plugins]] at the wiki startup
!! Overriding Shadow Tiddlers to modify plugins
A ShadowTiddler can be overridden with an ordinary tiddler of the same name. This leaves the shadow tiddler intact but the plugin will use the overriding tiddler in its place, effectively allowing users to modify the behaviour of plugins.
A [[ShadowTiddler|ShadowTiddlers]] can be overridden with an ordinary tiddler of the same name. This leaves the shadow tiddler intact but the plugin will use the overriding tiddler in its place, effectively allowing users to modify the behaviour of plugins.
Users are cautioned against overriding shadow tiddlers because if the shadow tiddler is changed in a plugin update, the overriding tiddler may no longer perform as intended. To remedy this, the overriding tiddler may be modified or deleted. If the overriding tiddler is deleted, then the plugin falls back to using the original shadow tiddler.

View File

@ -1,5 +1,5 @@
created: 20201123172925848
modified: 20211126120310891
modified: 20230803052005116
tags: [[Customise TiddlyWiki]]
title: Alternative page layouts
type: text/vnd.tiddlywiki
@ -8,7 +8,7 @@ type: text/vnd.tiddlywiki
! Creating an alternative page layout
Creating an alternative layout goes beyond [[adding or removing features|Page and tiddler layout customisation]] from the default interface and allows you to create an entirely new layout from scratch.
Creating an alternative layout goes beyond [[adding or removing features|Customising TiddlyWiki's user interface]] from the default interface and allows you to create an entirely new layout from scratch.
To create an alternative page layout and have the ability to switch to it, you need to create an alternative page template tiddler with the [[SystemTag: $:/tags/Layout]].

View File

@ -1,5 +1,5 @@
created: 20211124205415217
modified: 20211126162937536
modified: 20230803050345698
tags: [[Customise TiddlyWiki]]
title: Creating new toolbar buttons
type: text/vnd.tiddlywiki
@ -8,7 +8,7 @@ Let's say you have a skeleton tiddler called 'Recipe template', and you want to
# You will want an image for your button. If none of the core images (shadow tiddlers with the prefix $:/core/images/) work for you, then you will need to create or acquire an SVG image (for example, one of the images at http://flaticon.com), drag it into your file so that it becomes a tiddler, edit the tiddler and adjust the height and width to 22px
# You will want to create the tiddler that contains your tiddler. Create it, title it, and add the button code (see the code at the bottom of this tiddler for an example, with hints where you will need to adapt it). Tag it [[$:/tags/ViewToolbar]]
# You will need to create a tiddler that tells TiddlyWiki whether your button should be visible in the toolbar or hidden. Let's title it [[$:/config/ViewToolbarButtons/Visibility/Recipe]]. Type `show` into the text area, and save. If you want to hide it, type `hide` into the text area and save. The button will also be accessable from the ''ControlPanel : Appearance : Toolbars : ViewToolbar'' tab
# You will need to create a tiddler that tells TiddlyWiki whether your button should be visible in the toolbar or hidden. Let's title it [[$:/config/ViewToolbarButtons/Visibility/Recipe]]. Type `show` into the text area, and save. If you want to hide it, type `hide` into the text area and save. The button will also be accessable from the ''Control Panel : Appearance : Toolbars : View Toolbar'' tab
# You will want to position the button properly. Open the tiddler $:/tags/ViewToolbar and insert your button tiddler's title in the appropriate place in the list field.
```

View File

@ -1,10 +1,12 @@
created: 20130825161100000
modified: 20200104111952539
modified: 20230803051056946
tags: Definitions
title: TiddlyFox
type: text/vnd.tiddlywiki
TiddlyFox is an extension for older versions of Firefox that allows standalone TiddlyWiki files to save their changes directly to the file system. TiddlyFox works on both desktop and smartphone versions of [[Firefox]]. See [[Saving with TiddlyFox]] or [[Saving with TiddlyFox on Android]] for detailed instructions.
<<.deprecated-since "FireFox 57" "Saving">>
TiddlyFox is an extension for older versions of Firefox that allows standalone TiddlyWiki files to save their changes directly to the file system. TiddlyFox works on both desktop and smartphone versions of <a href="https://www.mozilla.org/en-US/firefox/">Firefox</a>. See [[Saving with TiddlyFox]] or [[Saving with TiddlyFox on Android]] for detailed instructions.
TiddlyFox is now obsolete due to its incompatibility with the latest versions of Firefox - see [[TiddlyFox Apocalypse]]. There are many alternatives to TiddlyFox, but none that work in precisely the same way -- see GettingStarted for details.

View File

@ -0,0 +1,10 @@
created: 20230803213647552
modified: 20230803214110365
tags: Definitions
title: UnaMesa
<<<
The UnaMesa Association, a 501(c)(3) non-profit, helps entrepreneurs strengthen communities, improve health, and increase well-being. Located in Palo Alto, CA, we incubate projects such as the Magical Bridge Foundation and ~InPlay that translate technology into better social services and new ways of connecting within and across communities. Our overarching goal is to work with networks of social enterprises to develop shared technologies and frameworks for appropriately valuing interactions and relationships in healthcare, education, social services and related domains that recieve short shrift in today's transaction based marketplace. In our view, the purpose of "impact accounting" should be to drive innovations in health, education, social services by making visible which opportunities and experiences are most meaningful in the lives of individuals and families.
<<<
[[UnaMesa|https://unamesa.org/]] holds the intellectual property rights in TiddlyWiki for the benefit of the community, ensuring that it always remains available under the present permissive license. It has supported the TiddlyWiki open source project since 2006.

View File

@ -1,8 +1,8 @@
caption: list
created: 20130830092500000
modified: 20150124202924000
modified: 20230803052727464
tags: Fields
title: ListField
caption: list
type: text/vnd.tiddlywiki
The `list` [[field of a tiddler|TiddlerFields]] is an optional feature that can be used to help structure your content. Its value is a [[title list|Title List]], and it can be used in several ways:
@ -10,4 +10,4 @@ The `list` [[field of a tiddler|TiddlerFields]] is an optional feature that can
* The `list` field of a tiddler that is being used as a tag determines the ordering of the tiddlers that carry that tag - see [[Tagging]] for details
* The `list` [[filter|Filters]] selects the entries from a list
* The `listed` [[filter|Filters]] selects the tiddlers that list the selected tiddler(s)
* The NavigatorWidget manipulates a StoryList tiddler containing a `list` field of the tiddlers that are displayed in the main story column
* The NavigatorWidget manipulates a [[StoryList|$:/StoryList]] tiddler containing a `list` field of the tiddlers that are displayed in the main story column

View File

@ -8,6 +8,6 @@ op-input: a [[selection of titles|Title Selection]]
op-parameter: none
op-output: any non-[[system|SystemTiddlers]] titles that contain [[transclusion|Transclusion]] to the input titles
Each input title is processed in turn. The corresponding tiddler's list of backtranscludes is generated, sorted alphabetically by title, and then [[dominantly appended|Dominant Append]] to the operator's overall output.
<<.from-version 5.3.4>> Similar to [[backlinks|backlinks Operator]]. Each input title is processed in turn. The corresponding tiddler's list of backtranscludes is generated, sorted alphabetically by title, and then [[dominantly appended|Dominant Append]] to the operator's overall output.
<<.operator-examples "backtranscludes">>

View File

@ -6,4 +6,4 @@ tags: shopping
title: Brownies
type: text/vnd.tiddlywiki
//This is a sample shopping list item for the [[Shopping List Example]]//
//This is a sample shopping list item for the [[reduce Operator (Examples)]]//

View File

@ -6,4 +6,4 @@ tags: shopping
title: Chick Peas
type: text/vnd.tiddlywiki
//This is a sample shopping list item for the [[Shopping List Example]]//
//This is a sample shopping list item for the [[reduce Operator (Examples)]]//

View File

@ -6,4 +6,4 @@ tags: shopping
title: Milk
type: text/vnd.tiddlywiki
//This is a sample shopping list item for the [[Shopping List Example]]//
//This is a sample shopping list item for the [[reduce Operator (Examples)]]//

View File

@ -6,4 +6,4 @@ tags: shopping
title: Rice Pudding
type: text/vnd.tiddlywiki
//This is a sample shopping list item for the [[Shopping List Example]]//
//This is a sample shopping list item for the [[reduce Operator (Examples)]]//

View File

@ -1,9 +1,11 @@
created: 201804111739
modified: 201804111739
created: 20180411173900000
modified: 20230803050721827
tags: data-tags-styles [[How to apply custom styles]] $:/tags/Stylesheet
title: Custom data-styles
type: text/vnd.tiddlywiki
\rules only filteredtranscludeinline transcludeinline macrodef macrocallinline html
[data-tiddler-title="Custom styles by data-tiddler-title"] {
border: 1px solid blue;
}

View File

@ -1,5 +1,5 @@
created: 20141117000000000
modified: 20161229175752081
modified: 20230803051806817
tags: Learning
title: How to embed PDF and other documents
type: text/vnd.tiddlywiki
@ -24,7 +24,7 @@ This method be OK as long as your PDF is not too big. There can be concerns if y
!!! 2. Embedding with '_canonical_uri'
The other way is to create a tiddler link to the external file. In this method the file is not actually incorporated into your TW5 file, but can be accessed with the `{{My Image File.jpg}}` transclusion syntax just like an embedded file. The location address of the file can also be changed under [[node.js]]. See [[ExternalImages]] for details of using external images with node.js.
The other way is to create a tiddler link to the external file. In this method the file is not actually incorporated into your TW5 file, but can be accessed with the `{{My Image File.jpg}}` transclusion syntax just like an embedded file. The location address of the file can also be changed under [[Node.js]]. See [[ExternalImages]] for details of using external images with node.js.
Create a tiddler with a field `_canonical_uri`. Put in the local address to the external file. Set the `type` field to `application/pdf`.

View File

@ -1,5 +1,5 @@
created: 20150417155912612
modified: 20160610082700598
modified: 20230803044412567
tags: [[Customise TiddlyWiki]]
title: Setting a page background image
type: text/vnd.tiddlywiki
@ -14,5 +14,5 @@ type: text/vnd.tiddlywiki
#* ''Cover'' causes the background image to be sized so that it completely covers the page. Some of the image may be clipped
#* ''Contain'' causes the background image to be sized so that it fits within the page
Note that the palette ''DarkPhotos'' is provided to make the sidebar more readable on dark background images.
Note that the palette [[DarkPhotos|ColourPalettes]] is provided to make the sidebar more readable on dark background images.

View File

@ -1,5 +1,5 @@
created: 20140904075400000
modified: 20160612132049797
modified: 20230803050201458
tags: [[Working with TiddlyWiki]] Concepts
title: Tagging
type: text/vnd.tiddlywiki
@ -20,7 +20,7 @@ By tagging your tiddlers, you can view, navigate and organise your information i
* You can use [[filters|Filters]] to create lists of tiddlers based on their tags. You can then display any combination of the [[fields|TiddlerFields]] of those tiddlers. For example, you could build a glossary by listing the title and text of all tiddlers tagged ''Glossary''. Such lists can be formatted in any way you wish: e.g. bulleted, numbered or comma-separated.
* There are a number of special ''system tags'' that control the layout of tiddlers and the entire ~TiddlyWiki page. See [[Page and tiddler layout customisation]] for instructions.
* There are a number of special ''system tags'' that control the layout of tiddlers and the entire ~TiddlyWiki page. See [[Page and tiddler layout customisation|Customising TiddlyWiki's user interface]] for instructions.
There are two more things you can do with tags:
@ -28,7 +28,7 @@ There are two more things you can do with tags:
You can use the <<.icon $:/core/images/tag-button>> [[tag manager|$:/TagManager]], found on the ''Tags'' tab under ''More'' in the sidebar, to change the colour of a tag's pill or add an icon to the pill.
* To change the colour, click the button in the ''Colour'' column to select from a colour picker. Alternatively, click the icon in the ''Info'' column, then type a [[CSS]] colour value in the ''Colour'' field
* To change the colour, click the button in the ''Colour'' column to select from a colour picker. Alternatively, click the icon in the ''Info'' column, then type a [[CSS|Cascading Style Sheets]] colour value in the ''Colour'' field
* To change the icon, click the <<.icon $:/core/images/down-arrow>> button in the ''Icon'' column and choose from the list of available icons
! Change the order in which tags are listed

View File

@ -1,11 +1,11 @@
created: 20160810122928198
modified: 20230505104214168
modified: 20230803044526608
tags: [[Editor toolbar]]
title: Using Excise
type: text/vnd.tiddlywiki
! Excise text
From the EditorToolbar you can export selected text to a new tiddler and insert a [[link|Linking in WikiText]], [[Transclusion]] or [[macro|Macros]] in its place. Click ''Excise text'' (<<.icon $:/core/images/excise>>), input name of the new tiddler, and choose excise method.
From the [[Editor toolbar]] you can export selected text to a new tiddler and insert a [[link|Linking in WikiText]], [[Transclusion]] or [[macro|Macros]] in its place. Click ''Excise text'' (<<.icon $:/core/images/excise>>), input name of the new tiddler, and choose excise method.
!! How to excise text
# Highlight the relevant piece of text

View File

@ -1,16 +1,37 @@
created: 20150221154907000
modified: 20150221155706000
title: lingo Macro
tags: Macros [[Core Macros]]
caption: lingo
created: 20150221154907000
modified: 20231028123405895
tags: Macros [[Core Macros]]
title: lingo Macro
type: text/vnd.tiddlywiki
The <<.def lingo>> [[macro|Macros]] relates to the translation of ~TiddlyWiki's user interface into other languages. It returns a piece of text in the user's currently selected language.
Translatable text is supplied by language plugins containing tiddlers with specific titles that start with `$:/language/`.
Translatable text is supplied by
!! Parameters
# Language plugins
# Any l10n (localization) strings outside of the language plugins
!! Language plugins
You can directly pass title to `lingo` macro, when there is a language plugin containing a tiddler with such title that start with `$:/language/`.
;title
: The title of the shadow tiddler that contains the text. The prefix `$:/language/` is added automatically
<<.macro-examples "lingo">>
<<.macro-examples "lingo (for language plugin)">>
!! Any l10n strings
To translate any text that directly placed in user's wiki, instead of in a language plugin, you can set the `lingo-base` variable to teach <<.def lingo>> macro the place to look for.
!!! Parameters
;key
: The last part of title of the tiddler that contains the text. The `<<lingo-base>>` prefix and current language name prefix is added automatically
;lingo-base-fallback
: Optional lingo-base when it is not possible to define `lingo-base` variable (for example, when using this macro in the caption field), you can set the lingo base by passing this parameter
<<.macro-examples "lingo (for custom base)">>
{{lingo Macro (file structure)}}

View File

@ -1,5 +1,5 @@
created: 20150221181835000
modified: 20150221223956000
modified: 20230803034031256
tags: Macros [[Core Macros]]
title: Stylesheet Macros
type: text/vnd.tiddlywiki
@ -16,6 +16,8 @@ The following core [[macros|Macros]] make it easy to specify alternative browser
: for the `x-transition-origin` properties
;`<<background-linear-gradient gradient>>`
: for the `x-linear-gradient` values of the `background-image` property
;`<<column-count columns>>`
: for the `x-column-count` property
The following macros are documented separately:

View File

@ -0,0 +1,21 @@
created: 20231028120432257
modified: 20240206113509050
tags: [[lingo Macro]] [[Macro Examples]]
title: lingo (for custom base) Macro (Examples)
type: text/vnd.tiddlywiki
\define lingo-base() lingo Macro (custom base examples)/
Given the `\define lingo-base() lingo Macro (custom base examples)/`, this example shows the localizaion key `ExampleKey` being translate to the text in [[lingo Macro (custom base examples)/en-GB/ExampleKey]]:
<$macrocall $name=".example" n="1" eg="""<<lingo ExampleKey>>"""/>
This example shows the `lingo-base` can be set as second parameter:
<$macrocall $name=".example" n="2" eg="""<<lingo ExampleKey "lingo Macro (custom base examples)/">>"""/>
When use lingo macro in a [[Inline Mode WikiText]] like [[list|Lists in WikiText]] or [[title|Headings in WikiText]], the parse mode will be inline, so translated text will be inlined too.
<$macrocall $name=".example" n="3" eg="""# <<lingo ExampleKey>>"""/>
<$macrocall $name=".example" n="4" eg="""!! <<lingo ExampleKey>>"""/>

View File

@ -0,0 +1,8 @@
created: 20231028120526948
modified: 20240206113155142
title: lingo Macro (custom base examples)/en-GB/ExampleKey
type: text/vnd.tiddlywiki
This is the translated text of key "~ExampleKey" under lingo-base `lingo Macro (custom base examples)/` (don't forget the tailing slash `/`)
And is multi-line, if it is translated in the block mode by default. (Become single line if set to inline mode.)

View File

@ -0,0 +1,73 @@
created: 20231028120432257
modified: 20240206122408606
tags: [[lingo Macro]] [[Macro Examples]]
title: lingo Macro (file structure)
!! Example file structure for [[TiddlyWiki on Node.js]]
!!! Suggested file structure
When developing a plugin, you may want to organize your language files like this on the file system as [[MultiTiddlerFiles]]:
```tree
├── language
│ ├── en-GB
│ │ ├── Translations.multids
│ │ └── SomeLongText.tid
│ └── zh-Hans
│ ├── Translations.multids
│ └── SomeLongText.tid
├── other files
└── plugin.info
```
See [[$:/plugins/tiddlywiki/menubar/tree]] for an example.
!!! Define Multiple Translations in One Tiddler
And the content of `language/en-GB/Translations.multids` may looks like this:
```multids
title: $:/plugins/yourName/pluginName/language/en-GB/
OpenInteractiveCard: Open Interactive Card
OpenStaticCard: Open Static Card
```
Later you can use it like:
```tid
title: someTiddler
caption: <<lingo OpenStaticCard "$:/plugins/yourName/pluginName/language/">>
\define lingo-base() $:/plugins/yourName/pluginName/language/
\whitespace trim
<<lingo OpenInteractiveCard>>
```
!!! Define Long Text in a regular Tiddler
You can also use a regular tiddler for long text, like `SomeLongText.tid` in the example above, to store a multi-paragraph long text:
```tid
title: $:/plugins/yourName/pluginName/language/en-GB/SomeLongText
!!! SubTitle
This is a long text.
```
Later you can use it like:
```tid
title: someTiddler
\define lingo-base() $:/plugins/yourName/pluginName/language/
!! <<lingo "OpenInteractiveCard">>
<<lingo SomeLongText>>
```
Note that lingo macro will use the [[parse mode|WikiText Parser Modes]] in the current position where this procedure is invoked.

View File

@ -1,7 +1,7 @@
created: 20150221151358000
modified: 20150221160113000
tags: [[lingo Macro]] [[Macro Examples]]
title: lingo Macro (Examples)
title: lingo (for language plugin) Macro (Examples)
type: text/vnd.tiddlywiki
This example shows the text used as the basis for the title of a newly created tiddler:

View File

@ -1,19 +1,19 @@
caption: list-thumbnails
created: 20200612170158838
modified: 20200612171804473
modified: 20230803033631967
tags: Macros [[Core Macros]]
title: list-thumbnails Macro
type: text/vnd.tiddlywiki
The <<.def list-thumbnails>> [[macros|Macros]] are used to create lists of linkable thumbnail panels.
The <<.def list-thumbnails>> [[macros|Macros]] are used to create lists of linkable thumbnail panels. It assumes that the input has <<.field icon>>, <<.field color>>, <<.field background-color>>, <<.field image>>, and <<.field caption>> fields, filled as desired.
!! Parameters
;filter
: filter for selecting thumbnails
: A [[filter|Filters]] for selecting thumbnails
;width
:Width of thumbnail (default 280 pixels)
: A width in px for the thumbnail, defaulting to `280`
;height
:Height of thumbnail (default 157 pixels)
: A height in px for the thumbnail, defaulting to `157`
<<.macro-examples "list-thumbnails">>

View File

@ -1,14 +1,29 @@
caption: thumbnail
created: 20150325172203603
modified: 20150325172336079
modified: 20230803033450805
tags: Macros [[Core Macros]]
title: thumbnail Macro
type: text/vnd.tiddlywiki
The <<.def thumbnail>> [[macros|Macros]] are used to create linkable thumbnail panels.
The <<.def thumbnail>> [[macro|Macros]] is used to create linkable thumbnail panels. An alternative <<.def thumbnail-right>> macro uses the same parameters, but floats to the right of its container.
!! Parameters
(none)
;link
: The tiddler to link to
;icon
: An icon to place in the center of the thumbnail. Must be enclosed in curly brackets
;color
: A color for the icon
;background-color
: A background color if there is no image. Does not show if the image has transparency
;image
: A background image for the thumbnail
;caption
: A caption for the element
;width
: A width in px for the thumbnail, defaulting to `280`
;height
: A height in px for the thumbnail, defaulting to `157`
<<.macro-examples "thumbnail">>
<<.macro-examples "thumbnail">>

View File

@ -1,5 +1,5 @@
created: 20191012080221911
modified: 20191013094002890
modified: 20230803052515281
tags: Mechanisms
title: WikificationMechanism
type: text/vnd.tiddlywiki
@ -8,8 +8,8 @@ type: text/vnd.tiddlywiki
It is composed of several distinct steps:
* ParserMechanism: reading the text of tiddlers and scanning for wikitext constructions, outputting a tree representation of the resulting structure. It is an expensive process so parse trees are cached, and only need to be updated if the corresponding tiddler is changed
* WidgetMechanism: starting with a specified root tiddler, recursively instantiate a widget for each parse tree node making a rendering tree. Widgets can optionally also create DOM nodes
* [[ParserMechanism|WikiText parser mode transitions]]: reading the text of tiddlers and scanning for wikitext constructions, outputting a tree representation of the resulting structure. It is an expensive process so parse trees are cached, and only need to be updated if the corresponding tiddler is changed
* [[WidgetMechanism|Widgets]]: starting with a specified root tiddler, recursively instantiate a widget for each parse tree node making a rendering tree. Widgets can optionally also create DOM nodes
* RefreshMechanism: handling changes to the tiddler store by selectively and efficiently updating a rendering tree
This mechanism is used in the browser to build TiddlyWiki's main interactive page. At startup, the tiddler $:/core/ui/PageTemplate is parsed and rendered to the DOM, recursively pulling in other tiddlers to build the entire user interface. Any user interactions -- following a link, clicking a button, or typing in a text box -- trigger a change in the tiddler store which then automatically propagates through the widget tree. For example, if the user clicks a link to navigate to a new tiddler, the following steps take place:

View File

@ -1,6 +1,6 @@
caption: tm-edit-bitmap-operation
created: 20160424204236050
modified: 20230723214716576
modified: 20230803045807664
tags: Messages
title: WidgetMessage: tm-edit-bitmap-operation
type: text/vnd.tiddlywiki
@ -37,7 +37,7 @@ A `tm-edit-bitmap-operation` invokes one of the available operations on a __surr
|//{any other params}// |Any other parameters are made available as variables within the context of the widget message. |
The `tm-edit-bitmap-operation` message is usually generated by a ButtonWidget or an ActionWidget and is handled by the surrounding bitmap editor.
The `tm-edit-bitmap-operation` message is usually generated by a ButtonWidget or an [[ActionWidget|ActionWidgets]] and is handled by the surrounding bitmap editor.
! Bitmap Operations

View File

@ -1,6 +1,6 @@
caption: tm-edit-text-operation
created: 20160424211339792
modified: 20230723214636245
modified: 20230803045746596
tags: Messages
title: WidgetMessage: tm-edit-text-operation
type: text/vnd.tiddlywiki
@ -123,7 +123,7 @@ A `tm-edit-text-operation` invokes one of the available operations on a __surrou
|param |Name of the operation to be executed, see ''below'' for a list of possible operations |
|//{any other params}// |Any other parameters are made available as variables within the context of the widget message. |
The `tm-edit-text-operation` message is usually generated by a ButtonWidget or an ActionWidget and is handled by the surrounding text editor.
The `tm-edit-text-operation` message is usually generated by a ButtonWidget or an [[ActionWidget|ActionWidgets]] and is handled by the surrounding text editor.
! Text Operations

View File

@ -24,6 +24,10 @@ The following parameters are used:
|header-* |Headers with string values |
|password-header-* |Headers with values taken from the password store |
|password-query-* |Query string parameters with values taken from the password store |
|basic-auth-username |<<.from-version "5.3.4">> Optional username for HTTP basic authentication |
|basic-auth-username-from-store |<<.from-version "5.3.4">> Optional username for HTTP basic authentication, specified as the name of the entry in the password store containing the username |
|basic-auth-password |<<.from-version "5.3.4">> Optional password for HTTP basic authentication |
|basic-auth-password-from-store |<<.from-version "5.3.4">> Optional password for HTTP basic authentication, specified as the name of the entry in the password store containing the password |
|var-* |Variables to be passed to the completion and progress handlers (without the "var-" prefix) |
|bind-status |Title of tiddler to which the status of the request ("pending", "complete", "error") should be bound |
|bind-progress |Title of tiddler to which the progress of the request (0 to 100) should be bound |

View File

@ -1,6 +1,6 @@
created: 20221123223127425
modified: 20230117112244779
tags: Pragma
tags: Pragmas
title: Pragma: \parsermode
type: text/vnd.tiddlywiki

View File

@ -14,7 +14,7 @@ This is the procedure, and the parameter is <<parameter>>.
\end
```
The name wrapped in double angled [[brackets|Brackets]] is used a shorthand way of [[transcluding|Transclusion]] the snippet. Each of these <<.def "procedure calls">> can supply a different set of parameters:
The name wrapped in double angled [[brackets|Brackets]] is a shorthand way of [[transcluding|Transclusion]] the snippet. Each of these <<.def "procedure calls">> can supply a different set of parameters:
```
<<my-procedure>>

View File

@ -1,12 +1,14 @@
created: 20140103134551508
modified: 20171113131640857
modified: 20230803051340676
tags: [[Saving with TiddlyFox]]
title: Saving with TiddlyFox on Android
type: text/vnd.tiddlywiki
<<.deprecated-since "FireFox 57" "Saving">>
(Alternatively, see the [[video tutorial|TiddlyWiki on Firefox for Android Video]])
# Ensure you have the latest version of [[Firefox for Android]]
# Ensure you have the latest version of [[Firefox for Android|http://getfirefox.com]]
#* http://getfirefox.com
# Install the latest release of the TiddlyFox extension from:
#* https://addons.mozilla.org/en-GB/firefox/addon/tiddlyfox/

View File

@ -10,4 +10,4 @@ tags: Saving Firefox
title: Saving with TiddlyFox
type: text/vnd.tiddlywiki
<<.deprecated-since "FireFox 57" "Saving with FireFox">>
<<.deprecated-since "FireFox 57" "Saving with FireFox">>

View File

@ -0,0 +1,14 @@
created: 20230803034230294
modified: 20230803043848449
tags: [[Macro Examples]] [[tag-pill Macro]]
title: tag-pill Macro (Examples)
This example displays the [[Community]] tag as a clickable element with no dropdown:
<$transclude $variable=".example" n="1" eg="""<<tag-pill Community>>"""/>
This example displays the [[Definitions]] tag as an unclickable, but still-styled, `big` element with no dropdown:
<$transclude $variable=".example" n="2" eg="""<<tag-pill Definitions element-tag:"big" element-attributes:"inert">>"""/>

View File

@ -1,12 +1,12 @@
title: EncryptWidget
created: 201310241419
modified: 201310300837
tags: Widgets
caption: encrypt
created: 20131024141900000
modified: 20230803050114889
tags: Widgets
title: EncryptWidget
! Introduction
The encrypt widget renders a filtered list of tiddlers to an encrypted block with the password currently held in the PasswordVault. The encrypted block can subsequently be decrypted by the TiddlyWiki5 BootMechanism. See the EncryptionMechanism for more details.
The encrypt widget renders a filtered list of tiddlers to an encrypted block with the password currently held in the PasswordVault. The encrypted block can subsequently be decrypted by the TiddlyWiki5 BootMechanism. See the [[EncryptionMechanism|Encryption]] for more details.
! Content and Attributes

View File

@ -1,14 +1,14 @@
caption: reveal
created: 20131024141900000
jeremy: tiddlywiki
modified: 20201121100908827
modified: 20230803052644851
tags: Widgets
title: RevealWidget
type: text/vnd.tiddlywiki
! Introduction
The reveal widget hides or shows its content depending upon the value of a [[state tiddler|StateTiddlers]]. The type of the widget determines the condition for the content being displayed:
The reveal widget hides or shows its content depending upon the value of a [[state tiddler|StateTiddler]]. The type of the widget determines the condition for the content being displayed:
* type=''match'': the content is displayed if the state tiddler matches the text attribute value
* type=''nomatch'': the content is displayed if the state tiddler doesn't match the text attribute value

View File

@ -1,5 +1,5 @@
created: 20140908163900000
modified: 20201228143412000
modified: 20230803052125981
tags: Learning
title: Sharing your tiddlers with others
type: text/vnd.tiddlywiki
@ -10,7 +10,7 @@ There are a number of ways that you can share [[tiddlers|Tiddlers]] or your whol
*You can publish your ~TiddlyWiki online and grab a link to send or message to others:
**A link to the web address of the whole ~TiddlyWiki file
**A [[permalink|PermaLinks]] (<<.icon $:/core/images/permalink-button>>) to a specific tiddler
**A [[permaview|PermaViews]] (<<.icon $:/core/images/permaview-button>>) link of all the currently open tiddlers
**A [[permaview|PermaLinks]] (<<.icon $:/core/images/permaview-button>>) link of all the currently open tiddlers
* You can [[share a Dropbox link to your TiddlyWiki|Sharing a TiddlyWiki on Dropbox]]
* You can [[export tiddlers|How to export tiddlers]] (<<.icon $:/core/images/export-button>>) in a variety of formats including text, static HTML and comma separated values (ie spreadsheet compatible)
*You can also share tiddlers merely by making your ~TiddlyWiki accessible to others, for example by publishing it online, so that they can [[import tiddlers|Importing Tiddlers]] from it

View File

@ -28,6 +28,7 @@ Encryption/ClearPassword/Caption: résilier le mot de passe
Encryption/ClearPassword/Hint: Résilie le mot de passe et sauvegarde ce wiki sans chiffrement
Encryption/SetPassword/Caption: affecter un mot de passe
Encryption/SetPassword/Hint: Affecte un mot de passe pour sauvegarde une version chiffrée de ce wiki
EmergencyDownload/Caption: Télécharge les tidders au format json
ExportPage/Caption: exporter tout
ExportPage/Hint: Exporte tous les tiddlers
ExportTiddler/Caption: exporter ce tiddler

View File

@ -206,6 +206,12 @@ Stylesheets/Caption: Feuilles de style
Stylesheets/Expand/Caption: Tout déployer
Stylesheets/Hint: Voici le rendu CSS courant pour les tiddlers feuilles de style tagués avec <<tag "$:/tags/Stylesheet">>
Stylesheets/Restore/Caption: Restaurer
TestCases/Caption: Scénarios de test
TestCases/Hint: Les scénarios de test sont des exemples sans dépendance extérieure, conçus à des fins de tests et d'apprentissage
TestCases/All/Caption: Tous les scénarios de test
TestCases/All/Hint: Tous les scénarios de test définis dans ce wiki
TestCases/Failed/Caption: Scénarios de test en échec
TestCases/Failed/Hint: Seulement les scénarios de test qui échouent
Theme/Caption: Thème
Theme/Prompt: Thème courant :
TiddlerFields/Caption: Champs des tiddlers

View File

@ -9,7 +9,7 @@ config: Données à inclure dans `$tw.config`.
filteroperator: Méthodes d'opérateurs pour les filtres.
global: Données globales à inclure dans `$tw`.
info: Publie des informations système via le pseudo-plugin [[$:/temp/info-plugin]].
isfilteroperator: Opérandes pour l'opérateur de filtre ''is''.
isfilteroperator: Paramètres pour l'opérateur de filtre ''is''.
library: Module générique pour les modules ~JavaScript de portée générale.
macro: Définitions de macros ~JavaScript.
parser: Parseurs pour divers types de contenu.

View File

@ -79,6 +79,9 @@ table-footer-background: Fond pour les bas de tableau
table-header-background: Fond pour les en-têtes de tableau
tag-background: Fond pour les tags
tag-foreground: Premier plan pour les tags
testcase-accent-level-1: Couleur d'accentuation des scénarios de test de premier niveau
testcase-accent-level-2: Couleur d'accentuation des scénarios de test de profondeur 2
testcase-accent-level-3: Couleur d'accentuation des scénarios de test de profondeur 3 et plus
tiddler-background: Fond pour les tiddlers
tiddler-border: Bordure pour les tiddlers
tiddler-controls-foreground-hover: Premier plan au passage de la souris sur les boutons de commande d'un tiddler

View File

@ -4,6 +4,7 @@ _canonical_uri: L'URI complet vers le contenu externe d'un tiddler image
author: Nom de l'auteur d'un plugin
bag: Nom du <q>bag</q> d'où provient le tiddler
caption: Texte à afficher sur un onglet ou un bouton
class: La classe CSS appliquée à un tiddler lors de son rendu — voir [[Custom styles by user-class]]. Également utilisée pour les [[Modals]]
code-body: Le template de visualisation affichera ce tiddler comme du code si la valeur est ''yes''
color: Couleur CSS associée au tiddler
component: Nom du composant responsable pour un [[tiddler d'alerte|AlertMechanism]]
@ -29,8 +30,9 @@ name: Dans le cas d'un tiddler plugin, le nom associé à ce plugin
parent-plugin: Dans le cas d'un tiddler plugin, spécifie de quel plugin il est un sous-plugin
plugin-priority: Dans le cas d'un tiddler plugin, un nombre indiquant sa priorité
plugin-type: Dans le cas d'un tiddler plugin, le type du plugin
revision: Numéro de révision du tiddler présent sur le serveur
stability: Le statut de développement d'un plugin : deprecated, experimental, stable, ou legacy
released: Date de version d'un TiddlyWiki
revision: Numéro de révision du tiddler présent sur le serveur
source: URL source associée à ce tiddler
subtitle: Texte du sous-titre pour une fenêtre modale
tags: Liste des tags associés à un tiddler

View File

@ -10,7 +10,7 @@ Lance la séquence des commandes retournées par un filtre
Exemples
```
--commands "[enlist{$:/commandes-build-sous-forme-de-texte}]"
--commands "[enlist:raw{$:/commandes-build-sous-forme-de-texte}]"
```
```

View File

@ -12,8 +12,23 @@ description: Enregistre un wiki dans un nouveau dossier wiki
* Les plugins appartenant à la bibliothèque officielle de plugins sont remplacés par des références à ces plugins dans le fichier `tiddlywiki.info`
* Les plugins sur mesure sont déballés dans leur propre dossier
Les options suivantes sont acceptées :
* ''filter'': une expression filtre qui définit les tiddlers à inclure en sortie.
* ''explodePlugins'': "yes" par défaut
** ''yes'' "explosera" les plugins en fichiers séparés (un par tiddler) et les sauvegardera dans le répertoire plugin sous le dossier principal du wiki
** ''no'' empêchera l'explosion des plugins en autant de fichiers que de tiddlers qui les constituaient. Le plugin sera sauvegardé en un seul tiddler JSON sous le dossier tiddlers/.
On notera que les deux options ''explodePlugins'' produiront des dossiers wiki qui ne changeront pas le wiki original. La différence réside dans la manière dont les plugins sont représentés sous le dossier principal du wiki.
On utilise typiquement cette commande avec la commande `--load` pour convertir un fichier TiddlyWiki HTML en un dossier wiki&nbsp;:
```
tiddlywiki --load ./monwiki.html --savewikifolder ./mondossierwiki
```
Sauvegarde des plugins directement sous le répertoire tiddlers/ du dossier wiki cible :
```
tiddlywiki --load ./mywiki.html --savewikifolder ./mywikifolder explodePlugins=no
```

View File

@ -1,5 +1,5 @@
title: $:/language/Help/server
description: Fournit une interface serveur HTTP à TiddlyWiki (déprécié en faveur de la nouvelle commande listen)
description: (déprécié en faveur de la nouvelle commande 'listen') Fournit une interface serveur HTTP à TiddlyWiki
Ancienne commande pour servir un wiki sur HTTP.

View File

@ -1,5 +1,5 @@
title: $:/language/Docs/Types/application/javascript
description: Code JavaScript
description: code JavaScript
name: application/javascript
group: Développeur
group-sort: 2
group: Developer
group-sort: 2

View File

@ -1,5 +1,5 @@
title: $:/language/Docs/Types/application/json
description: Données au format JSON
description: données JSON
name: application/json
group: Développeur
group: Developer
group-sort: 2

View File

@ -1,5 +1,5 @@
title: $:/language/Docs/Types/application/x-tiddler-dictionary
description: Dictionnaire de données
name: application/x-tiddler-dictionary
group: Développeur
group-sort: 2
group: Developer
group-sort: 2

View File

@ -1,5 +1,5 @@
title: $:/language/Docs/Types/image/gif
description: Image au format GIF
description: image GIF
name: image/gif
group: Image
group-sort: 1
group-sort: 1

View File

@ -1,5 +1,5 @@
title: $:/language/Docs/Types/image/jpeg
description: Image au format JPEG
description: image JPEG
name: image/jpeg
group: Image
group-sort: 1

View File

@ -1,5 +1,5 @@
title: $:/language/Docs/Types/image/png
description: Image au format PNG
description: image PNG
name: image/png
group: Image
group-sort: 1

View File

@ -1,5 +1,5 @@
title: $:/language/Docs/Types/image/svg+xml
description: Image au format SVG
description: image SVG
name: image/svg+xml
group: Image
group-sort: 1

View File

@ -1,5 +1,5 @@
title: $:/language/Docs/Types/image/x-icon
description: Fichier icone au format ICO
description: icône au format ICO
name: image/x-icon
group: Image
group-sort: 1

View File

@ -1,5 +1,5 @@
title: $:/language/Docs/Types/text/css
description: Feuille de style CSS statique
description: Feuille de style statique
name: text/css
group: Développeur
group: Developer
group-sort: 2

View File

@ -1,5 +1,5 @@
title: $:/language/Docs/Types/text/html
description: Marquage HTML
name: text/html
group: Texte
group-sort: 0
group: Text
group-sort: 0

View File

@ -1,5 +1,5 @@
title: $:/language/Docs/Types/text/plain
description: Format texte
description: Texte simple
name: text/plain
group: Texte
group: Text
group-sort: 0

View File

@ -1,5 +1,5 @@
title: $:/language/Docs/Types/text/vnd.tiddlywiki
description: TiddlyWiki version 5
description: TiddlyWiki 5
name: text/vnd.tiddlywiki
group: Texte
group: Text
group-sort: 0

View File

@ -1,5 +1,5 @@
title: $:/language/Docs/Types/text/x-tiddlywiki
description: TiddlyWiki Classic
name: text/x-tiddlywiki
group: Texte
group: Text
group-sort: 0

View File

@ -569,3 +569,5 @@ Kim I. McKinley, @PotOfCoffee2Go, 2024/03/16
Anders Jarmund, @andjar, 2024/04/05
@sarna, 2024/04/28
Fokzo Kat, @CyberFoxar, 2024/05/20

View File

@ -4,13 +4,13 @@ title: $:/plugins/tiddlywiki/aws/lambda/sjcl
(function() {
var module;
var module, window = {};
global.sjcl = (function() {
{{ $:/library/sjcl.js ||$:/core/templates/plain-text-tiddler}}
return sjcl;
return window.sjcl;
})();

View File

@ -3,12 +3,13 @@ tags: $:/tags/ControlPanel/Toolbars
caption: Menu Bar
\define config-base() $:/config/plugins/menubar/MenuItems/Visibility/
\define lingo-base() $:/plugins/tiddlywiki/menubar/language/
! Menu Bar Configuration
! <<lingo Config/Heading1>>
!! Menu Items
!! <<lingo Config/MenuItems/Heading>>
Select which menu items will be shown. You can also drag items to reorder them.
<<lingo Config/MenuItems/Description>>
<$set name="tv-config-toolbar-icons" value="yes">
@ -20,18 +21,18 @@ Select which menu items will be shown. You can also drag items to reorder them.
</$set>
!! Breakpoint Position
!! <<lingo Config/BreakpointPosition/Heading>>
The breakpoint position between narrow and wide screens. Should include CSS units (eg. `400px`).
<<lingo Config/BreakpointPosition/Description>>
<$edit-text tiddler="$:/config/plugins/menubar/breakpoint" default="" tag="input"/>
!! Contents Tag
!! <<lingo Config/ContentsTag/Heading>>
The tag for the ~TableOfContents used in the Contents dropdown
<<lingo Config/ContentsTag/Description>>
<$edit-text tiddler="$:/config/plugins/menubar/TableOfContents/Tag" default="" tag="input"/>
!! Menu Bar Colours
!! <<lingo Config/MenuBarColours/Heading>>
To change the colour of the menu bar, define the colours `menubar-foreground` and `menubar-background` in the currently selected palette
<<lingo Config/MenuBarColours/Description>>

View File

@ -1,6 +1,6 @@
title: $:/plugins/tiddlywiki/menubar/items/contents
caption: Contents
description: Table of Contents
caption: <<lingo Items/TOC/Name $:/plugins/tiddlywiki/menubar/language/>>
description: <<lingo Items/TOC/Description $:/plugins/tiddlywiki/menubar/language/>>
is-dropdown: yes
tags: $:/tags/MenuBar

View File

@ -1,7 +1,7 @@
title: $:/plugins/tiddlywiki/menubar/items/hamburger
tags: $:/tags/MenuBar
caption: Hamburger
description: Show the full menu bar on a narrow screen
caption: <<lingo Items/Hamburger/Name $:/plugins/tiddlywiki/menubar/language/>>
description: <<lingo Items/Hamburger/Description $:/plugins/tiddlywiki/menubar/language/>>
custom-menu-content: {{$:/plugins/tiddlywiki/menubar/items/hamburger}}
show-when: narrow

View File

@ -1,7 +1,7 @@
title: $:/plugins/tiddlywiki/menubar/items/pagecontrols
tags: $:/tags/MenuBar
description: Page controls from the sidebar
caption: Page controls
description: <<lingo Items/PageControls/Name $:/plugins/tiddlywiki/menubar/language/>>
caption: <<lingo Items/PageControls/Name $:/plugins/tiddlywiki/menubar/language/>>
custom-menu-content: <$transclude tiddler="$:/plugins/tiddlywiki/menubar/items/pagecontrols" mode="inline"/>
\whitespace trim

View File

@ -1,7 +1,7 @@
title: $:/plugins/tiddlywiki/menubar/items/search
custom-menu-content: {{$:/plugins/tiddlywiki/menubar/items/search}}
description: Search
caption: Search
description: <<lingo Items/Search/Name $:/plugins/tiddlywiki/menubar/language/>>
caption: <<lingo Items/Search/Name $:/plugins/tiddlywiki/menubar/language/>>
tags: $:/tags/MenuBar
\define cancel-search-actions()

View File

@ -1,7 +1,7 @@
title: $:/plugins/tiddlywiki/menubar/items/server
tags: $:/tags/MenuBar
description: Server options
caption: Server
description: <<lingo Items/Server/Description $:/plugins/tiddlywiki/menubar/language/>>
caption: <<lingo Items/Server/Name $:/plugins/tiddlywiki/menubar/language/>>
custom-menu-content: <$transclude tiddler="$:/plugins/tiddlywiki/menubar/items/server" mode="inline"/>
<$list filter="[[$:/status/IsLoggedIn]get[text]else[no]match[yes]]" variable="ignore">

View File

@ -1,6 +1,6 @@
title: $:/plugins/tiddlywiki/menubar/items/sidebar
caption: Sidebar
description: Sidebar
caption: <<lingo Items/Sidebar/Name $:/plugins/tiddlywiki/menubar/language/>>
description: <<lingo Items/Sidebar/Name $:/plugins/tiddlywiki/menubar/language/>>
is-dropdown: yes
tags: $:/tags/MenuBar

View File

@ -1,7 +1,7 @@
title: $:/plugins/tiddlywiki/menubar/items/topleftbar
tags: $:/tags/MenuBar
description: Items from $:/tags/TopLeftBar
caption: Legacy Top Left Bar
description: <<lingo Items/TopLeftBar/Description $:/plugins/tiddlywiki/menubar/language/>>
caption: <<lingo Items/TopLeftBar/Name $:/plugins/tiddlywiki/menubar/language/>>
custom-menu-content: <$transclude tiddler="$:/plugins/tiddlywiki/menubar/items/topleftbar" mode="inline"/>
<$list filter="[all[shadows+tiddlers]tag[$:/tags/TopLeftBar]!has[draft.of]]" variable="listItem" storyview="pop">

View File

@ -1,7 +1,7 @@
title: $:/plugins/tiddlywiki/menubar/items/toprightbar
tags: $:/tags/MenuBar
description: Items from $:/tags/TopRightBar
caption: Legacy Top Right Bar
description: <<lingo Items/TopRightBar/Description $:/plugins/tiddlywiki/menubar/language/>>
caption: <<lingo Items/TopRightBar/Name $:/plugins/tiddlywiki/menubar/language/>>
custom-menu-content: <$transclude tiddler="$:/plugins/tiddlywiki/menubar/items/toprightbar" mode="inline"/>
custom-menu-styles-wide: float: right;

View File

@ -0,0 +1,25 @@
title: $:/plugins/tiddlywiki/menubar/language/en-GB/
Config/Heading1: Menu Bar Configuration
Config/MenuItems/Heading: Menu Items
Config/MenuItems/Description: Select which menu items will be shown. You can also drag items to reorder them.
Config/BreakpointPosition/Heading: Breakpoint Position
Config/BreakpointPosition/Description: The breakpoint position between narrow and wide screens. Should include CSS units (eg. `400px`).
Config/ContentsTag/Heading: Contents Tag
Config/ContentsTag/Description: The tag for the ~TableOfContents used in the Contents dropdown
Config/MenuBarColours/Heading: Menu Bar Colours
Config/MenuBarColours/Description: To change the colour of the menu bar, define the colours `menubar-foreground` and `menubar-background` in the currently selected palette
Items/TOC/Name: Contents
Items/TOC/Description: Table of Contents
Items/Hamburger/Name: Hamburger
Items/Hamburger/Description: Show the full menu bar on a narrow screen
Items/PageControls/Name: Page controls
Items/PageControls/Description: Page controls from the sidebar
Items/Search/Name: Search
Items/Server/Name: Server
Items/Server/Description: Server options
Items/Sidebar/Name: Sidebar
Items/TopLeftBar/Name: Legacy Top Left Bar
Items/TopLeftBar/Description: Items from $:/tags/TopLeftBar
Items/TopRightBar/Name: Legacy Top Right Bar
Items/TopRightBar/Description: Items from $:/tags/TopRightBar

View File

@ -0,0 +1,30 @@
title: $:/plugins/tiddlywiki/menubar/language/en-GB/readme
!! Introduction
This plugin provides a menu bar with the following features:
* Menu items take the form of simple text links, dropdowns, or entirely custom content
* Menu items can be individually enabled via the control panel
* Responds to reduced screen width by abbreviating the menu items to a "hamburger" dropdown
!! Menu Item Tiddlers
Menu items are tagged <<tag $:/tags/MenuBar>>. The following fields are used by this plugin:
|!Field Name |!Purpose |
|title |Each menu item must have a unique title (not shown to the user) |
|description |Description for use in listings |
|tags |Must contain `$:/tags/MenuBar` |
|caption |The text that is displayed for the menu item. Avoid links, using `~` to suppress CamelCase links if required |
|target |For simple link menu items specifies a tiddler title as the target of the link |
|is-dropdown |Set to `yes` to indicate a dropdown menu item |
|dropdown-position |Optional position for the dropdown (can be ''left'', ''above'', ''aboveleft'', ''aboveright'', ''right'', ''belowleft'', ''belowright'' or ''below'') |
|text |For dropdown menu items, specifies the body of the dropdown |
|custom-menu-content |Optional wikitext to be displayed in place of the caption |
|custom-menu-styles-wide |Optional string of styles to be applied to menu item when the menubar is wide |
|custom-menu-styles-narrow |Optional string of styles to be applied to menu item when the menubar is narrow |
Custom menu items should make sure that the clickable link or button is an immediate child, and not wrapped in another element.
Note that menu items can be pushed to the right of the menu bar setting the ''custom-menu-styles'' field to `float: right;`.

View File

@ -0,0 +1,25 @@
title: $:/plugins/tiddlywiki/menubar/language/zh-Hans/
Config/Heading1: 菜单栏配置
Config/MenuItems/Heading: 菜单项
Config/MenuItems/Description: 选择要显示的菜单项。您还可以通过拖动项目来重新排序。
Config/BreakpointPosition/Heading: 响应式断点位置
Config/BreakpointPosition/Description: 窄屏和宽屏之间的分界点位置。应包含 CSS 单位(如 `400px`)。
Config/ContentsTag/Heading: 内容标签
Config/ContentsTag/Description: 内容下拉菜单中使用的 TOC 目录标签
Config/MenuBarColours/Heading: 菜单栏颜色
Config/MenuBarColours/Description: 要更改菜单栏的颜色,请在当前选定的调色板中定义颜色 `menubar-foreground` 和 `menubar-background`。
Items/TOC/Name: 内容
Items/TOC/Description: 目录
Items/Hamburger/Name: 抽屉
Items/Hamburger/Description: 在窄屏幕上显示完整的菜单栏
Items/PageControls/Name: 页面控件
Items/PageControls/Description: 来自侧边栏的页面控件
Items/Search/Name: 搜索
Items/Server/Name: 服务器
Items/Server/Description: 服务器选项
Items/Sidebar/Name: 侧边栏
Items/TopLeftBar/Name: 旧版左上角栏
Items/TopLeftBar/Description: 来自 $:/tags/TopLeftBar 的项目
Items/TopRightBar/Name: 旧版右上角栏
Items/TopRightBar/Description: 来自 $:/tags/TopRightBar 的项目

View File

@ -0,0 +1,30 @@
title: $:/plugins/tiddlywiki/menubar/language/zh-Hans/readme
!! 简介
该插件提供的菜单栏具有以下功能:
* 菜单项的形式可以是简单的文本链接、下拉菜单或完全自定义的内容
* 可通过控制面板单独启用菜单项
* 通过将菜单项缩减为抽屉式导航(也叫"汉堡包"下拉菜单)来应对屏幕宽度减小的情况
!! 菜单项标记
菜单项被标记为 <<tag $:/tags/MenuBar>>。本插件使用以下字段:
|!字段名称 |!用途 |
|title |每个菜单项必须有一个唯一的标题(不显示给用户)|
|description |在列表中使用的描述 |
|tags |必须包含 `$:/tags/MenuBar` |
|caption |菜单项显示的文本。避免使用链接,必要时使用 `~` 来抑制 CamelCase 链接 |
|target |对于简单链接菜单项,指定一个 tiddler 标题作为链接的目标 |
|is-dropdown |设置为 `yes` 表示下拉菜单项 |
|dropdown-position |下拉位置(可选 "左"、"上"、"左上" 等,需要使用英文 ''left'', ''above'', ''aboveleft'', ''aboveright'', ''right'', ''belowleft'', ''belowright'', ''below'' |
|text |对于下拉菜单项,指定下拉菜单的正文 |
|custom-menu-content |可选显示的维基文本,以代替标题 |
|custom-menu-styles-wide |当菜单栏是宽模式时,应用于菜单项的样式字符串选项 |
|custom-menu-styles-narrow |当菜单栏是窄模式时,应用于菜单项的样式的可选字符串 |
自定义菜单项应确保可点击链接或按钮是直接子元素,而不是包裹在其他元素中。
请注意,菜单项可以通过将 ''custom-menu-styles'' 字段设置为 `float: right;` 而推到菜单栏的右侧。

View File

@ -1,30 +1,5 @@
title: $:/plugins/tiddlywiki/menubar/readme
!! Introduction
\define lingo-base() $:/plugins/tiddlywiki/menubar/language/
This plugin provides a menu bar with the following features:
* Menu items take the form of simple text links, dropdowns, or entirely custom content
* Menu items can be individually enabled via the control panel
* Responds to reduced screen width by abbreviating the menu items to a "hamburger" dropdown
!! Menu Item Tiddlers
Menu items are tagged <<tag $:/tags/MenuBar>>. The following fields are used by this plugin:
|!Field Name |!Purpose |
|title |Each menu item must have a unique title (not shown to the user) |
|description |Description for use in listings |
|tags |Must contain `$:/tags/MenuBar` |
|caption |The text that is displayed for the menu item. Avoid links, using `~` to suppress CamelCase links if required |
|target |For simple link menu items specifies a tiddler title as the target of the link |
|is-dropdown |Set to `yes` to indicate a dropdown menu item |
|dropdown-position |Optional position for the dropdown (can be ''left'', ''above'', ''aboveleft'', ''aboveright'', ''right'', ''belowleft'', ''belowright'' or ''below'') |
|text |For dropdown menu items, specifies the body of the dropdown |
|custom-menu-content |Optional wikitext to be displayed in place of the caption |
|custom-menu-styles-wide |Optional string of styles to be applied to menu item when the menubar is wide |
|custom-menu-styles-narrow |Optional string of styles to be applied to menu item when the menubar is narrow |
Custom menu items should make sure that the clickable link or button is an immediate child, and not wrapped in another element.
Note that menu items can be pushed to the right of the menu bar setting the ''custom-menu-styles'' field to `float: right;`.
<<lingo readme>>

View File

@ -0,0 +1,4 @@
title: $:/plugins/tiddlywiki/menubar/tree
type: text/vnd.tiddlywiki
<<tree prefix:"$:/plugins/tiddlywiki/menubar/">>

View File

@ -1,16 +1,7 @@
title: GettingStarted
tags: $:/tags/GettingStarted
caption: Step 1<br>Syncing
caption: <<lingo GettingStartedStep1 "$:/plugins/tiddlywiki/tiddlyweb/language/">>
Welcome to ~TiddlyWiki and the ~TiddlyWiki community
\define lingo-base() $:/plugins/tiddlywiki/tiddlyweb/language/
Visit https://tiddlywiki.com/ to find out more about ~TiddlyWiki and what it can do.
! Syncing Changes to the Server
Before you can start storing important information in ~TiddlyWiki it is important to make sure that your changes are being reliably saved by the server.
# Create a new tiddler using the {{$:/core/images/new-button}} button in the sidebar on the right
# Click the {{$:/core/images/done-button}} button at the top right of the new tiddler
# Check the ~TiddlyWiki command line for a message confirming the tiddler has been saved
# Refresh the page in the browser to and verify that the new tiddler has been correctly saved
<<lingo GettingStarted>>

View File

@ -4,4 +4,6 @@ url: https://tiddlywiki.com/library/v5.1.23/index.html
caption: {{$:/language/OfficialPluginLibrary}}
enabled: no
The official plugin library is disabled when using the client-server configuration. Instead, plugins should be installed via the `tiddlywiki.info` file, as described [[here|https://tiddlywiki.com/#Installing%20a%20plugin%20from%20the%20plugin%20library]].
\define lingo-base() $:/plugins/tiddlywiki/tiddlyweb/language/
<<lingo ConfigOfficialPluginLibrary>>

View File

@ -0,0 +1,14 @@
title: $:/plugins/tiddlywiki/tiddlyweb/language/en-GB/GettingStarted
Welcome to ~TiddlyWiki and the ~TiddlyWiki community
Visit https://tiddlywiki.com/ to find out more about ~TiddlyWiki and what it can do.
! Syncing Changes to the Server
Before you can start storing important information in ~TiddlyWiki it is important to make sure that your changes are being reliably saved by the server.
# Create a new tiddler using the {{$:/core/images/new-button}} button in the sidebar on the right
# Click the {{$:/core/images/done-button}} button at the top right of the new tiddler
# Check the ~TiddlyWiki command line for a message confirming the tiddler has been saved
# Refresh the page in the browser to and verify that the new tiddler has been correctly saved

View File

@ -0,0 +1,12 @@
title: $:/plugins/tiddlywiki/tiddlyweb/language/en-GB/
ConfigOfficialPluginLibrary: The official plugin library is disabled when using the client-server configuration. Instead, plugins should be installed via the `tiddlywiki.info` file, as described [[here|https://tiddlywiki.com/#Installing%20a%20plugin%20from%20the%20plugin%20library]].
GettingStartedStep1: Step 1<br>Syncing
CopySyncerLogs: Copy syncer logs to clipboard
LoginAs: You are logged in<$reveal state="$:/status/UserName" type="nomatch" text="" default=""> as <strong><$text text={{$:/status/UserName}}/></strong></$reveal>
Readonly: <$reveal state="$:/status/IsReadOnly" type="match" text="yes" default="no"> (read-only)</$reveal>
Login: Login
Logout: Logout
SaveSnapshot: Save snapshot for offline use
Refresh/Label: Refresh from server
Refresh/Button: Get latest changes from the server

View File

@ -0,0 +1,7 @@
title: $:/plugins/tiddlywiki/tiddlyweb/language/en-GB/readme
This plugin runs in the browser to synchronise tiddler changes to and from a TiddlyWeb-compatible server (including TiddlyWiki 5 itself, running on Node.js). It is inert when run under Node.js. Disabling this plugin via the browser can not be undone via the browser since this plugin provides the mechanism to synchronize settings with the server.
Changes made while offline are saved in memory and automatically synchonised with the server when the connection is re-established. However, if the browser tab is closed or another URL is loaded, the in-memory changes will be lost. The [[https://tiddlywiki.com/#BrowserStorage Plugin]] may be added to provide temporary filesystem storage of tiddler changes made while offline and enable them to be synchronised with the server the next time the wiki is loaded in the same browser.
[[Source code|https://github.com/Jermolene/TiddlyWiki5/blob/master/plugins/tiddlywiki/tiddlyweb]]

View File

@ -0,0 +1,14 @@
title: $:/plugins/tiddlywiki/tiddlyweb/language/zh-Hans/GettingStarted
欢迎来到太微和太微社区
访问 https://tiddlywiki.com/ 了解太微的细节和了解它能做什么。
! 同步更改到服务器
在你开始在太微中存储重要信息之前,确保你的修改被服务器可靠地保存是非常重要的。
# 使用右侧边栏的 {{$:/core/images/new-button}} 按钮创建一个新条目
# 点击新条目右上方的 {{$:/core/images/done-button}} 按钮
# 检查太微命令行是否有确认条目已保存的信息
# 刷新浏览器页面,确认新条目已正确保存

View File

@ -0,0 +1,12 @@
title: $:/plugins/tiddlywiki/tiddlyweb/language/zh-Hans/
ConfigOfficialPluginLibrary: 使用客户端-服务器配置时,官方插件库将被禁用。取而代之的是,应按照[[here|https://tiddlywiki.com/#Installing%20a%20plugin%20from%20the%20plugin%20library]]所述,通过 "tiddlywiki.info" 文件安装插件。
GettingStartedStep1: 第一步<br>同步
CopySyncerLogs: 将同步器日志复制到剪贴板
LoginAs: 您目前已登录<$reveal state="$:/status/UserName" type="nomatch" text="" default="">为<strong><$text text={{$:/status/UserName}}/></strong></$reveal>
Readonly: <$reveal state="$:/status/IsReadOnly" type="match" text="yes" default="no">(只读)</$reveal>
Login: 登录
Logout: 登出
SaveSnapshot: 保存快照以供离线使用
Refresh/Label: 从服务器刷新
Refresh/Button: 从服务器获取最新变更

View File

@ -0,0 +1,7 @@
title: $:/plugins/tiddlywiki/tiddlyweb/language/zh-Hans/readme
该插件在浏览器中运行,用于双向同步更改的条目到与 TiddlyWeb 兼容的服务器上(包括在 Node.js 上运行的 TiddlyWiki 5 本身)。在 Node.js 上运行时,它是无法自救的:由于就是该插件提供了与服务器同步设置和插件的机制,因此通过浏览器禁用该插件后,是无法撤销对自己的禁用的。
离线时所作的更改会保存在内存中,并在重新建立连接时自动与服务器同步。不过,如果关闭浏览器标签页或加载另一个 URL内存中的更改就会丢失。可以添加[[https://tiddlywiki.com/#BrowserStorage Plugin]],为离线时的条目更改提供临时文件系统存储,并使其在下次在同一浏览器中加载知识库时与服务器同步。
[[源代码|https://github.com/Jermolene/TiddlyWiki5/blob/master/plugins/tiddlywiki/tiddlyweb]]

View File

@ -1,7 +1,5 @@
title: $:/plugins/tiddlywiki/tiddlyweb/readme
This plugin runs in the browser to synchronise tiddler changes to and from a TiddlyWeb-compatible server (including TiddlyWiki 5 itself, running on Node.js). It is inert when run under Node.js. Disabling this plugin via the browser can not be undone via the browser since this plugin provides the mechanism to synchronize settings with the server.
\define lingo-base() $:/plugins/tiddlywiki/tiddlyweb/language/
Changes made while offline are saved in memory and automatically synchonised with the server when the connection is re-established. However, if the browser tab is closed or another URL is loaded, the in-memory changes will be lost. The [[https://tiddlywiki.com/#BrowserStorage Plugin]] may be added to provide temporary filesystem storage of tiddler changes made while offline and enable them to be synchronised with the server the next time the wiki is loaded in the same browser.
[[Source code|https://github.com/Jermolene/TiddlyWiki5/blob/master/plugins/tiddlywiki/tiddlyweb]]
<<lingo readme>>

View File

@ -1,6 +1,8 @@
title: $:/plugins/tiddlywiki/tiddlyweb/syncer-actions/copy-logs
tags: $:/tags/SyncerDropdown
\define lingo-base() $:/plugins/tiddlywiki/tiddlyweb/language/
<$button message="tm-copy-syncer-logs-to-clipboard" class="tc-btn-invisible">
{{$:/core/images/copy-clipboard}} Copy syncer logs to clipboard
{{$:/core/images/copy-clipboard}} <<lingo CopySyncerLogs>>
</$button>

View File

@ -1,9 +1,11 @@
title: $:/plugins/tiddlywiki/tiddlyweb/syncer-actions/login-status
tags: $:/tags/SyncerDropdown
\define lingo-base() $:/plugins/tiddlywiki/tiddlyweb/language/
<$reveal state="$:/status/IsLoggedIn" type="match" text="yes">
<div class="tc-drop-down-info">
You are logged in<$reveal state="$:/status/UserName" type="nomatch" text="" default=""> as <strong><$text text={{$:/status/UserName}}/></strong></$reveal><$reveal state="$:/status/IsReadOnly" type="match" text="yes" default="no"> (read-only)</$reveal>
<<lingo LoginAs>><<lingo Readonly>>
</div>
<hr/>
</$reveal>

Some files were not shown because too many files have changed in this diff Show More