Implement Pango RenderText for Linux.

ui/gfx/render_text.h

 // Copyright (c) 2011 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 #ifndef UI_GFX_RENDER_TEXT_H_
 #define UI_GFX_RENDER_TEXT_H_
 #pragma once
 
 #include <algorithm>
 #include <vector>
@@ skipping 103 matching lines @@
   CaretPlacement caret_placement() const { return caret_placement_; }
   void set_caret_placement(CaretPlacement placement) {
     caret_placement_ = placement;
   }
 
   bool Equals(const SelectionModel& sel) const;
 
  private:
   void Init(size_t start, size_t end, size_t pos, CaretPlacement status);
 
-  // Logical selection start. If there is non-empty selection, the selection
-  // always starts visually at the leading edge of the selection_start. So, we
-  // do not need extra information for visual selection bounding.
+  // Logical selection start. If there is non-empty selection, if
+  // selection_start_ is less than selection_end_, the selection starts visually
+  // at the leading edge of the selection_start_. If selection_start_ is greater
+  // than selection_end_, the selection starts visually at the trailing edge of
+  // selection_start_'s previous grapheme. So, we do not need extra information

[msw, 2011/08/19 23:16:59]

Is that true? Isn't it always leading the selection start?
What does the selection range of "abc[DE]F" look like? I don't think there's any
component of that selection that trails 'c', it's just "abcF[ED]".

Can you show an example of when MoveCursorLeft/Right should move the
cursor&caret to trail the selection start's previous grapheme?

[xji, 2011/08/22 23:57:28]

The above example wont show any difference.
But the difference shows up when you select "abc[FE]D".

logically, the selection range is the same no matter you select from left to
right or right to left. For the above example, the selection range is (6, 4) or
(4, 6).

But the visual starting point is different between select from right to left and
from left to right.

If you click right half of 'E' and move mouse left, the selection visually start
from (4, leading).
If you click left half of 'F' and move mouse right, the selection visually start
from (5, trailing), but (6, leading).

The difference probably wont affect the selection's substring bounds.
But it affects when moving cursor left or right when there is selection, in
which case, the selection should be collapsed to visual left or right.
For the above example, when selection range (6, 4), selection_start is at
visually left when using (5, trailing) as visual start point. But selection_end
is at visually left when using (6, 0) as visual start point, which is wrong.

[msw, 2011/08/23 08:01:01]

Ok, I think I understand and it seems that you are correct.

+  // for visual bounding.
   size_t selection_start_;
 
   // The logical cursor position that next character will be inserted into.
   // It is also the end of the selection.
   size_t selection_end_;
 
   // The following two fields are used to guide cursor visual position.
   // The index of the character that cursor is visually attached to.
   size_t caret_pos_;
   // The visual placement of the cursor, relative to its associated character.
@@ skipping 154 matching lines @@
 
   // Clear out |style_ranges_|.
   void ClearStyleRanges();
 
   bool IsPositionAtWordSelectionBoundary(size_t pos);
 
   // Update the cached bounds and display offset to ensure that the current
   // cursor is within the visible display area.
   void UpdateCachedBoundsAndOffset();
 
+  // Returns the selection model of selection_start_.
+  // The returned value represents a cursor/caret position without a selection.
+  SelectionModel GetSelectionModelForSelectionStart();
+
   // Logical UTF-16 string data to be drawn.
   string16 text_;
 
   // Logical selection range and visual cursor position.
   SelectionModel selection_model_;
 
   // The cached cursor bounds; get these bounds with GetUpdatedCursorBounds.
   Rect cursor_bounds_;
 
   // The cursor visibility and insert mode.
@@ skipping 21 matching lines @@
   // SetCursorPosition, SetSelectionModel, Font related style change, and other
   // operations that adjust the visible text bounds.
   bool cached_bounds_and_offset_valid_;
 
   DISALLOW_COPY_AND_ASSIGN(RenderText);
 };
 
 }  // namespace gfx
 
 #endif  // UI_GFX_RENDER_TEXT_H_