1. Roman Telezhynskyi Avatar Roman Telezhynskyi
  2. Untitled project
  3. Valentina
  4. Issues

New feature: 'New User guided tutorial' dialog

Issue #555 wontfix
Susan Spencer created an issue

Currently when a user creates a new pattern, they click on the File/New. Then the Pattern Piece dialog appears which prompts for Pattern Piece name, skipping the opportunity to input data about the whole pattern.

Creating a new file should work like this:

  1. Click File/New
  2. The 'New User' dialog appears, asking 'Would you like a guided tutorial to create a pattern?' 'Yes', 'No', or 'Don't show this again' are the options.

If yes...

  1. The Pattern Properties dialog box appears. User enters data in tabs, clicks OK.
  2. A new Measurement File dialog box appears (this dialog box will be listed as a separate issue). User selects radio button from 'Individual', 'Standard', or 'None'. If 'Individual' or 'Standard' then user chooses the measurement file.
  3. The Pattern Piece name dialog appears. User enters pattern piece name, clicks OK, and point A is created. Processing continues in non-New-User mode.

Comments (14)

  1. Roman Telezhynskyi repo owner

    Don't like completely. You forget about very important rule. The less user click the better. In your current proposal i see a lot clicking before actual start of working.

    Currently when a user creates a new pattern, they click on the File/New. Then the Pattern Piece dialog appears which prompts for Pattern Piece name, skipping the opportunity to input data about the whole pattern.

    Why do you think a user want to input this data on this step? Don't you forget which data contains this dialog? All they useful later, on next stages or only in the end. When you only start to create a pattern you don't know most of information about a pattern. If user really want and have what to add he can easily open the dialog himself.

    A new Measurement File dialog box appears (this dialog box will be listed as a separate issue). User selects radio button from 'Individual', 'Standard', or 'None'. If 'Individual' or 'Standard' then user chooses the measurement file.

    Why? I don't understand this. If you don't need measurements you will not see anything. Quick start it is what i like in current implementation. Do you see any troubles with not understanding how to add measurements. Maybe all we need is documentation?

    Sorry, but popping up dialog after dialog is really bad idea.

  3. Susan Spencer reporter

    I disagree about the user experience in this case. It's confusing to select 'New' pattern, then be prompted for a name for a Pattern Piece.

    Believe me the global data will be very important once patterns start to be shared. Having to go back, outside of the workflow, to enter important information is a pain in the neck. Many users will forget or ignore if we don't prompt for this info at the creation of each pattern.

    Good GUI design is more than minimum clicks.

  4. Roman Telezhynskyi repo owner

    It's confusing to select 'New' pattern, then be prompted for a name for a Pattern Piece.

    Can you explain me what exactly is wrong with my logic? Because i don't get it. New pattern-> select units, select the first pattern piece name. The minimum you should decide. Then you can go in many ways: begin with global data, start just drawing, load measurements. And many, many other. You can't be sure what a user want because we support several cases.

    This more look like issue with names for you. Not the workflow.

    Believe me the global data will be very important once patterns start to be shared.

    Agree, it is important. But how many will really share own patterns. Just now you are trying to share experience from this small/big group to all users.

  6. Roman Telezhynskyi repo owner

    Having to go back, outside of the workflow, to enter important information is a pain in the neck.

    I don't agree, how can you say "to go outside of workflow" if on this stage you have so many ways to go. It is impossible to predict what users want.

    Many users will forget or ignore if we don't prompt for this info at the creation of each pattern.

    Don't think so. First of all that data is visible on detail in labels. The second, with same success user will ignore the dialog on early stage because it is unnatural to edit this data only after creation. Don't make us smarter than our users. Showing the dialog will not guarantee you that patternmakers will add necessary data. This rule should be checked on another level. For example in pattern share service.

    For example libreoffice help you create document, but never say you "no, i think you should edit this field". Because no one can't know what you are doing. A publisher/mentor/professor will check your document and will say if all is right.

  7. Susan Spencer reporter

    The New dialog asks for units - this is global data.
    The user has to go to the Measurements menu and load a file.
    The user has to go to Pattern Properties and enter pattern number and pattern name, which are used in Labels.
    The user has to do too much work in a disorderly route to get a proper pattern completed.
    We should look at the workflow as a total symphony, not simply as individual musical phrases.

  8. Susan Spencer reporter

    Let's table this issue until we get more feedback from users after the Grainlines and Passmarks are implemented.

    We should investigate how project data is collected when using parametric design applications for architecture, as this is the software most similar in concept to Valentina.

  9. Roman Telezhynskyi repo owner

    The New dialog asks for units - this is global data.

    Yes, and what? This is global minimum to begin work. If only i could i would never ask even this.

    The user has to do too much work in a disorderly route to get a proper pattern completed.

    For example take measurements. If i want to propose for a user any dialog it should include:

    1. Case load individual, standard, none measurements.
    2. What if i want to create new? I need create it here too? Because if no, i will return to my way - Load individual/standard after creating.

    We should look at the workflow as a total symphony, not simply as individual musical phrases.

    Totally agree, that's why i discussing this with you instead of just saying ok even when i don't like something. You giving idea, i also giving idea. Let's find compromise that all will understand.

  10. Roman Telezhynskyi repo owner

    Let's table this issue until we get more feedback from users after the Grainlines and Passmarks are implemented. We should investigate how project data is collected when using parametric design applications for architecture, as this is the software most similar in concept to Valentina.

    You know we could make another way. We could left manual way and create special wizard that will guide users thought most common cases. Some app use this way too. For example WinRAR. Qt has fine widget for this.

    This will give you a freedom to make a wizard how do you like and add as much cases as you need. Advanced users will still get freedom to decide what and in which sequence they will select and edit.

  15. Log in to comment
Assignee
–
Type
proposal
Priority
minor
Status
wontfix
Component
Menus, Icons, Dialogs, UI
Milestone
TBD
Version
–
Votes
0
Watchers
1
Jira: the preferred issue tracker for Bitbucket. Join the team!