TEXT_AUTO_CHAIN_BEHAVIOUR_R1

[Astea]

wiki page: TEXT_AUTO_CHAIN_BEHAVIOUR_R1 - effort: 1d

[deyan]

The aim of the task is not clear in the analysis section. Why do we need update of platform standards manual tests? Also, a lot of the analysis is a copy of the previous one.

[deyan]

Replying to deyan:

The aim of the task is not clear in the analysis section. Why do we need update of platform standards manual tests? Also, a lot of the analysis is a copy of the previous one.

mistake, not this ticket

[dido]

• If there is 'Auto Chain' label inside the combo box, please make another one called 'None' and set it to default. Remove the empty item.
• If it's possible develop the following behavior
  • When 'Auto Chain' is selected and the text overflows, after creation of new frame - the combo box content should be set to the name of the next frame, not to auto chain

Analysis Reviewed 3.5p (30m)

[boyan]

finished design

[boyan]

finished implementation as well, now merging with trunk (after natives)

[meddle]

Quite simple design... I guess

• The hud in the design section differs with that from the analysis, why is that?
• The resource name prefixes will be more stable without spaces after them (I'm talking about the page in your code).
• I personally don't like ctrl+shift+F formatting...
• You will fix TextSelectionTest, or? I'll be happy if you do that...
• Do you have problems with the templating?
• I should explain how will work deleting of a page, you will delete the frames in it, but in what order?
• How will work auto-chaining work with groups?

Please explain these things for the implementation...

3p (30m)

[boyan]

Notes on the comments of the design review:

• The HUD in the analysis section is designed for full auto-chaining behavior: when you select auto-chaining mode, text flow is monitored in real time and frames are added/deleted correspondingly. After discussion with milo, we decided that at this point a button that recomputes the flow should be available and no auto-tracking will be present. That's why the HUD has a button instead of an item in the drop-down.
• I thought that a space after the resource name prefixes makes them a bit more readable. I will get rid of them at all places.
• I won't use Ctrl+Shift+F anymore :)
• TextSelectionTest will not be fixed at this iteration. It is improved though but fails because of a missing icon.
• Templating behaves strangely and unstable - try inserting some frames on a page and click twice on the Use Template halo button :) That's a great way of deleting frames...
• The bug with page deleting is now fixed, all frames are deleted as well but there is no time to implement underflowing now.
• Currently grouping will not affect auto-chaining in any way - no matter whether a frame is a group or not, default frames are inserted on next pages. This will be fixed soon together with the other bug related to chaining and grouping - 2074).

Now a lot of features are not implemented but we need to get something in trunk because the newly created branch will get outdated again and merging will be problematic.

[boyan]

implementation finished

[meddle]

• Desktop book doesn't behave properly (when autochain is used there new pages are created)
• Deleting first frame results in exception
• When deleting frame of the autochain, the chain is broken the next of the text is missing but the newly created pages after that doesn't disappear.
• The relative ref in the HeadTextFrameH helper result is not right...
• The design notes are important.
• Your test does not pass.
• Deleting the first page when you have many pages has the areas exceptions...
• Try to fix your known issues for Monday, the next release.

2p (80m)

[boyan]

restarting implementation

[boyan]

finished

[meddle]

• I don't know if using ResourceRef#append instead ResourceRef#getRelative is bad. May be it is...
• Some of the bugs like the html export are not fixed.
• Fix the chaining when working with server.

I like the implementation though...

3.5p (2h)

[deyan]

Batch update from file query-10.csv