Discuss the UI design of ngrinder 3.1

[Alex Qin]

Hi, all

I do some UI dessign for v3.1 and have some questions, please discuss them together and get some ideas.

1. Script sample list display and content page.


I put the script sample ("Sample") as a folder item at the top of script list for every user, click this item will show the script sample list (same as script list), click any sample, can show the content page.



In the sample content page, can look the script contents, also can edit the content, input a new name and commit message, click copy button and then save the content as a new script to your own script list.


2. Test default option configuration

Right now I don't comfirm which option is necessary, we'll discuss and add other test default options into the form.


3. User share.
Before implement the detailed UI, need to know some things, I have two possibilities.
   1) User share some test to others, this is complex for the DB relationship design and script management myabe, but user can manage which test he want to share, it's detailed to control.
       Design:
          Put the share operation in test detail page.
          Shared test shown in perftest list and the shared items will be marked.
    2) User share himself to others,  this is simpler than 1), user just need to know who is shared for him, and than he can see the shared user's all test. But I think it's a little savage, user has to share all of his tests to others even though he just want to share one of them.
       Design:
          Put the share operation in user profile modal.
          In perftest list page, put a share user dropdown list option on top of list, can shift different shared user's test list.
 
Second, need to confirm the shared user authority:
   1) Only can look the shared and finished tests in perftest list.
   2) Can look any status tests shared, modify the test configuration and run them.
   3) Can delete the shared tests.
   4) Can clone tests to himself, whether or not to clone scripts at the same time.

That's all, please participate the discussion and give some feedbacks.

Thanks.

[junoyoon]

Dear Alex.. My comments are just below concerns.

JunHo Yoon
Global Platform Development Lab / Senior Engineer

13th FL., Bundang First Tower, 266-1, Seohyeon-dong, Bundang-gu, Seongnam-si, Gyeonggi-do, 463-824, KOREA
Tel [phone]   Fax --   Mobile [phone]
Email  [hidden email]

-----Original Message-----
From: "Alex Qin [via ngrinder]"<[hidden email]>
To: "junoyoon"<[hidden email]>;
Cc:
Sent: 2012-10-29 (월) 10:36:57
Subject: Discuss the UI design of ngrinder 3.1

Hi, all

I do some UI dessign for v3.1 and have some questions, please discuss them together and get some ideas.

1. Script sample list display and content page.

==> It's good to see such a great idea. :-) I love you.

==> However we need to think of the code complexity. This seem to make the script list implementation complex.. 

==> For Sample, we need different implementation. Isn't it?

==> And We should consider the question which this place is good to refer the script sample.

==> Mostly script writer need script sample while there are editing script. Isn't it better to place script sample in the script editor page?

==> What If we provide the button script sample in the script editor and shows the sample list on the poped up layer. and If we click one of them, then sniffet  is inserted into the script editor.

==> Futhermore, We need the dynamic script sample update feature. As time goes by, we may have more experience of writing script. And the  more script samples are accumulated.

==> We need dynamically to access recent script sample list. It might be good idea to achieve this by access cubrid wiki rss. (Just like I did for Developer resources in front page)

I put the script sample ("Sample") as a folder item at the top of script list for every user, click this item will show the script sample list (same as script list), click any sample, can show the content page.



In the sample content page, can look the script contents, also can edit the content, input a new name and commit message, click copy button and then save the content as a new script to your own script list.


2. Test default option configuration

Right now I don't comfirm which option is necessary, we'll discuss and add other test default options into the form.
==> Test Options are not very important feature, What we need is just to provide system.conf setup feature in the web page. 

==> Considering flexibility, instead of showing each fields on the Test Option page, just show raw system.conf text fields and let user configure it through web page.

==> Then refresh the configuration when the user saves the system.conf.

3. User share.
Before implement the detailed UI, need to know some things, I have two possibilities.
   1) User share some test to others, this is complex for the DB relationship design and script management myabe, but user can manage which test he want to share, it's detailed to control.
       Design:
          Put the share operation in test detail page.
          Shared test shown in perftest list and the shared items will be marked.
    2) User share himself to others,  this is simpler than 1), user just need to know who is shared for him, and than he can see the shared user's all test. But I think it's a little savage, user has to share all of his tests to others even though he just want to share one of them.
       Design:
          Put the share operation in user profile modal.
          In perftest list page, put a share user dropdown list option on top of list, can shift different shared user's test list.
 
Second, need to confirm the shared user authority:
   1) Only can look the shared and finished tests in perftest list.
   2) Can look any status tests shared, modify the test configuration and run them.
   3) Can delete the shared tests.
   4) Can clone tests to himself, whether or not to clone scripts at the same time.

==> Yes. I prefer second one. First one is complex to implement.

==> When user change its user identity to the other user, then just see what the other has.

==> For design, I agree we need "Put the share operation in user profile modal. "

==> But not for "perftest list page, put a share user dropdown list option on top of list, can shift different shared user's test list. "

==> What we need a menu to change its identity to the other. All goes to the top left menu.

That's all, please participate the discussion and give some feedbacks.

Thanks.

---

If you reply to this email, your message will be added to the discussion below:

http://ngrinder.642.n7.nabble.com/Discuss-the-UI-design-of-ngrinder-3-1-tp42.html

To start a new topic under ngrinder_dev, email [hidden email]
To unsubscribe from ngrinder_dev, click here.
NAML