Import images
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 12.9k
- Forks
- 2k
- Avg merge
- 4h 27m
- Merged PRs (30d)
- 8
Description
This is the semi-reverse of 'save as image'.
(Moving https://sourceforge.net/apps/mantisbt/tiled/view.php?id=17 here)
> I am involved in a huge community, where "mapping" ist part of the fanwork section
> ( http://fanart.pokefans.net/maps/ ). In addition to map editors, we use image editing
> programs like Paint/Gimp/Fireworks (some work cannot be done with map editors).
> In order to edit them again, images need to be imported. Of course, this could be
> done by importing those maps as a tileset - nevertheless, a proper import-function
> would be much more convenient (the image should be imported as a single layer).
Related to #169:
I wonder if "Import Image" should be a toplevel functionality (such as layer menu->Import Image into Tilelayer)
or if it would be better to first import an image into an image layer and then
converting that image layer to a tile layer by adding the image as a tileset and filling the map with the tiles accordingly.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the issue's linked Mantis report and related issue #169, then determine which of the two proposed import flows is intended. Done means the editor can import an image as a single layer, but the issue does not identify files, tests, or a settled design.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- desktop
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100