We are good to go!
by Joshua A. Andler
Hey all,
I made the first commit on LP after our trunk branch was established and
it went smoothly. So, everyone, feel free to go to town!
As a side thought, since 0.48 will be maintained for a bit while 0.49 is
under development. What do people think about our use of LP and how we
use Fix Released rather than Fix Committed... are people game to perhaps
try using Fix Committed (and target them for 0.48 when doing so) for
this cycle? If we properly use committed and mark where it will be
available, we can then just script it to change to released when it
really is (I think it will be nicer for users). Just a thought.
Cheers,
Josh
13 years, 8 months
Video markup
by Александр Горбань
Hi,
I'm thinking about creating tool to markup video (select areas containing
objects, add tags) for my computer vision algorithms (head tracking, human
detection and the like). The core functions of such tool: split video into
separate frames, possibility to markup some object by drawing rectangles,
circles or other closed contours objects on each frame, play markuped video,
interpolate unmarked object coordinates between frames.
It is seemed to me, that within inkscape it can be done in the following
way:
1. Input extension that "convert" video frames into inkscape layers
2. Toolbar with play/stop buttons that toggle layer visibility to simulate
video playback
if you catch the idea, can you tell how difficult to implement the tool on
inkscape basis? If it isn't very hard task what is the best way to do it:
creating extension or creating patch?
---
Best regards,
Alexander Gorban
13 years, 8 months
Re: [Inkscape-devel] Specification: Improved image properties dialog (0.48)
by Krzysztof Kosiński
W dniu 23 października 2009 17:18 użytkownik Jon A. Cruz
<jon@...18...> napisał:
> You are thinking of *your* intuition. There is roughly half the user
> population who's intuition is the *opposite* of yours.
You say that 50% of people prefer linking and 50% prefer embedding. I
am certain this is not true. Most people expect the image to stay in
place. When you send an email attachment, it is not a magical link to
the data on your computer. When you paste an image into a Word / ODT
file, it is not a link to that file on your hard disk. When you paste
SVG elements from another document, they do not magically become a
link to that second document.
> However... I don't think the "Therefore" actually quite matches. Among other
> issues, a drag-n-drop is actually a complex paste operation. So I think the
> code is doing a few things you don't expect.
Drag and drop is currently not related to pasting, because drag and
drop is implemented in src/interface.cpp, and pasting in
src/ui/clipboard.cpp. They don't use the same code path. In fact the
import code is simpler, because imported / dragged items are put into
a group. Not sure if that's what you meant.
> Also for the import case, embedding will break things for many, many users.
> We've looked at that a few times.
For who, and in what cases? You sometimes say that a proposed solution
will cause 'important issues for many users', but don't say what those
issues actually are.
> The good solution is to create a "media manager" that handles things like
> images, linked css files, ICC profile files, etc.
This would be great to have, along with UI improvements to enable
using common styles. The image links manager proposed in this thread
is a good start, and could be extended to Still, I think this is
orthogonal to what the defaults are.
> Things can then be worked
> out with the UI and perhaps a "Publish" menu/command that does things a bit
> more explicitly than "save as" or "export".
I think that "Publish" is a stupidity cloned from Corel Draw. Why
should saving a PDF be completely different from saving any other
file? Moreover the name is misleading: you are actually not
'publishing' anything in the sense of showing it to the outside world.
You are only saving a file. A better name is "save standalone
document" or something like this, but I don't see a difference between
this and Export.
Regards, Krzysztof
13 years, 8 months
Re: [Inkscape-devel] [Inkscape-user] Slow performance on 4.5 MB file [SOLVED]
by Jasper van de Gronde
And please be sure to file a bug/feature request at
http://bugs.launchpad.net/inkscape/
In the end there will obviously always be cases where Inkscape is too
slow, but Inkscape could most definitely be faster in some cases. And
just locking/unlocking the layer should (from an intuitive standpoint)
NOT cause such a big pause.
Dave M G wrote:
> Donn,
>
> Thank you for responding.
>
>> I have long moaned that "Nodes mean slow" :( I have a fast machine and 2gigs
>> of RAM. It makes no difference. I think it's all the looping through those long
>> lists of nodes....
>>
>> You are doomed. Unless you can simplify or chop-up your comic page into frames
>> and assemble them later in Gimp.
>
> Okay. While it's a little disappointing that there isn't a way to
> optimize the file for better performance, it's good to know that at
> least I'm not doing something wrong.
>
> I'll export the paths into a PNG and handle the colouring in Photoshop
> or GIMP. It means committing to rasterizing the images sooner in my
> process than I had hoped, but hey, life is full of compromises.
>
13 years, 9 months
Re: [Inkscape-devel] [bug tracker] Guideslines for tags?
by unknown＠example.com
-----Original Message-----
From: suv@...2204... [mailto:suv@...2204...] On Behalf Of ~suv
Sent: zondag 25 oktober 2009 21:35
To: Engelen, J.B.C. (Johan)
Subject: Re: [Inkscape-devel] [bug tracker] Guideslines for tags?
On 25/10/09 21:11, J.B.C.Engelen@...1578... wrote:
> From: Maximilian Albert [mailto:maximilian.albert@...1439...]
>> 2009/10/25 Pajarico <pajarico@...400...>:
>>> I started using the tag 'cli' for command line problems.
>> Wouldn't it be better to use a more descriptive name?
>> Frankly, if I hadn't read this email I'd have no clue what it is
>> supposed to mean.
>
> I agree with Max. Just write it out "command line", like we do with
> the other tags.
> (I read it as "clear interrupts" assembly ;)
'command-line' or 'commandline' - Launchpad doesn't allow spaces in
tags, and 'command' and 'line' don't make much sense as separate tags
imho.
~suv
13 years, 9 months
Re: [Inkscape-devel] URGENT: Please update Mac OS X install instructions in the tarball !
by ~suv
On 30/11/09 13:24, Wolf Drechsel wrote:
>>> I am very grateful that a lot of people invested lots of time in the
>>> wonderful packaging/macosx/osx-build.sh script.
>>>
>>> PLEASE, add a few lines to the READMEs - or create a distinguished
>>> "README_Mac_OS_X" to make clear, that the install procedure on a Mac
>>> is a different one.
>>
>> Could you propose what should be added to the README. I think it's a
>> good idea to update it, but I'm afraid that I would write something
>> incorrect if I tried as I have no experience on OSX.
>
> I'll be happy to give it a try - could friend ~suv have a look on it in
> order to avoid greater portions of nonsense please ?
I am not very comfortable with the proposed changes by Wolf:
a) README
why only adding hints for OS X users? There are other platforms with
special build tools (e.g. btool for win32) and - judging from the list
of wiki pages about compilation on different linux platforms -
deviations/adaptations from the generic 'configure/make/make install'
routine are more common and not limited to Mac OS X.
b) INSTALL
again - why adding only one of the sub-pages from the wiki which is
already linked from the top wiki page about compilation and not the
others as well? Personally I'd keep it as it is. If you need more
information, the instructions are clear: read the wiki pages.
Alternative proposal
1) In the README file add a section to or after the description of the
generic installation, mentioning the wiki pages for more information
about platform specific issues.
2) In 'packaging/macosx' and 'packaging/win32' add new README files
containing either a summary or a copy of the platform specific wiki page
about building and packaging.
OTOH a 'packaging/macosx/README' could be as short as
1) please read the wiki page about compiling Inkscape on OS X:
<http://wiki.inkscape.org/wiki/index.php/CompilingMacOsX>
2) consider additional information about
MacPorts installation: <http://www.macports.org/install.php>
using MacPorts: <http://guide.macports.org/#using>
3) run './osx-build.sh help' for an overview of the options available
to configure, build and package Inkscape on OS X
~suv
appending fullquote since Wolf's mail didn't make it to the list:
>>> I am very grateful that a lot of people invested lots of time in the
>>> wonderful packaging/macosx/osx-build.sh script.
>>>
>>> PLEASE, add a few lines to the READMEs - or create a distinguished
>>> "README_Mac_OS_X" to make clear, that the install procedure on a Mac
>>> is a different one.
>>
>> Could you propose what should be added to the README. I think it's a
>> good idea to update it, but I'm afraid that I would write something
>> incorrect if I tried as I have no experience on OSX.
>
> I'll be happy to give it a try - could friend ~suv have a look on it in order to avoid greater portions of nonsense please ?
>
> I suggest to change this chapter of the README:
>
>> Inkscape uses the standard procedure for compilation and installation:
>>
>> ./configure
>> make
>> make install
>>
>> If a "./configure" file is not present, you can create it by running
>> the "./autogen.sh" command, which calls in turn a number of other
>> programs such as automake and autoconf. See INSTALL for more
>> details.
>
> into:
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++
> Installation for *nixes (Mac OS X users please have a look at the end of the file):
> ==========================================================
>
> Inkscape uses the standard procedure for compilation and installation:
>
> ./configure
> make
> make install
>
> If a "./configure" file is not present, you can create it by running
> the "./autogen.sh" command, which calls in turn a number of other
> programs such as automake and autoconf. See INSTALL for more
> details.
> ++++++++++++++++++++++++++++++++++++++++++++++++++++
>
>
> At end of file:
> ++++++++++++++++++++++++++++++++++++++++++++++++++++
> Installation for Mac OS X users
> =======================
>
> We try to keep the Wiki pages on compiling inkscape up-to-date and comprehensive. It is here:
>
> http://wiki.inkscape.org/wiki/index.php/CompilingMacOsX
>
> For a brief overlook:
> We suggest to use macports (http://macports.org) in order to achieve all the necessary components and libraries. Than there is a mighty tool called "osx-build.sh" in the packaging/macosx directory of the unpacked tarball. This script will do most of the work for you.
> ++++++++++++++++++++++++++++++++++++++++++++++++++++
>
>
> In the INSTALL file change:
>
>> Basic Installation
>> ==================
>>
>> If you have problems compiling Inkscape, then see
>> http://wiki.inkscape.org/wiki/index.php/CompilingInkscape .
>>
>> The remainder of this file gives generic installation instructions.
>
> into
>
>>> Basic Installation for *nixes - Mac OS X users please have a look at the README
>>> ===========================================================
>>>
>>> If you have problems compiling Inkscape, then see
>>> http://wiki.inkscape.org/wiki/index.php/CompilingInkscape
>>>
>>> if you are a Mac OS X user, please dont read on, keep to the wiki pages instead:
>>> http://wiki.inkscape.org/wiki/index.php/CompilingMacOsX
>>>
>>> The remainder of this file gives generic installation instructions.
>>> …
>
>
>
>
13 years, 9 months
Spray Tool
by Joshua A. Andler
Hey All,
Would anyone be against the Spray Tool that the high school students
made being merged into trunk? It definitely needs some love (however, it
is really awesome too), but I don't think it can get the needed
attention until more people use it and can comment on how to improve it.
Cheers,
Josh
13 years, 9 months
Inkscape 0.47 is released!
by Joshua A. Andler
Greeting to the community,
After over a year of intensive development and refactoring, Inkscape
0.47 is out. This version of the SVG-based vector graphics editor brings
improved performance and tons of new features, some of which are as
follows: Timed autosave, Spiro splines, Auto-smooth nodes, Eraser tool,
New modes in Tweak tool, Snapping toolbar & greater snapping abilities,
New Live Path Effects (including Envelope), A huge collection of preset
filters, New cairo-based PS and EPS export, Spell checker, Many new
extensions, Optimized SVG code options, and much more. Additionally, it
would be wrong to not mention the hundreds of bug fixes as well. Check
out the full release notes for more information about what has changed,
enjoy the screenshots, or just jump right to downloading your package
for Windows, Linux or Mac OS X.
Release Notes:
http://wiki.inkscape.org/wiki/index.php/ReleaseNotes047
Downloads:
http://inkscape.org/download/
Cheers,
Josh
P.S. Let the PR blitz begin!
13 years, 9 months
Should other repositories move to Bazaar/LP?
by Ted Gould
Well, that's the question. Things like webpage and others. I have no
opinion as I rarely edit them, but I thought I'd throw this out there
while I still remember all the deep magic involved with converting
things ;)
--Ted
13 years, 9 months
