Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ide-dev] [ui-best-practices-working-group] Working sets (WAS: Re: Java IDEs comparison)

When you switch editors, the tool bar changes. I think the a subset of the views should also change, allowing for editor specific views. We actually had a guy prototype something like that and it was pretty slick. We were able to switch between QML and C++ editors and the couple of views we had for QML would swap in and out.

Unfortunately he left the company and we lost his code, but I think this was just done by listening to active editor changes and changing the visibility of the views in question.

And funny enough we were talking this morning about an editor we have for QNX things and I’d like to add a view or two to visualize the contents of the editor in different ways. Love to have those views only show when the editor is active.


From: <ui-best-practices-working-group-bounces@xxxxxxxxxxx> on behalf of Marc-André Laperle <marc-andre.laperle@xxxxxxxxxxxx>
Reply-To: UX Group <ui-best-practices-working-group@xxxxxxxxxxx>
Date: Monday, October 3, 2016 at 11:40 AM
To: UX Group <ui-best-practices-working-group@xxxxxxxxxxx>, Discussions about the IDE <ide-dev@xxxxxxxxxxx>
Subject: Re: [ui-best-practices-working-group] [ide-dev] Working sets (WAS: Re: Java IDEs comparison)

I think this talk about multi-language is quite important.

I'd like to bring up a slightly different case. There is already a multi-language "Debug" perspective, but not all views pertain to all languages. If I'm debugging a C program, I'm looking at a C editor then if I step into assembly I'm looking at an assembly editor, but I'd like different views to show for Assembly vs C. This is just one example of the layout that would need to change depending on the editor in focus. I wonder if perspectives should have sub-layouts, based on other things like the editor input (Assembly/C example) or even the screen resolution. What I mean for screen resolution is if I go from a 27" 4K monitor to a projector in 1024x768, it would switch to a "presentation" layout automatically where some views could be closed or resized based on the last time I was on a projector of that resolution.

Those are just a few ideas but I think perspectives need some rethinking in general. What should they be about? When should I create one as a developer?


From: ui-best-practices-working-group-bounces@xxxxxxxxxxx <ui-best-practices-working-group-bounces@xxxxxxxxxxx> on behalf of Doug Schaefer <dschaefer@xxxxxxxxxxxxxx>
Sent: Friday, September 30, 2016 10:31:05 AM
To: UX Group; Discussions about the IDE
Subject: Re: [ui-best-practices-working-group] [ide-dev] Working sets (WAS: Re: Java IDEs comparison)
I think the biggest issue with a multi-language perspective is how to do a multi-language “Open Type”. It’s really the only thing I run into when trying to do Java in the C++ perspective or C++ in the Java perspective.

Any thoughts on that? Is this something we can even fix?


From: <ui-best-practices-working-group-bounces@xxxxxxxxxxx> on behalf of Mickael Istria <mistria@xxxxxxxxxx>
Reply-To: UX Group <ui-best-practices-working-group@xxxxxxxxxxx>
Date: Friday, September 30, 2016 at 7:30 AM
To: UX Group <ui-best-practices-working-group@xxxxxxxxxxx>
Subject: Re: [ui-best-practices-working-group] [ide-dev] Working sets (WAS: Re: Java IDEs comparison)

On 09/30/2016 01:15 PM, Brian de Alwis wrote:
Not sure what makes a blocker
I was thinking about the context of the IDEs as we ship them (EPP packages).
But this is for sure an important issue. I'll try to look at it one of these days.

Mickael Istria
Eclipse developer for Red Hat Developers
My blog - My Tweets

Back to the top