Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[ice-dev] New Visualization Perspective mockups
Here are some mockups.  Each page of the PDF is a different page.  There are other 4 different versions of one page since it was the most controversial :)

Let me know if you have any questions.
Ray
-------- Original Message --------
Subject: Re: [ice-dev] Updates?
From: "Ray Braithwood" <ray@xxxxxxxxxxxxxx>
Date: Thu, September 10, 2015 10:33 am
To: "ice developer discussions" <ice-dev@xxxxxxxxxxx>

I will get a set of them out this evening.  I have some changes to make based on feedback from Jay.  Plus they should not be too large since I can export them as a PDF file from the tool I am using.

Ray
-------- Original Message --------
Subject: Re: [ice-dev] Updates?
From: "Patterson, Taylor C." <pattersontc@xxxxxxxx>
Date: Thu, September 10, 2015 10:23 am
To: ice developer discussions <ice-dev@xxxxxxxxxxx>

Jay or Ray,

Could one of you send out the mockups? Hopefully, they don’t get bounced by the mail server because of size restrictions.

Taylor

On Sep 10, 2015, at 9:19 AM, Jay Jay Billings <jayjaybillings@xxxxxxxxx> wrote:

Ray,

Let's get this discussion out on the dev list.

On points...
1.) I really like the info pops and I hope you put them everywhere.
4.) Yeah, take a look at it and let me know. We can also ask Jordan about it if we need to. His primary reasoning for using our data structures is that they have built in notifications and dedicated widgets. One possible alternative or compromise is to use one of our MasterDetailsComponents instead of a TableComponent and then to use a MasterDetailsSectionPart instead of a Table. But take a look at the code and let me know what you are thinking, then I will dig in some more.
5.) I see what you are saying. Hari has definitely already done this in his branch and can probably share it with you. As for stock views, I'm actually pro stock views. What I don't want is a million custom views. If we can ship something off to Properties or Tabbed Properties, Console, etc., then we should. One of the primary design goals of ICE is promote a common look a feel, which means that we need to avoid proliferation of views.
7.) Plots go in their own editor. The most I am willing to compromise on this is if a tool bar or something overlays via a pop up or can be minimized. The issue here is that scientific visualizations are feature rich and users want all the real estate possible. This is why we hide the close button until mouse over and put the controls in right clicks. We have tried designs like what you suggest in the past and *no one* wanted it. We even had people throw up their hands and say they wouldn't use it until we put the visualizations in their own editor. We don't have enough users that we can say "Sorry you don't like it," so for now they go in their own editor.

Jay



On Sat, Sep 5, 2015 at 6:23 PM, Jay Jay Billings <jayjaybillings@xxxxxxxxx> wrote:
Let's talk about it next week.
Jay
On Sep 5, 2015 15:27, "Ray Braithwood" <ray@xxxxxxxxxxxxxx> wrote:
Jay,

Thanks for the feedback.

1.) Preferences are exposed on a per-service basis. There are no general preferences that cross all visualization services, at least not yet. Maybe this will change in a few years after people use the tools.

This page already has the checkbox in the mockup so I am proposing to just add the hyperlinks to automatically switch to other pref pages and the infopop.  It seems to me though that the hyperlinks are not necessary just yet since we do not have any prefs for CSV and ParaView.

I would still like to do the infopop as it will get used a lot in other places anyway.


2.) We never reuse the same editor for all renderings. Aside from being exceptionally difficult from a code perspective, our users need to be able to separate out graphs for visual comparisons. Also, there are no preferences for the CSV plotting engine.

I was not sure if we had anything to go here so I will not worry about implementing the page.


3.) We haven't yet figured out any preferences for ParaView. That will come in the future.

Again just proposing ideas.  I will not implement right now.


4.) I really like what you have in mind for the VisIt preferences. That is a good design and would help a lot. I'm not sure how easy this will be to do because Jordan based his implementation for that page on our TableComponent data structure, which can be rendered using a TableComponentSectionPart. We have since copied this over to a new class called VizTableComponent. It is common infrastructure that is used by all the services. We can look at the code together if you want.

I will take a look at the code but my idea would be to go to using a more traditional List or Table that does not have multiple columns and have all the details in the section below.  We can discuss more but it will not be much work for me to code what I have in mind.


5 & 6.) I like splitting the details into their own view, but I don't want to have a massive proliferation of views. Can this be done just as well in the properties view?

I think what you see is a small limitation of the wireframe.  My idea is to only have a single view "Visualizations".  The details area is actually just a section of the view.  I would prefer to not use the Properties view as I too would like to limit the number of "stock" views.


7.) I like the idea of breaking the plot types out into their own menu and I believe that Hari Krishnan has already done this in one of his branches. He might be able to share that code with you. However, that should not be within the same canvas as the plot and the time slider controls. They can be in their own view part, but I don't want anything taking up render space in the viz canvas.

Ok.  I have a couple of other ideas I can mockup for other possibilities.  I would like to avoid having the plots in their own view.  My main UI design paradigm is what I call "directed UI".  I like to keep everything contained together in a view or editor so that a user does not need to know that a view is connected to an editor vs. being a stand alone view.  I will still mockup having them in a separate view so we can see what works best.

I will send you the amended mockups in a little bit.

Ray
-------- Original Message --------
Subject: Re: Updates?
From: Jay Jay Billings <jayjaybillings@xxxxxxxxx>
Date: Sat, September 05, 2015 12:21 pm
To: Ray Braithwood <ray@xxxxxxxxxxxxxx>
Cc: Harinarayan Krishnan <hkrishnan@xxxxxxx>

Ray,

Overall I like the mockups. Here are a few notes, by slide.

1.) Preferences are exposed on a per-service basis. There are no general preferences that cross all visualization services, at least not yet. Maybe this will change in a few years after people use the tools.
2.) We never reuse the same editor for all renderings. Aside from being exceptionally difficult from a code perspective, our users need to be able to separate out graphs for visual comparisons. Also, there are no preferences for the CSV plotting engine.
3.) We haven't yet figured out any preferences for ParaView. That will come in the future.
4.) I really like what you have in mind for the VisIt preferences. That is a good design and would help a lot. I'm not sure how easy this will be to do because Jordan based his implementation for that page on our TableComponent data structure, which can be rendered using a TableComponentSectionPart. We have since copied this over to a new class called VizTableComponent. It is common infrastructure that is used by all the services. We can look at the code together if you want.
5 & 6.) I like splitting the details into their own view, but I don't want to have a massive proliferation of views. Can this be done just as well in the properties view?
7.) I like the idea of breaking the plot types out into their own menu and I believe that Hari Krishnan has already done this in one of his branches. He might be able to share that code with you. However, that should not be within the same canvas as the plot and the time slider controls. They can be in their own view part, but I don't want anything taking up render space in the viz canvas.

Jay

On Sat, Sep 5, 2015 at 12:03 AM, Ray Braithwood <ray@xxxxxxxxxxxxxx> wrote:
Attached are the mockups.  Let me know what you think and I am available to discuss this if you want/are up to it.

Ray
-------- Original Message --------
Subject: RE: Updates?
From: Jay Jay Billings <jayjaybillings@xxxxxxxxx>
Date: Fri, September 04, 2015 5:09 pm
To: Ray Braithwood <ray@xxxxxxxxxxxxxx>

Ray,
Sorry, I should have gotten in touch with you before today but I ran out of time. If you send your mockups I'll look at them in the morning.
Jay
On Sep 4, 2015 11:18 AM, "Ray Braithwood" <ray@xxxxxxxxxxxxxx> wrote:
Jay,

I cannot make the meeting at 1:30 today but I would still like to meet with you later on (after 3PM if possible).  I would like to immediate feedback on my mockups as well as a couple questions answered.  I plan on working a lot on implementation this weekend so meeting with you would help that a lot.

Thanks
Ray
-------- Original Message --------
Subject: Re: Updates?
From: Jay Jay Billings <jayjaybillings@xxxxxxxxx>
Date: Fri, August 28, 2015 1:13 pm
To: Ray Braithwood <ray@xxxxxxxxxxxxxx>

Let's plan to do it next week. Enjoy your family time!

Jay

On Fri, Aug 28, 2015 at 1:12 PM, Ray Braithwood <ray@xxxxxxxxxxxxxx> wrote:
It is taking longer than I wanted. I have hangouts on my phone to try to be on the call. Up to you

Sent from my Verizon 4G LTE Smartphone

------ Original message------
From: Jay Jay Billings
Date: Fri, Aug 28, 2015 10:39
To: Ray Braithwood;Tony McCrary;
Subject:Updates?

Hi guys,
Do you have any updates for our status meeting today? Ray, are you going to join it?
Jay



--
Jay Jay Billings
Oak Ridge National Laboratory
Twitter Handle: @jayjaybillings



--
Jay Jay Billings
Oak Ridge National Laboratory
Twitter Handle: @jayjaybillings



--
Jay Jay Billings
Oak Ridge National Laboratory
Twitter Handle: @jayjaybillings
_______________________________________________
ice-dev mailing list
ice-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ice-dev

_______________________________________________
ice-dev mailing list
ice-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ice-dev
_______________________________________________
ice-dev mailing list
ice-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ice-dev

Attachment: ICE Vis Perspective v2.pdf
Description: Adobe PDF document

Back to the top