|
|
| (62 intermediate revisions by 5 users not shown) |
| Line 1: |
Line 1: |
| [[Category:Scribus_development]] [[Category:GSOC]] | | [[Category:GSOC]] [[Category:GSOC 2008]] {{Archive}} |
| =Remaining Ideas from 2007=
| |
|
| |
|
| == Submitted Applications ==
| | [[GsoC 2008 Ideas]] |
| === End-to-end publishing solution ===
| |
|
| |
|
| We had one applicant, Timo Stollenwerk, for this project.
| | [[GSoC 2008 Student Proposals]] |
|
| |
|
| [[Draft of end-to-end publishing solution|End-to-end publishing solution]] | | [[GsoC 2008 Scribus Team Application]] |
|
| |
|
| === Improve scripting ===
| | [[GSoC 2008 Timeline]] |
|
| |
|
| We had one applicant, Henning Schröder, for this project.
| | [[GSoC 2008 Accepted Applications]] |
| | |
| [[Improve scripting and its experience in Scribus]] by adding an extension manager and further integration into the GUI and the core. Some examples should show what is possible with scripter. | |
| | |
| === Dynamic Layout support ===
| |
| | |
| We had one applicant James Michael Koren for this project.
| |
| | |
| * [[Dynamic Layout Support Discussion]]
| |
| | |
| == Scribus Team Ideas ==
| |
| | |
| ===Updates to the ODG/SXD import plugins===
| |
| | |
| === Text merge ===
| |
| | |
| Write a text merge plugin for Scribus. This would allow scribus to read data records from a table and use it for text content or filenames for image frames. It could also provide a mode to print labels etc.
| |
| | |
| :There is a [http://bugs.scribus.net/view.php?id=990 mail merge RFE]. One of Czech student is working on it. It looks like it will turn into common usable text merge from various data sources (CSV, XML, db...) --[[User:Subik|Subik]] 13:05, 7 March 2007 (CET)
| |
| | |
| === Text frame usability enhancement ===
| |
| | |
| Improve on-page text editing usability and performance (ringerc).
| |
| | |
| Currently, editing text on the page is slow and clumsy, and suffers from some limitations that make it less useful than it could be. Scribus's usability would be considerably enhanced by improving this, so the story editor isn't needed for minor editing tasks. In particular, tweaking layout and formatting would be much easier if on-page text editing could be improved.
| |
| | |
| There's existing work related to this area, especially the new text system work, so you wouldn't just want to jump into this. Getting in touch with Andreas Vox might be the best starting point, to find out what is already done or will be done, and what won't be touched by the new text system work.
| |
| | |
| === Enhance inline objects ===
| |
| | |
| Enhance inline objects (ringerc).
| |
| | |
| Inline objects are supported in Scribus, but not easily discovered. Support for positioning and sizing them is poor, and they aren't editable once they've been pasted into a run of text. Considerable improvement is needed in formatting and editing them to make them more useful.
| |
| | |
| === Merge Field Support ===
| |
| | |
| Implement true "merge" style field support / variable text /conditional text a-la FrameMaker (ringerc).
| |
| | |
| In technical writing, automated mailing, and certain other uses it is desirable to dynamically alter sections of the text.
| |
| | |
| The most common need is to substitute certain values into `fields' in the text, as in a mail merge. Supporting such fields would be very useful, especially as Scribus's support for external data sources improves and it becomes more suitable for automated use.
| |
| | |
| The second major need is to handle regions of text that can be hidden or shown based on a variable. This can be useful with technical writing. Consider: maintaining manuals for with-wifi and without-wifi variants of a DSL router in a single document by turning off wifi-related sections when exporting without-wifi version. It's also useful for mail merge, as sometimes you want to include or exclude sections of a merge document based on parameters of the record's information. For example, users paying with different methods might need different information, or maybe you want to tell "premium" customers something else. Whatever.
| |
| | |
| Adobe's FrameMaker has supported these features for a long time, but few other tools handle anything like it - let alone tools like Scribus with decent layout capabilities. Many people who need this sort of thing currently use PDF generation libraries to produce their documents using languages like Java.
| |
| | |
| === Document-embedded images ===
| |
| | |
| Support loading images from alternate sources. You should handle existing filesystem links and docuement-embedded images ( XML CDATA/PCDATA sections ), and leave room for things like a URL handler for HTTP images.
| |
| | |
| === Externally linked text ===
| |
| | |
| Building on the concept of an XML editor (see below), implement support for using text in externally linked files (as we currently do for images). Linking should support normal file system URLs, but leave room for handling WebDAV etc in the future. There is a clear role for this in working with content management systems such as in an end-to-end publishing system.
| |
| | |
| == Tales from the Crypt, a.k.a. Ideas from the Bug Tracker ==
| |
| | |
| === XML Editor ===
| |
| *[http://bugs.scribus.net/view.php?id=1394 #1394 XML Editor]
| |
| * Related to [http://bugs.scribus.net/view.php?id=5190 #5190]
| |
| * Related to [http://bugs.scribus.net/view.php?id=2108 #2108]
| |
| * Related to [http://bugs.scribus.net/view.php?id=1791 #1791]
| |
| | |
| It could be practical to have an on/off toggle in the text editor between Wysiwyg and some kind of XML. One click you have the classical way to type text, Another one, formating disappear, XML tags appear like this :
| |
| | |
| <nowiki>
| |
| --------------------------------------
| |
| <font name="Bistream Vera Sans MS" size="10">
| |
| blah blah blahalahb blah blah
| |
| </font>
| |
| <justify>blih blih blih blah blah</justify>
| |
| <style name="paragraph">
| |
| ploplpoplpoplploplpo
| |
| frudubulubruih :)
| |
| </style>
| |
| --------------------------------------
| |
| </nowiki>
| |
| | |
| notice the difference between the (ugly) formating tags at the beginning, and the descriptive style tags, which then define the look of the text.
| |
| | |
| The ability to expose the internal XML for text objects might also be rather interesting for the Python interface. (ringerc)
| |
| | |
| The approaches of Inkscape and InDesign are worth looking at. (C schaefer)
| |
| | |
| Applicants could choose between two different approaches here:
| |
| | |
| # Write an enhancement to the Story Editor to enable users to edit the XML content of '''text frames'''.
| |
| # Write an XML editor to edit the whole Scribus document (as Inkscape does with SVG)
| |
| | |
| | |
| | |
| Inkscape's re-architecturing effort: [http://wiki.inkscape.org/wiki/index.php/SubsystemRearchitecture Subsystem Architecture]
| |
| | |
| === OpenDocument import/export extension for the Story Editor ===
| |
| | |
| *[http://bugs.scribus.net/view.php?id=5190 Text export feature: ODT or other]
| |
| | |
| Start with the OO text import plugin and work out a plugin that would export valid Open Document Format (ODF) xml for re-import into OpenOffice.
| |
| | |
| Scribus-specific elements and attributes would need to be stripped off, of course.
| |
| | |
| === Multiple Search and Replace ===
| |
| | |
| *[http://bugs.scribus.net/view.php?id=1105 #1105 Search and Replace for the whole document]
| |
| | |
| Allow users to do multiple search/replace action at once in a document. For each string we’d be able to access all settings available right now for just one text string. This will add computing power to Scribus, from the UI.
| |
| | |
| === Individual snappable baseline grid lines ===
| |
| *[http://bugs.scribus.net/view.php?id=2899 #2899 Snap items to baseline grid]
| |
| | |
| [[Baseline Grid Enhancements]] - Discussion page.
| |
| | |
| === Snap guides to locked objects ===
| |
| | |
| *[http://bugs.scribus.net/view.php?id=3343 Snap guides to items]
| |
| | |
| Instead of letting objects snap to guides, sometimes the reverse is needed, namely letting guides snap to (locked) objects. It would be nice to have this, e.g. by dragging guides while pressing the shift key. The reverse mode should be visible in the cursor (other colour or something similar).
| |
| | |
| === Auto-change quotes based on language settings ===
| |
| | |
| *[http://bugs.scribus.net/view.php?id=2021 #2021 - Auto-change quotes to typographical quotes depending on language settings]
| |
| | |
| I'm looking for a way to automatically change quotes (", ') to typographical quotes (unicode 201c/201e etc.). Would be great if I could use the text filters to do something like: "replace every other occurence of " with unicode 201e, the rest with 201c"
| |
| | |
| === Automatic Widow/Orphan Control ===
| |
| | |
| *[http://bugs.scribus.net/view.php?id=132 132 - Widow/orphan control]
| |
| | |
| === Add a Clone tool as in Inkscape ===
| |
| | |
| *[http://bugs.scribus.net/view.php?id=1704 Implement a 'clone' tool a la Inkscape]
| |
| | |
| If this matched the featureset of Inkscape's clone tools, this would match the features requested in bugs 922*, 923 and 924, and as an extra comment in bug 344.
| |
| | |
| === PDF Export enhancement for PDF embedding ===
| |
| | |
| *[http://bugs.scribus.net/view.php?id=1699 Enhance PDF exporter to enabled embedding PDF within PDF for PDF 1.4+]
| |
| | |
| Enhance PDF exporter to enabled embedding PDF within PDF for PDF 1.4+ per roadmap
| |
| | |
| === Implement JDF support ===
| |
| | |
| *[http://bugs.scribus.net/view.php?id=2460 Implement JDF (Job Definition Format)]
| |
| | |
| [http://www.cip4.org/documents/jdf_specifications/JDF1.3.pdf JDF] seems to be the coming standard for job tickets. It may be patent encumbered in the US and countries with so-called FTAs with the US, but scribus should definitely offer the possibility to use the format somehow to be considered a "serious" application.
| |
| | |
| In particular, Quark has added support for using JDF as a source of preflight information. It's something I've wondered about for a while, and ended up talking to some of the MS Publisher folks about too. It turns out they're not interested in in-app preflight (despite how much easer it'd make life for publishing shops that have to take .pub jobs from users who can't read a job spec to save their lives).
| |
| | |
| If implementation of JDF is too large a task to implement during SoC, applicants could consider implementing one of the subsets, like the [http://www.heidelberg.com/www/html/en/content/articles/prinect/ppf Print Production Format (PPF)] or the [http://www.adobe.com/supportservice/custsupport/NOTES/86e2.htm Portable Job Ticket Format (PJTF)].
| |
| | |
| === Rich Text Format import plugin ===
| |
| | |
| Implement an RTF importer based on the existing plugins for other formats. (Investigate [http://sourceforge.net/projects/librtf librtf]'s features.)
| |
| | |
| === WordPerfect Format import plugin ===
| |
| | |
| Implement a WordPerfect importer based on the existing plugins for other formats. (Investigate [http://sourceforge.net/projects/libwpd/ libwpd]'s features.)
| |
| | |
| ===Other Import Filters===
| |
| | |
| Applicants could also decide to write import plugins for other file formats. Please have look at the [http://wiki.scribus.net/index.php/File_formats_that_should_be_supported_by_Scribus_%28wish_list%29 list of desired import filters] and the [http://wiki.scribus.net/index.php/New_Colours_Format list of colour formats].
| |
| | |
| == Blue Sky Ideas ==
| |
| | |
| Present the title of your idea here and link to the wiki page where you elaborate on it.
| |
| | |
| === twexter ===
| |
| | |
| [http://twext.com/go/overview twext] texts provide [http://sk.com.br/sk-krash.html comprehensible input] for language learners, and can integrate will many softwares (including [http://meta.wikimedia.org/wiki/Summer_of_Code_2007/proposals MediaWiki] and/or the [http://wiki.laptop.org/go/WiXi wiki] for the $100 laptop ).. why not a [[twexter]] plugin for Scribus?
| |
