GSoC 2013 Ideas: Difference between revisions

From Scribus Wiki
Jump to navigation Jump to search
(first ideas for GSOC 2013)
 
No edit summary
Line 1: Line 1:
Idéas for GSOC 2013 :
[[Category:GSOC 2013]][[Category:EN]]
 
Ideas for GSOC 2013 :


- Compliance -- turn the compiler up to all warnings are bugs. Make all warnings go away.  In C++ every "warning" means "it will not work on a class of popular systems, or will work but give bad data". Fix them.
- Compliance -- turn the compiler up to all warnings are bugs. Make all warnings go away.  In C++ every "warning" means "it will not work on a class of popular systems, or will work but give bad data". Fix them.

Revision as of 17:15, 13 December 2012


Ideas for GSOC 2013 :

- Compliance -- turn the compiler up to all warnings are bugs. Make all warnings go away. In C++ every "warning" means "it will not work on a class of popular systems, or will work but give bad data". Fix them.

- generally make it easier for somebody to jump in quickly to try out stuff on your software, either by removing the the obstacles : the unfriendly build issues, write some simple demos/guides (but GSOC cannot cover documentation).

- "export to true web enabled PDF" option, that is create lightweight PDFs.