Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1232090

Summary:	Make new editor the default
Product:	[Retired] Zanata	Reporter:	David Mason <damason>
Component:	TranslationEditor	Assignee:	Michelle Kim <mkim>
Status:	CLOSED UPSTREAM	QA Contact:	Zanata-QA Mailling List <zanata-qa>
Severity:	unspecified	Docs Contact:	David Mason <damason>
Priority:	unspecified
Version:	3.6	CC:	aeng, lbrooker, zanata-bugs
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-07-28 22:52:59 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1122350, 1235063, 1235064, 1235065, 1235067, 1235069, 1235071, 1235072, 1235074, 1235075, 1235077, 1235078, 1235079, 1235080, 1235082, 1245442
Bug Blocks:

Description David Mason 2015-06-16 04:03:03 UTC

When the new editor has all the crucial features implemented, it should be made the default editor opened when editing translations for a document.

An option should be provided to switch to the old editor until the new editor covers every use-case covered by the old editor.

Here is an initial list of features that have not yet been implemented in the new editor. Some of these already have bugzilla entries, for the rest I will create them. I will add them as blockers to this bug.

## Crucial features to implement before the switch:

- Show current workspace info as title of browser tab
- Multiple-field search to filter text flows.
- Highlight matching words in text flows.
- Document list
- Document stats
- Uploaded info (user, timestamp)
- Translated info (user, timestamp)
- Add activity panel (for comments, history, etc.)
- Text flow history (in activity panel)
- Translation comments (in activity panel)
- TM match details panel
- TM suggestions highlight mode (default mode when diff turned off)
- Show reference translations from another language
- Live validations
- Concurrent save conflict resolution

## Feature we may want to implement before the switch:

- Improved "Undo". Undo is available in the new editor, but only until the next save. In the old editor, undo is available as long as there is a previous version to revert to.
- TM merge (replace with auto-fill). Before this is implemented, translators would still be able to run TM merge in the old editor. This may be too much of an annoyance though. Instant-TM may also offset the need for this.
- Phrase (exact) search. Fuzzy search should rank exact matches at the top anyway, so exact-only search does not seem crucial.
- Concurrent editing information (which users are working on which strings, are they typing, etc.)

## Features to implement to cover all use-cases:

Can implement these after the switch.

- Allow multi-field search to be saved as personal filters.
- Advanced search dropdown
- Replacement for project-wide search & replace:
- Allow multiple-document selection for editing
- Allow "replace" in searches that include text
- Allow translation download & upload in document list
- Add text flow details panel for TM match details (extra level of detail, not available in old editor).
- Instant TM (entered translations available immediately as TM matches, TM matches pre-fetched so they show up instantly when a row is selected).
- Glossary (inline definitions of words, with option to open panel)
- Improve validations so errors are shown in the string

Comment 1 Michelle Kim 2015-06-16 05:47:42 UTC

Hi David,

Thanks for identifying the crucial features list for new Editor.
I agree with all except one :  
- Show reference translations from another language

Manuel and I believe this doesn't have to be part of crucial feature.

Comment 2 David Mason 2015-06-17 03:55:54 UTC

For all the non-crucial features, I will create a separate bug to track those. They are all things that should be added in the new editor before we can completely remove the old editor. It will be handy to have that feature list when we are deciding about removing it.

Comment 3 Alex Eng 2015-06-17 04:12:25 UTC

I think document list mentioned should be part of the version page/or just in the editor. We should try to avoid having to maintain 2 document list UI.

>> Document list
   - Document stats
   - Uploaded info (user, timestamp)
   - Translated info (user, timestamp)

Comment 4 Luke Brooker 2015-06-17 04:17:26 UTC

(In reply to Alex Eng from comment #3)

The idea is to end up using the same component to display the list. When it is one big SPA it can possibly be 1 list, but from my experience, translator rely on the "in editor" document list all the time, we can't remove that functionality.

Comment 5 David Mason 2015-06-23 02:11:46 UTC

Another crucial feature that is missing:

 - Notify users of failed save.

Comment 6 Michelle Kim 2015-06-23 06:00:56 UTC

David, 

If we finalized the crucial feature list for new editor, 
Can I ask you to create individual RFEs for each tasks included in crucial list? so that I can prioritize them into the backlog.

Thanks,
Michelle

Comment 7 David Mason 2015-06-24 00:11:34 UTC

I have added all the items in "Crucial features" as blockers to this bug. See the dependency tree for a summary that includes the bug names: https://bugzilla.redhat.com/showdependencytree.cgi?id=1232090&hide_resolved=1

Comment 8 Zanata Migrator 2015-07-28 22:52:59 UTC

Migrated; check JIRA for bug status: http://zanata.atlassian.net/browse/ZNTA-36