46 |
ISSUE: If we don't want people to see AbstractUpdateManager |
ISSUE: If we don't want people to see AbstractUpdateManager |
47 |
should we hide some of it's methods to package private? |
should we hide some of it's methods to package private? |
48 |
|
|
49 |
Small demos might still need these methods. |
RESOLVED: Issue can be solved later because this PEG |
50 |
Otoh, safer is better. One possibility is to |
still gives a plenty of room for handling it in future. |
|
add this API within the demo framework but then it would be |
|
|
very hard to call from the java side. |
|
|
|
|
|
RESOLVED: Issue can be solved in future because this PEG |
|
|
still gives a plenty of room for handling it. |
|
51 |
Implementing the interfaace in demo framework also makes |
Implementing the interfaace in demo framework also makes |
52 |
it much more easier to use than old way and increments readability |
it much more easier to use than old way and increments readability |
53 |
of source. |
of source. |