15 |
16 |
17 |
18 |
--------------------------------------------------------------------------------
/Resources/Public/GPXViewer/GPXViewer6.8/GM_Utils/Icons/whereami.svg:
--------------------------------------------------------------------------------
1 |
2 |
3 |
--------------------------------------------------------------------------------
/Resources/Public/GPXViewer/GPXViewer6.8/GM_Utils/Icons/marker.svg:
--------------------------------------------------------------------------------
1 |
2 |
3 |
--------------------------------------------------------------------------------
/Documentation.tmpl/Localization.de_DE.tmpl/README:
--------------------------------------------------------------------------------
1 | How to translate
2 | ================
3 |
4 | This directory contains the German translation of your documentation.
5 | This is a complete Sphinx project but you may reuse assets from the
6 | main documentation under Documentation/.
7 |
8 | If you plan to translate your documentation to German, you should
9 | rename this directory and remove the suffix ".tmpl":
10 |
11 | Localization.de_DE.tmpl -> Localization.de_DE
12 |
13 | As this file is not needed either, feel free to delete it as well.
14 |
15 |
16 | Supported languages
17 | ===================
18 |
19 | Please visit http://sphinx-doc.org/latest/config.html#intl-options for a
20 | list of languages supported by Sphinx.
21 |
22 | Please note however that TYPO3 is using locales so you may need to
23 | extend the language code from Sphinx into a proper locale to be used
24 | by TYPO3.
25 |
--------------------------------------------------------------------------------
/Documentation.tmpl/Localization.fr_FR.tmpl/README:
--------------------------------------------------------------------------------
1 | How to translate
2 | ================
3 |
4 | This directory contains the French translation of your documentation.
5 | This is a complete Sphinx project but you may reuse assets from the
6 | main documentation under Documentation/.
7 |
8 | If you plan to translate your documentation to French, you should
9 | rename this directory and remove the suffix ".tmpl":
10 |
11 | Localization.fr_FR.tmpl -> Localization.fr_FR
12 |
13 | As this file is not needed either, feel free to delete it as well.
14 |
15 |
16 | Supported languages
17 | ===================
18 |
19 | Please visit http://sphinx-doc.org/latest/config.html#intl-options for a
20 | list of languages supported by Sphinx.
21 |
22 | Please note however that TYPO3 is using locales so you may need to
23 | extend the language code from Sphinx into a proper locale to be used
24 | by TYPO3.
25 |
--------------------------------------------------------------------------------
/Resources/Private/Language/locallang_db.xlf:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 |
6 |
7 | Display
8 |
9 |
10 | GPXViewer tracks display
11 |
12 |
13 | Display GPX tracks with GPXViewer
14 |
15 |
16 |
17 |
18 |
--------------------------------------------------------------------------------
/Resources/Public/GPXViewer/GPXViewer6.8/Foto5.html:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 |
6 | Fotoanzeige V5
7 |
10 |
11 |
12 |
29 |
30 |
--------------------------------------------------------------------------------
/Documentation.tmpl/Configuration/Index.rst:
--------------------------------------------------------------------------------
1 | .. include:: ../Includes.txt
2 |
3 |
4 | .. _configuration:
5 |
6 | =============
7 | Configuration
8 | =============
9 |
10 | Target group: **Developers, Integrators**
11 |
12 | How is the extension configured? Aim to provide simple instructions detailing
13 | how the extension is configured. Always assume that the user has no prior experience
14 | of using your extension.
15 |
16 | Try and provide a typical use case for your extension and detail each of the
17 | steps required to get the extension running.
18 |
19 |
20 | Typical Example
21 | ===============
22 |
23 | - Do we need to include a static template?
24 | - For example add a code snippet with comments
25 |
26 | Minimal example of TypoScript:
27 |
28 | - Code-blocks have support for syntax highlighting
29 | - Use any supported language
30 |
31 | .. code-block:: typoscript
32 |
33 | plugin.tx_myextension.settings {
34 | # configure basic email settings
35 | email {
36 | subject = Some subject
37 | from = someemail@domain.de
38 | }
39 | }
40 |
41 | .. _configuration-typoscript:
42 |
43 | TypoScript Reference
44 | ====================
45 |
46 | When detailing data types or standard TypoScript
47 | features, don't hesitate to cross-link to the TypoScript
48 | Reference.
49 |
50 | Information about how to use cross-references:
51 | https://docs.typo3.org/typo3cms/HowToDocument/WritingReST/Hyperlinks.html
52 |
53 | See the :file:`Settings.cfg` file for the declaration of cross-linking keys.
54 | You can add more keys besides tsref.
55 |
--------------------------------------------------------------------------------
/Resources/Public/Icons/Extension.svg:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
25 |
--------------------------------------------------------------------------------
/Documentation.tmpl/Introduction/Index.rst:
--------------------------------------------------------------------------------
1 | .. include:: ../Includes.txt
2 |
3 |
4 | .. _introduction:
5 |
6 | ============
7 | Introduction
8 | ============
9 |
10 |
11 | .. tip::
12 |
13 | New to reStructuredText and Sphinx?
14 |
15 | Get an introduction:
16 | https://docs.typo3.org/m/typo3/docs-how-to-document/master/en-us/WritingReST/Index.html
17 |
18 | Use this cheat sheet as reference:
19 | https://docs.typo3.org/m/typo3/docs-how-to-document/master/en-us/WritingReST/CheatSheet.html
20 |
21 | .. _what-it-does:
22 |
23 | What does it do?
24 | ================
25 |
26 | The aim of this chapter is to provide a general overview of your extension.
27 |
28 | * What does it do?
29 | * What problems does it solve?
30 | * Who is the target audience?
31 |
32 | This chapter should provide information that will help inform
33 | potential users and assist them in deciding if they should
34 | install and use this extension.
35 |
36 | .. important::
37 |
38 | Don't forget to repeat your extension's version number in the
39 | :file:`Settings.cfg` file, in the :code:`release` property. It will be
40 | automatically picked up on the cover page by the :code:`|release|`
41 | substitution.
42 |
43 |
44 | .. _screenshots:
45 |
46 | Screenshots
47 | ===========
48 |
49 | This chapter should help people understand how the extension works. Remove it
50 | if it is not relevant.
51 |
52 | .. figure:: ../Images/IntroductionPackage.png
53 | :class: with-shadow
54 | :alt: Introduction Package
55 | :width: 300px
56 |
57 | Introduction Package just after installation (caption of the image)
58 |
59 | How the Frontend of the Introduction Package looks like just after installation (legend of the image)
--------------------------------------------------------------------------------
/Documentation.tmpl/Developer/Index.rst:
--------------------------------------------------------------------------------
1 | .. include:: ../Includes.txt
2 |
3 |
4 | .. _developer:
5 |
6 | ================
7 | Developer Corner
8 | ================
9 |
10 | Target group: **Developers**
11 |
12 | This is your opportunity to pass on information to other developers who may be using your extension.
13 |
14 | Use this section to provide examples of code or detail any information that would be deemed relevant to a developer.
15 |
16 | You may wish to explain how a certain feature was implemented or detail any changes that might of been
17 | made to the extension.
18 |
19 | .. _developer-hooks:
20 |
21 | Hooks
22 | =====
23 |
24 | Possible hook examples. Input parameters are:
25 |
26 | +----------------+---------------+---------------------------------+
27 | | Parameter | Data type | Description |
28 | +================+===============+=================================+
29 | | $table | string | Name of the table |
30 | +----------------+---------------+---------------------------------+
31 | | $field | string | Name of the field |
32 | +----------------+---------------+---------------------------------+
33 |
34 | Use parameter :code:`$table` to retrieve the table name...
35 |
36 | .. _developer-api:
37 |
38 | API
39 | ===
40 |
41 | How to use the API...
42 |
43 | .. code-block:: php
44 |
45 | $stuff = \TYPO3\CMS\Core\Utility\GeneralUtility::makeInstance(
46 | '\\Foo\\Bar\\Utility\\Stuff'
47 | );
48 | $stuff->do();
49 |
50 | or some other language:
51 |
52 | .. code-block:: javascript
53 | :linenos:
54 | :emphasize-lines: 2-4
55 |
56 | $(document).ready(
57 | function () {
58 | doStuff();
59 | }
60 | );
--------------------------------------------------------------------------------
/Resources/Public/GPXViewer/GPXViewer6.8/Beispiel2.html:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 |
6 | GPXViewer Beispiel 2
7 |
10 |
11 |
19 |
20 |
21 |
GPXViewer Beispiel 2 - weitere Karten mit Button anzeigen
32 |
33 |
--------------------------------------------------------------------------------
/Documentation.tmpl/User/Index.rst:
--------------------------------------------------------------------------------
1 | .. ==================================================
2 | .. FOR YOUR INFORMATION
3 | .. --------------------------------------------------
4 | .. -*- coding: utf-8 -*- with BOM.
5 |
6 | .. include:: ../Includes.txt
7 |
8 |
9 | .. _user-manual:
10 |
11 | Users Manual
12 | ============
13 |
14 | Target group: **Editors**
15 |
16 | Here should be described how to use the extension from the editor perspective.
17 |
18 | - How does it work?
19 |
20 | - works well when doing this.
21 |
22 | - does not work so well when doing that
23 | but we can live with it.
24 |
25 | - **mind indentation when nesting lists**.
26 |
27 | - How to install the plugin on a web page?
28 |
29 | - What options are available?
30 |
31 | Language should be non-technical, explaining, using small examples.
32 | Don't use to many acronyms unless they have been explained.
33 | Don't be confusing by putting information targeting administrators.
34 |
35 | .. tip::
36 |
37 | Take a break from time to time.
38 |
39 | Admonitions should be used to warn the users about potential
40 | pitfalls, attract their attention to important elements
41 | or just add some notes for for information (further reading,
42 | for example).
43 |
44 | .. important::
45 |
46 | Remember to always say "please" when asking your software to
47 | do something.
48 |
49 | Provide screenshots as needed for making things clear. When creating
50 | screenshots, try using the `Introduction Package `_
51 | as a neutral TYPO3 CMS instance.
52 |
53 | .. figure:: ../Images/UserManual/BackendView.png
54 | :class: with-shadow
55 | :width: 500px
56 | :alt: Backend view
57 |
58 | Default Backend view (caption of the image)
59 |
60 | The Backend view of TYPO3 after the user has clicked on module "Page". (legend of the image)
61 |
62 |
63 | .. _user-faq:
64 |
65 | FAQ
66 | ---
67 |
68 | Possible subsection: FAQ
69 |
--------------------------------------------------------------------------------
/Resources/Public/GPXViewer/GPXViewer6.8/Beispiel4.html:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 |
6 | GPXViewer Beispiel 4
7 |
19 |
20 |
21 |
GPXViewer Beispiel 4 - Karte und Profile gegen Weg
In diesem Beispiel wird gezeigt, wie alle in einem Ordner auf dem Server abgelegten GPX-Dateien angezeigt werden können. Dazu muss auf dem Webserver das Dirctorylisting eingeschaltet werden. Auf dem Apache-Server muss dazu in den Ordner mit den GPX-Dateien eine Datei mit Namen .htaccess und dem Inhalt Options +Indexes gelegt werden.
In diesem Beispiel wird gezeigt, wie alle in einem Ordner auf dem Server abgelegten GPX-Dateien über ein Auswahlmenü angezeigt werden können. Dazu muss auf dem Webserver das Dirctorylisting eingeschaltet werden. Auf dem Apache-Server muss dazu in den Ordner mit den GPX-Dateien eine Datei mit Namen .htaccess und dem Inhalt Options +Indexes gelegt werden.
22 |
23 |
71 |
72 |
--------------------------------------------------------------------------------
/Configuration/ExtensionBuilder/settings.yaml:
--------------------------------------------------------------------------------
1 | #
2 | # Extension Builder settings for extension wok_gpxviewer
3 | # generated 2018-03-20T09:41:00Z
4 | #
5 | # See http://www.yaml.org/spec/1.2/spec.html
6 | #
7 |
8 | ---
9 |
10 | ########### Overwrite settings ###########
11 | #
12 | # These settings only apply, if the roundtrip feature of the extension builder
13 | # is enabled in the extension manager
14 | #
15 | # Usage:
16 | # nesting reflects the file structure
17 | # a setting applies to a file or recursive to all files and subfolders
18 | #
19 | # merge:
20 | # means for classes: All properties ,methods and method bodies
21 | # of the existing class will be modified according to the new settings
22 | # but not overwritten
23 | #
24 | # for locallang xlf files: Existing keys and labels are always
25 | # preserved (renaming a property or DomainObject will result in new keys and new labels)
26 | #
27 | # for other files: You will find a Split token at the end of the file
28 | # see: \EBT\ExtensionBuilder\Service\RoundTrip::SPLIT_TOKEN
29 | #
30 | # After this token you can write whatever you want and it will be appended
31 | # everytime the code is generated
32 | #
33 | # keep:
34 | # files are never overwritten
35 | # These settings may break the functionality of the extension builder!
36 | # Handle with care!
37 | #
38 | #
39 |
40 | ############ extension settings ##############
41 |
42 | overwriteSettings:
43 | Classes:
44 | Controller: keep
45 | Domain:
46 | Model: merge
47 | Repository: merge
48 |
49 | Configuration:
50 | #TCA merge not possible - use overrides directory
51 | TypoScript: keep
52 |
53 | Resources:
54 | Private:
55 | // Language set to keep. Merge will strip all translations
56 | Language: keep
57 | #Templates: keep
58 | Templates:
59 | Index.html: keep
60 | Public:
61 | Icons:
62 | Extension.svg: keep
63 | user_plugin_gpxtracks.svg: keep
64 |
65 | user_extension.svg: keep
66 |
67 | ext_localconf.php: merge
68 |
69 | ext_tables.php: keep
70 |
71 | ext_tables.sql: merge
72 |
73 | ## use static date attribute in xliff files ##
74 | #staticDateInXliffFiles: 2018-03-20T09:41:00Z
75 |
76 | ## skip docComment (license header) ##
77 | #skipDocComment
78 |
79 | ## list of error codes for warnings that should be ignored ##
80 | #ignoreWarnings:
81 | #503
82 |
83 | ######### settings for classBuilder #############################
84 | #
85 | # here you may define default parent classes for your classes
86 | # these settings only apply for new generated classes
87 | # you may also just change the parent class in the generated class file.
88 | # It will be kept on next code generation, if the overwrite settings
89 | # are configured to merge it
90 | #
91 | #################################################################
92 |
93 | classBuilder:
94 |
95 | Controller:
96 | parentClass: \TYPO3\CMS\Extbase\Mvc\Controller\ActionController
97 |
98 | Model:
99 | AbstractEntity:
100 | parentClass: \TYPO3\CMS\Extbase\DomainObject\AbstractEntity
101 |
102 | AbstractValueObject:
103 | parentClass: \TYPO3\CMS\Extbase\DomainObject\AbstractValueObject
104 |
105 | Repository:
106 | parentClass: \TYPO3\CMS\Extbase\Persistence\Repository
107 |
108 | setDefaultValuesForClassProperties: true
--------------------------------------------------------------------------------
/Classes/ViewHelpers/IncludeFileViewHelper.php:
--------------------------------------------------------------------------------
1 |
23 | *
24 | *
25 | *
28 | *
29 | */
30 | class IncludeFileViewHelper extends \TYPO3Fluid\Fluid\Core\ViewHelper\AbstractViewHelper implements ViewHelperInterface
31 | {
32 | use CompileWithRenderStatic;
33 |
34 | /**
35 | */
36 | public function initializeArguments()
37 | {
38 | $this->registerArgument('path', 'string', 'Path to the CSS/JS file which should be included', true);
39 | $this->registerArgument('compress', 'bool', 'Define if file should be compressed', false, false);
40 | $this->registerArgument('footer', 'bool', 'Define if JS file should be loaded in the footer', false, false);
41 | }
42 |
43 | /**
44 | * @param array $arguments
45 | * @param \Closure $renderChildrenClosure
46 | * @param RenderingContextInterface $renderingContext
47 | */
48 | public static function renderStatic(
49 | array $arguments,
50 | \Closure $renderChildrenClosure,
51 | RenderingContextInterface $renderingContext
52 | ) {
53 | $path = $arguments['path'];
54 | $compress = (bool)$arguments['compress'];
55 | $footer = (bool)$arguments['footer'];
56 |
57 | $pageRenderer = GeneralUtility::makeInstance(PageRenderer::class);
58 | if (TYPO3_MODE === 'FE') {
59 | $sanitizer = GeneralUtility::makeInstance(FilePathSanitizer::class);
60 | try {
61 | $path = $sanitizer->sanitize($path);
62 | // JS
63 | if (strtolower(substr($path, -3)) === '.js') {
64 | if ($footer) {
65 | $pageRenderer->addJsFooterFile($path, null, $compress, false, '', true);
66 | } else {
67 | $pageRenderer->addJsFile($path, null, $compress, false, '', true);
68 | }
69 |
70 | // CSS
71 | } elseif (strtolower(substr($path, -4)) === '.css') {
72 | $pageRenderer->addCssFile($path, 'stylesheet', 'all', '', $compress, false, '', true);
73 | }
74 | } catch (\Exception $e) {
75 | // do nothing (todo handle properly?)
76 | }
77 | } else {
78 | // JS
79 | if (strtolower(substr($path, -3)) === '.js') {
80 | $pageRenderer->addJsFile($path, null, $compress, false, '', true);
81 |
82 | // CSS
83 | } elseif (strtolower(substr($path, -4)) === '.css') {
84 | $pageRenderer->addCssFile($path, 'stylesheet', 'all', '', $compress, false, '', true);
85 | }
86 | }
87 | }
88 | }
89 |
--------------------------------------------------------------------------------
/README.md:
--------------------------------------------------------------------------------
1 | # wok_gpxviewer
2 | This is a [TYPO3](https://typo3.org) extension, which provides a plugin for integration of [GPXViewer](https://www.j-berkemeier.de/GPXViewer) from Jürgen Berkemeier.
3 |
4 | ## What does it do?
5 | With including the [GPXViewer](https://www.j-berkemeier.de/GPXViewer) javascript one can display GPX tracks, routes, waypoints in Google Maps or Openstreetmap. Please refer to the [GPXViewer website](https://www.j-berkemeier.de/GPXViewer) for more informations about the features of [GPXViewer](https://www.j-berkemeier.de/GPXViewer).
6 |
7 | This extension/plugin for [TYPO3](https://typo3.org) integrate most of the features of [GPXViewer](https://www.j-berkemeier.de/GPXViewer). For some examples please refer to [my website](https://wolfgangkleinbach.de/test/GPXViewer). I will also try to do some documentation for the use of the extension there.
8 |
9 | ## What prerequisites are needed?
10 | * [TYPO3](https://typo3.org) 9.5.x or above.
11 | * The [bootstrap_package](https://www.bootstrap-package.com/) is highly recommended. I only use the extension/plugin with the bootstrap_package and it's ScssPHP compiler and therefore the layout might be broken if you don't.
12 | * For some features you need [exiftool](https://exiftool.org) installed on your server.
13 | * Probably you need API keys for use of Google maps or OSM. Find more information about API keys [here](https://www.j-berkemeier.de/GPXViewer/#Apikey).
14 | * You don't necessarily need GPX files, you even can create a GPXViewer content element and add your own waypoints or waypoint images with GPS coordinates. You need to know the coordinates from another source. This extension does not provide a way to determine GPS coordinates from a map.
15 | * Commercial use of [GPXViewer](https://www.j-berkemeier.de/GPXViewer) of Jürgen Berkemeier is restricted. Read more about this and other restrictions [here](https://www.j-berkemeier.de/GPXViewer/#Rechtliches).
16 | * The use of this TYPO3 extension is only restricted insofar as [GPXViewer](https://www.j-berkemeier.de/GPXViewer) and other provided resources are underlying restrictions.
17 |
18 | ## How to set up?
19 | * Download and install the extension [wok_gpxviewer](https://github.com/zeichensatz/wok_gpxviewer).
20 | * Create a new page in [TYPO3](https://typo3.org) backend or edit an existing one.
21 | * Create an extension template for that page or edit an existing template and `"Include static (from extensions)"` for `GPXViewer (wok_gpxviewer)`.
22 | * Change to `Constant Editor` and edit the settings for GPXViewer if needed.
23 | * Now you can create a content element of type `plugin` and then select `GPXViewer tracks display`.
24 | * In the tab `Plug-in` you are able to add GPX files for display in the frontend. There are several tabs with settings to explore. Hopefully most of them are self explaining. If not, don't hesitate to contact me (see below).
25 |
26 | ## How can you give your feedback
27 | * I would like to hear from you, how you're using the extension and what can be improved.
28 | * You can write me a mail, see [my website](https://wolfgangkleinbach.de) for contact data.
29 | * You can add issues or pull requests on [github](https://github.com/zeichensatz/wok_gpxviewer).
30 |
31 | ## Todos
32 | * Check button formatting for imgdivs: perhaps change to a tag? This would mean changes in the javascript too.
33 | * Check CSS file option and update CSS file
34 | * Map+imgdiv+profiles: Some minor problems in display
35 | * make each map/imgdiv/profiles scaleable from backend
36 | * more examples
37 | * more documentation
38 | * create TER version
39 | * make extension compatible to extension_builder
40 |
--------------------------------------------------------------------------------
/Resources/Public/GPXViewer/MyAdditionalJS/animation.js:
--------------------------------------------------------------------------------
1 | // This file is based on a sample script of GPXViewer created by Jürgen Berkemeier
2 | // Lizenz CC BY-NC-SA 4.0
3 | // Jürgen Berkemeier
4 | // www.j-berkemeier.de
5 | // The file was modified for use with the TYPO3 GPXViewer-Plugin by Wolfgang Kleinbach
6 | // wolfgangkleinbach.de
7 | //
8 | // This file has to be included AFTER GPX2GM.js
9 | //
10 | // With this javascript code, you can easily realize animationed markers along GPX tracks with GPXViewer
11 | //
12 | // To use animated markers, you only have to add an additional class to the GPXViewer map div:
13 | //
30 | 
66 | 
