Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Eclipse 4 » Show View request
Show View request [message #526325] Fri, 09 April 2010 16:35 Go to next message
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 #526328 is a reply to message #526325] Fri, 09 April 2010 16:48 Go to previous messageGo to next message
Thomas Schindl is currently offline Thomas Schindl
Messages: 5316
Registered: July 2009
Senior Member
Well you can contribute simply a Part in e4 which is only a member of
the UI (question is what to do if the user closes the view => it should
be probably not closeable :-).

The e4 equivalent of a view-contribution in e3 is a part descriptor
which is used to create the real UI element.

Another probably more interesting thing is that I think one would NOT
contribute a such a view but make it up programmically (e.g. when the
user presses a button, ... ) - just in time :-)

Tom


Am 09.04.10 18:35, schrieb Dilton:
> 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 #526329 is a reply to message #526328] Fri, 09 April 2010 16:49 Go to previous messageGo to next message
Thomas Schindl is currently offline Thomas Schindl
Messages: 5316
Registered: July 2009
Senior Member
Am 09.04.10 18:48, schrieb Tom Schindl:
> Well you can contribute simply a Part in e4 which is only a member of
> the UI (question is what to do if the user closes the view => it should
> be probably not closeable :-).
>
> The e4 equivalent of a view-contribution in e3 is a part descriptor

"PartDescriptor" is the class name

> which is used to create the real UI element.
>
> Another probably more interesting thing is that I think one would NOT
> contribute a such a view but make it up programmically (e.g. when the
> user presses a button, ... ) - just in time :-)
>
> Tom
>
>
> Am 09.04.10 18:35, schrieb Dilton:
>> 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 #526330 is a reply to message #526329] Fri, 09 April 2010 16:51 Go to previous messageGo to next message
Thomas Schindl is currently offline Thomas Schindl
Messages: 5316
Registered: July 2009
Senior Member
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

Am 09.04.10 18:49, schrieb Tom Schindl:
> Am 09.04.10 18:48, schrieb Tom Schindl:
>> Well you can contribute simply a Part in e4 which is only a member of
>> the UI (question is what to do if the user closes the view => it should
>> be probably not closeable :-).
>>
>> The e4 equivalent of a view-contribution in e3 is a part descriptor
>
> "PartDescriptor" is the class name
>
>> which is used to create the real UI element.
>>
>> Another probably more interesting thing is that I think one would NOT
>> contribute a such a view but make it up programmically (e.g. when the
>> user presses a button, ... ) - just in time :-)
>>
>> Tom
>>
>>
>> Am 09.04.10 18:35, schrieb Dilton:
>>> 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 Go to previous message
Dilton McGowan II is currently offline Dilton McGowan II
Messages: 108
Registered: July 2009
Senior Member
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 #573862 is a reply to message #526325] Fri, 09 April 2010 16:48 Go to previous message
Thomas Schindl is currently offline Thomas Schindl
Messages: 5316
Registered: July 2009
Senior Member
Well you can contribute simply a Part in e4 which is only a member of
the UI (question is what to do if the user closes the view => it should
be probably not closeable :-).

The e4 equivalent of a view-contribution in e3 is a part descriptor
which is used to create the real UI element.

Another probably more interesting thing is that I think one would NOT
contribute a such a view but make it up programmically (e.g. when the
user presses a button, ... ) - just in time :-)

Tom


Am 09.04.10 18:35, schrieb Dilton:
> 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 #573886 is a reply to message #526328] Fri, 09 April 2010 16:49 Go to previous message
Thomas Schindl is currently offline Thomas Schindl
Messages: 5316
Registered: July 2009
Senior Member
Am 09.04.10 18:48, schrieb Tom Schindl:
> Well you can contribute simply a Part in e4 which is only a member of
> the UI (question is what to do if the user closes the view => it should
> be probably not closeable :-).
>
> The e4 equivalent of a view-contribution in e3 is a part descriptor

"PartDescriptor" is the class name

> which is used to create the real UI element.
>
> Another probably more interesting thing is that I think one would NOT
> contribute a such a view but make it up programmically (e.g. when the
> user presses a button, ... ) - just in time :-)
>
> Tom
>
>
> Am 09.04.10 18:35, schrieb Dilton:
>> 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 #573916 is a reply to message #526329] Fri, 09 April 2010 16:51 Go to previous message
Thomas Schindl is currently offline Thomas Schindl
Messages: 5316
Registered: July 2009
Senior Member
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

Am 09.04.10 18:49, schrieb Tom Schindl:
> Am 09.04.10 18:48, schrieb Tom Schindl:
>> Well you can contribute simply a Part in e4 which is only a member of
>> the UI (question is what to do if the user closes the view => it should
>> be probably not closeable :-).
>>
>> The e4 equivalent of a view-contribution in e3 is a part descriptor
>
> "PartDescriptor" is the class name
>
>> which is used to create the real UI element.
>>
>> Another probably more interesting thing is that I think one would NOT
>> contribute a such a view but make it up programmically (e.g. when the
>> user presses a button, ... ) - just in time :-)
>>
>> Tom
>>
>>
>> Am 09.04.10 18:35, schrieb Dilton:
>>> 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 #573955 is a reply to message #526330] Mon, 12 April 2010 14:04 Go to previous message
Dilton McGowan II is currently offline Dilton McGowan II
Messages: 108
Registered: July 2009
Senior Member
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
Previous Topic:Nested XWT
Next Topic:Default alignment of labels
Goto Forum:
  


Current Time: Tue Sep 16 11:43:20 GMT 2014

Powered by FUDForum. Page generated in 0.04737 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software