DME development roadmap

Open
#91 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
55/100
Issue type
Documentation
Clarity
Clearly specified
Activity status
Active
Tech stack
cpp
Domain
documentation

Research direction

Read the roadmap issue and its linked milestones and referenced issues (#87–#89) to understand the listed priorities and their status. The issue itself names no repository files or tests to change. Done means the roadmap accurately reflects the current priorities and links contributors to the relevant work.

Written by the indexing model from the issue text.

Description

This roadmap tracks the current priorities for Dewral Map Editor. Milestones group related work. Release scope and timing depend on review and test results.

Current focus

Editor stability and workflows

  • Collect comparable Windows performance results for opening large maps (#87).
  • Run the existing map save and recovery tests before publishing Windows packages (#88).

Next

Canary client profiles

  • Add an optional Canary client profile to DME and verify OTBM 5 maps, client assets and associated XML files (#89).

Contribute

Browse open issues to find work in testing or code. If a request already has an issue, add your use case or a reproducible example there. For a new report, include the DME version, client profile, reproduction steps, and expected and actual behavior. Share a minimal example you can publish or describe how to recreate it.

See Releases for the current stable Windows build.

Dominant language
C++
Stars
12
Forks
10
Avg merge
4h 38m
Merged PRs (30d)
38

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from dewral/DewralMapEditor

All issues in dewral/DewralMapEditor

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.