expo/expoweb
1
0
Fork 0
mirror of https://expo.survex.com/repositories/expoweb/.git/ synced 2025-12-08 14:54:28 +00:00
Code Issues Packages Projects Releases Wiki Activity

TinyMCE text - online edit of handbook/computing/hbmanual1.html - on dev machine 'SnowWhite'

Browse Source
This commit is contained in:
Philip Sargent
2025-07-07 09:11:49 +01:00
parent 3f5b58a3a0
commit e569247d7b
1 changed files with 11 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

18
handbook/computing/hbmanual1.html
View File

@@ -44,7 +44,7 @@ nearly all pages in this website. If you click on it you will be able to edit th
<p>After editing the page you save your work by clicking on the "Submit" button at the bottom (see it at the bottom-left of the image).
<p>There is nothing to stop you editing lots of pages by this method but you will find it extremely tedious. It is especially tedious creating the links between pages.
<p><b>Footnote:</b> Currently this process does not properly tidy up after itself. Everyone can see your new edited page on the website immediately but you will need to ask a nerd to finish the process to make sure that your changes become persistent and don't get overwritten. [See the explanation at <a href="#tidy">the bottom of this page</a> if you want to know more.]
<h3 id="auto">Autogenerated pages</h3>
<p>Some key sections of the online webpages are autogenerated from cave survey data
@@ -78,7 +78,8 @@ This covers all files and names, not just just the handbook pages. Other parts o
<ul>
<li>We do not use any javascript framework: just HTML and CSS.
<li>You may come across historic references to jquery <strike>but this is not used</strike> and this is used sparingly, e.g. to provide editing buttons on some fo the data entry forms. (We use the Django-provided copy of jquery which is embedded in the /admin/ part of Django.)
<li>We use CaveView (Javascript) and may be using CodeMirror and/or TinyMCE for editing HTML online.</ul>
<li>We use CaveView (Javascript) and may be using CodeMirror and/or TinyMCE for editing HTML online (work in progress 2025).</ul>
<h4>Automated formatting</h4>
<ul>
<li>When any .html page is loaded by troggle it replaces all the <em> &lt;head&gt;...&lt;/head&gt; </em> material with the expo standard header. So don't put anything in the header of any page you edit as it will be ignored. This is also where troggle inserts the <a href="/css/main2.css">/css/main2.css</a> standard stylesheet.
@@ -87,6 +88,7 @@ This covers all files and names, not just just the handbook pages. Other parts o
<em>&lt;meta name="keywords" content="NOEDIT"&gt;</em>
it will be stripped out by troggle when it replaces the header, but it will notice it and will not insert "Edit this page" at the end of the inserted menu.
</ul>
<h4>Filenames</h4>
<ul>
<li>No spaces in filenames. Use underscores or hyphens.
@@ -101,10 +103,11 @@ Otherwise it's easy to make pages that work on Windows, but which don't on Linux
</ul>
<h4 id="images">Images: Relative and Absolute URLs</h4>
<ul>
<li>Older parts of the website have sub-folders "i/", "l/", and "t/" holding respectively<br />
<li>Many parts of the website have sub-folders "i/", "l/", and "t/" holding respectively<br />
i/ - the image file at full resolution (600px width usually)</br>
l/ - an html file which displays the full image with a caption and some description</br>
t/ - a thumbnail image which is usually used inside an &lt;a&gt; tag to link to the l/ html file.
<li>These are created automatically if you use the "Image" button on the two-pane HTML editor (which also uploads the original image in full resolution to /expofiles/ and extracts any GPS information embedded int eh EXIF data for a .jpg file).
</ul>
<p>When creating figures use one of these two constructions. The first with "rooted" URLs beginning with a "/":</p>
@@ -136,14 +139,15 @@ P.S. In older pages that have not been updated recently, you may see this archai
</pre></code>
Where the <var>class="onright"</var> attribute is set on the IMG tag and not on the FIGURE tag or an enclosing DIV tag. If you find one of those in a page you are editing, please update it to use the current &lt;figure&gt; and &lt;figcaption&gt; structure. [Note the mixed URLs in this example, one is absolute and one is relative: this is not a recommended style.]
<h4>TinyMCE</h4>
<p>We used to use a WYSIWYG editor but it got terminally out of date in 2019. We should re-enable it, but it will need modifying because of the way we do images these days.
<img class="onright" alt="gosser bier" src="../i/editthispage.jpg" / width=50%>
<h4>TinyMCE</h4>
<p>We used to use a WYSIWYG editor but it got terminally out of date in 2019. We should re-enable it, but it will need modifying because of the way we do images these days. It lused to look like this and may do again in future:<br>
<hr />
<h3 id="tidy">Tidying up and committing the edits</h3>
<p>'Edit This Page' edits the file served on the web, saves it, adds it to the list of proposed git updates, then finally does the git 'commit' on the server. Things can go wrong at each step of the process.
<h3 id="tidy">Tidying up and committing broken edits</h3>
<p>'Edit This Page' edits the file served on the web, saves it, adds it to the list of proposed git updates, then finally does the git 'commit' on the server. Things can sometimes go wrong at each step of the process.
<p>Specific error message pages are produced if the file cannot be saved (usually a permissions error), if it cannot be added to git's list, or if the git commit fails (which would be due to a merge failure on a previous commit attempt).