pdf import again: poppler native vs. poppler cairo
by the Adib
Hello All,
as the problem is still there I would propose following intermediate solution:
currently in the codebasis there is also an pdf import via
poppler-cairo. This one is disabled.
I would like to enable this as an additional pdf import possibility.
We have to decide later when it comes to the release which one to
integrate into the release.
so we can test in parallel the two options.
we have a big tester basis (compared to separate launchpad branch)
we get the possibility to switch to an tested poppler-internals
independent solution (while using poppler)
I there is no big NONO I will go forward and enable this within the next days.
attached the patch that is needed for this (tested on windows, should
work on Linux)
regards,
Adib.
8 years, 10 months
Re: [Inkscape-devel] OCAL Dialog Redesign
by Andrew
Hi Guys,
So I have been doing a lot of work on the Import from OCAL dialog and I
have finally finished! I was wondering whether I could get some testing,
especially on some different platforms with different internet connections.
All you need to do is get my branch using:
bzr branch lp:~and471/inkscape/ocal-dialog-improvements
And then compile as usual. You will find the dialog in File > Import
Clip Art
So yeah, basically I want a lot of testing, to iron out any errors that
I have missed and also feedback on the stuff I have done. Then once that
is all done, I shall propose for merging into trunk.
A list of changes is below, as well as a link to screenshots of the new
dialog.
Thanks!
--
Andrew
Screenshots:
http://wiki.inkscape.org/wiki/index.php/OCAL_Dialog_Re-Design
== Changes ==
* UI Redesign (which includes)
- Altered the padding and packing of all widgets
- Added search entry with clear and search icons
- Added OCAL Logo overlay
- Put descriptions inline in list
- New preview widget that shows extra metadata
- New status widget to notify on errors/success etc.
- Dialog is now persistent (retains state)
- Better messages for the user
- Changed title/menuitem to 'Import Clip Art'
* Backend stuff (which includes)
- Use new GFile API instead of depreciated GNOMEVFS
- Use async methods so the UI isn't blocked
- Use smaller, thumbnail images in the preview widget (save on
bandwidth and increase speed)
- Implement cancelling of operations
- Put downloaded resources into one directory, from which we can
use later
- Big cleanup in terms of code
9 years, 3 months
Curve sketching--Cornucopia
by Ilya Baran
Hi,
A while ago I asked the Inkscape list whether there was interest in an
implementation of my curve sketching algorithm (see the thread at
http://sourceforge.net/mailarchive/message.php?msg_id=24902605).
There seemed to be interest and I wrote a cleaner (and much faster)
version, although this took longer than I anticipated. There are
still a bunch of improvements possible, but at this point it's quite
usable. The code and a windows installer for a demo binary are
available at http://code.google.com/p/cornucopia-lib/ and there's some
documentation.
I am completely unfamiliar with Inkscape's codebase, so the
integration would need to be done by one of the Inkscape devs. As a
proof-of-concept, however, I wrote a very crude replacement of the
bezier_fit_cubic_r call with a call to Cornucopia in the pencil tool
(patch attached--of course, you have to build and link to Cornucopia
to try it). For the real thing, I'd need to find a better mapping
from the "smoothness" slider in Inkscape to my myriad of parameters.
Is someone interested in working on this? I would, of course, help in
what way I can (although I'm pretty busy these days and my response
latency may be high occasionally).
Thanks,
-Ilya
9 years, 12 months
Re: [Inkscape-devel] Curve sketching--Cornucopia
by Ilya Baran
Hi,
Ok, I understand about LPE's now.
On Mon, Apr 25, 2011 at 3:40 PM, Johan Engelen
<jbc.engelen@...2592...> wrote:
> On 25-4-2011 10:25, Ilya Baran wrote:
> > ...
> > For the real thing, I'd need to find a better mapping
>> from the "smoothness" slider in Inkscape to my myriad of parameters.
>
> What would be the minimal amount of parameters for your fitting? If we
> decide to replace the current fitting with yours, it is easy to add
> parameters to the toolbar.
My implementation essentially exposes almost every magic constant in
every algorithm as a parameter, so there are 30 or so. There are
parameters that specify what kinds of primitives (arcs, lines,
clothoids) and transitions are preferred, and the rest mostly tradeoff
accuracy vs. simplicity and quality vs. performance.
For a real UI, therefore, I think that one or two sliders (the quality
vs. performance slider is probably optional) and some buttons for
choosing the curve type should be sufficient.
Thanks,
-Ilya
> Ciao,
> Johan
>
> ------------------------------------------------------------------------------
> Fulfilling the Lean Software Promise
> Lean software platforms are now widely adopted and the benefits have been
> demonstrated beyond question. Learn why your peers are replacing JEE
> containers with lightweight application servers - and what you can gain
> from the move. http://p.sf.net/sfu/vmware-sfemails
> _______________________________________________
> Inkscape-devel mailing list
> Inkscape-devel(a)lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/inkscape-devel
>
9 years, 12 months
disabled viewbox attribute for symbols when using cairo export
by Christopher Dyck
Hi,
I have a question about the handling or not-handling of the viewbox
attribute in symbols when using cairo export.
I tried to export a map from openstreetmap to pdf and got
http://s1.directupload.net/file/d/2504/thghng78_png.htm as result.
So I took a look in the code and stumbled over the following lines,
which disable the viewbox attribute for symbols completely.
---- src/extension/internal/cairo-renderer.cpp #391
// apply viewbox if set
if (0 /*symbol->viewBox_set*/) {
-----
Perhaps this is related to this fixme comments
--- src/sp-symbol.cpp #144
/* fixme: We have to take original item affine into account */
/* fixme: Think (Lauris) */
----
So my question is: Is this still needed or is it possible to activate
symbols viewboxes again?
9 years, 12 months
Cairo branch builds on win32, what next?
by Jasper van de Gronde
I just committed a patch that completely removes the win32.cpp/.h that
were causing build problems (and apparently weren't used anymore). Apart
from ripping out some printing related code that wasn't used anymore
this also removed the is_os_wide function. Although this function is in
principle unrelated and could have been kept, I decided to get rid of
that as well. This means that any remaining support for Win9x/ME that
depended on this is now gone (as far as know we didn't support those
windows versions anymore anyway, so it was just extra baggage).
So, what next? I might have encountered a pretty serious regression in
text rendering, but I haven't looked deeper into that yet. (And it might
be known already or it might be something specific to my set up.)
10 years
Usability development help for Inkscape available
by Aslak Karsi
Hello
We are a group of five students from Finland, studying at University of
Oulu, Department of Information Processing Science. We are currently working
on a project assignment to offer help in usability development for an open
source software project of our choice.
Past few weeks we have been familiarizing ourselves with Inkscape and its
community and now we would like to offer our work resources for your use.
We have already figured out a few ideas of what we could do for the Inkscape
project:
* Heuristic evaluation
* Usability testing
* Prioritization of usability related bugs on the buglist
To produce as useful results as possible, we would like to hear your ideas.
How do you feel about the tasks suggested? Is there some specific part of
the software we should focus on? Any ideas and feedback at this point would
be greatly appreciated.
Project leader Aslak Karsi
Marko Arffman
Matias Patosalmi
Jouni Rissanen
Matti Siipola
10 years
