Fossil SCM
Added "chat" to the list in javascript.md
Commit
debb410e9bf7991215178ace25732798a5ba1a4882a208ee261202ac18971028
Parent
20c193d8d41771c…
1 file changed
+19
+19
| --- www/javascript.md | ||
| +++ www/javascript.md | ||
| @@ -548,10 +548,29 @@ | ||
| 548 | 548 | local time zone to be a useful fallback for the current feature, so [a |
| 549 | 549 | patch to do this][cg] may well be accepted. Since this is not a |
| 550 | 550 | *necessary* Fossil feature, an interested user is unlikely to get the |
| 551 | 551 | core developers to do this work for them. |
| 552 | 552 | |
| 553 | + | |
| 554 | +### <a id="chat"></a>Chat | |
| 555 | + | |
| 556 | +The [chat feature](./chat.md) added in Fossil 2.14 is deeply dependent | |
| 557 | +on JavaScript. There is no obvious way to do this sort of thing without | |
| 558 | +active client-side code of some sort. | |
| 559 | + | |
| 560 | +_Potential Workaround:_ It would not be especially difficult for someone | |
| 561 | +sufficiently motivated to build a Fossil chat gateway, connecting to | |
| 562 | +IRC, Jabber, etc. The messages are stored in the repository’s `chat` | |
| 563 | +table with monotonically increasing IDs, so a poller that did something | |
| 564 | +like | |
| 565 | + | |
| 566 | + SELECT xfrom, xmsg FROM chat WHERE msgid > 1234; | |
| 567 | + | |
| 568 | +…would pull the messages submitted since the last poll. Making the | |
| 569 | +gateway bidirectional should be possible as well, as long as it properly | |
| 570 | +uses SQLite transactions. | |
| 571 | + | |
| 553 | 572 | ---- |
| 554 | 573 | |
| 555 | 574 | ## <a id="future"></a>Future Plans for JavaScript in Fossil |
| 556 | 575 | |
| 557 | 576 | As of mid-2020, the informal provisional plan is to increase Fossil |
| 558 | 577 |
| --- www/javascript.md | |
| +++ www/javascript.md | |
| @@ -548,10 +548,29 @@ | |
| 548 | local time zone to be a useful fallback for the current feature, so [a |
| 549 | patch to do this][cg] may well be accepted. Since this is not a |
| 550 | *necessary* Fossil feature, an interested user is unlikely to get the |
| 551 | core developers to do this work for them. |
| 552 | |
| 553 | ---- |
| 554 | |
| 555 | ## <a id="future"></a>Future Plans for JavaScript in Fossil |
| 556 | |
| 557 | As of mid-2020, the informal provisional plan is to increase Fossil |
| 558 |
| --- www/javascript.md | |
| +++ www/javascript.md | |
| @@ -548,10 +548,29 @@ | |
| 548 | local time zone to be a useful fallback for the current feature, so [a |
| 549 | patch to do this][cg] may well be accepted. Since this is not a |
| 550 | *necessary* Fossil feature, an interested user is unlikely to get the |
| 551 | core developers to do this work for them. |
| 552 | |
| 553 | |
| 554 | ### <a id="chat"></a>Chat |
| 555 | |
| 556 | The [chat feature](./chat.md) added in Fossil 2.14 is deeply dependent |
| 557 | on JavaScript. There is no obvious way to do this sort of thing without |
| 558 | active client-side code of some sort. |
| 559 | |
| 560 | _Potential Workaround:_ It would not be especially difficult for someone |
| 561 | sufficiently motivated to build a Fossil chat gateway, connecting to |
| 562 | IRC, Jabber, etc. The messages are stored in the repository’s `chat` |
| 563 | table with monotonically increasing IDs, so a poller that did something |
| 564 | like |
| 565 | |
| 566 | SELECT xfrom, xmsg FROM chat WHERE msgid > 1234; |
| 567 | |
| 568 | …would pull the messages submitted since the last poll. Making the |
| 569 | gateway bidirectional should be possible as well, as long as it properly |
| 570 | uses SQLite transactions. |
| 571 | |
| 572 | ---- |
| 573 | |
| 574 | ## <a id="future"></a>Future Plans for JavaScript in Fossil |
| 575 | |
| 576 | As of mid-2020, the informal provisional plan is to increase Fossil |
| 577 |