Post reply

Name:
Email:
Subject:
Tags:

Seperate each tag by a comma
Message icon:

Attach:
(Clear Attachment)
(more attachments)
Allowed file types: apk, doc, docx, gif, jpg, mpg, pdf, png, txt, zip, xls, 3gpp, mp2, mp3, wav, odt, ods, html, mp4, amr, apk, m4a, jpeg, aac
Restrictions: 50 per post, maximum total size 150000KB, maximum individual size 150000KB
Note that any files attached will not be displayed until approved by a moderator.
Anti-spam: complete the task

shortcuts: hit alt+s to submit/post or alt+p to preview


Topic Summary

Posted by: Dhammañāṇa
« on: August 21, 2018, 12:12:20 AM »

Having now given it a t/dry, in including in in a sample in page templates (see product in foundation of mindfulness) it seems to work optical with the current plugin, which is now signed as "ausgebremst" by others.

How ever, if understood right, if setting alias via the adminsection, it would not require a field value edit on each page manual, would it?

The draft, used in dictionary: (incl: data entrance) looks like that for now.

Code: [Select]
===== meta data =====
---- dataentry metadata ----
page ID: @ID@
pagename: @PAGE@
file: @FILE@
permanent link: http://accesstoinsight.eu/doku.php?id=@ID@
page initially given by: @NAME@
page creation date: @DATE@
origin author and source: see [[en:dictionary:source_of_dictionaries]].
source: various [[en:dictionaries]]
scope of gift: **This is a gift of Dhamma** and given to use for any skilful/wholesome purpose and undertaking but not for any commercial use or other use of exchange for worldly aims. For additional information see [[en:dhamma-dana|Dhamma-Dana]] and possible details at the [[en:dictionary|source pages]] for included parts. Much joy in using and share of the merits!
owner of this copy: Sublime [[en:wiki:sangha:Sangha]] of the eight directions.
current maintainer: The [[aramika]] and monastic disciples on [[http://forum.sangham.net/index.php?action=forum|sangham.net]]
dedications of editors: [[@Name@]]: for the Sublime Sangha of the Buddha and those following and interested, my teachers, parents and ancestors, all beings welfare.
----

* Johann : and now Atmas eyes, no more able to read the small letters, says: it's good to take a short sleep  :)
Posted by: Dhammañāṇa
« on: June 18, 2018, 11:48:13 AM »

Thought again: Actually, if all Datas are keep within the txt file, independent of a Database, it seems for a long therme better. And if one likes to include any converting, fine.

* Johann Guess my person needs to think more in thermes: no need to start perfect: it's a "wiki-ground", place for small and large contributions according to ones skills and joy.
Posted by: Dhammañāṇa
« on: June 17, 2018, 11:46:49 PM »

Not sure if struct would not fit all means and posdible, as favored by the main developer, would resist longer than plugs into plugs "horror".

But what ever might nourish good possibilities, such a sacrifice, big or small, is praiseworthy.

No more fuel today.

Sadhu!
Posted by: Moritz
« on: June 17, 2018, 10:13:25 PM »

Atma thought, maybe it contains such, that a fix set of Datas (incl. a form) would be added to a all pages, and its items might be useable anywhere.

DataTemplate plugin might be the solution for this.

Quote
This plugin adds the possibility to display the structured data of the Data Plugin using templates. Templates can be applied to individual data entries or lists of multiple entries. Additionally, this plugin offers a custom search form, pagination and result caching.

Looks like an enhancement of Data plugin, with additional possibility to add "templates" into the data (or, in the opposite, fill the data of the "Data Entry" boxes into some templates) that could maybe also have some default values when no data is specified... not sure if yet understood. And also the original Data plugin not yet quite understood...

I have no time to look deeper into it now, but I will try when I have time.

Vom Hudln kommen die Kinder...

Some samples to show the plugin in action:
Quote
Demonstration

For a demonstration, see for instance the Publications page of the Group of Applied Physics at the University of Geneva. There, both the datatemplate list and the filter form can be seen in action. Each item in the list is a datatemplate entry (created by a separate plugin that accepts BibTeX as input).

The Members page is equally based on this plugin, the members are listed by datatemplatelist and the member pages contains a datatemplateentry.

As another example I am using this plugin on my personal website to provide a pretty index page for a collection of recipes and documents . (This was broken for a while after a Doku upgrade, but not that the plugin has been fixed it's working again). – Adam

I think something useful can be done with that for footer data / license / author etc.

And I think for general layout of pages there may be other useful plugins that provide possibilities for page layout templates.

*  will try look into it in the next days.
Posted by: Dhammañāṇa
« on: June 17, 2018, 09:18:00 PM »

The sample… something to play around, helps a lot for imagination how things at large, 10.000s of pages could be integrated by those with tools for such!

Atma thought, maybe it contains such, that a fix set of Datas (incl. a form) would be added to a all pages, and its items might be useable anywhere.

Thought of generating the header of zze-pages also in the header, footer as well.

Let's look around... such "jump in" are possible not to imagen sacrifice.

* Johann If such sati and samadhi skills can be used for higher attaining... ! But probably as hard as my persons dislike to try to gain all skills to be of more value in this sphere, "independent"... Again Sadhu!
Posted by: Moritz
« on: June 17, 2018, 03:13:15 PM »

I have tried out the [https://www.dokuwiki.org/plugin:data#data_table_output]Data Table[/url] as well.
As far as I understand, it should somehow aggregate the data from all Data Entry inputs everywhere into one table, with possibility for filtering for what data one needs.
But I don't understand it. The table is empty.

A useful thing is probably the "Related pages" output. With that one should somehow be able to list all pages that have similar tags, according to some rules that one can define oneself.

But I think it would take some time to understand all these things. At the moment I have not enough time for much here.
Posted by: Moritz
« on: June 17, 2018, 02:33:09 PM »

Okay, what I understood so far:

The most basic ingredient of Plugin Syntax possibilities is the Data Entry input.

With this one can associate some data to each individual page. The Wiki syntax for adding a data entry is given in the example:

Code: [Select]
---- dataentry projects ----
type            : web development
volume          : 1 Mrd    # how much do they pay?
employees       : Joe, Jane, Jim
description_wiki: **Important** project
customer_page   : customers:microsoft
deadline_dt     : 2009-08-17
server_pages    : servers:devel01, extern:microsoft
website_url     : http://www.microsoft.com
task_tags       : programming, coding, design, html
----

So it starts with "---- dataentry {{some-class-name}} ----" and ends with "----". And the lines in between are definitions for all the data fields that one wants to define.
The name ({{some-class-name}}, or "projects" in the example) is added as a CSS class to the data enry box. One can define the CSS for that in the "{%dokuwiki%}/conf/userstyle.css" file on the server.

I have tried some things out on the Playground page :
Code: [Select]
====== PlayGround ======


Test test test.


---- dataentry whatever ----
something    : something **something**
puhelin      : Nokia, Samsung, Sony, Lg, Motorola
perkele_tags : Perun, Perkwunos
rölli-peikko : Alavaka Yakkha
yksi         : ០
kaksi        : ១
kolme        : ៣
neljä        : ៤
viisii       : ៥
numeros      : ០, ១, ៣, ៤, ៥
smiley_imgs  : http://forum.sangham.net/Smileys/sangham/smile_sangham_sw.gif, http://forum.sangham.net/Smileys/sangham/happy_sangham_sw.gif, http://forum.sangham.net/Smileys/sangham/sad_sangham_sw.gif, http://forum.sangham.net/Smileys/sangham/shock_sangham_sw.gif, http://forum.sangham.net/Smileys/sangham/confused_sangham_sw.gif, http://forum.sangham.net/Smileys/sangham/well_sangham_sw.gif, http://forum.sangham.net/Smileys/sangham/gift_sangham_sw.gif, http://forum.sangham.net/Smileys/sangham/sanghagift_sangham_sw.gif, http://forum.sangham.net/Smileys/sangham/thumb_sangham_sw.gif, http://forum.sangham.net/Smileys/sangham/forgiveme_sangham_sw.gif, http://forum.sangham.net/Smileys/sangham/sadhu_sangham_sw.gif, http://forum.sangham.net/Smileys/sangham/wink_sangham_sw.gif, http://forum.sangham.net/Smileys/sangham/neutral_sangham_sw.gif
smileysmall_img14s  : http://forum.sangham.net/Smileys/sangham/smile_sangham_sw.gif, http://forum.sangham.net/Smileys/sangham/happy_sangham_sw.gif, http://forum.sangham.net/Smileys/sangham/sad_sangham_sw.gif, http://forum.sangham.net/Smileys/sangham/shock_sangham_sw.gif, http://forum.sangham.net/Smileys/sangham/confused_sangham_sw.gif, http://forum.sangham.net/Smileys/sangham/well_sangham_sw.gif, http://forum.sangham.net/Smileys/sangham/gift_sangham_sw.gif, http://forum.sangham.net/Smileys/sangham/sanghagift_sangham_sw.gif, http://forum.sangham.net/Smileys/sangham/thumb_sangham_sw.gif, http://forum.sangham.net/Smileys/sangham/forgiveme_sangham_sw.gif, http://forum.sangham.net/Smileys/sangham/sadhu_sangham_sw.gif, http://forum.sangham.net/Smileys/sangham/wink_sangham_sw.gif, http://forum.sangham.net/Smileys/sangham/neutral_sangham_sw.gif
----
This now looks like this picture in the attached screenshot :


After typing the data entry in with Wiki syntax as shown, it is now possible to use the "Edit" button below the data display box on the page to change everything and add new entries etc. It seems that this is the Edit form you have been looking for.

The syntax description for the Data entry input also includes some explanations about different data types:

Quote
dt    a date in the form YYYY-MM-DD, formatted as simple text but the input is checked for correct format
page    the entry is treated as Wiki pagename and will be linked in output. It is always considered to be an absolute pagename starting in the root namespace. Relative pagenames are not possible.
title    like page, but an additional display title can be given separated by a pipe. It is always considered to be an absolute pagename starting in the root namespace. Relative pagenames are not possible.
nspage    like page, but the column name is treated as namespace for the link.
url    the value will be treated as external link
tag    the values are linked to a page named after the column name, using the value as control filter for a data table (change target by a type alias)
mail    the value is checked to contain a valid email address, additional text is used as name that will be linked with the given email address
img<num>    the input is assumed to be a image URL or local media id. The optional <num> is the wanted width in pixels to resize the image to (defaults to 40)
wiki    render the input as wikitext (use sparingly as this type impacts performance)
pageid    the input is the caption for a link to the data entry page
hidden    the input will not be shown in the data entry or the entry editor

One can specify a data type for an entry by adding '_{{type}}' to its name, where '{{type}}' is one of the data type nams in that table above.
So for example, in my test example there is an entry 'smiley_imgs'.
The 'img' indicates that the data type is expected to be an url to an image file. In the Edit form , this can be set by selecting a type from the Type dropdown menu.
And the 's' at the end indicates that it is a list of multiple values, separated by commas. In the Edit form , one can set the check mark "multi" for this option.

On the displayed wiki page the 'type' and the 's' ending are not displayed. So, although I wrote 'smiley_imgs', the displayed name is only 'smiley', and the 'imgs' is only helping the program interpret the data in the right way, and that is also what is modified in the Edit form "Type" dropdown and "Multi" checkmark.

Images are displayed as 40 pixels wide by default. One can change this by adding the width after 'img'.

For the 'smileysmall' entry, I have typed in 'smileysmall_img14s'. The 14 in this places indicates that the images should all be displayed with the width of 14 pixels.

One thing not workign as expected with the Edit form:
But this is one thing missing from the Edit form . One can not set the size for images in the edit form. It is only possible by editing the code in the page.
Also, if one had defined the size of 'img' entries by editing the page code, then this type info will be deleted by using the edit form.

The entry "perkele" is of type "tag", and is multi-valued. So I typed in "perkele_tags" as the name in Wiki code.
Tags are displayed as links, and when clicking on it, it seems to link to a page where all other pages including this tag should be displayed. But I am not sure yet how that works. At the moment, there is no page for that yet.



So this "Data entry" input is for defining all the data on each wiki page. And this data is displayed in a small box.

I think the other syntax options : Data Table , Data List , Related Pages , Tag Cloud are somehow for collecting all that data from various different pages together and display them all together in some ways.

Posted by: Moritz
« on: June 17, 2018, 01:34:44 PM »

Hmm... yes, on taking a closer look, it looks a bit complicated.   ^-^

I'm going to try out some things to see if I can find out how things work.

http://www.accesstoinsight.eu/doku.php?id=playground:playground (nothing there yet...)
Posted by: Dhammañāṇa
« on: June 17, 2018, 11:57:31 AM »

* Johann :Totally no Upanissaya to Databases and its languages (language-ignorant) ... Atma is just useable for "Wishing/Perceiving" and "Fließbandarbeiten" and only good in "imitating" and developing certain given samples.  ::) His maths, out of merits, was quite-able before integrals and his firm basics lead to end in simple excel-coding and tables. Output and queries, and macros... never lifted up this matters. Probably because such skills would be dangerous like owning a Ferrari.

So far...

No idea how to gain an Data imput interface in the editor at first place and how to build an output in the page display.

No idea how and where to find access to such an edit form (perfect seemin)
Posted by: Dhammañāṇa
« on: June 17, 2018, 11:19:48 AM »

Sadhu!

Lets explore it *smoking head*  :) Always fascinated how that concentration stress of IT, Maths and DB-management is managed without getting crazy.
Posted by: Moritz
« on: June 17, 2018, 11:12:55 AM »

Vandami, Bhante. _/\_

No, I think it would not require much DB and server knowledge.

I have now installed the SQLite plugin and structured data plugin, seen that it is very easy to do this in the administration settings "Extension Manager". Just need to type in the name, search and one click to install.

Now one just needs to find out what do do with it. The settings are found in Administration under "Additional Plugins".
Posted by: Dhammañāṇa
« on: June 17, 2018, 10:28:18 AM »

struct Plugin requires something called SQLite Plugin .

Would that be able to handle without much ddb and server-knowledge, Nyom Moritz ?
Posted by: Dhammañāṇa
« on: June 16, 2018, 09:09:51 PM »

"Required Fields"

Page header:

Titel: primary title of the page/article
Code: [Select]
<div id="H_docTitle">
fieldname: {title_doc}

Sub-Title: sub title of the page/article
Code: [Select]
<div id="H_docSubtitle">
{title_sub_doc}

2. Sub-title: 2nd sub title of the page/article
Code: [Select]
<div id="H_docSubtitle2">
{title_sub2_doc}

Orig Edit info: introduction to author, discriminated by certain text like "by" or "translated from Pali to English by" or "edited/compiled by..."
Code: [Select]
<div id="H_docBy">
{docby}

Title of Author: like "Ven." or "Upasaka"
Code: [Select]
no existing class
{addr_author}

Orig. Author: Name of original Autor
Code: [Select]
<div id="H_docAuthor">
{doc_author}

Translation Edit info: introduction to translator, discriminated by certain text like "translated from English Original to German by" or "translated and edited/compiled by..."
Code: [Select]
<div id="H_docAuthorTransInfo">
{docby_trans}

Title of Translator of original: like "Ven." or "Upasaka" or "Team, Sangha...", optional: if no authorship
Code: [Select]
no existing class
{addr_trans}

Author Translation: Name of translator or team
Code: [Select]
<div id="H_docAuthorTrans">
{doc_author_trans}

Alternativ Translation of Original Links: Links to alternativ translations of the original
Code: [Select]
<div id="H_docAuthorTransAlt">
{doc_author_trans_alt}

Date of Original: Date of Original file and last edit "2012/2016-2018"now, incl "copy-gift"-link to footer; first date original, secound translation
Code: [Select]
<div id="H_copyright">
{doc_date}

Date of Translation: see before
Code: [Select]
no class existing
{doc_date_trans}

Alternative Original-Translation: for Suttas for example (not sure if required for imput or generated)
Code: [Select]
<div id="H_docAltTrans">
{doc_alt_trans}

Alternativ Edition: of Original and/or it's Translation, text with link
Code: [Select]
<div id="H_docAltTrans">
{doc_edition}

Alternativ Formats: kind with icon and link to media file
Code: [Select]
<div id="H_altFormat">
{doc_media}
{doc_media_pdf}
{doc_media_audio}
{...

Previous page/sutta: link (maybe possible to generate)
Code: [Select]
<a class='menu_l' href="..." title="go back to ..."><img src="left.png" alt='[previous]'/></a>
{doc_previous}

Next page/sutta: link (maybe possible to generate)
Code: [Select]
<a class='menu_r' href="..." title="go to ..."><img src="right.png" alt='[previous]'/></a>
{doc_next}

Footer and add Infos, licence, origin, last edits, dedication
Posted by: Dhammañāṇa
« on: June 16, 2018, 07:05:42 PM »

Atma thinks it would be good if a possibility con be used to organice the page/file datas, such as Titel, Subtitel, Author, translator, Edition... kind of gift (licence).

At one had, if such could be organised as Datas, the content-area could be clean of such, putting such as Titel, author (like ATI) in the header, and infos in the footer with certain php requests.

Since my persons view for such is rather limited: maybe such tools as Structured Data Plugin or struct Plugin would match such.