GSoC 2011 Ideas: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
Line 21: | Line 21: | ||
# Improve Hyphenation Settings (this could also be discussed with many of the apps using text, right?) — include a hyphenation exception list (from a text file, not like it is now — remember, too many clicks...) | # Improve Hyphenation Settings (this could also be discussed with many of the apps using text, right?) — include a hyphenation exception list (from a text file, not like it is now — remember, too many clicks...) | ||
# Allow thin space in Short Words (or by any other automated way): a must in French typography and a blocking issue for pros. | # Allow thin space in Short Words (or by any other automated way): a must in French typography and a blocking issue for pros. | ||
# Make the text runaround image easier than the actual way (text again) | |||
# Clean-up the UI so we have less clics and overall a much smoother workspace. | |||
# Add whatever we miss in the interactive PDF (this is a very powerful tool) | |||
# Make the Render Frame work on OS X (if it does, make it work for everyone, it never worked for me on any machine) | |||
# Add export to PDF/X-1a (de facto standard in Norh America) | |||
=Project 1= | =Project 1= |
Revision as of 20:46, 14 February 2011
List ideas for prospective Google Summer of Code 2011 projects here...
Real table support
- Skills required: C++, Qt4 knowledge
- Scribus lacks real table support. Currently if one wants to have a table he will need to make it in external application and paste it as PS.
- Tables need to become a new kind of object (aside from image and text objects).
- Scribus should do the layouting, including ensuring row height is big enough to provide enough room for the text, the same for columns (plus text wrapping and/or eliding). A possibility for table to flow over several pages should be available.
- Scribus should allow importing data from CSV [and other sorts of data] easily (like specifying delimiter, " symbol handling -- see how openoffice.org it does).
- Easy way to navigate through the cells, and doing table-wide formatting (of all features, text, lines, background...) are much needed.
- Completing at least first item of this list will count as a success for the project.
Ideas from Louis D
- First line indent must be available in the PP (and everything that's available in the Styles must be in the PP too)
- PP and Styles sorted out (see above)
- Undo/Redo.
- Filters to clean-up text at Get Text.
- Style Manager (If it was me, I would start from scratch. Just a suggestion. The bugtracker is full of nice ideas about the SM)
- Improve Hyphenation Settings (this could also be discussed with many of the apps using text, right?) — include a hyphenation exception list (from a text file, not like it is now — remember, too many clicks...)
- Allow thin space in Short Words (or by any other automated way): a must in French typography and a blocking issue for pros.
- Make the text runaround image easier than the actual way (text again)
- Clean-up the UI so we have less clics and overall a much smoother workspace.
- Add whatever we miss in the interactive PDF (this is a very powerful tool)
- Make the Render Frame work on OS X (if it does, make it work for everyone, it never worked for me on any machine)
- Add export to PDF/X-1a (de facto standard in Norh America)
Project 1
- Introduction
- Rationale
- Deliverables
- Part
- Part
- Time scale
- Skills required
- Summary