Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • KMyMoney KMyMoney
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 38
    • Issues 38
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 11
    • Merge requests 11
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Releases
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • OfficeOffice
  • KMyMoneyKMyMoney
  • Issues
  • #40
Closed
Open
Issue created Mar 09, 2021 by Dawid Wrobel@wrobeldaDeveloper

A UI/UX consistent RegEx/Wildcard selection where appropriate

We offer RegEx in a number of areas, but a regular Jane/Joe would most likely benefit more from a wildcard syntax (QRegularExpression::wildcardToRegularExpression), which they surely are more likely to be familiar with.

We probably need a more systemic approach to this. I suppose offering an "options" button next to applicable text inputs with "Use Regular Expressions", "Use Wildcards" and "Case Sensitive" switches would work, akin to e Konsole's or Kate's find bar settings showcased in the comments in system/dolphin!74 (comment 136631)

Moreover, we should consider approaching the regex usage in automatically created filters differently, e.g. possibly conceal the the implicit regex symbols by default, to avoid confusion as exemplified by this post: https://forum.kde.org/viewtopic.php?f=69&t=170270#p443335

Edited Mar 09, 2021 by Dawid Wrobel
Assignee
Assign to
Time tracking