| 2012-03-14 12:12:16 |
Eike |
bug |
|
|
added bug |
| 2012-03-14 12:12:18 |
Eike |
bug-repo-syncer: importance |
Undecided |
Wishlist |
|
| 2012-03-14 12:12:18 |
Eike |
bug-repo-syncer: status |
New |
Confirmed |
|
| 2012-03-14 12:12:18 |
Eike |
bug-repo-syncer: milestone |
|
0.3.0 |
|
| 2012-03-14 12:12:18 |
Eike |
bug-repo-syncer: assignee |
|
Eike (eike-welk) |
|
| 2012-03-14 12:12:19 |
Eike |
summary |
dummy |
Separate Translator Objects |
|
| 2012-03-14 12:12:19 |
Eike |
description |
dummy |
Currently there are two translators, that are shared by all repository
controllers: the translator for people's names, and the translator for
milestones. Translation for bug status values is hard coded into the repository
controllers.
Proposal
The two different tasks: translating bugs, and communicating with the
repository, should be separated. Separate objects should be responsible for
them. This probably simplifies the whole architecture, the different
translation tasks are all unified in one filter object. (Translating people,
milestones, bug status values, bug links.)
== TODO ==
Design
== Done ==
== See Also ==
https://sourceforge.net/apps/trac/bug-repo-syncer/wiki/SeparateTranslators
https://blueprints.launchpad.net/bug-repo-syncer/+spec/separate-translator-objects |
|
| 2012-03-16 09:54:53 |
Eike |
description |
Currently there are two translators, that are shared by all repository
controllers: the translator for people's names, and the translator for
milestones. Translation for bug status values is hard coded into the repository
controllers.
Proposal
The two different tasks: translating bugs, and communicating with the
repository, should be separated. Separate objects should be responsible for
them. This probably simplifies the whole architecture, the different
translation tasks are all unified in one filter object. (Translating people,
milestones, bug status values, bug links.)
== TODO ==
Design
== Done ==
== See Also ==
https://sourceforge.net/apps/trac/bug-repo-syncer/wiki/SeparateTranslators
https://blueprints.launchpad.net/bug-repo-syncer/+spec/separate-translator-objects |
Currently there are two translators, that are shared by all repository
controllers: the translator for people's names, and the translator for
milestones. Translation for bug status values is hard coded into the repository
controllers.
Proposal
The two different tasks: translating bugs, and communicating with the
repository, should be separated. Separate objects should be responsible for
them. This probably simplifies the whole architecture, the different
translation tasks are all unified in one filter object. (Translating people,
milestones, bug status values, bug links.)
== TODO ==
* port `RepoController` descendants to new infrastructure
* Design nice convention for associated objects for one type of repository:
controller, filter, bug data, comparison function,
factory function for creating the objects
* remove filter code and create separate filters from it
* port tests
== Done ==
Design (mostly)
== See Also ==
https://sourceforge.net/apps/trac/bug-repo-syncer/wiki/SeparateTranslators
https://blueprints.launchpad.net/bug-repo-syncer/+spec/separate-translator-objects |
|
| 2012-03-16 09:59:39 |
Eike |
description |
Currently there are two translators, that are shared by all repository
controllers: the translator for people's names, and the translator for
milestones. Translation for bug status values is hard coded into the repository
controllers.
Proposal
The two different tasks: translating bugs, and communicating with the
repository, should be separated. Separate objects should be responsible for
them. This probably simplifies the whole architecture, the different
translation tasks are all unified in one filter object. (Translating people,
milestones, bug status values, bug links.)
== TODO ==
* port `RepoController` descendants to new infrastructure
* Design nice convention for associated objects for one type of repository:
controller, filter, bug data, comparison function,
factory function for creating the objects
* remove filter code and create separate filters from it
* port tests
== Done ==
Design (mostly)
== See Also ==
https://sourceforge.net/apps/trac/bug-repo-syncer/wiki/SeparateTranslators
https://blueprints.launchpad.net/bug-repo-syncer/+spec/separate-translator-objects |
Currently there are two translators, that are shared by all repository
controllers: the translator for people's names, and the translator for
milestones. Translation for bug status values is hard coded into the repository
controllers.
Proposal
The two different tasks: translating bugs, and communicating with the
repository, should be separated. Separate objects should be responsible for
them. This probably simplifies the whole architecture, the different
translation tasks are all unified in one filter object. (Translating people,
milestones, bug status values, bug links.)
== TODO ==
* Port `RepoController` descendants to new infrastructure
* Design nice convention for associated objects for one type of repository:
controller, filter, bug data, comparison function,
factory function for creating the objects
* Remove filter code and create separate filters from it
* Port tests
* Port `SyncTaskExecutor` to new infrastructure
== Done ==
* Design (basic structure)
* Implementation of `BugPipeline`
== See Also ==
https://sourceforge.net/apps/trac/bug-repo-syncer/wiki/SeparateTranslators
https://blueprints.launchpad.net/bug-repo-syncer/+spec/separate-translator-objects |
|
| 2012-03-17 17:28:32 |
Eike |
bug-repo-syncer: status |
Confirmed |
In Progress |
|
| 2012-03-17 17:28:32 |
Eike |
description |
Currently there are two translators, that are shared by all repository
controllers: the translator for people's names, and the translator for
milestones. Translation for bug status values is hard coded into the repository
controllers.
Proposal
The two different tasks: translating bugs, and communicating with the
repository, should be separated. Separate objects should be responsible for
them. This probably simplifies the whole architecture, the different
translation tasks are all unified in one filter object. (Translating people,
milestones, bug status values, bug links.)
== TODO ==
* Port `RepoController` descendants to new infrastructure
* Design nice convention for associated objects for one type of repository:
controller, filter, bug data, comparison function,
factory function for creating the objects
* Remove filter code and create separate filters from it
* Port tests
* Port `SyncTaskExecutor` to new infrastructure
== Done ==
* Design (basic structure)
* Implementation of `BugPipeline`
== See Also ==
https://sourceforge.net/apps/trac/bug-repo-syncer/wiki/SeparateTranslators
https://blueprints.launchpad.net/bug-repo-syncer/+spec/separate-translator-objects |
Currently there are two translators, that are shared by all repository
controllers: the translator for people's names, and the translator for
milestones. Translation for bug status values is hard coded into the repository
controllers.
Proposal
The two different tasks: translating bugs, and communicating with the
repository, should be separated. Separate objects should be responsible for
them. This probably simplifies the whole architecture, the different
translation tasks are all unified in one filter object. (Translating people,
milestones, bug status values, bug links.)
== TODO ==
* Design nice convention for organizing `RepoController`s, `Filter`s,
comparison functions, and bug records.
controller, filter, bug data, comparison function,
* Factory function for creating `RepoController` objects, and possibly
complete pipeline.
* Port `SyncTaskExecutor` to new infrastructure
== Done ==
* Design (basic structure)
* Implementation of `BugPipeline`
* Port `RepoController` descendants to new infrastructure
* Remove filter code and create separate filters from it
* Port tests
== See Also ==
https://sourceforge.net/apps/trac/bug-repo-syncer/wiki/SeparateTranslators
https://blueprints.launchpad.net/bug-repo-syncer/+spec/separate-translator-objects |
|
| 2012-03-19 13:04:54 |
Eike |
bug-repo-syncer: status |
In Progress |
Fix Released |
|
| 2012-03-19 13:04:54 |
Eike |
description |
Currently there are two translators, that are shared by all repository
controllers: the translator for people's names, and the translator for
milestones. Translation for bug status values is hard coded into the repository
controllers.
Proposal
The two different tasks: translating bugs, and communicating with the
repository, should be separated. Separate objects should be responsible for
them. This probably simplifies the whole architecture, the different
translation tasks are all unified in one filter object. (Translating people,
milestones, bug status values, bug links.)
== TODO ==
* Design nice convention for organizing `RepoController`s, `Filter`s,
comparison functions, and bug records.
controller, filter, bug data, comparison function,
* Factory function for creating `RepoController` objects, and possibly
complete pipeline.
* Port `SyncTaskExecutor` to new infrastructure
== Done ==
* Design (basic structure)
* Implementation of `BugPipeline`
* Port `RepoController` descendants to new infrastructure
* Remove filter code and create separate filters from it
* Port tests
== See Also ==
https://sourceforge.net/apps/trac/bug-repo-syncer/wiki/SeparateTranslators
https://blueprints.launchpad.net/bug-repo-syncer/+spec/separate-translator-objects |
Currently there are two translators, that are shared by all repository
controllers: the translator for people's names, and the translator for
milestones. Translation for bug status values is hard coded into the repository
controllers.
Proposal
The two different tasks: translating bugs, and communicating with the
repository, should be separated. Separate objects should be responsible for
them. This probably simplifies the whole architecture, the different
translation tasks are all unified in one filter object. (Translating people,
milestones, bug status values, bug links.)
== TODO ==
== Done ==
* Design (basic structure)
* Implementation of `BugPipeline`
* Port `RepoController` descendants to new infrastructure
* Remove filter code and create separate filters from it
* Port tests
* Design nice convention for organizing `RepoController`s, `Filter`s,
comparison functions, and bug records.
controller, filter, bug data, comparison function,
* Factory function for creating `RepoController` objects, and possibly
complete pipeline.
* Port `SyncTaskExecutor` to new infrastructure
* Port all tests
* Rename `BugData` to `BugInternal`
* Rename `SyncTaskExecutor` to `BugSyncer` ?
== See Also ==
https://sourceforge.net/apps/trac/bug-repo-syncer/wiki/SeparateTranslators
https://blueprints.launchpad.net/bug-repo-syncer/+spec/separate-translator-objects |
|
