Merge remote-tracking branch 'origin/master'

Conflicts:
	src/org/openlowcode/tools/pdf/PDFMultiPageTable.java

Author: Open Lowcode SAS

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,38 @@
+---
+name: Bug report
+about: Create a report to help us improve
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+**Describe the bug**
+A clear and concise description of what the bug is.
+
+**To Reproduce**
+Steps to reproduce the behavior:
+1. Go to '...'
+2. Click on '....'
+3. Scroll down to '....'
+4. See error
+
+**Expected behavior**
+A clear and concise description of what you expected to happen.
+
+**Screenshots**
+If applicable, add screenshots to help explain your problem.
+
+**Desktop (please complete the following information):**
+ - OS: [e.g. iOS]
+ - Browser [e.g. chrome, safari]
+ - Version [e.g. 22]
+
+**Smartphone (please complete the following information):**
+ - Device: [e.g. iPhone6]
+ - OS: [e.g. iOS8.1]
+ - Browser [e.g. stock browser, safari]
+ - Version [e.g. 22]
+
+**Additional context**
+Add any other context about the problem here.

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,23 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+**Is your feature request related to a problem? Please describe.**
+A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+
+**Describe the solution you'd like**
+A clear and concise description of what you want to happen.
+
+**Describe alternatives you've considered**
+A clear and concise description of any alternative solutions or features you've considered.
+
+**Additional context**
+Add any other context or screenshots about the feature request here.
+
+**Timeframe and Conditions**
+Precise here if you have a specific timeframe in mind, and may consider having the feature developed for a fee

CODE_OF_CONDUCT.md

@@ -0,0 +1,76 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, sex characteristics, gender identity and expression,
+level of experience, education, socio-economic status, nationality, personal
+appearance, race, religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or
+ advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic
+ address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+ professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or
+reject comments, commits, code, wiki edits, issues, and other contributions
+that are not aligned to this Code of Conduct, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. Examples of
+representing a project or community include using an official project e-mail
+address, posting via an official social media account, or acting as an appointed
+representative at an online or offline event. Representation of a project may be
+further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team at welcome@openlowcode.com. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. The project team is
+obligated to maintain confidentiality with regard to the reporter of an incident.
+Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see
+https://www.contributor-covenant.org/faq

CONTRIBUTING.md

@@ -0,0 +1,26 @@
+# How to contribute
+
+You are welcome to contribute to the Open-Lowcode framework. Guidelines will be setup more precisely with time, feel free to:
+* raise bugs and issues on Github
+* propose simple improvements on Github. Of course, proposing a solution (pull request) is really appreciated. 
+* discuss architecture questions and major priorities on the [forum](https://openlowcode.org/open-lowcode-forum/)
+
+As a company using the Open-Lowcode framework, you can support the initiative by:
+* asking for extensions of the framework for a fee (available, just precise it when writing a feature request)
+* purchasing support to the product (not yet available)
+
+# Courtesy & Manners
+
+Some of the greatest mind in many areas practice perfect courtesy, there is no reason we do not do the same. Exchanging in a courteous and considerate manner is really appreciated.
+
+# Core Values
+
+Debate on the framework is highly welcome. The author of the framework fully acknowledges you may have stronger skills in a number of areas, and bring a lot of value and insights. 
+
+Nonetheless, the framework is built on a number of strong hypothesis and choices, contributors are expected to accept, or, at least, tolerate them. Values are discussed in greater length in the [Open Lowcode blog](https://openlowcode.com/blog/). Please take this as a warning that this is, say, a bossa-nova concert, and if you are expecting heavy-metal (or the other way round), you will likely be disappointed.
+
+Some core values include:
+* keep complexity reasonnable. To make a parallel, if the tool was a rich-text format, the objective would be something like markdown (easy and good enough), not something like html (powerful but verbose). This is driven by the need to be usable in enterprise context with varying development skill levels. 
+* prioritize performance and ease of debugging. This is one of the main drivers behind automatically generated code, compared to alternative approaches such as complex frameworks using reflection.
+* limit the number of dependencies, within reasons. Open Lowcode relies on major technological frameworks and standards such as SQL, Java SDK (not Enterprise), JavaFX, and some outstanding Apache libraries around PDF and reading office documents. However, the core of the framework is all home-made. This allows end-to-end optimization, and better control of obsolescence. There may be discussions on this point though on the margin, as probably, the current version takes things slightly to the extreme.
+* have reasonnable formal quality of code (but not more). The framework was developped under time constraints, and is likely to remain so for the foreseable future. It is fully acknowledge the code produced may not be used as example of good coding practices.

README.md

@@ -1,9 +1,9 @@
 # Open-Lowcode
 ### Open-source Low-code platform to build applications quick and fast.
 
-published by [Open Lowcode SAS](https://openlowcode.com). You may also want to look at the [Community Page](https://openlowcode.org).
+published by [Open Lowcode SAS](https://openlowcode.com). You may also want to look at the [Community Page](https://openlowcode.org) and the [javadoc](https://openlowcode.org/javadoc/).
 
-The project includes the main low-code platform (a full application server), and also some java tools you may find useful in other contexts. You are of course very welcome to use just the java tools if it makes sense for you.
+The project includes the main low-code platform (a full application server), and also some java tools you may find useful in other contexts. You are of course very welcome to use just the java tools if it makes sense for you. As of today, the Open Lowcode PDF framework is released.
 
 You are welcome to get involved and contribute to the project by:
 * suggesting new features or bug corrections. right here on github or on the [community forum](https://openlowcode.org/open-lowcode-forum/). Of course, the fixes will be best effort
@@ -12,14 +12,4 @@ You are welcome to get involved and contribute to the project by:
 
 This is the first open-source project of the author, so there may be technical mistakes done, do not hesitate to suggest improvements on the way the project is organized too.
 
-# Core Values
-
-Debate on the framework is highly welcome. The author of the framework fully acknowledges you may have stronger skills in a number of areas, and bring a lot of value and insights. 
-
-Nonetheless, the framework is built on a number of strong hypothesis and choices, contributors are expected to accept, or, at least, tolerate them. Values are discussed in greater length in the [Open Lowcode blog](https://openlowcode.com/blog/). Please take this as a warning that this is, say, a bossa-nova concert, and if you are expecting heavy-metal (or the other way round), you will likely be disappointed.
-
-Some core values include:
-* keep complexity reasonnable. To make a parallel, if the tool was a rich-text format, the objective would be something like markdown (easy and good enough), not something like html (powerful but verbose). This is driven by the need to be usable in enterprise context with varying development skill levels. 
-* prioritize performance and ease of debugging. This is one of the main drivers behind automatically generated code, compared to alternative approaches such as complex frameworks using reflection.
-* limit the number of dependencies, within reasons. Open Lowcode relies on major technological frameworks and standards such as SQL, Java SDK (not Enterprise), JavaFX, and some outstanding Apache libraries around PDF and reading office documents. However, the core of the framework is all home-made. This allows end-to-end optimization, and better control of obsolescence. There may be discussions on this point though on the margin, as probably, the current version takes things slightly to the extreme.
-* have reasonnable formal quality of code (but not more). The framework was developped under time constraints, and is likely to remain so for the foreseable future. It is fully acknowledge the code produced may not be used as example of good coding practices.
+You may also want to consult the [contributor guidelines](https://github.com/openlowcode/Open-Lowcode/blob/master/CONTRIBUTING.md) and [code of conduct](https://github.com/openlowcode/Open-Lowcode/blob/master/CODE_OF_CONDUCT.md).

src/org/openlowcode/tools/pdf/PDFMultiPageTable.java

@@ -276,7 +276,7 @@ private float getLineHeight(float leftinmm, float rightinmm, int lineindex) thro
 		float maxheight = 0;
 
 		for (int i = 0; i < this.columnnumber; i++) {
-			float columnwidth = this.columnwidthinmm[i];
+			float columnwidth = this.columnwidthinmm[i];
 			float cellheight = getCellHeight(columnwidth, lineindex, i);
 			if (cellheight > maxheight)
 				maxheight = cellheight;