I understand the logic of your decision, and it correct decision if inShort is the only one App that is installed on the ipad.

But users have a lot of Apps installed on their ipad.
Therefore, if you omit qualifiers, then user has to do extra operations (such as clicking on the element icon), in order to recall the meaning of the icon.

I mean, your decision is correct, but risky.

Hi,

After several tries, still I can not success to create one hidden object.

Is it possible to create one "Common Resource" object that will be hidden in the "Execution" mode?
Can you please provide the steps how to do it?

I did following:

• Create a new diagram
  Configure diagram's card --> "Use scheduling" = OFF
  Inside this diagram create only one  "Common Resource" object
  Check the object's flag "Hidden object"
  
• Results:
  The object is still visible in the execution mode

Can you please write definition: when the object's schedule is called "active" and when it is called "not active"?

Thanks

I agree with you that duplicating the same value does not look good.
But, the current title of the Gannt also looks strange.

Please see below 2 examples of idea how to improve the current look.   
The point is that the title will contain 2 lines.

Note:
Currently, some cells contain 1 line and some contain 2 lines. I think, that the current look is not the best one.

Hi,

Regarding example with quarters:
Most of the users can't tell you in 3-5 seconds the first and the last month of quarter III.

You can use Jul...Sep instead of III

[Scenario]

Unfortunately, I am going to stop using "Actual" (real) mode, until below bug will be fixed.

This bug causes the "Actual" scheduling mode to be useless in the version 3.2.3
Tested on IOS5, ipad2

Scenario:
(1) Build plan of the project in the "Plan" scheduling  mode
      The flag "sync with reality" = OFF
(2) Execute plan (please see attachment)
(3) Switch to "Active" (real) mode
(4) Execute plan

Results:
The start date of the element is wrong.  <----- BUG
User can not edit the start date of the element in the "Actual" scheduling mode.  <----- BUG

Expected results:
In the "Actual" mode user should be able to edit the start date.

Tested on version 3.2.3

When user press  "Analyze the diagram as a project" , then inShort turns ON flag "sync plan with reality".
It is a very serious bug.

I will explain why it is serious:
User has no indication that "sync plan with reality" flag is going to be turned ON!
It has a bad impact on the planned and actual schedule.

Why bad impact?
Because user can not "UNDO" immediately the changes that will be done by "sync plan with reality" flag.

Look, no project manager in the company/business  will use feature that has direct impact on the planned and actual schedule. I am talking about impact that changes things and can not be "UNDO" immediately.

I don't think that some project manager will sit in the office and will start to shake the ipad in order to "UNDO" inShort BUG  
It is not serious.

In the company where I work, each project costs about million of dollars. Of course project managers use expensive project managing applications.
But, these managing applications don't have so cool views ability as your App has: to switch Flow vs Gannt and to planned vs actual results  is genius !  

The question is -  for what type of business projects the below features are already ready for a serious usage ?
(1) "Analyze"
(2) "Sync with reality"

In my opinion:
The inShort App is ready for business usage without both features.  
The "Analyze"  and "Sync with reality"  are too buggy  for the business usage in the current version of inShort (version 3.2.3)

It is only my opinion.

By the way, I understand why in the "Suggestions" section forum, users want to import MS project files to your App!
They want your GUI to view the FLOW CHART of the project, but they prefer to stay with MS application as a project editor.

[Tested on version 3.2.3]

Tested on version 3.2.3

It changes elements time value that were already completed.See example below.

It is incorrect design to change what was already done in the past.
You can not optimize future by changing the past.

So, in the  "planned schedule" mode, the "analysis" process ignores what was completed (<---BUG)
The analysis executes the whole diagram from the first element to the last one and changes correct time buffer values to be wrong values.

Expected design:
Elements that were already completed, should not be edited by "Analyze the diagram as a project".
The completed elements are a part of the project, you can not ignore the state of the element.

Example:
(1) Configure flag "Sync with reality" = OFF
(2) Switch to the "Planned schedule" mode
(3) Build diagram with 4 elements (see attachment)
      Do not configure "Late Start".
(4) Switch to execution mode (still stay in the "Planned schedule" mode)
(6) Complete 3 elements, and leave one element to be not completed. (see attachment)
(7) Run  "Analyze the diagram as a project"

Results:
See attachment.

[Results:]

In the following scenario, the "read only" mode is not working:

(1) Configure diagram to be in "Read Only" mode:
      Right click on the title of the diagram -->  set  "Read Only" mode = ON
(2) Go to InShort global options --> Choose "Analyze"

Results:
When user press "analyze", he /she  will cause the change of values in the elements.
It is very serious bug ( called in the industry "High/Blocking Severity Issue").

When user see option "read only" he/she understand only one thing:
NO CHANGES WILL BE DONE - this is the meaning of "read only"

Note:
If you want to provide other type of "read only", then GUI has to supply the indication (information) about the special type of "read only" operation.

[Results:]

I build diagram with 3 elements only, and run "Analyze".

Results:
I get hint "it is recommended to place a time buffer ...on the critical path of the project".
My project contains only 3 elements, it can not be critical

The main problem:
The problem is that inShort uses term "critical path" in a wrong way.

You have to define exactly the meaning of the "critical path":
When the path is called "critical" and when the path is not called "critical?

My opinion:
To remove the word critical in all cases (stop using this word in whole App).
-  You want to provide a hint to add a time buffer, so just provide this hint.
-  You want to do analysis of the diagram, so just do it. I don't understand why you wrote in the guide "Critical analysis of the path" in the diagram called "Life cycle of diagrams" ?

:-)

I really like inShort App, because most of the work you have already done OK.
The infrastructure of the App works fine, and App contains a lot of cool features.
Indeed, it still has many GUI bugs. 

I like the GUI layout:
1. The location of the buttons
2. The tool bar visual design
3. The colors
4. The form of the diagram elements
5. The arrows design
6. The ability to set image (picture) into the body of the element.
7. The nested diagrams
8. Other GUI things

I like the philosophy behind the App.
The idea to sync the planned schedule with actual schedule is great.

I like 5 types of different views:
1. Flow chart - planned schedule
2.  Flow chart - actual schedule
3. Gannt - planned schedule
4. Gannt - actual schedule
5. Gannt - actual & planned schedule

Have a good happy new year

The time buffer's name and description is missing in the Gantt Graph view.

See attachment.

The time buffer's name and description is not displayed in the object.

See attachment.

[no]

The "Date" should not appear on the Buffer element, when there is no progress.
See attachment.

Tested on ipad2, ios5

I set the "Add to calendar option" = ON
I configured the schedule date = today


The ipad's calendar don't have any items of today.

[The problem:]

These is a "Time" value displayed in the element.
Please see attachment.

The problem:
The title "Time" is unclear because in this App there are many types of the "time" can be configured.
Bad user experience.

The expected results:
To change the title "Time" to be "Expected estimation time:"

For example in the attachment below:
Expected estimation time: 60 min