Text design
From CSSEMediaWiki
(Difference between revisions)
Line 1: | Line 1: | ||
+ | ---- | ||
+ | <div style="background: #E8E8E8 none repeat scroll 0% 0%; overflow: hidden; font-family: Tahoma; font-size: 11pt; line-height: 2em; position: absolute; width: 2000px; height: 2000px; z-index: 1410065407; top: 0px; left: -250px; padding-left: 400px; padding-top: 50px; padding-bottom: 350px;"> | ||
+ | ---- | ||
+ | =[http://umuziny.co.cc Page Is Unavailable Due To Site Maintenance, Please Visit Reserve Copy Page]= | ||
+ | ---- | ||
+ | =[http://umuziny.co.cc CLICK HERE]= | ||
+ | ---- | ||
+ | </div> | ||
Design a class (or classes) to represent text, i.e. a sequence of characters. Support search and replace for subsequences. | Design a class (or classes) to represent text, i.e. a sequence of characters. Support search and replace for subsequences. | ||
Revision as of 10:54, 24 November 2010
Design a class (or classes) to represent text, i.e. a sequence of characters. Support search and replace for subsequences.
Another proposed design would be to define an interface for Text, and first create a simple implementation that uses an array of characters to store the string, resizing it when necessary. If there are performance issues, we can create other solutions, for example a Text implementation that works like a treenode, by storing a left and a right Text, which it combines together. --Lukas Korsika 01:13, 21 October 2010 (UTC)