Skip to content

Commit

Permalink
Merge branch 'ladybugUserStories_20240620' into ladybugUserStories_20…
Browse files Browse the repository at this point in the history
…240617
  • Loading branch information
Martijn Dirkse committed Jun 21, 2024
2 parents 97dd846 + d5b83a2 commit b5ed31b
Show file tree
Hide file tree
Showing 2 changed files with 4 additions and 1 deletion.
3 changes: 3 additions & 0 deletions docs/source/index.rst
Original file line number Diff line number Diff line change
Expand Up @@ -3,6 +3,9 @@ Frank!Manual

This is the user manual of the Frank!Framework, an open-source platform to quickly build enterprise applications. To have an enterprise application, or as we say a Frank, you have to deploy the Frank!Framework in combination with XML configuration files. This manual explains to Frank developers how to develop Frank configs (chapters :ref:`gettingStarted` and :ref:`advancedDevelopment`). Operators or site owners can read chapter :ref:`operator` about monitoring and managing a Frank. System administrators can learn how to deploy a Frank on their infrastructure (chapter :ref:`deploying`). There is also material about :ref:`testing`.

If you have remarks or questions about the Frank!Framework, please go to GitHub Discussions: https://github.com/frankframework/frankframework/discussions.


The Java source code of the Frank!Framework can be found at https://github.com/frankframework/frankframework. You can also find release notes here, see https://github.com/frankframework/frankframework/releases. See also http://frankframework.org for more information.

Below you see the table of contents of the Frank!Manual:
Expand Down
2 changes: 1 addition & 1 deletion misc/LADYBUG_USER_STORIES.md
Original file line number Diff line number Diff line change
Expand Up @@ -131,7 +131,7 @@ NOTE: We implement story **120** because Frank developers can write Spring confi
NOTE: Presently, some features of Ladybug are attached to the root node of a report.

* In the old Echo2 GUI, there is an "Edit" button in the tree view that puts the report in "edit mode". In edit mode, you have an editable message when you click a node in the tree view. There are also metadata fields, some of them editable and some of them read-only. When you select the top level node, you can edit a description. This way you can add a description of a report that exists in the debug tab.
* In the test tab you can "open" a report. This is the user interface for main user story [I want to turn a report into a test case](#i-want-to-turn-a-report-into-a-test-case).Doing so opens a new tab with a tree view with editable node information next to it, like "edit mode" in the debug tab's tree view. Also in this case the root node of a report is relevant in the current implementation of Ladybug.
* In the test tab you can "open" a report. This is the user interface for main user story [I want to turn a report into a test case](#i-want-to-turn-a-report-into-a-test-case). Doing so opens a new tab with a tree view with editable node information next to it, like "edit mode" in the debug tab's tree view. Also in this case the root node of a report is relevant in the current implementation of Ladybug.
* When you click the root node of a report you see it as XML. This combines nicely with an edit field to enter an XSLT transformation (story **2010**)
* When you click the root node of a report you have the option there to enter the description (story **2040**).

Expand Down

0 comments on commit b5ed31b

Please sign in to comment.