Hi all,
I think Gez posted the most compelling reason to get rid of pdf and the like in the save as dialog. Inkscape will happily destroy the multipage document with prepress ready infromation with its own export file. If all you do with it is edit an image that doesn't need to go to print that's fine, but I guess those that are accustomed to using Adobe software with its extended pdf files that enable editing it with retaining all the extra stuff Adobe puts into to it to enable a prepress work flow in their own format will have been swearing at the current method.
I saw multipage support on the todo list. Would be a nice start for better pdf support. CMYK is another one of the desires related to that. But even then I would really suggest making SAVE only save to Inkscape native and get the rest where it belongs in the export formats with their limited support. I haven't worked in print for quite some time now, but used to dabble around with postscript fill rasters quite a lot to get different effects on similar ink percentages. When using 2 colour print and a varnish, you could create really nice effects with that. None of such information would be maintained in an Inkscape PS export either.
They are lossy export filters. Hence they should be in the export menu. The work flow in Inkscape is not ideal when you destroy half the info with a program that seems to claim to save all those file types as if it where native. Whether you put opening a file in the import or open dialog doesn't matter all that much as long as it is clear that the output file is an export or information gets lost by saving it as InkSVG.
While following the discussion on SVG2 it became clear that the focus there is web content and for that Inkscape pretty much does everything you'd desire. However, as it turns out Inkscape is a really good and useful vector editor that has found its way into the prepress world and others despite its shortcomings in those fields, I would really like to see a work flow philosophy that reflects those shortcomings for the casual and first time users to prevent them from totally screwing up their work. Otherwise they will be disappointed. I guess that is what drove the Gimp to separate it as well.
No Johan,.. it's not okay. Its like boiled and poached eggs. Similar results but different using the same tools and ingredients. But the end result differs through the method.
Jelle
Only a question about export PNG. In previous versions, if the export has no extension or is diferent to PNG, apend ".png" it to the end of the exported image. But now, we can export without extension or overwrite other files like current SVG whith the png info.
To me is a big problem. Never read about and not sure if this subject is discussed.
Regards, Jabier.
El vie, 17-04-2015 a las 03:08 +0800, Jelle Mulder escribió:
Hi all,
I think Gez posted the most compelling reason to get rid of pdf and the like in the save as dialog. Inkscape will happily destroy the multipage document with prepress ready infromation with its own export file. If all you do with it is edit an image that doesn't need to go to print that's fine, but I guess those that are accustomed to using Adobe software with its extended pdf files that enable editing it with retaining all the extra stuff Adobe puts into to it to enable a prepress work flow in their own format will have been swearing at the current method.
I saw multipage support on the todo list. Would be a nice start for better pdf support. CMYK is another one of the desires related to that. But even then I would really suggest making SAVE only save to Inkscape native and get the rest where it belongs in the export formats with their limited support. I haven't worked in print for quite some time now, but used to dabble around with postscript fill rasters quite a lot to get different effects on similar ink percentages. When using 2 colour print and a varnish, you could create really nice effects with that. None of such information would be maintained in an Inkscape PS export either.
They are lossy export filters. Hence they should be in the export menu. The work flow in Inkscape is not ideal when you destroy half the info with a program that seems to claim to save all those file types as if it where native. Whether you put opening a file in the import or open dialog doesn't matter all that much as long as it is clear that the output file is an export or information gets lost by saving it as InkSVG.
While following the discussion on SVG2 it became clear that the focus there is web content and for that Inkscape pretty much does everything you'd desire. However, as it turns out Inkscape is a really good and useful vector editor that has found its way into the prepress world and others despite its shortcomings in those fields, I would really like to see a work flow philosophy that reflects those shortcomings for the casual and first time users to prevent them from totally screwing up their work. Otherwise they will be disappointed. I guess that is what drove the Gimp to separate it as well.
No Johan,.. it's not okay. Its like boiled and poached eggs. Similar results but different using the same tools and ingredients. But the end result differs through the method.
Jelle
BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT Develop your own process in accordance with the BPMN 2 standard Learn Process modeling best practices with Bonita BPM through live exercises http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_ source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
On 16-4-2015 21:08, Jelle Mulder wrote:
No Johan,.. it's not okay. Its like boiled and poached eggs. Similar results but different using the same tools and ingredients. But the end result differs through the method.
I just mentioned that the open PDF/edit/save thing works for me, and has been useful occasionally in the past. But you know, go ahead, fire away. I already left Inkscape development.
I'd appreciate it if people stop "contributing" opinions/arguments only, for the sake of the few developers and _actual_ contributors left. They are unfortunately very silent in many of the discussions on this devel (!!!) list, but I hope it's clear to everybody that it's foremost *their* program. Why would someone keep contributing if he does not even like the program?
- Johan
"As open source started booming, more people joined. Opinionated people. People who listened to the "we welcome everyone!" message and felt that their opinion could be their primary contribution. For some, they felt showing up at the gig gave them the right to dictate what the band played." http://opensource.com/life/15/3/how-to-fire-community-members
On Thu, Apr 16, 2015 at 11:36 PM, Johan Engelen wrote:
I'd appreciate it if people stop "contributing" opinions/arguments only
In the traditional UX design process, user interaction experts interview actual users to figure out what needs doing, and that happens offline. There is no traditional UX design process in Inkscape, so if you expect Inkscape to have a sensible solution that takes into consideration a variety of workflows, you'll have to somehow deal with the fact that this list will be plagued by opinionated users from time to time.
Please correct me if I'm wrong, but there is no final decision on saving/exporting in Inkscape, so what else do you expect people to contribute with? Patches that won't be accepted? I'm just trying to make a sense of what you are saying...
Alex
On Thu, Apr 16, 2015 at 10:08 PM, Jelle Mulder wrote:
While following the discussion on SVG2 it became clear that the focus there is web content
???
SVG2 is featuring uncalibrated CMYK colors, LAB, and ICC named colors (which opens a possibility to support spot colors at last).
Alex
participants (4)
-
Alexandre Prokoudine -
Jabiertxo Arraiza Cenoz -
Jelle Mulder -
Johan Engelen