| At line 1 changed one line |
| Wiki and shell |
| !!!Wiki and shell |
|
| At line 14 changed 7 lines |
| Ideas for markup: |
| * makes table a table |
| * add links to documentation |
| * add links that execute a command in the current shell) |
| * add image (e.g. Gnuplot output) |
| * add menu of contextual actions |
| * add anchors that can be used to reuse output into new shell commands. |
| !!Ideas for markup |
| * makes table a table |
| * add links to documentation |
| * add links that execute a command in the current shell) |
| * add image (e.g. Gnuplot output) |
| * add tag that tells JSPWiki to use a plugin (e.g. JfreeChart around some data). |
| * add menu of contextual actions |
| * add anchors that can be used to reuse output into new shell commands. |
| At line 22 changed 8 lines |
| * click on prompt showing path, choose ls |
| * type lsof, output is decorated, pids show a menu of actions (pargs, stack, pwdx...) |
| * file prettifier annotates documentation with doc links etc. |
| * script displays information with local links and certain information as popups, linked pages |
| Bad scenarios: |
| * How to handle tail? |
| * ls -l on big directory is useless, big, pollutes search results, how to get rid of it? |
| * vi and other interactive programs don't mix well |
| * click on prompt showing path, choose ls |
| * type lsof, output is decorated, pids show a menu of actions (pargs, stack, pwdx...) |
| * file prettifier annotates documentation with doc links etc. |
| * script displays information with local links and certain information as popups, linked pages |
| !!Bad scenarios |
| * How to handle tail? |
| * ls -l on big directory is useless, big, pollutes search results, how to get rid of it? |
| * vi and other interactive programs don't mix well |
|
| !!Terminal Emulation in JavaScript |
| Several terminal emulators are available which could be modified to enhance the text they display and or redirect it to web services. |
|
| * [Anyterm|http://anyterm.org/] |
|
| %%prettify |
| {{{ |
| <html> |
| <head> |
| <title>Anyterm</title> |
| <script type="text/javascript" src="anyterm.js"> |
| </script> |
| <script type="text/javascript"> |
| window.onload=function() { |
| create_term("term1","%h (Anyterm%v)",25,80,"","",50); |
| }; |
| var on_close_goto_url = ""; |
| </script> |
| <link rel="stylesheet" type="text/css" href="anyterm.css"> |
| </head> |
| <body> |
| <div id="term1"></div> |
| </body> |
| </html> |
| }}} |
| /% |
|
| The JavaScript terminal even handles applications like {{top}} nicely: |
| [anyterm.png] |
|
| * [Gate One|http://liftoffsoftware.com/Products/GateOne] |
| * [Onion Term|https://github.com/davidmoreno/onion/tree/master/examples/oterm] |
|
| !Extend anyterm |
| It would be nice to have escape characters in a terminal that allow shell scripts and programs to add hyperlinks to the text. Or javascript, for,instance to define a unix command. The user can then click on the text that is thus annotated and follow the hyperlink or see the annotation appear at the prompt |
|
|
|
|
|
|
| !! Writing to a wiki from the shell |
|
| If we have FUSE and a filesystem view of the wiki then it's easy to write to a wiki from the shell. |
| But one is not always root and some systems don't have fuse. So another idea would be to create a couple of commands that access a wiki and use environment variables. |
|
| Ideally curl would be used but authentication is not always easy. So it might be necessary to use a Java/XMLRPC API to acces the wikis: |
| *[WikiAPI|http://jwikiapi.sourceforge.net/] |
| * A REST API would be nice to update pages (cf. [WikiWiki#Eliminate Ugly URLs and Modal Views] |
|
