Difference between revisions of "Free Desktop Graphic Suite"

From Inkscape Wiki
Jump to navigation Jump to search
(Add link to freiefarbe)
 
(7 intermediate revisions by 3 users not shown)
Line 10: Line 10:
* Scribus (page layout)
* Scribus (page layout)


[[Common dialogs]]
== [[Common dialogs]] ==


[[Tool consistency]]
== [[Tool consistency]] ==


'''Resources that can be shared:'''
== Resources that can be shared: ==
* Patterns (PNGs)
* Patterns (PNGs)
* Gradients (SVGs)
* Gradients (SVGs)
* Palettes (We need a standard here.) (suggestion: .xml format, based on .ai format (each text line with each colour name and its rgb, cmyk or whatever))
* Palettes (We need a standard here.) (suggestion: .xml format, based on .ai format (each text line with each colour name and its rgb, cmyk or whatever))
* Clipart (SVG[[/PNG]])
* Clipart (SVG/PNG)
:: Could some kind of work-sharing connection be developed: a toolbar with links to import recent/open  files in the GIMP/Paint.net? On Windows at least surely it would be possible through MRUs, on Linux I don't know how it's stored. Would this break platform/software agnosticism, if so, could it be implemented as an extension? Is there a way extensions can create a toolbar in Inkscape itself? Should there be? The GIMP/Openshot/whatever developers should be asked if they would consider adding something like this into their own software. Also, the community  needs some kind of universial, portable and standard svg rendering engine that can cope with InkscapeSvg. I think the ability to know that your source svg looks fine in the GIMP or several other programs on anyone else's computer would encourage people to use it a lot more (and would leapfrog the Adobe formats). It would also mean that when you used a vector image in another program you wouldn't have to rasterise it, so output would be better quality. [[User:Legio noctis|Legio noctis]] 14:56, 31 March 2010 (UTC)  
:: We need some kind of universal, portable and standard svg rendering engine that can cope with InkscapeSvg. I think the ability to know that your source svg looks fine in the GIMP or several other programs on anyone else's computer would encourage people to use it a lot more (and would leapfrog the Adobe formats). It would also mean that when you used a vector image in another program you wouldn't have to rasterise it, so output would be better quality. [[User:Legio noctis|Legio noctis]] 14:56, 31 March 2010 (UTC)  
* Icons
* Icons
* Cursors  
* Cursors  
Line 29: Line 29:
To help manage these resources it would probably be wise to try and incorporate some kind of Thumbnail Browser into any such suite.  Unfortunately there is no obvious choice of cross platform and open source Thumbnail browser.
To help manage these resources it would probably be wise to try and incorporate some kind of Thumbnail Browser into any such suite.  Unfortunately there is no obvious choice of cross platform and open source Thumbnail browser.


:: Could all the open source projects agree on one location to store all these resources or links to them e.g. <tt>~/.graphicsresources</tt> (ugly name, I know) or <tt> %appdata%\Graphic resources\</tt>.
:: Could all the open source projects agree on one location to store all these resources or links to them e.g. <tt>~/.graphicsresources</tt> or <tt> %appdata%\Graphic resources\</tt>?


Could this system be turned into a new open source project/standard of its own? For example, say we called it something like 'Interleave' or 'Pixelshare', for lack of a graphic-y sounding name.  We could then say that every Pixelshare-supporting program makes sure that a <tt>Pixelshare resources</tt> folder has been established. This would then contain a set directory structure, e.g. there could be a database (XML?) of the various programs/files/whatever is needed for efficient operation. For example:
Could this system be turned into a new open source project/standard of its own? For example, say we called it something like 'Pixelshare', for lack of a graphic-y sounding name.  We could then say that every Pixelshare-supporting program makes sure that a <tt>Pixelshare resources</tt> folder has been established. This would then contain a set directory structure, e.g. there could be a database (XML?) of the various programs/files/whatever is needed for efficient operation. For example:
<tt>
<tt>
/cursors<br />
/cursors<br />
Line 46: Line 46:
I suggest information.xml contains metadata about the programs, what they produce, formats etc, and the (potential) database inside the <tt>Inkscape</tt> folder  actually contains information such as location of the image, when it was last opened, by what, created, by what, notes attached to it, whether it is a derivative of another file in the database etc.
I suggest information.xml contains metadata about the programs, what they produce, formats etc, and the (potential) database inside the <tt>Inkscape</tt> folder  actually contains information such as location of the image, when it was last opened, by what, created, by what, notes attached to it, whether it is a derivative of another file in the database etc.


I will try to return to this page and expand on my ideas more solidly. Someone had a grand vision creating this page, and I don't want to see it come to nothing. --legio_noctis, January 2010 (If you're reading this
I will try to return to this page and expand on my ideas more solidly. Someone had a grand vision creating this page, and I don't want to see it come to nothing. [[User:Legio noctis|Legio noctis]] 18:27, 1 April 2010 (UTC)
far in the future, shaking your head and sighing: sorry.)


Working on mockups for a toolbar [[User:Legio noctis|Legio noctis]] 14:55, 31 March 2010 (UTC)
== A file sharing toolbar ==


[[Feature Requests]]
Some mockups:
 
Standard toolbar:
 
[[File:Opengraphics_toolbar_mockup_1.png|800px]]
 
Toolbar with 'send to another application' menu open:
 
[[File:Opengraphics_toolbar_mockup_2.png|800px]]
 
Toolbar with 'my collections' menu open:
 
[[File:Opengraphics_toolbar_mockup_3.png|800px]]
 
Mini toolbar:
 
[[File:Opengraphics_toolbar_mockup_4.png|800px]]
 
Is this feasible? [[User:Legio noctis|Legio noctis]] 15:12, 31 March 2010 (UTC)
 
== [[Feature Requests]] ==


There are many features in the GIMP that Inkscape will want to copy such as the Dock Widgets for managing Palettes.   
There are many features in the GIMP that Inkscape will want to copy such as the Dock Widgets for managing Palettes.   
Line 77: Line 96:


* http://openclipart.org/
* http://openclipart.org/
=== The Open Publishing Tools Organization (OPTO) ===
This idea comes out of a discussion online with MRDOCS, about the need for Open Publishing Tools to unite and develop some sort of presence so that printers understand that there are other tools that are being used, other than QUARK, PHOTOSHOP, ILLUSTRATOR, and INDESIGN. There are other issues too that need to be dealt with, such as PANTONE's monopoly over the color industry. A project idea that OPTO could commission is/are open swatchbooks, which could be sold for the price of printing them (standard color formulas for printers) and could be downloaded as PDF files as well.
Initial Applications that would fall under OPTO:
* Scribus
* Ghostscript
* Inkscape
* CUPS
* [[The_Gimp]]
* GIMP-Print
==== Open Swatches ====
pastels, grays, coated, uncoated, Web, sheetfed, Web Offset, metallics
See https://www.freiefarbe.de/en/
==== Font Management Software (like suitcase or atm) ====
It should be relatively easy to slap together a GTK+ frontend for fontconfig that will allow the management of fonts, loading of new permanent and temporary fonts for a system, and then run 'fc-cache' to update a desktop to the new fonts installed. This is very necessary for designers whom work with MANY fonts and need to be able to load new ones without restarting their system. Commandline is not the most user-friendly for this type of task.
Scribus, has a capability to package up all the images and layout files into a separate directory, which can then be tarred.  Would be nice if the fonts could be managed in a compatible fashion. Already, packaging fonts is in the Scribus tracker as a request.
For everyday installing, this is not needed with KDE, as of 3.2 it has KIOslave for fonts: fonts:// linked to ~/.fonts and a previewer for individual font faces. It works really well. Gnome has fontilus, but I have less experience with it.
Perhaps focus should be on packaging with files ([[The_Gimp]] and other image files, Inkscape files and Scribus layouts) and making it easy to restore, files and fonts on other machines..
Scribus has added preliminary support for [[The_Gimp]] integration in 29022004 1.2cvs. This allows a user to launch [[The_Gimp]] to edit an image from within Scribus and edit the file with return to Scribus after saving changes. Would be a nice option for Inkscape.
--mrdocs
See Also:
* [[ScribusInteroperability]]
* [[Related programs]]
* [[InkscapeColor]]
* [[OpenClipart]]


[[Category:Developer Discussion]]
[[Category:Developer Discussion]]
[[Category:Needs Work]]
[[Category:Needs Work]]

Latest revision as of 00:30, 20 April 2019

Common interface for graphic programs on the free desktop.

Many artists use several applications in their workflow. This includes using one program for photo editing, one for illustration and one for page layout. To ease the user experience for someone using these apps, consistency in wording, looks and similar working tools needs to be adressed.

The three programs that will be adressed are:

  • GNU Image Manipulator Program aka GIMP (bitmap image editing)
  • Inkscape (scalable graphics illustration)
  • Scribus (page layout)

Common dialogs

Tool consistency

Resources that can be shared:

  • Patterns (PNGs)
  • Gradients (SVGs)
  • Palettes (We need a standard here.) (suggestion: .xml format, based on .ai format (each text line with each colour name and its rgb, cmyk or whatever))
  • Clipart (SVG/PNG)
We need some kind of universal, portable and standard svg rendering engine that can cope with InkscapeSvg. I think the ability to know that your source svg looks fine in the GIMP or several other programs on anyone else's computer would encourage people to use it a lot more (and would leapfrog the Adobe formats). It would also mean that when you used a vector image in another program you wouldn't have to rasterise it, so output would be better quality. Legio noctis 14:56, 31 March 2010 (UTC)
  • Icons
  • Cursors
  • Color Management
  • Fonts
  • Symbols
  • Filters

To help manage these resources it would probably be wise to try and incorporate some kind of Thumbnail Browser into any such suite. Unfortunately there is no obvious choice of cross platform and open source Thumbnail browser.

Could all the open source projects agree on one location to store all these resources or links to them e.g. ~/.graphicsresources or %appdata%\Graphic resources\?

Could this system be turned into a new open source project/standard of its own? For example, say we called it something like 'Pixelshare', for lack of a graphic-y sounding name. We could then say that every Pixelshare-supporting program makes sure that a Pixelshare resources folder has been established. This would then contain a set directory structure, e.g. there could be a database (XML?) of the various programs/files/whatever is needed for efficient operation. For example: /cursors
/icons
/images

/Inkscape
...insert here either actual files, shortcuts to files or database of files...
/GIMP

information.xml
/sound
/videos

I suggest information.xml contains metadata about the programs, what they produce, formats etc, and the (potential) database inside the Inkscape folder actually contains information such as location of the image, when it was last opened, by what, created, by what, notes attached to it, whether it is a derivative of another file in the database etc.

I will try to return to this page and expand on my ideas more solidly. Someone had a grand vision creating this page, and I don't want to see it come to nothing. Legio noctis 18:27, 1 April 2010 (UTC)

A file sharing toolbar

Some mockups:

Standard toolbar:

Opengraphics toolbar mockup 1.png

Toolbar with 'send to another application' menu open:

Opengraphics toolbar mockup 2.png

Toolbar with 'my collections' menu open:

Opengraphics toolbar mockup 3.png

Mini toolbar:

Opengraphics toolbar mockup 4.png

Is this feasible? Legio noctis 15:12, 31 March 2010 (UTC)

Feature Requests

There are many features in the GIMP that Inkscape will want to copy such as the Dock Widgets for managing Palettes.

There are also some enhancements to the GIMP like this request for a standard toolbar that would be helpful for Inkscape users.

Links


The Open Publishing Tools Organization (OPTO)

This idea comes out of a discussion online with MRDOCS, about the need for Open Publishing Tools to unite and develop some sort of presence so that printers understand that there are other tools that are being used, other than QUARK, PHOTOSHOP, ILLUSTRATOR, and INDESIGN. There are other issues too that need to be dealt with, such as PANTONE's monopoly over the color industry. A project idea that OPTO could commission is/are open swatchbooks, which could be sold for the price of printing them (standard color formulas for printers) and could be downloaded as PDF files as well.

Initial Applications that would fall under OPTO:

  • Scribus
  • Ghostscript
  • Inkscape
  • CUPS
  • The_Gimp
  • GIMP-Print

Open Swatches

pastels, grays, coated, uncoated, Web, sheetfed, Web Offset, metallics

See https://www.freiefarbe.de/en/


Font Management Software (like suitcase or atm)

It should be relatively easy to slap together a GTK+ frontend for fontconfig that will allow the management of fonts, loading of new permanent and temporary fonts for a system, and then run 'fc-cache' to update a desktop to the new fonts installed. This is very necessary for designers whom work with MANY fonts and need to be able to load new ones without restarting their system. Commandline is not the most user-friendly for this type of task.

Scribus, has a capability to package up all the images and layout files into a separate directory, which can then be tarred. Would be nice if the fonts could be managed in a compatible fashion. Already, packaging fonts is in the Scribus tracker as a request.

For everyday installing, this is not needed with KDE, as of 3.2 it has KIOslave for fonts: fonts:// linked to ~/.fonts and a previewer for individual font faces. It works really well. Gnome has fontilus, but I have less experience with it.

Perhaps focus should be on packaging with files (The_Gimp and other image files, Inkscape files and Scribus layouts) and making it easy to restore, files and fonts on other machines..

Scribus has added preliminary support for The_Gimp integration in 29022004 1.2cvs. This allows a user to launch The_Gimp to edit an image from within Scribus and edit the file with return to Scribus after saving changes. Would be a nice option for Inkscape.

--mrdocs

See Also: