| Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision |
| dev:how_to_write_a_zotero_translator_plusplus [2011/08/25 15:11] – [Chapter 11: XPath containers] Clarification. Correction and addition of HWZT example number. clint | dev:how_to_write_a_zotero_translator_plusplus [2017/11/12 19:53] – external edit 127.0.0.1 |
|---|
| | <html><p id="zotero-5-update-warning" style="color: red; font-weight: bold">We’re |
| | in the process of updating the documentation for |
| | <a href="https://www.zotero.org/blog/zotero-5-0">Zotero 5.0</a>. Some documentation |
| | may be outdated in the meantime. Thanks for your understanding.</p></html> |
| | |
| | |
| | **Note: This guide's advice on translator code [[https://github.com/zotero/translators/pull/1282#issuecomment-287574730|may be outdated]].** Instead, model your code on [[https://github.com/zotero/translators/pulls|recently updated translators]], [[https://github.com/zuphilip/translators/wiki/Common-code-blocks-for-translators|common code templates]], [[https://www.zotero.org/support/dev/translators/coding|the translator coding documentation]], and search for answers in the [[https://forums.zotero.org/discussions|Zotero Forums]] and [[https://github.com/zotero/translators/issues|on GitHub]]. |
| | |
| ===== Chapter 0: Introduction ===== | ===== Chapter 0: Introduction ===== |
| |
| Be sure you have the most up to date version of Zotero. You can find this information on the [[http://www.zotero.org/|Zotero website]]. | Be sure you have the most up to date version of Zotero. You can find this information on the [[http://www.zotero.org/|Zotero website]]. |
| |
| ==== Scaffold 2.0 ==== | ==== Scaffold ==== |
| |
| install Scaffold from [[http://bitbucket.org/rmzelle/scaffold/downloads|here]] (temporarily) | Install [[https://www.zotero.org/support/dev/translators/scaffold Scaffold]]. Note that it has been updated more recently than most of this wiki, and some features may have changed. |
| |
| The makers of Zotero created Scaffold specifically for writing translators. It's a sort of a "sandbox," which means you can muck around with the code without worrying about really messing anything up, and it automates some tasks. In this guide, all code will be written, tested, and retested in Scaffold. | The makers of Zotero created Scaffold specifically for writing translators. It's a sort of a "sandbox," which means you can muck around with the code without worrying about really messing anything up, and it automates some tasks. In this guide, all code will be written, tested, and retested in Scaffold. |
| ===== Chapter 5: XPath directions ===== | ===== Chapter 5: XPath directions ===== |
| |
| [[http:/XPath directions/niche-canada.org/member-projects/zotero-guide/chapter5.html|HWZT chapter 5 (XPath directions)]]: | [[http://niche-canada.org/member-projects/zotero-guide/chapter5.html|HWZT chapter 5 (XPath directions)]]: |
| |
| The {DOM Inspector + XPather} workflow differs from that of Solvent. After opening the [[http://niche-canada.org/member-projects/zotero-guide/sample1.html|first sample page]], | The {DOM Inspector + XPather} workflow differs from that of Solvent. After opening the [[http://niche-canada.org/member-projects/zotero-guide/sample1.html|first sample page]], |
| - Open DOM Inspector (aka //DI//) with C-S-i or from the Firefox main menu with Tools>DOM Inspector. XPather functionality is available from UI within the DI window. | - Open DOM Inspector (aka //DI//) with CTRL+SHIFT+C or from the Firefox main menu with Tools>DOM Inspector. XPather functionality is available from UI within the DI window. |
| - Hit button=Inspect at the upper right of the DI window. This will open pane=Browser in the DI window displaying the contents of the first sample page. | - Hit button=Inspect at the upper right of the DI window. This will open pane=Browser in the DI window displaying the contents of the first sample page. |
| - To test the XPath string denoting the heading (text="Method and Meaning in Canadian Environmental History") of the first sample page, | - To test the XPath string denoting the heading (text="Method and Meaning in Canadian Environmental History") of the first sample page, |
| - Hit button="Test Regex". You should get a result, in the "Test Frame" on the right of the tab, similar to that described in HWZT. | - Hit button="Test Regex". You should get a result, in the "Test Frame" on the right of the tab, similar to that described in HWZT. |
| - Instead of <code>Click on the "Detect Code" tab</code>, click on tab=Code. This is the tab where code should be entered. | - Instead of <code>Click on the "Detect Code" tab</code>, click on tab=Code. This is the tab where code should be entered. |
| - Up to chapter 11, HWZT has you click the "Run doWeb" (thunderbolt) icon to debug code. But from example 11.6 through the end of chapter 11, you are working with a "detectWeb" function, so you'll need to use the "Run detectWeb" (the eye) button to run your function and debug. For example, at example 11.6, when you click "Run detectWeb", you should get results like <code>12:00:00 Title:</code> | - To excute code and debug, HWZT has you click an "Execute" button with a thunderbolt icon. In newer versions of Scaffold, the single execute button as been replaced by one "Run doWeb" button (thunderbolt icon) and one "Run detectWeb" button (eye icon). Starting in HWZT exampe 11.6, you'll be writing detectWeb functions, so you'll need to click the "Run detectWeb" button to run your detectWeb function. For example, at example 11.6, when you click "Run detectWeb", you should get results like <code>12:00:00 Title:</code> |
| |
| |
Upgrade Storage