Chiming in a bit late on this since I was
traveling. I definitely agree with continuing the current approach of
integrating with the existing perspectives rather than taking the PDE’s
approach of introducing a new perspective that has no clear role other than
adding a view or two. The usage data from our study of 41 Java developers
indicates that the Java and Debug perspectives are used considerably more than
the others (sorry, no link to the publication yet). That said, I think
the current perspective integration could be improved a bit so I’ve filed
a couple of bug reports:
151730: automatically show the
Crosscutting Comparison in relevant perspectives
https://bugs.eclipse.org/bugs/show_bug.cgi?id=151730
- By
default show the Crosscutting Comparison in the Team Synchronizing and CVS
Repositories perspectives.
151731: make the triggering of the Cross
References view more explicit
https://bugs.eclipse.org/bugs/show_bug.cgi?id=151731
- Instead
of automatically opening when first triggered, which is easy to miss, open
a dialog that describes its role similar to how perspectives are triggered.
Something like “You have just created an aspect, open the Cross
References view in order to see the crosscutting structure of AspectJ
Declarations”? It allows a yes/no choice, and offers the “do
not show again” checkbox. The view is likely to be blank when
first opened so stating its role will help.
Mik
From:
ajdt-dev-bounces@xxxxxxxxxxx [mailto:ajdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Matt Chapman
Sent: Tuesday, July 18, 2006 4:28 AM
To: AspectJ Development Tools
developer discussions
Subject: Re: [ajdt-dev] AspectJ
Perspective?
Thanks for your input,
it's not too late.
It currently looking as though a new perspective wouldn't allow for any notable
new functionality.
We're totally committed to making the tool support natural and close to what
developers already know. If you (or anyone else of course) can point to
specific weaknesses in this area, then please shout so we can use that to
prioritise the things to focus on.
Regards,
Matt.
On 17/07/06, Alexandru Popescu
<the.mindstorm.mailinglist@xxxxxxxxx
> wrote:
Sorry to jumping to this discussion so late, but I want to give my
feedback on this topic.
If a new perspective would bring more functionality (and would help the AJ
parts work more in the Java way), than I am all for it. Because more
functionality will make developers feel more confortable and so some of the
problems that we are seeing when introducing AJ to people. All people I have
worked with have always complained about 1 single thing: the tool support. They
don't give a damn if it is a new perspective or a view or something else. They
want it to work natural and as close as what they know.
Unfortunately, my knowledge about Eclipse platform is limitted and I don't know
the impact of this. However, I am 1000% for the idea to have better and better
integration and IDE behavior when working with aspects.
BR,
./alex
On 7/17/06, Ron Bodkin
<rbodkin@xxxxxxxxxxxxxx
> wrote:
I think this perspective could usefully remap some other keys
into their AspectJ type-aware equivalent (e.g., F3 to look up an
AspectJ-defined type or a method in one or an ITD). I'm assuming that it's not
possible to It could also show buttons only for the AspectJ version (e.g.,
remove the open Java type button and only show the AspectJ one). Of course if a
perspective like this is popular, it would lead to demand for AspectJ Browsing
and AspectJ Debug perspectives… I would definitely prefer to have all
this functionality in the Java perspective if it were possible.
Maybe a fallback position for the keyboard bindings would be
to define a new set of bindings. Does Eclipse allow a plugin to bind new key
sequences in existing perspectives?
To: AspectJ Development Tools
developer discussions
Subject: Re: [ajdt-dev]
AspectJ Perspective?
This is an interesting issue. If implemented, it
wouldn't stop anything that works today from working - users could continue to
use the Java perspective for AspectJ development, just as I use the Java
perspective for plug-in development, instead of the Plug-in Development perspective.
Perspectives are little more than a layout of views and as eclipse users are
already familiar with this concept, I think adding an new perspective as an
"optional extra" has a fairly low risk of causing confusion. The
other question is of course what could be gained from such a new perspective. I
can only think of the things already mentioned, a layout of the 2 AJDT views,
and providing a key binding for Ctrl-Shift-T to open AspectJ type instead of
open Java type. I'd say it's debatable whether this is worth the implementation
cost, as the new perspective would have to contribute everything the Java one
does (and keep this up-to-date as the Java one changes over time). Does anyone
have any thoughts as to what else such a perspective could offer?
Regards,
Matt.
Matt,
I
think we tried this with early versions of AJDT. One problem is that it
emphasizes the difference between Java and AspectJ; something we are trying to
avoid. Also might user's get confused if for some reason they switch back to
the Java perspective or start using one of the other special ones like plug-in
or web development?
Matthew Webster
AOSD
Project
Java Technology Centre, MP146
IBM Hursley
Park, Winchester, SO21 2JN,
England
Telephone: +44 196
2816139 (external) 246139 (internal)
Email: Matthew Webster/UK/IBM @ IBMGB, matthew_webster@xxxxxxxxxx
Hi
Ron,
That has occurred to me also. It could include the
Cross References
and Crosscutting Comparison views in its layout.
People could of
course continue to use the Java development
perspective if they
preferred, but this would offer an alternative.
Regards,
Matt.
On 14/07/06, Ron Bodkin
<rbodkin@xxxxxxxxxxxxxx > wrote:
> I was thinking about how to remedy some of
the limitations for AspectJ
> support in Eclipse like the ctrl+shift+t (and
f3?) keyboard bindings that
> use the Java type system rather than the
AspectJ one. It occurred to me that
> it might be possible to get a lot better
support (e.g., new key bindings,
> show only the AJ type button by default etc.)
with an AspectJ *perspective*
> in Eclipse. Am I just being optimistic here,
or would that be a way to
> improve usability of AJDT?
>
>
>
> Thanks,
>
> Ron
>
>
>
_______________________________________________
> ajdt-dev mailing list
> ajdt-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/ajdt-dev
>
>
>
_______________________________________________
ajdt-dev mailing list
ajdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ajdt-dev
_______________________________________________
ajdt-dev mailing list
ajdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ajdt-dev
_______________________________________________
ajdt-dev mailing list
ajdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ajdt-dev
_______________________________________________
ajdt-dev mailing list
ajdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ajdt-dev
|
