Dia issueshttps://gitlab.gnome.org/GNOME/dia/-/issues2019-09-27T16:56:24Zhttps://gitlab.gnome.org/GNOME/dia/-/issues/5[Patch] Please document dia's environment variables2019-09-27T16:56:24ZTomáš Pospíšek[Patch] Please document dia's environment variablesone use case for environment variables for dia: when building dia, a test harness will run. The test harness will use shapes and data from /usr/share/dia, which is incorrect because random shapes installed under /usr/share/dia/shapes (su...one use case for environment variables for dia: when building dia, a test harness will run. The test harness will use shapes and data from /usr/share/dia, which is incorrect because random shapes installed under /usr/share/dia/shapes (such as those from Debian's additional dia-shapes package) will make the tests fail.
So it's important to having DIA_SHAPE_PATH set before running the test harness. However the existence of DIA_SHAPE_PATH has not been documented until now...https://gitlab.gnome.org/GNOME/dia/-/issues/24[cleanup / update] checktrans.py requires xml.sax.saxexts and saxlib2019-09-28T02:09:18ZEduard[cleanup / update] checktrans.py requires xml.sax.saxexts and saxlibWhile going through the makefiles for #19, I noticed `sheets/checktrans.py` was not working because it couldn't import `xml.sax.saxexts` and `xml.sax.saxlib`. These are not part of standard python installations.
Creating issue in case ...While going through the makefiles for #19, I noticed `sheets/checktrans.py` was not working because it couldn't import `xml.sax.saxexts` and `xml.sax.saxlib`. These are not part of standard python installations.
Creating issue in case anybody is looking for easy work, `checktrans.py` currently consists of 195 lines of python which need to be changed to use more standard python components:
Suggested tasks:
- [ ] get checktrans.py working as it is
- [ ] install `saxlib` and `saxexts`
- [ ] ensure python detects them
- [ ] run the same command as `make`:
```
./checktrans UML.sheet ER.sheet sybase.sheet FS.sheet network.sheet Flowchart.sheet Circuit.sheet Contact.sheet GRAFCET.sheet chronogram.sheet SADT.sheet Pneumatic.sheet Electric.sheet civil.sheet jigsaw.sheet MSE.sheet SDL.sheet Logic.sheet Misc.sheet Assorted.sheet ciscocomputer.sheet ciscohub.sheet ciscomisc.sheet cisconetwork.sheet ciscotelephony.sheet Cybernetics.sheet IsometricMap.sheet Istar.sheet Jackson.sheet KAOS.sheet ChemEng.sheet AADL.sheet Gane_and_Sarson.sheet BPMN.sheet Lights.sheet Database.sheet Sozi.sheet Shape_Design.sheet
```
- [ ] reverse engineer `checkscript.py` to understand what it does (hopefully it should be similar to `./po-checktrans po/dia.pot ./po/*.po` - the command used to gather statistics from `*.po` files at the end of `make`)
- [ ] remove/replace/rewrite anything that depends on `saxlib` and `saxexts`
Feel free to leave comments if you have any questions or if you like to work on this.
edit by @neduard 10/Feb: add above line.https://gitlab.gnome.org/GNOME/dia/-/issues/30Update ALLCAPS files in root folder2019-09-18T13:45:12ZEduardUpdate ALLCAPS files in root folderThe following files are probably in need of cleanup:
- [ ] AUTHORS
- [ ] COPYING
- [ ] HACKING
- [ ] INSTALL
- [ ] KNOWN_BUGS
- [ ] MAINTAINERS
- [ ] NEWS
- [ ] PACKAGE-MAINTAINERS
- [ ] README
- [ ] RELEASE-PROCESS
- [ ] TODO
Also we ...The following files are probably in need of cleanup:
- [ ] AUTHORS
- [ ] COPYING
- [ ] HACKING
- [ ] INSTALL
- [ ] KNOWN_BUGS
- [ ] MAINTAINERS
- [ ] NEWS
- [ ] PACKAGE-MAINTAINERS
- [ ] README
- [ ] RELEASE-PROCESS
- [ ] TODO
Also we need to:
- [ ] Update / delete / redirect http://www.gnome.org/projects/dia/https://gitlab.gnome.org/GNOME/dia/-/issues/33Build instructions for Windows needed2019-09-18T13:22:41ZkmpmBuild instructions for Windows neededTo be able to help out with Windows related issues it would be nice to have
a current instruction on how to build on windows.
That would make helping out on #22 much easier.
Could be on the gitlab wiki or as a document in the source code.To be able to help out with Windows related issues it would be nice to have
a current instruction on how to build on windows.
That would make helping out on #22 much easier.
Could be on the gitlab wiki or as a document in the source code.https://gitlab.gnome.org/GNOME/dia/-/issues/362Obsolete FSF address is used2019-09-20T13:16:25ZBugzillaObsolete FSF address is used## Submitted by Anders Jonsson `@ajonsson`
**[Link to original bug (#753046)](https://bugzilla.gnome.org/show_bug.cgi?id=753046)**
## Description
In many places app/commands.c:1023 the address to the FSF is included: "Free Software ...## Submitted by Anders Jonsson `@ajonsson`
**[Link to original bug (#753046)](https://bugzilla.gnome.org/show_bug.cgi?id=753046)**
## Description
In many places app/commands.c:1023 the address to the FSF is included: "Free Software Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111-1307, USA."
This is an old address for the FSF. It changed some years ago and is no longer at Temple Place.
Current address can be seen at http://www.fsf.org/about/contact/
Many other occurrences of the address can be found by grepping for "Temple Place".
Regards,
Anders Jonsson
Version: develhttps://gitlab.gnome.org/GNOME/dia/-/issues/515Doc HACKING.md - File contains outdated information2021-12-26T23:21:28ZJim GunnarssonDoc HACKING.md - File contains outdated information## Version
Commit 0997887d97f01be28bf3886dfd3e2002de437930
## Description
The `HACKING.md` is great. It provide a description of the code base and
references to tools used for analysis.
## Issue
The file contains outdated information....## Version
Commit 0997887d97f01be28bf3886dfd3e2002de437930
## Description
The `HACKING.md` is great. It provide a description of the code base and
references to tools used for analysis.
## Issue
The file contains outdated information.
For instance
~~~
`render_object.h` (for doing picture-like objects).
~~~
This file was removed in commit b9181a2b73a1627b498f6d555415d5a656792b50 way
back in 2002.
There might be more outdated info in this file but I do not have a list.
Reference to doxygen is missing.
## Effects
Minor but it would be nice if the file was up to date with the code base.
## Setup
None
## Test case
None