Bug 457915 - Jubula client API - UI proxy interfaces: hierarchy, naming and relevance should be re-visited
Summary: Jubula client API - UI proxy interfaces: hierarchy, naming and relevance shou...
Status: NEW
Alias: None
Product: Jubula (Archived)
Classification: Technology
Component: Core (show other bugs)
Version: 3.0   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact: Oliver Goetz CLA
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks: 459191 470025
  Show dependency tree
 
Reported: 2015-01-20 05:52 EST by Marcel Hein CLA
Modified: 2022-04-21 18:04 EDT (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Marcel Hein CLA 2015-01-20 05:52:01 EST
-base and concrete comp-system interfaces have the same name, e.g. TextComponent. This is confusing/annoying, because in most cases in eclipse the fully qualified name is not shown and therefore most interfaces can't be distinguished on the first look.
Additionally the concrete TextComponent interface extends the base TextComponent interface but doesn't extend the functionality, therefore the concrete interface could be removed. This is also the case for other components.

-the naming for comp-system interface on the concrete ui level, e.g. JavaFX, should be improved as well, because the names don't differ from concrete, base or from other ui toolkit names.
Comment 1 Alexandra Schladebeck CLA 2015-01-22 06:24:15 EST
Markus, can you comment?
Comment 2 Markus Tiede CLA 2015-01-26 11:10:12 EST
I agree that we should add real documentation / meaningful for these abstracted types as they make - in many cases - sense. However some of them may not / may have been introduced for abstraction capabilities in future. Removing / altering these interfaces and their names is an incompatible API change. Therefore I'm adjusting the minimum required target version.
Comment 3 Eclipse Genie CLA 2018-05-10 18:16:25 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 4 Eclipse Genie CLA 2020-04-30 14:39:40 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 5 Eclipse Genie CLA 2022-04-21 13:44:02 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 6 Eclipse Genie CLA 2022-04-21 18:04:31 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.