| Show View request [message #526325] |
Fri, 09 April 2010 16:35  |
Eclipse User |
|
|
|
Originally posted by: n.n.nnn
There are times when the declarative nature of having views listed
in plugin.xml gets in the way of application logic. Will the programmer
in e4 be able to specify when a view should not be shown on the
Window | Show View menu?
|
|
|
|
|
|
| Re: Show View request [message #526656 is a reply to message #526330] |
Mon, 12 April 2010 14:04  |
|
On Fri, 09 Apr 2010 18:51:01 +0200, Tom Schindl wrote:
> Am 09.04.10 18:49, schrieb Tom Schindl:
> Probably one more note on this. An e4 application can be built
> completely in a NONE declarative way probably something we need to make
> us self aware from time to time.
>
> Tom
>
Agreed, in 3.x, we create all the views in our product using a special
module we wrote. It centers around first asking Eclipse to create
the view, then we update it, then we ask Eclipse to show it. In
other environments, you just create the window and update it then command
the OS to show it.
When the user picks a view from Window | Show View, we have a listener
which detects this, closes the erroneous view created by Eclipse
which can only draw from the declared information in plugin.xml and
we then create our view the way we want it.
For example, we limit some views to a certain numbers of instances.
Which reminds me, instance management in 3.x is difficult, we have
superimposed our own concept of a custom SecondaryID and even a
TertiaryID, so the view knows how to instantiate itself, what "mode"
it should come up in.
For very dynamic applications like ours, the combination of declarative
and dynamic is awkward so it is good to hear we have the ability
to be all dynamic in e4.
Dilton
|
|
|
|
|
|
| Re: Show View request [message #573955 is a reply to message #526330] |
Mon, 12 April 2010 14:04 |
|
On Fri, 09 Apr 2010 18:51:01 +0200, Tom Schindl wrote:
> Am 09.04.10 18:49, schrieb Tom Schindl:
> Probably one more note on this. An e4 application can be built
> completely in a NONE declarative way probably something we need to make
> us self aware from time to time.
>
> Tom
>
Agreed, in 3.x, we create all the views in our product using a special
module we wrote. It centers around first asking Eclipse to create
the view, then we update it, then we ask Eclipse to show it. In
other environments, you just create the window and update it then command
the OS to show it.
When the user picks a view from Window | Show View, we have a listener
which detects this, closes the erroneous view created by Eclipse
which can only draw from the declared information in plugin.xml and
we then create our view the way we want it.
For example, we limit some views to a certain numbers of instances.
Which reminds me, instance management in 3.x is difficult, we have
superimposed our own concept of a custom SecondaryID and even a
TertiaryID, so the view knows how to instantiate itself, what "mode"
it should come up in.
For very dynamic applications like ours, the combination of declarative
and dynamic is awkward so it is good to hear we have the ability
to be all dynamic in e4.
Dilton
|
|
|
Powered by
FUDForum. Page generated in 0.02662 seconds
] 
Search
Help
Register
Login
Home
