Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Support
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
monkeysign
monkeysign
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
    • Cycle Analytics
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
  • Issues 27
    • Issues 27
    • List
    • Boards
    • Labels
    • Milestones
  • Merge Requests 2
    • Merge Requests 2
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Charts
  • External Wiki
    • External Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • monkeysphere
  • monkeysignmonkeysign
  • Issues
  • #43

Closed
Open
Opened Sep 15, 2016 by anarcat@anarcat
  • Report abuse
  • New issue
Report abuse New issue

switch to the logging module

Instead of rolling our own log/warn/debug interface like right now, we should reuse the logging module, which will enable us to have global logging access.

Right now, we can't log in the gpg module for example, because it doesn't have access to the ui object. gpg, like all other modules, should use logging and the ui should just hook a Handler adequate for its needs.

For example, in the GTK UI, this could be a status bar. An archive of all logging could also be kept accessible in memory for consultation in a specific window, see #44 (closed) for the help dialogs implementation.

Assignee
Assign to
Monkeysign 2.3.0
Milestone
Monkeysign 2.3.0
Assign milestone
Time tracking
None
Due date
None
3
Labels
Development Priority: Normal feature
Assign labels
  • View project labels
Reference: monkeysphere/monkeysign#43