rizinorg/cutter

Rework configuration in InitialOptionDialog

Open

#1,423 opened on Apr 4, 2019

View on GitHub
 (0 comments) (0 reactions) (1 assignee)C++ (14,852 stars) (1,123 forks)batch import
EnhancementHacktoberFestQuestiongood first issue

Description

Too many "cmd ?e". Should also move setConfig API from CutterCore to Configuration I think. Maybe even rename Configuration to core/CutterConfiguration.

Contributor guide

Tech stack
cpp
Domain
desktop
Issue type
refactor
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
unclear
Prerequisites
C++QtCutter architecture
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20
Research direction
Investigate the InitialOptionDialog class and its use of 'cmd ?e' commands. Also examine the CutterCore and Configuration classes to understand the current setConfig API. Consider moving setConfig to Configuration and possibly renaming Configuration to core/CutterConfiguration. There are no comments or PRs to guide further, so the exact scope needs clarification from maintainers.