Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

actual version of gears-dev.inx does not show menu-item under rendering #27

Open
StefanL38 opened this issue Sep 3, 2015 · 7 comments

Comments

@StefanL38
Copy link

Hi,

I downloaded the two files gears-dev.inx and gears-dev.py to my computer
But in the menu extensions-render the menu-item gear-dev is not shown.
So I did a rollback to a earlier version of gear-dev but then I got the error from issue 24
AttributeError: 'module' object has no attribute 'uutounit'

If I combined the new fixed gears-dev.py with the old gears-dev.inx I got another error
something about wrong doctype html don't remember exactly

So finally I googled for the error AttributeError: 'module' object has no attribute 'uutounit'
and did the fix manually again.

Anyway the written instruction
"Copy the two files gears-dev.inx and gears-dev.py to your computer:"
does not work. the file gears-dev.inx need to be revised to create a menu-item "dev-gear" in InkScape

And the instructions should be improved by adding with something like
"a new menu-Item named "Gear-Dev" will show up under
extensions-render

It is very important to give a description of the WHOLE click-path where to find the function.
Imagine a new user knowing almost nothing about InkScape and the instructions just say

click on "dev-gear". The new user will not know where to find it.

best regards

Stefan

@Neon22
Copy link
Contributor

Neon22 commented Sep 3, 2015

It sounds like you have tried to install it in 0.48. This version is designed for 0.91. Released January 2015.

@StefanL38
Copy link
Author

No.
I installed InkScape 0.91 and then copied the two files gears-dev.inx and gears-dev.py into
folder C:\Program Files\Inkscape\share\extensions and then I got the things described in the issue

I also made a content-comparison of the old and new file gears-dev.inx

the working versions begins with

<_name>Gear-dev org.ekips.filter.gears-dev gears-dev.py inkex.py 24 1.0 <_option value="MM">Metric Module <_option value="CP">Circular Pitch <_option value="DP">Diametral Pitch

the actual downloadable version downloadable from https://github.com/jnweiger/inkscape-gears-dev/blob/master/gears-dev.inx

begins

<title>inkscape-gears-dev/gears-dev.inx at master · jnweiger/inkscape-gears-dev</title>
<link rel="search" type="application/opensearchdescription+xml" href="/opensearch.xml" title="GitHub">
<link rel="fluid-icon" href="https://github.com/fluidicon.png" title="GitHub">

I'm pretty sure the actual downloadable file is corrupted.

best regards

Stefan

@Neon22
Copy link
Contributor

Neon22 commented Sep 3, 2015

You have not downloaded the file correctly - you are looking at the html of the encapsulating page.
There are many ways to download from Github. Personally I L-click on the filename until I can see the program or text file exposed on screen. Then I R-click on the RAW button and "save link to file". (but your Browser may offer a different name for this operatoin)
When opened the file looks exactly like it was presented in the Github HTML document.
Specifically the python file wil start with "#! /usr/bin/env python"

@StefanL38
Copy link
Author

Hi Neon22,

thank you very much for explaining. Now I got the actual version working.

Gitub seems to be for coding-nerds.
What's the advantage of showing links with filenames that look like downloadable files
but are html-encapsulated? This is an uncommon way to present downloads.

I'm used to start reading from the top-left corner.
So I didn't recognized that there is a download-zip-file button in the bottom-right corner.

best regards

Stefan

@Neon22
Copy link
Contributor

Neon22 commented Sep 3, 2015

no problem Stefan - yes its def for coding nerds :) good luck with the extension

@jnweiger
Copy link
Owner

jnweiger commented Dec 3, 2015

This is a very common user error.
We should change the documentation to always say download the zip file, then extract.
That seems to be safest.

Anybody out there do the pull request?

@Neon22
Copy link
Contributor

Neon22 commented Dec 4, 2015

submitted

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants