7

Would it be too much? A Treeline-Equivalent or more?

For example I have Notes handwritten for schooling. Or I've written it directly into my Notes-Tree under the adequate categories.

- PART I: BAUKONSTRUKTION (building construction)
-- CHAPTER 1: TUEREN UND FENSTER (doors and windows)
--- SUBCHAPTER 1.1: BAURECHTLICHE VORSCHRIFTEN (building law)
---- PARAGRAPH 1
----- NUMBERED LIST
------ ITEM 1
------ ITEM 2
------ ITEM 3
...etc

Now I would like to link a category to an Output-Style, to say: if the node has an output-style, print it into the Document, and show it in the right-view of the window under the register 'preview'.

A Kjots 3.0
________________________________________________________________________
|-> note 1..........|..............Part I..................................
|--> note 1.1......|..........{note1@title}...............................
|--> note 1.2......|......................................................
|---> note 1.2.1..|.Chapter I: {note1.1@title}...........................
|--> note 1.3......|.Chapter II: {note1.2@title}..........................
|.....etc..............|______________________________________________________
|........................| preview |_edit_|_define datatypes_|_templates_|
_________________________________________________________________________
within Kontact to structure a Kword-Document
and fill it up with parameter-wired akonadi-ressources

Or edit additional userdefined fields for Notes,
Define the datatype (text, number, array, table, picture, formula, graphviz)
Define templates to say how and where the data is printed into the document
(for example if the note-type is table, a kspread kpart is available in edit-view)
Define relations to other ressources (is that what rdf is about?)

One more Example:
[note 2] should be a report who of my classmates is working on chapter III
- its name would be 'classmates working on chapter III'
- its children would be note 2.2, childrens type would be a query (lets say
give me all contacts which are related to chapter III)
- and as output-template use the nice-looking table I defined and fill it up
with the data.
[note 3] should be a table filled up with the query:
- give me all chapters, its period dates in a degree-course-scheme
(a calendar-ressource the notes are linked with), the names of the
subchapters and its writers.

Do you know what I mean? Hopefully my concept is not very imposing

Is anyone working on? would like to participate in my free-time

It looks like you are recommending a regex-customised (as everybody has their own way of formatting their plaintext notes) markup language that could be imported into documents.

The regex-customisable bit is a new idea (but imho a little impractical). Have you looked at LaTeX? I think it'll suit your requirements better.

yes for sure, it looks like
you are right, now I use treeline and added scripts to export a pdf via LaTeX, and its working fine. But its a workaround.

To make it a bit clearer, I thought of a Mulit-Dimensional-Note-Tree within KJots. A Database for Note-Nodes, but with opportunity to define custom Note-Types for example (like treeline does). And ability to define an Output-Type and -Templates. I think it would be very practical.
Especially if we could
- make References to other Akonadi-Resources, filter them, append as children
- Access the Resources within Templates with a kind of xpath/jsonquery syntax (+regex)
- Write plaintext-templates or optional use Template-Editor (like KPlato has for Reports)
- Access to Koffice-functions within Template-Editor (like Braindump 0.9.0 does)
- assign Pre- and Post-Processing Scripts (python) to Nodes (for example give the output result to pdflatex)

Just dreamin, but on the other hand these ideas are probably refered to the wrong architecture-level.
What do you think?