extensions usability
by unknown＠example.com
We need to rethink this approach to warning about unloaded
extensions. It seems to be causing a LOT of confusion amongst our
user community, of which the below is representative.
At the very least the dialog needs some text explaining the
implications for the users so they don't jump to the conclusion
that Inkscape is broken.
----- Forwarded message from "Robert C. Smith" <rcsthrax@...106...>
-----
Date: Wed, 09 Mar 2005 13:51:27 -0700
From: "Robert C. Smith" <rcsthrax@...106...>
Reply-To: inkscape-user(a)lists.sourceforge.net
Subject: Re: [Inkscape-user] autopackage
To: inkscape-user(a)lists.sourceforge.net
"One or more extensions failed to load The failed
extensions have been skipped. Inkscape will continue to
run normally but those extensions will be unavailable."
Wayne...I plan to run dual-boot but had problems loading
Mandrake which I am investigating. The above shows
that the Windows load of Inkscape HAS PROBLEMS and
that this isn't just an open-source distribution issue. I
would appreciate that this fact be recognized as
discussion proceeds. I am new to open-source except for
the Gimp. What is an "extension?" What are the
implications of lacking an extension? What is new in .41
which would provoke this error message? (The situation
is independent of service packs.) ....RCs
On 9 Mar 2005 at 9:37, wayne wrote:
> On Wednesday 09 March 2005 07:03 am, oisin feeley wrote:
> > On Tue, 8 Mar 2005 18:10:46 -1000, wayne <iw@...131...> wrote:
> > > Just installed inkscape 0.41 with autopackage. When I open it,
I
> > > get a message saying that one or more extensions failed to
load.
> >
> > I get that message too and it doesn't appear to affect running
> > inkscape-0.41, so you may be able to discount it from your
> > debugging. Examining the file ~/.inkscape/extension-errors.log
shows
> > the following.
> >
> > Extension "Sketch Input" failed to load because a dependency was
not
> > met. Dependency::
> > type: executable
> > location: path
> > string: skconvert
> >
> > Extension "Postscript Input" failed to load because a dependency
was
> > not met. Dependency::
> > type: extension
> > location: path
> > string: org.inkscape.input.sk
> >
> > Extension "Postscript Input" failed to load because a dependency
was
> > not met. Dependency::
> > type: executable
> > location: path
> > string: pstoedit
> >
> > Extension "AI Output" failed to load because a dependency was
not
> > met. Dependency::
> > type: executable
> > location: path
> > string: pstoedit
> > Extension "EPS Input" failed to load because a dependency was
not
> > met. Dependency::
> > type: extension
> > location: path
> > string: org.inkscape.input.ps
> >
> > Oisin
>
> 0.4.1 doesn't run at all after the "one or more extensions failed
to
> load" error window. I end up with the command line error message
> about:
>
> SCIM: im_module_init
> > > free(): invalid pointer 0x9453670!
> > > free(): invalid pointer 0x9453650!
>
> Segmentation fault (core dumped)
>
> Wayne
>
>
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real
> users. Discover which products truly live up to the hype. Start
> reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> _______________________________________________ Inkscape-user
mailing
> list Inkscape-user(a)lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/inkscape-user
----- End forwarded message -----
18 years, 2 months
New GUI projects
by Bryce Harrington
Here are some areas where help is needed in the new gui code. If you'd
like to help, pick anything off this list that looks interesting and
have at it.
* Transformation dialog. There's some bits of code that are currently
commented out because they depended on inkscape internals that weren't
available while inkscape_gtkmm was separate. With the code
integrated, these can now be hooked up. Uncomment something,
recompile, and fix any errors that occur.
* src/ui/dialog/dialog.cpp. Search for 'TODO'. A lot of little
leftover things that need to be reviewed/implemented/fixed. Pick
something that looks interesting.
* Hook in the canvas. I assume there's something in the existing
codebase we can just link up to, but don't know what that'd be.
In any case, there's a stub for it in src/application/editor-impl.cpp
called initSvgCanvas().
* Implement preferences loading/saving.
In src/application/application.cpp, implement the functions
Application::loadPreferences() and Application::savePreferences.
For reference, the current preferences code is in inkscape.cpp.
* Commandline options
Implement code that takes argc,argv, parses it via popt, and stores it
in a member of Inkscape::Application::Application in
src/application/application.cpp. If you've not used popt before,
here's a handy PDF on it: http://www.rpm.org/local/popt.pdf
The current option handling code is in main.cpp, but is kind of
hackish so feel free to redesign it a bit.
* Finish (re-)implementation of Inkscape Preferences dialog. Car
Hetherington did much of the work of gtkmmifying the preferences
dialog, but it's diverged from mainline.
Also, there was some thought put into reimplementing it, so if you
feel ambitious, go ahead and rework the dialog to fit the new design.
* Gtkmmify the Statusbar.
This should hook in to src/application/editor-impl.cpp in the
initStatusbar() routine.
The current code for the statusbar is in desktop.cpp. Start by
looking at SPDesktop::_set_status_message, then search on 'statusbar'
and 'select_status'.
I *think* what is needed is to implement a new class
Inkscape::UI::Widget::Statusbar that subclasses Gtk::Statusbar and
adds the Inkscape-specific functionality we need, but that's just a
rough guess; I haven't put much thought into it so if you know a
better approach, go for it.
The above tasks are what we need most desperately right now, but I think
if we can get these items done, that will move us a *huge* step
forward. I'd love the help, and if you have any questions on any of it,
let me know.
Bryce
18 years, 2 months
Gtkmm updates
by Bryce Harrington
I've just checked in a few improvements to the gtkmm code:
* Added support for share/ui to path-prefix.h and removed all
hardcoded paths in the gtkmm code. You should now be able to run
inkscape --new-gui with inkscape installed in either /usr or
/usr/local without issue.
* Integrated the new Transformation dialog. Looks much like the
original one, but is implemented in gtkmm instead of gtk. This
dialog is intended to serve as a complete working example of a
gtkmmified dialog.
* Added a bunch of individual icons to share/icons/. This is a mix
of .svg and .xpms. This should probably be redone. We now prefer
having all icons as svg, and having all of the icons in 'icons.svg'
instead of as individual files. These files were done like this
simply because in the separated inkscape_gtkmm codebase we of
course did not have access to the inkscape renderer; now that the
code is integrated, it would be a good project for someone to
replace these temporary implementations with use of the inkscape
renderer.
Bryce
18 years, 2 months
Re: [Inkscape-devel] extensions usability
by Jose Hevia
> Ted Gould wrote:
> > Yes, I think the text needs to change -- but I think the dialog needs to
> > stay.
>
> I'd like to recommend disabling the dialog, at least until it's pretty
> common people will have most extensions.
Let me tell you a story:
I'm a inkscape user that eventually learned to use inkscape to make
vector drawings.
I use debian sid ,so I just made an update to apt-get.If you have used
it you know how easy is to upgrade +30 programs at once.I was working
hard until night for a deadline project so I just shut down the computer
and didn't use this computer for some days when finished.
Later ,I needed to open a SVG to work with and so it happened:
One or more extensions failed to load!!!
The failed extensions have been skipped...
What the hell? (#?!(%$·#!!!!!).Something is crashed,but what?,I open
inkscape from command line ,no indication.No help.Nada.Nil.Nothing.
Simply ,I don't know what an extension here means,I only recently read
the mailing list,and don't know.They are optional parts like extras or
fundamental part? It says:
[...]please refer to the error log located a[...]ooh, so it's an error.
(If it wasn't inkscape will start without pushing an (annoying) OK button.)
But it's strange ,I could use inkscape like I was used to and nothing
breaks (but beware ,don't trust, something is broken and could make lost
your important data).
I didn't unmarked "Show dialog on startup" because if something is
broken I don't want it to hide this fact.
No need to tell you that I didn't read
/home/xxx/.inkscape/extension-errors.log(or if I did don't remember),
and it took me some time to connect the general update with this
"crash".I thought it was inkscape having problems,then I notice
something different with the program,had a look to about dialog to see
that I just installed a new version.
Sorry for my behavior, if I had no others things to do I'd do better
Jose Hevia
18 years, 2 months
'using namespace' considered harmful
by MenTaLguY
Guys, I've been noticing a lot of usage of 'using namespace' starting to
creep into the codebase. With few exceptions, that's not a good
thing...
The reason is that as more classes get added to the imported namespace,
a class or function may eventually get added that conflicts with one in
your own namespace.
Depending on the exact nature of the conflict, it may not result in a
compile failure, but instead introduce subtle bugs into the compiled
code (e.g. if overload resolution picks the wrong function).
So, as a rule, please 'using' the individual classes or functions that
you actually need. Do NOT 'using' an entire namespace, and especially
DO NOT use any form of 'using' in the global scope of a header file --
that will pollute the namespace of every file that directly or
indirectly includes your header.
Current offenders:
(header files with inappropriate 'using's that MUST be fixed)
src/ui/dialog/align-and-distribute.h:using namespace
Inkscape::UI::Widget;
src/ui/dialog/document-preferences.h:using namespace
Inkscape::UI::Widget;
src/ui/dialog/export.h:using namespace Inkscape::UI::Widget;
src/ui/dialog/fill-and-stroke.h:using namespace Inkscape::UI::Widget;
src/ui/dialog/find.h:using namespace Inkscape::UI::Widget;
src/ui/dialog/inkscape-preferences.h:using namespace
Inkscape::UI::Widget;
src/ui/dialog/messages.h:using namespace Inkscape::UI::Widget;
src/ui/dialog/text-properties.h:using namespace Inkscape::UI::Widget;
src/ui/widget/unit-menu.h:using namespace Inkscape::Util;
(modules where individual 'using's would be better)
src/ui/dialog/inkscape-preferences.cpp:using namespace
Inkscape::UI::Widget;
src/ui/stock-items.cpp: using namespace Gtk::Stock;
src/application/editor-impl.cpp:using namespace Inkscape::UI;
src/application/editor-impl.cpp:using namespace Inkscape::UI::Widget;
src/io/ftos.cpp:using namespace std;
src/svg/ftos.cpp:using namespace std;
src/svg/itos.cpp:using namespace std;
Please fix, thanks.
-mental
18 years, 2 months
NEW: more gradient stuff
by bulia byak
Some improvements since the last announcement:
- All tools that were previously able to click to select (namely node,
shapes, and gradient tools), can now do Shift+click (add to selection)
and Alt+click (select under) exactly as the Selector tool.
- Dragging a gradient handle with Ctrl+Shift will scale the entire
linear or radial gradient around its center.
- Gradient handles for each gradient are connected by blue lines for
fill gradient and yellow lines for stroke gradient.
- In gradient tool, instead of dragging, you can double-click an
object to create a new gradient centered within the object's bounding
box. If you have several objects selected, or if your selected object
is behind another one, you can double-click with Ctrl to create
gradients on selected object(s) without changing selection.
- The selected gradient handle will intercept any color/opacity
setting commands and apply them to the corresponding stop(s) of its
gradient(s). This means that at least two-stop gradients can be
completely edited without ever opening the Gradient Editor dialog. In
particular, you can use these methods to change the color of the
selected handle:
+ Dropper tool (for example, to blend a radial gradient onto
background, select its outer handle and pick the background color with
the dropper).
+ Paste style (if the pasted style contains both fill and
stroke style, the stop will take the fill style).
+ Fill and stroke dialog [this does not quite work yet because
the dialog switches to gradient button and won't let you edit the
color]
- Double-clicking any gradient handle will open the Gradient Editor
dialog with that handle's gradient loaded and the corresponding stop
selected in the list.
- Before, the actual direction of the linear gradient was not always
perpendicular to the line connecting it handles if the bounding box of
the object was not a square. This is now fixed, though the fix only
works for new gradients that you create (i.e. gradients in old files
are not affected).
In other news, Richard Hughes' text layout rewrite appears to have
reduced the memory consumption on a text-heavy document by about 20%,
and rendering is faster by the same percentage. Hooray! :)
18 years, 2 months
Inkscape hangs; create rectangle, lock layer, select (root)
by xscd
Can someone confirm the following issue?
I'm using Inkscape 0.41 (Feb 10 2005), installed via Debian package, in
Debian with a dual-CPU Tyan motherboard.
I can reliably cause this hang by doing the following steps:
* launch Inkscape, and in the default new document, choose the rectangle
tool and draw a rectangle
* with the rectangle still selected and its handles visible, click the
"lock layer" icon on the status bar at the bottom of the window
* click the layer menu on the status bar next to the lock icon, and
select "(root)"
At this point Inkscape hangs and begins to monopolize the CPU(s).
Thank you,
Steve D, New Mexico, US
--
----------------------------------------------------------------
The difference between a violin and a viola is that a viola burns
longer. -Victor Borge
----------------------------------------------------------------
18 years, 2 months
gradient editing strangeness
by Johan Forsberg
Hello,
I *really* like the new "on canvas" gradient editing mode. However,
the gradient editing still has a feature that I find puzzling. Maybe
it's part of the svg standard or something and then it can't be
changed I suppose.
When editing a linear gradient, the line between the handles seems
like it should represent the actual direction of the gradient, but it
doesn't, exactly, unless the object has a perfectly square bounding
box. If the bounding box is rectangular, the only directions in which
the line and the direction of the gradient are the same are horizontal
and vertical; all other directions the gradient appears "sheared" ('m
not sure if this is the correct term); it is not parallel to the line.
(This is a bit hard to explain, perhaps I should make a screen shot to
demonstrate what I mean?)
Even more confusing is the fact that this behaviour does not change
even if the object is resized to have a square bounding box.
This sometimes makes it difficult, for example to fine-tune a gradient
on a very long and thin object, depending on its orientation.
I don't know it I should report this as a bug or if there is some
rational explanation :)
Cheers,
Johan Forsberg
18 years, 2 months
Absolute paths for website
by Jonathan Leighton
I've been working on a prototype of the Inkscape news using WordPress,
but am having trouble as URIs for archives come out like
"/archives/2005/01/". Due to the relative paths used on the website, the
browser then can't locate the stylesheets, and links point to the wrong
place on those pages.
So... does it matter if I change to absolute paths? (Which, IMHO, are
better anyway)
--
Jonathan Leighton aka. Turnip
http://turnipspatch.com/ | http://digital-proof.org/
18 years, 2 months
