GitHub user bamaer created a discussion: 2.18 roadmap and goals
We're entering the code freeze for the 2.17 release, so we'll need to start thinking about our focus for the 2.18 release. One of the areas we can work on is improving the consistency and in Apache Hop. - Incoming/outgoing transforms: just like in #4877, there are other transforms that have incoming or outgoing transforms that are not (always) updated correctly - Transform dialog harmonization: the Database Lookup transform dialog has been updated for 2.17, but there are quite a lot of other lookup (and other) transforms that have the same or similar UI problems. We could walk through all of the transform and action dialogs that pack too many UI elements and try to simplify them like we did for the Database Lookup dialog. - File inputs: a lot of our text based input transforms have a similar dialog to pick up files. Similar does not mean identical, and these little differences can cause confusing. Ideally, we'd move the file inputs to one or a couple of widgets and/or annotations that we can then use from the various transforms. - Metadata editors: some have an icon in the top right corner, some don't. Some have the metadata item on a separate line at the top of the editor, some don't, etc. We could walk through all of the editors and make sure their layout is consistent. - Code consistency: there are plenty of areas where we repeat the same or similar code blocks. Sometimes that's acceptable, but often the code would be more maintainable by moving to a single implementation in e.g. helper classes and methods that we can call from the current implementations. The UI topics here could be a good opportunity to start working on (and enforcing) UI guidelines, so developers will know what is expected when they build new UI elements. My 2 cents, let me know what you think our focus should be for 2.18. GitHub link: https://github.com/apache/hop/discussions/6445 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
