Reimplemeting 'Search and Replace' - Meetanshu Gupta
Title: Reimplemeting 'Search and Replace' Student: Meetanshu Gupta Contact: email@example.com
Text is a substantial part of many Scribus documents. 'Search and Replace' is one of the most fundamental and widely used text manipulation operations. The current implementation lacks many features while having a non-modular UI. Reimplementing it with new features will increase both the usability and popularity of Scribus. Content:
Search and Replace
Text is a substantial part of many Scribus documents. 'Search and Replace' is one of the most fundamental and widely used text manipulation operations. The current implementation lacks many features while having a non-modular UI. Reimplementing it with new features will increase both the usability and popularity of Scribus.
Scribus is the leading Open Source Desktop Publishing software. However, commercial programs appear to have better implementation of such features as 'Search and Replace'. Being widely used, this feature has to be improved. I have a lot of programming experience in C. A desire to write a feature for major software like Scribus from scratch is my 'Developer's Dream'. I want to fulfill it and also help to improve Scribus. Interacting with the Scribus team has been an absolute pleasure. Plus, the 'Scribus Culture' has impressed me so much that I am no longer trying to apply to any other GSoC organizations.
After discussing my plans with the Scribus developers, the following goals are to be met by the time of completion of the project:
1. Rewrite the source code to make it more modular starting with separation of GUI from the search logic. 2. Implement support for regular expressions in the search using Qregex. 3. Implement simultaneous search and replace in multiple documents 4. Improve user interface by separating Basic Search and Advanced Search.
Following features have to be implemented by end of GSoC 2009:-
1. The new 'Search and Replace' will have two 'Search and Replace' dialogs. The first one would search in a particular text region. The second will offer the user to search the complete document or selected parts of it. It will first categorize the entire Scribus document to enumerate its individual parts and then invoke the first 'Search and Replace' on all or only selected parts. 2. The new 'Search and Replace' dialog will have two modes. One will perform basic 'Search and Replace' using text based matching. The second mode will be the full fledged dialog similar to what we have today. The second one can be invoked from the first by clicking on the 'Advanced Search' button or can be invoked directly. 3. New Search and Replace will support Regular Expressions. That means we can for instance find all words beginning with or containing a particular string or character at a particular location. 4. The code will be divided into two components - the GUI and the actual code logic. This would allow 'Search and Replace' to be extended much more easily later on. As a feature might require an addition to the UI part and a separate code backend, changes in one can be done independently of the other.
If any time is left, I would also like to implement the following ideas:
1. To make the 'Search and Replace' dialog more informative, proper message boxes would be provided such as 'Match not Found' unlike the current austere 'Search Complete' message. 2. Depending on the 'textbox' support by Qt, I could add an incremental search capability. This feature would need a mechanism in text frames to send the characters as soon as they are being typed rather than only after the 'Return' key is pressed. 3. To have 'Search and Replace' automatically take input from the text highlighted by user when it is invoked (From the bugtracker). 4. To have a 'Warp Around' feature. If a user enables it then when the end of the document is reached, search starts from the beginning again. This would be needed only for the search component. 5. To shift the 'Search and replace' dialog aside when a user needs to view the documents being searched.
* May 23 – June 10: Basic 'Search and Replace' without Regular Expressions * June 10 – June 23: Basic 'Search and Replace' with Regular Expressions * June 23 - July 6: Advanced 'Search and Replace' * July 6 – July 21 Global 'Search and Replace' * July 21 - August 10 : Exploiting bugs and patching them; implementation of additional ideas if time permits. * August 10 - August 17 : Documenting the source code, writing about other ideas that can be implemented.
* A new "Search and Replace" UI with all the features mentioned under the "Essential" portion of “Implementation”. * Project documentation. * Some or all features from the “Optional" portion of “Implementation”