From 25141bec595a5aa13db2cb9ae75d44a2f103a457 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Uwe=20A=C3=9Fmann?= <uwe.assmann@tu-dresden.de>
Date: Wed, 13 Dec 2023 12:07:39 +0100
Subject: [PATCH] new project

---
 README.md         |  92 +------------------
 test-varylist.tex | 228 ++++++++++++++++++++++++++++++++++++++++++++++
 varylist.sty      |  84 +++++++++++++++++
 3 files changed, 314 insertions(+), 90 deletions(-)
 create mode 100644 test-varylist.tex
 create mode 100644 varylist.sty

diff --git a/README.md b/README.md
index a40b768..872cd7e 100644
--- a/README.md
+++ b/README.md
@@ -1,93 +1,5 @@
-# varylist
+#  LaTeX varylist package
 
 
+This package helps to write papers in bullet lists, and morph them by several global configuration switches to plain texts.
 
-## Getting started
-
-To make it easy for you to get started with GitLab, here's a list of recommended next steps.
-
-Already a pro? Just edit this README.md and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)!
-
-## Add your files
-
-- [ ] [Create](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#create-a-file) or [upload](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#upload-a-file) files
-- [ ] [Add files using the command line](https://docs.gitlab.com/ee/gitlab-basics/add-file.html#add-a-file-using-the-command-line) or push an existing Git repository with the following command:
-
-```
-cd existing_repo
-git remote add origin https://git-st.inf.tu-dresden.de/stgroup/misc/latex-templates/varylist.git
-git branch -M main
-git push -uf origin main
-```
-
-## Integrate with your tools
-
-- [ ] [Set up project integrations](https://git-st.inf.tu-dresden.de/stgroup/misc/latex-templates/varylist/-/settings/integrations)
-
-## Collaborate with your team
-
-- [ ] [Invite team members and collaborators](https://docs.gitlab.com/ee/user/project/members/)
-- [ ] [Create a new merge request](https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html)
-- [ ] [Automatically close issues from merge requests](https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically)
-- [ ] [Enable merge request approvals](https://docs.gitlab.com/ee/user/project/merge_requests/approvals/)
-- [ ] [Set auto-merge](https://docs.gitlab.com/ee/user/project/merge_requests/merge_when_pipeline_succeeds.html)
-
-## Test and Deploy
-
-Use the built-in continuous integration in GitLab.
-
-- [ ] [Get started with GitLab CI/CD](https://docs.gitlab.com/ee/ci/quick_start/index.html)
-- [ ] [Analyze your code for known vulnerabilities with Static Application Security Testing (SAST)](https://docs.gitlab.com/ee/user/application_security/sast/)
-- [ ] [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/ee/topics/autodevops/requirements.html)
-- [ ] [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/ee/user/clusters/agent/)
-- [ ] [Set up protected environments](https://docs.gitlab.com/ee/ci/environments/protected_environments.html)
-
-***
-
-# Editing this README
-
-When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thanks to [makeareadme.com](https://www.makeareadme.com/) for this template.
-
-## Suggestions for a good README
-
-Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information.
-
-## Name
-Choose a self-explaining name for your project.
-
-## Description
-Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors.
-
-## Badges
-On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge.
-
-## Visuals
-Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method.
-
-## Installation
-Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection.
-
-## Usage
-Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README.
-
-## Support
-Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc.
-
-## Roadmap
-If you have ideas for releases in the future, it is a good idea to list them in the README.
-
-## Contributing
-State if you are open to contributions and what your requirements are for accepting them.
-
-For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self.
-
-You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser.
-
-## Authors and acknowledgment
-Show your appreciation to those who have contributed to the project.
-
-## License
-For open source projects, say how it is licensed.
-
-## Project status
-If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers.
diff --git a/test-varylist.tex b/test-varylist.tex
new file mode 100644
index 0000000..fdb0de7
--- /dev/null
+++ b/test-varylist.tex
@@ -0,0 +1,228 @@
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+% test file for varylist.sty, with examples
+% @author Uwe A�mann
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+
+\documentclass[a4paper,12pt]{article}
+\usepackage[latin1]{inputenc}
+\usepackage[T1]{fontenc}
+\usepackage{varyenumitem}
+
+\usepackage{xspace}
+\usepackage{lipsum}
+
+% creating some blind lipsum text fragments
+\def\a{\lipsum[][1-2] }
+\def\b{\lipsum[][3-4] }
+\def\c{\lipsum[][5-6] }
+\def\d{\lipsum[][7-8] }
+
+% new environments for variable bullet lists
+\usepackage{varyenumitem}
+
+\begin{document}
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+
+\title{Morphing Sketches of Paragraphs into Real Text based on Variable Lists
+  with  the \LaTeX\ Style  \texttt{enumitem.sty}}
+\author{Uwe A�mann}
+\maketitle
+\begin{abstract}
+  This contains examples of configurable lists for sketching of papers
+  with bullet lists.
+  Because these lists can be configured by global switches, the layout
+  of the list can be changed globally. 
+  In particular, this can be used to morph bullet-list papers in
+  sketch form to papers with nice looking running texts, just by
+  changing a global configuration parameter.
+\end{abstract}
+\section{Enumerate Lists}
+
+\SEPARATEPARtrue
+\textbf{Paragraphed enumeration:}
+\begin{varyenumerate}
+\item \a
+\item \b
+\item \c
+\item \d
+\end{varyenumerate}
+
+\SEPARATEPARfalse
+\LABELINGtrue
+\textbf{Inlined enumeration:}
+\begin{varyenumerate}
+\item \a
+\item \b
+\item \c
+\item \d
+\end{varyenumerate}
+
+\SEPARATEPARfalse
+\LABELINGfalse
+\textbf{Inlined enumeration without labels:}
+\begin{varyenumerate}
+\item \a
+\item \b
+\item \c
+\item \d
+\end{varyenumerate}
+
+\section{Itemize Lists}
+
+\SEPARATEPARtrue
+\textbf{Paragraphed itemized:}
+\begin{varyitemize}
+\item \a
+\item \b
+\item \c
+\item \d
+\end{varyitemize}
+
+\SEPARATEPARfalse
+\LABELINGtrue
+\textbf{Inlined itemized:}
+\begin{varyitemize}
+\item \a
+\item \b
+\item \c
+\item \d
+\end{varyitemize}
+
+\SEPARATEPARfalse
+\LABELINGfalse
+\textbf{Inlined itemized without labels:}
+\begin{varyitemize}
+\item \a
+\item \b
+\item \c
+\item \d
+\end{varyitemize}
+
+\section{Variable Lists}
+%%%%%%%%%%%%%%%%%%%%%%%%
+\label{sec:variable-lists}
+
+\ENUMtrue
+\SEPARATEPARfalse
+\LABELINGtrue
+\textbf{Inlined enumeration with labels:}
+\begin{varylist}
+\item \a
+\item \b
+\item \c
+\item \d
+\end{varylist}
+
+
+\ENUMfalse
+\SEPARATEPARfalse
+\LABELINGtrue
+\textbf{Inlined itemized with labels:}
+\begin{varylist}
+\item \a
+\item \b
+\item \c
+\item \d
+\end{varylist}
+
+
+
+\section{How to Morph a Bullet List (from a Sketch Paper) to a Running Paragraph}
+%%%%%%%%%%%%%%%%%%%%%%%%
+\label{sec:variable-lists}
+
+\def\a{The main result of this paper is a new method for generating cooking recipes
+  from Petri nets.}
+\def\b{The cooking recipe is specified with a Petri net in which the places are characterized by a photo of the (partial) state (\emph{place photo}).}
+\def\c{Cooking activities are modeled by transitions of the Petri net.}
+\def\d{The end state is characterized by an end place and a photo of
+  the finished cooking process.}
+\def\e{Our main observation is that a cooking process can be naturally
+  modeled by a SESEP (single entry - single exit place) petri
+  net. Cook with Petri!}
+
+
+Morphing can start with a paragraph sketch in enumerate-list form 
+\emph{(Outlined enumeration with labels):}
+
+\vspace{1mm} \hrule
+
+\ENUMtrue\SEPARATEPARtrue\LABELINGtrue
+\begin{varylist}
+\item \a
+\item \b
+\item \c
+\item \d
+\item \e
+\end{varylist}
+\hrule \vspace{2mm}
+
+Alternatively, it may start with an itemized list
+\emph{(Outlined bullet list with labels):}
+
+\vspace{1mm} \hrule
+
+\ENUMfalse\SEPARATEPARtrue\LABELINGtrue
+\begin{varylist}
+\item \a
+\item \b
+\item \c
+\item \d
+\item \e
+\end{varylist}
+
+\vspace{2mm}
+\hrule 
+\vspace{2mm}
+If \texttt{SEPARATEPAR} is set to false, the paragraph is inlined
+\emph{(Inlined enumerated with labels):}
+
+\vspace{1mm} 
+\hrule
+\vspace{1mm} 
+
+\ENUMtrue
+\SEPARATEPARfalse
+\LABELINGtrue
+\begin{varylist}
+\item \a
+\item \b
+\item \c
+\item \d
+\item \e
+\end{varylist}
+
+\vspace{1mm} 
+\hrule \vspace{2mm}
+
+If, additionally, \texttt{LABELING} is set to false, the labels vanish,
+and the bullet list looks like running text
+\emph{(Inlined running without labels):}
+
+\vspace{2mm} 
+\hrule
+\vspace{1mm} 
+
+\ENUMtrue
+\SEPARATEPARfalse
+\LABELINGfalse
+\begin{varylist}
+\item \a
+\item \b
+\item \c
+\item \d
+\item \e
+\end{varylist}
+
+\vspace{2mm}
+\hrule 
+
+
+
+
+\end{document}
+
+%%% Local Variables: 
+%%% mode: latex
+%%% TeX-master: t
+%%% End: 
diff --git a/varylist.sty b/varylist.sty
new file mode 100644
index 0000000..8eaf64b
--- /dev/null
+++ b/varylist.sty
@@ -0,0 +1,84 @@
+% varylist.sty 
+% varylists are configurable lists, based on the
+% configuration switches for varylist, varyenumerate and varyitemize
+% @author: Uwe Aßmann @date: 2023-12-13
+
+
+\ProvidesPackage{varylist}[2023/12/12 v0.1 variable enum and item lists based on enumitem.sty]
+
+\RequirePackage[inline]{enumitem}
+
+\newif\ifENUM\ENUMtrue
+\newif\ifSEPARATEPAR\SEPARATEPARfalse
+\newif\ifLABELING\LABELINGtrue
+
+% this is a new environment on lists-in-a-paragraph-as-sentences.
+\newlist{VErunninglist}{itemize*}{2}
+\setlist[VErunninglist]{label=\hspace{-1mm}}
+%\setlist[VErunninglist]{label=\xspace}
+
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+% Variable enumerate list with several modes
+\newenvironment{varyenumerate}{%
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+\ifSEPARATEPAR
+\begin{enumerate}[noitemsep]
+\else
+ \ifLABELING
+ \begin{enumerate*}
+ \else
+ \begin{VErunninglist}
+ \fi
+\fi
+}{%%%%%%%%%%%%
+\ifSEPARATEPAR
+\end{enumerate}
+\else
+ \ifLABELING
+ \end{enumerate*}
+ \else
+ \end{VErunninglist}
+ \fi
+\fi
+}
+
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+% Variable itemize list with several modes
+\newenvironment{varyitemize}{%
+%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
+\ifSEPARATEPAR
+\begin{itemize}[noitemsep]
+\else
+ \ifLABELING
+ \begin{itemize*}
+ \else
+ \begin{VErunninglist}
+ \fi
+\fi
+}{%%%%%%%%%%%%
+\ifSEPARATEPAR
+\end{itemize}
+\else
+ \ifLABELING
+ \end{itemize*}
+ \else
+ \end{VErunninglist}
+ \fi
+\fi
+}
+
+% enumerations or iteimizes
+\newenvironment{varylist}{%
+\ifENUM
+\begin{varyenumerate}
+\else
+\begin{varyitemize}
+\fi
+}{%%%%%%%%%%%%
+\ifENUM
+\end{varyenumerate}
+\else
+ \end{varyitemize}
+\fi
+}
+
-- 
GitLab