PyPI - backlogops-gui - Versions diffs - 0.1__tar.gz → 0.2__tar.gz - Mend

backlogops-gui 0.1tar.gz → 0.2tar.gz

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (30) hide show

{backlogops_gui-0.1 → backlogops_gui-0.2}/PKG-INFO RENAMED Viewed

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: backlogops-gui
-Version: 0.1
+Version: 0.2
 Summary: Graphical user interface for backlog operations.
 Author: Tom Björkholm
 Author-email: Tom Björkholm <klausuler_linnet0q@icloud.com>
@@ -21,8 +21,9 @@ Classifier: Topic :: Office/Business :: Scheduling
 Requires-Python: >=3.12
 Description-Content-Type: text/markdown
 License-File: LICENSE.txt
-Requires-Dist: backlogops>=0.1
+Requires-Dist: backlogops>=0.2
 Requires-Dist: argcomplete>=3.6.3
+Requires-Dist: versionreporter>=0.3
 Dynamic: author
 Dynamic: license-file
 Dynamic: requires-dist
@@ -32,16 +33,17 @@ Dynamic: requires-python
 There are 3 related packages for backlog operations:
-- backlogops: a collection of library functions to manipulate backlogs
+- **[backlogops](https://pypi.org/project/backlogops/)** a collection of library
+  functions to manipulate backlogs
-- backlogops-cli: command line interface to use the functions in the library.
-  This is just a thin wrapper around the library functions. It serves a dual
-  purpose as both an example of how to use the library and as a tool for the
-  user to use the library.
+- **[backlogops-cli](https://pypi.org/project/backlogops-cli/)** command line
+  interface to use the functions in the library. This is just a thin wrapper
+  around the library functions. It serves a dual purpose as both an example of
+  how to use the library and as a tool for the user to use the library.
-- backlogops-gui: graphical user interface to use the functions in the library.
-  It is based on TkInter. The ambition is to keep it as a thin wrapper around
-  the library.
+- **[backlogops-gui](https://pypi.org/project/backlogops-gui/)** graphical user
+  interface to use the functions in the library. It is based on TkInter. The
+  ambition is to keep it as a thin wrapper around the library.
 ## Available functionality
@@ -70,6 +72,9 @@ The following functionality is available in all 3 packages:
   the key is at a higher level it will bring all items it is a parent of in
   front of it (recursively).
+- Reorder the backlog in release order, optionally taking dependencies into
+  account.
 - Set planned release dates from the estimated release dates.
 - Calculate the release dates from the backlog items estimated ready dates, with
@@ -77,7 +82,23 @@ The following functionality is available in all 3 packages:
 - Validate the backlog and releases for consistency.
-- A wizard to create an available teams configuration.
+- Convert a backlog and releases between table file formats.
+- Order the releases by their planned or estimated date.
+- Rename columns when reading a file and when writing a file.
+- Map custom status names in input files to backlog item statuses.
+- Choose how backlog item levels are written: by number, by name, or both, and
+  configure custom level names.
+- Create stand-alone input or output preset configuration files.
+- Migrate an older configuration or preset file to the current file format.
+- A wizard to create a backlog-ops configuration file with the workforce, named
+  input and output presets, level names, and status name mapping.
 ## The operating model
@@ -95,45 +116,45 @@ availability of the team members.
 Each backlog item has the following fields that are used by the algorithms in
 the library:
-- key: The key of the backlog item. Required. Must be unique. Must not be empty,
-  must not contain whitespace and must not contain any of the characters , . ; :
-  ( ) \[ \] \{ \}.
+- `key` The key of the backlog item. Required. Must be unique. Must not be
+  empty, must not contain whitespace and must not contain any of the characters
+  , . ; : ( ) \[ \] \{ \}.
-- level: The level of the backlog item. Required. Must be an integer.
+- `level` The level of the backlog item. Required. Must be an integer.
-- title: The title of the backlog item. Required.
+- `title` The title of the backlog item. Required.
-- story_points: The story points of the backlog item. Required.
+- `story_points` The story points of the backlog item. Required.
-- status: The status of the backlog item. Required.
+- `status` The status of the backlog item. Required.
-- parent_key: The key of the parent backlog item. Optional. Must exist as a key
+- `parent_key` The key of the parent backlog item. Optional. Must exist as a key
   in the backlog. Parent keys are used to build the hierarchy of the backlog.
   The parent key must be at a higher level than the current item. Parent keys
   introduce implicit dependencies between items: the current item cannot start
   before the parent item starts, and the parent item cannot finish before all
   its children have finished.
-- release: The release of the backlog item. Optional. Follows the same character
-  rules as the key. Must not be empty string.
+- `release` The release of the backlog item. Optional. Follows the same
+  character rules as the key. Must not be empty string.
-- team: The team responsible for the backlog item. Optional. Must not be empty
+- `team` The team responsible for the backlog item. Optional. Must not be empty
   string. Must be a valid team name. If None the item can be done by any team.
   If not None. the item can only be done by the specified team.
-- depends_on_f2s: The list of keys of the backlog items that must have been
+- `depends_on_f2s` The list of keys of the backlog items that must have been
   finished before the current item can start. May be empty.
-- depends_on_f2f: The list of keys of the backlog items that must have been
+- `depends_on_f2f` The list of keys of the backlog items that must have been
   finished before the current item can finish. May be empty.
-- depends_on_s2s: The list of keys of the backlog items that must have been
+- `depends_on_s2s` The list of keys of the backlog items that must have been
   started before the current item can start. May be empty.
-- planned_ready_date: The planned ready date of the backlog item. The date that
+- `planned_ready_date` The planned ready date of the backlog item. The date that
   is communicated to the customer. Optional.
-- estimated_ready_date: The estimated ready date of the backlog item. Optional.
+- `estimated_ready_date` The estimated ready date of the backlog item. Optional.
 Additionally each backlog item can have any number of other fields.
@@ -214,16 +235,29 @@ is in the menus.
     - New demo backlog: Create a demo backlog with some backlog items and
       releases. A new backlog window will be opened with the demo backlog.
+    - Exit: Close the application.
 - Configuration
-    - Run teams wizard...: this lets you configure the teams that work on
+    - Run configuration wizard...: this lets you configure the teams that work on
       the backlog and also other aspects like the dates the company is
       closed for vacation, and preset configuration for the inputs or
       outputs you want to use.
+    - Create IO preset file...: Create a stand-alone input or output preset
+      configuration file via a wizard.
+    - Migrate IO preset file...: Migrate an older input or output preset
+      file to the current file format.
     - Write configuration...: This lets you write the configuration you
       have in application to a file.
+- Help
+    - Report version information: Show version information for the
+      application and its dependencies.
 ## Backlog window
 The backlog window shows 2 read-only tables: one with the backlog and
@@ -235,14 +269,18 @@ one with the list of releases. You will want to use the menus.
     - Order by dependencies...
+    - Order by release order...
     - Estimate ready date...
     - Set planned date from estimated
-    - Adjust release content
+    - Adjust release content...
     - Adjust planned release dates...
+    - Order releases by date...
     - Extract keys...
     - Save to file...
@@ -251,9 +289,9 @@ one with the list of releases. You will want to use the menus.
 ## Test summary
-- Test result: 1066 passed in 16s
+- Test result: 1545 passed in 32s
 - No flake8 warnings.
 - No mypy errors found.
 - No python layout warnings.
-- Built version(s): 0.1
+- Built version(s): 0.2
 - Build and test using Python 3.14.6

{backlogops_gui-0.1 → backlogops_gui-0.2}/README_pypi.md RENAMED Viewed

@@ -2,16 +2,17 @@
 There are 3 related packages for backlog operations:
-- backlogops: a collection of library functions to manipulate backlogs
+- **[backlogops](https://pypi.org/project/backlogops/)** a collection of library
+  functions to manipulate backlogs
-- backlogops-cli: command line interface to use the functions in the library.
-  This is just a thin wrapper around the library functions. It serves a dual
-  purpose as both an example of how to use the library and as a tool for the
-  user to use the library.
+- **[backlogops-cli](https://pypi.org/project/backlogops-cli/)** command line
+  interface to use the functions in the library. This is just a thin wrapper
+  around the library functions. It serves a dual purpose as both an example of
+  how to use the library and as a tool for the user to use the library.
-- backlogops-gui: graphical user interface to use the functions in the library.
-  It is based on TkInter. The ambition is to keep it as a thin wrapper around
-  the library.
+- **[backlogops-gui](https://pypi.org/project/backlogops-gui/)** graphical user
+  interface to use the functions in the library. It is based on TkInter. The
+  ambition is to keep it as a thin wrapper around the library.
 ## Available functionality
@@ -40,6 +41,9 @@ The following functionality is available in all 3 packages:
   the key is at a higher level it will bring all items it is a parent of in
   front of it (recursively).
+- Reorder the backlog in release order, optionally taking dependencies into
+  account.
 - Set planned release dates from the estimated release dates.
 - Calculate the release dates from the backlog items estimated ready dates, with
@@ -47,7 +51,23 @@ The following functionality is available in all 3 packages:
 - Validate the backlog and releases for consistency.
-- A wizard to create an available teams configuration.
+- Convert a backlog and releases between table file formats.
+- Order the releases by their planned or estimated date.
+- Rename columns when reading a file and when writing a file.
+- Map custom status names in input files to backlog item statuses.
+- Choose how backlog item levels are written: by number, by name, or both, and
+  configure custom level names.
+- Create stand-alone input or output preset configuration files.
+- Migrate an older configuration or preset file to the current file format.
+- A wizard to create a backlog-ops configuration file with the workforce, named
+  input and output presets, level names, and status name mapping.
 ## The operating model
@@ -65,45 +85,45 @@ availability of the team members.
 Each backlog item has the following fields that are used by the algorithms in
 the library:
-- key: The key of the backlog item. Required. Must be unique. Must not be empty,
-  must not contain whitespace and must not contain any of the characters , . ; :
-  ( ) \[ \] \{ \}.
+- `key` The key of the backlog item. Required. Must be unique. Must not be
+  empty, must not contain whitespace and must not contain any of the characters
+  , . ; : ( ) \[ \] \{ \}.
-- level: The level of the backlog item. Required. Must be an integer.
+- `level` The level of the backlog item. Required. Must be an integer.
-- title: The title of the backlog item. Required.
+- `title` The title of the backlog item. Required.
-- story_points: The story points of the backlog item. Required.
+- `story_points` The story points of the backlog item. Required.
-- status: The status of the backlog item. Required.
+- `status` The status of the backlog item. Required.
-- parent_key: The key of the parent backlog item. Optional. Must exist as a key
+- `parent_key` The key of the parent backlog item. Optional. Must exist as a key
   in the backlog. Parent keys are used to build the hierarchy of the backlog.
   The parent key must be at a higher level than the current item. Parent keys
   introduce implicit dependencies between items: the current item cannot start
   before the parent item starts, and the parent item cannot finish before all
   its children have finished.
-- release: The release of the backlog item. Optional. Follows the same character
-  rules as the key. Must not be empty string.
+- `release` The release of the backlog item. Optional. Follows the same
+  character rules as the key. Must not be empty string.
-- team: The team responsible for the backlog item. Optional. Must not be empty
+- `team` The team responsible for the backlog item. Optional. Must not be empty
   string. Must be a valid team name. If None the item can be done by any team.
   If not None. the item can only be done by the specified team.
-- depends_on_f2s: The list of keys of the backlog items that must have been
+- `depends_on_f2s` The list of keys of the backlog items that must have been
   finished before the current item can start. May be empty.
-- depends_on_f2f: The list of keys of the backlog items that must have been
+- `depends_on_f2f` The list of keys of the backlog items that must have been
   finished before the current item can finish. May be empty.
-- depends_on_s2s: The list of keys of the backlog items that must have been
+- `depends_on_s2s` The list of keys of the backlog items that must have been
   started before the current item can start. May be empty.
-- planned_ready_date: The planned ready date of the backlog item. The date that
+- `planned_ready_date` The planned ready date of the backlog item. The date that
   is communicated to the customer. Optional.
-- estimated_ready_date: The estimated ready date of the backlog item. Optional.
+- `estimated_ready_date` The estimated ready date of the backlog item. Optional.
 Additionally each backlog item can have any number of other fields.
@@ -184,16 +204,29 @@ is in the menus.
     - New demo backlog: Create a demo backlog with some backlog items and
       releases. A new backlog window will be opened with the demo backlog.
+    - Exit: Close the application.
 - Configuration
-    - Run teams wizard...: this lets you configure the teams that work on
+    - Run configuration wizard...: this lets you configure the teams that work on
       the backlog and also other aspects like the dates the company is
       closed for vacation, and preset configuration for the inputs or
       outputs you want to use.
+    - Create IO preset file...: Create a stand-alone input or output preset
+      configuration file via a wizard.
+    - Migrate IO preset file...: Migrate an older input or output preset
+      file to the current file format.
     - Write configuration...: This lets you write the configuration you
       have in application to a file.
+- Help
+    - Report version information: Show version information for the
+      application and its dependencies.
 ## Backlog window
 The backlog window shows 2 read-only tables: one with the backlog and
@@ -205,14 +238,18 @@ one with the list of releases. You will want to use the menus.
     - Order by dependencies...
+    - Order by release order...
     - Estimate ready date...
     - Set planned date from estimated
-    - Adjust release content
+    - Adjust release content...
     - Adjust planned release dates...
+    - Order releases by date...
     - Extract keys...
     - Save to file...
@@ -221,9 +258,9 @@ one with the list of releases. You will want to use the menus.
 ## Test summary
-- Test result: 1066 passed in 16s
+- Test result: 1545 passed in 32s
 - No flake8 warnings.
 - No mypy errors found.
 - No python layout warnings.
-- Built version(s): 0.1
+- Built version(s): 0.2
 - Build and test using Python 3.14.6

{backlogops_gui-0.1 → backlogops_gui-0.2}/backlogops_gui.egg-info/PKG-INFO RENAMED Viewed

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: backlogops-gui
-Version: 0.1
+Version: 0.2
 Summary: Graphical user interface for backlog operations.
 Author: Tom Björkholm
 Author-email: Tom Björkholm <klausuler_linnet0q@icloud.com>
@@ -21,8 +21,9 @@ Classifier: Topic :: Office/Business :: Scheduling
 Requires-Python: >=3.12
 Description-Content-Type: text/markdown
 License-File: LICENSE.txt
-Requires-Dist: backlogops>=0.1
+Requires-Dist: backlogops>=0.2
 Requires-Dist: argcomplete>=3.6.3
+Requires-Dist: versionreporter>=0.3
 Dynamic: author
 Dynamic: license-file
 Dynamic: requires-dist
@@ -32,16 +33,17 @@ Dynamic: requires-python
 There are 3 related packages for backlog operations:
-- backlogops: a collection of library functions to manipulate backlogs
+- **[backlogops](https://pypi.org/project/backlogops/)** a collection of library
+  functions to manipulate backlogs
-- backlogops-cli: command line interface to use the functions in the library.
-  This is just a thin wrapper around the library functions. It serves a dual
-  purpose as both an example of how to use the library and as a tool for the
-  user to use the library.
+- **[backlogops-cli](https://pypi.org/project/backlogops-cli/)** command line
+  interface to use the functions in the library. This is just a thin wrapper
+  around the library functions. It serves a dual purpose as both an example of
+  how to use the library and as a tool for the user to use the library.
-- backlogops-gui: graphical user interface to use the functions in the library.
-  It is based on TkInter. The ambition is to keep it as a thin wrapper around
-  the library.
+- **[backlogops-gui](https://pypi.org/project/backlogops-gui/)** graphical user
+  interface to use the functions in the library. It is based on TkInter. The
+  ambition is to keep it as a thin wrapper around the library.
 ## Available functionality
@@ -70,6 +72,9 @@ The following functionality is available in all 3 packages:
   the key is at a higher level it will bring all items it is a parent of in
   front of it (recursively).
+- Reorder the backlog in release order, optionally taking dependencies into
+  account.
 - Set planned release dates from the estimated release dates.
 - Calculate the release dates from the backlog items estimated ready dates, with
@@ -77,7 +82,23 @@ The following functionality is available in all 3 packages:
 - Validate the backlog and releases for consistency.
-- A wizard to create an available teams configuration.
+- Convert a backlog and releases between table file formats.
+- Order the releases by their planned or estimated date.
+- Rename columns when reading a file and when writing a file.
+- Map custom status names in input files to backlog item statuses.
+- Choose how backlog item levels are written: by number, by name, or both, and
+  configure custom level names.
+- Create stand-alone input or output preset configuration files.
+- Migrate an older configuration or preset file to the current file format.
+- A wizard to create a backlog-ops configuration file with the workforce, named
+  input and output presets, level names, and status name mapping.
 ## The operating model
@@ -95,45 +116,45 @@ availability of the team members.
 Each backlog item has the following fields that are used by the algorithms in
 the library:
-- key: The key of the backlog item. Required. Must be unique. Must not be empty,
-  must not contain whitespace and must not contain any of the characters , . ; :
-  ( ) \[ \] \{ \}.
+- `key` The key of the backlog item. Required. Must be unique. Must not be
+  empty, must not contain whitespace and must not contain any of the characters
+  , . ; : ( ) \[ \] \{ \}.
-- level: The level of the backlog item. Required. Must be an integer.
+- `level` The level of the backlog item. Required. Must be an integer.
-- title: The title of the backlog item. Required.
+- `title` The title of the backlog item. Required.
-- story_points: The story points of the backlog item. Required.
+- `story_points` The story points of the backlog item. Required.
-- status: The status of the backlog item. Required.
+- `status` The status of the backlog item. Required.
-- parent_key: The key of the parent backlog item. Optional. Must exist as a key
+- `parent_key` The key of the parent backlog item. Optional. Must exist as a key
   in the backlog. Parent keys are used to build the hierarchy of the backlog.
   The parent key must be at a higher level than the current item. Parent keys
   introduce implicit dependencies between items: the current item cannot start
   before the parent item starts, and the parent item cannot finish before all
   its children have finished.
-- release: The release of the backlog item. Optional. Follows the same character
-  rules as the key. Must not be empty string.
+- `release` The release of the backlog item. Optional. Follows the same
+  character rules as the key. Must not be empty string.
-- team: The team responsible for the backlog item. Optional. Must not be empty
+- `team` The team responsible for the backlog item. Optional. Must not be empty
   string. Must be a valid team name. If None the item can be done by any team.
   If not None. the item can only be done by the specified team.
-- depends_on_f2s: The list of keys of the backlog items that must have been
+- `depends_on_f2s` The list of keys of the backlog items that must have been
   finished before the current item can start. May be empty.
-- depends_on_f2f: The list of keys of the backlog items that must have been
+- `depends_on_f2f` The list of keys of the backlog items that must have been
   finished before the current item can finish. May be empty.
-- depends_on_s2s: The list of keys of the backlog items that must have been
+- `depends_on_s2s` The list of keys of the backlog items that must have been
   started before the current item can start. May be empty.
-- planned_ready_date: The planned ready date of the backlog item. The date that
+- `planned_ready_date` The planned ready date of the backlog item. The date that
   is communicated to the customer. Optional.
-- estimated_ready_date: The estimated ready date of the backlog item. Optional.
+- `estimated_ready_date` The estimated ready date of the backlog item. Optional.
 Additionally each backlog item can have any number of other fields.
@@ -214,16 +235,29 @@ is in the menus.
     - New demo backlog: Create a demo backlog with some backlog items and
       releases. A new backlog window will be opened with the demo backlog.
+    - Exit: Close the application.
 - Configuration
-    - Run teams wizard...: this lets you configure the teams that work on
+    - Run configuration wizard...: this lets you configure the teams that work on
       the backlog and also other aspects like the dates the company is
       closed for vacation, and preset configuration for the inputs or
       outputs you want to use.
+    - Create IO preset file...: Create a stand-alone input or output preset
+      configuration file via a wizard.
+    - Migrate IO preset file...: Migrate an older input or output preset
+      file to the current file format.
     - Write configuration...: This lets you write the configuration you
       have in application to a file.
+- Help
+    - Report version information: Show version information for the
+      application and its dependencies.
 ## Backlog window
 The backlog window shows 2 read-only tables: one with the backlog and
@@ -235,14 +269,18 @@ one with the list of releases. You will want to use the menus.
     - Order by dependencies...
+    - Order by release order...
     - Estimate ready date...
     - Set planned date from estimated
-    - Adjust release content
+    - Adjust release content...
     - Adjust planned release dates...
+    - Order releases by date...
     - Extract keys...
     - Save to file...
@@ -251,9 +289,9 @@ one with the list of releases. You will want to use the menus.
 ## Test summary
-- Test result: 1066 passed in 16s
+- Test result: 1545 passed in 32s
 - No flake8 warnings.
 - No mypy errors found.
 - No python layout warnings.
-- Built version(s): 0.1
+- Built version(s): 0.2
 - Build and test using Python 3.14.6

{backlogops_gui-0.1 → backlogops_gui-0.2}/backlogops_gui.egg-info/SOURCES.txt RENAMED Viewed

@@ -10,12 +10,16 @@ backlogops_gui.egg-info/requires.txt
 backlogops_gui.egg-info/top_level.txt
 src/backlogops_gui/__init__.py
 src/backlogops_gui/__main__.py
+src/backlogops_gui/_migrate_warn.py
 src/backlogops_gui/application.py
 src/backlogops_gui/backlog_io.py
 src/backlogops_gui/backlog_window.py
+src/backlogops_gui/blog_version_reporter.py
+src/backlogops_gui/gui_style.py
 src/backlogops_gui/gui_wizard.py
 src/backlogops_gui/io_dialogs.py
 src/backlogops_gui/log_buffer.py
 src/backlogops_gui/py.typed
+src/backlogops_gui/python_version.py
 src/backlogops_gui/table_view.py
 src/backlogops_gui/tcltk_version.py

backlogops_gui-0.2/backlogops_gui.egg-info/requires.txt ADDED Viewed

@@ -0,0 +1,3 @@
+backlogops>=0.2
+argcomplete>=3.6.3
+versionreporter>=0.3

{backlogops_gui-0.1 → backlogops_gui-0.2}/pyproject.toml RENAMED Viewed

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 [project]
 name = "backlogops-gui"
-version = "0.1"
+version = "0.2"
 authors = [
   { name="Tom Björkholm", email="klausuler_linnet0q@icloud.com" },
 ]

{backlogops_gui-0.1 → backlogops_gui-0.2}/setup.py RENAMED Viewed

@@ -5,7 +5,7 @@ from setuptools import setup
 setup(
   name='backlogops-gui',
-  version='0.1',
+  version='0.2',
   description='Graphical user interface for backlog operations.',
   author='Tom Björkholm',
   author_email='klausuler_linnet0q@icloud.com',
@@ -19,7 +19,8 @@ setup(
     ]
   },
   install_requires=[
-    'backlogops >= 0.1',
-    'argcomplete >= 3.6.3'
+    'backlogops >= 0.2',
+    'argcomplete >= 3.6.3',
+    'versionreporter >= 0.3'
   ]
 )

backlogops-gui 0.1__tar.gz → 0.2__tar.gz

backlogops-gui 0.1tar.gz → 0.2tar.gz