Version 1.0 is only available as beta right now. As far as I understand (and you apparently discovered) the extensions aren't available yet. You'll need to use 0.92.4 (or other version) to get those extensions.
I'm not clear exactly which extension you mean. Probably the ones in the menu. But there are many others, 3rd party extensions, which you could install (into current stable version or earlier), if you want or need them.
That's a third-party extension. Visit the manufacturer's web page and install it, or notify them that their extension will soon cease to work with the next Inkscape version, if it is already installed, so they can update it in time for the release.
If you want to install a 3rd party extension, you need to install it in your user directory. Otherwise, you will lose them every time you install a new version of Inkscape.
Here's how to find the proper place. Edit menu > Preferences > System. Look on the right side at the file path indicated for User Extensions. That's where you need to paste the INX and PY files.
Note that on Windows, sometimes AppData is hidden. We can tell you how to find if you can't.
(Maren, I thought extensions weren't working in 1.0beta. Thought Martin was still working on them?)
Stock extensions work for the most part, everything that is being discovered is getting fixed quickly. Third-party extensions will probably cease to work, especially if their inx files list dependencies on modules that have been removed.
So....our couple of lists of 3rd party extensions (mine and the one in the wiki) will soon be mostly irrelevant? We will need to start a new list of only the ones that work with 1.0? Or find some way to indicate which ones work?
Some will probably still work, depending on how diligent the authors were (the more diligent, the less likely they'll work...). Some will be easy to fix. Some will be hard to fix.
I've been notifying extension authors whenever I stumbled over their extension, but it probably won't hurt to let their respective developers know more systematically. The best way to update the extensions quickly is to crowd-source the fixing.
We're going to have some extensions that work with 1.0 in the gallery (there are a couple already).
And in 1.1, Martin plans to add an 'extension manager', which requires extension authors to package their extension in a specific way, and upload it to a canonical Python package website. Those extensions can then be installed with a single click, and might be viewable in a gallery inside Inkscape.
Since we have a list of most of the 3rd party extensions, why don't we just send out a mass mail? I don't mind collecting the addresses, at least those that I can find. But I'm probably not the best one to compose a message (not knowing exactly what needs to be said, technically).
Or if there were some way to contact them via GitHub (most of them are there, anyway). I never have found a way to use GH to contact a repo owner. (unless it's new in the last couple of years)
Well anyway, if we work together on it, taking some kind of action, rather than "sorry folks...." would be better, in my opinion.
There is a problem we need to solve before we do that (GitHub users could potentially be contacted via the issues section of one of their projects, if they set one to be available).
We do not have any instructions that outline at least 80% of 'how to update your extension to 1.0'. Without that, though, personally, I'd feel embarrassed to tell people about this, but not to be able to provide a path about what to do next.
(I could maybe put together something very generic... I have updated two extensions already (or rather, mostly rewritten). There's a start on the Wiki, too.) But it might not be enough.
You mean that what an extension author needs to do to update the extension would not be obvious to them? I mean, they figured out how to create an extension by themselves in the first place.
Sigh. I think I'd rather see all the energy going into fixing the remaining bugs (the ones I've seen don't seem that bad) going into this issue. TONS of users have 3rd party extensions already installed, and they are going to break the moment they upgrade, with no fix available. Then they will have to downgrade to get their working extension back.
Actually, when I can't find contact info, and I'm already on github, and they have Issues available, could I already submit one? Or maybe I should just put this off for another week, until everything is ready?
You can start right away, if the chance opens up to you! The more time people have, the better.
As Martin has mentioned he had also opened some issues, and I have, too - so maybe you could check if there's one already, and add the missing info to it, if there is.
And.... You mean if there's an open issue in the extension's repo? This would primarily be on github. If there's already an issue, just add to it? Or start a new Issue, if there aren't any open?
I haven't found this yet, but I assume there could theoretically be more than one issue open. What would I do then?
Or are you talking about something in GL?
Edit
You're not suggesting I could edit extensions? Are you?
And yes, an open issue in the extension's issue tracker, if it has one. I think you know the answer to the adding / opening a new question. In case there are two issues, decide for yourself ;-)
You probably could do some edits, but I've not asked you to, or suggested that you should.
Using Inkscape with Cutters/Plotters Gcode extension in version 1.0
Inkscape.org
How do you install the Gcode extension in inkscape 1.0 ?
There's no extension library, and creating one makes no difference.
Regards, Kim
Welcome to the forum!
Version 1.0 is only available as beta right now. As far as I understand (and you apparently discovered) the extensions aren't available yet. You'll need to use 0.92.4 (or other version) to get those extensions.
I'm not clear exactly which extension you mean. Probably the ones in the menu. But there are many others, 3rd party extensions, which you could install (into current stable version or earlier), if you want or need them.
The GCodetools are included with Inkscape 1.0(beta).
I'm not sure which extension you are missing.
I miss the Jtec laser extension
Regards, Kim
That's a third-party extension. Visit the manufacturer's web page and install it, or notify them that their extension will soon cease to work with the next Inkscape version, if it is already installed, so they can update it in time for the release.
If you want to install a 3rd party extension, you need to install it in your user directory. Otherwise, you will lose them every time you install a new version of Inkscape.
Here's how to find the proper place. Edit menu > Preferences > System. Look on the right side at the file path indicated for User Extensions. That's where you need to paste the INX and PY files.
Note that on Windows, sometimes AppData is hidden. We can tell you how to find if you can't.
(Maren, I thought extensions weren't working in 1.0beta. Thought Martin was still working on them?)
Stock extensions work for the most part, everything that is being discovered is getting fixed quickly. Third-party extensions will probably cease to work, especially if their inx files list dependencies on modules that have been removed.
So....our couple of lists of 3rd party extensions (mine and the one in the wiki) will soon be mostly irrelevant? We will need to start a new list of only the ones that work with 1.0? Or find some way to indicate which ones work?
Some will probably still work, depending on how diligent the authors were (the more diligent, the less likely they'll work...). Some will be easy to fix. Some will be hard to fix.
I've been notifying extension authors whenever I stumbled over their extension, but it probably won't hurt to let their respective developers know more systematically. The best way to update the extensions quickly is to crowd-source the fixing.
We're going to have some extensions that work with 1.0 in the gallery (there are a couple already).
And in 1.1, Martin plans to add an 'extension manager', which requires extension authors to package their extension in a specific way, and upload it to a canonical Python package website. Those extensions can then be installed with a single click, and might be viewable in a gallery inside Inkscape.
Since we have a list of most of the 3rd party extensions, why don't we just send out a mass mail? I don't mind collecting the addresses, at least those that I can find. But I'm probably not the best one to compose a message (not knowing exactly what needs to be said, technically).
Or if there were some way to contact them via GitHub (most of them are there, anyway). I never have found a way to use GH to contact a repo owner. (unless it's new in the last couple of years)
Well anyway, if we work together on it, taking some kind of action, rather than "sorry folks...." would be better, in my opinion.
There is a problem we need to solve before we do that (GitHub users could potentially be contacted via the issues section of one of their projects, if they set one to be available).
We do not have any instructions that outline at least 80% of 'how to update your extension to 1.0'. Without that, though, personally, I'd feel embarrassed to tell people about this, but not to be able to provide a path about what to do next.
(I could maybe put together something very generic... I have updated two extensions already (or rather, mostly rewritten). There's a start on the Wiki, too.) But it might not be enough.
You mean that what an extension author needs to do to update the extension would not be obvious to them? I mean, they figured out how to create an extension by themselves in the first place.
Sigh. I think I'd rather see all the energy going into fixing the remaining bugs (the ones I've seen don't seem that bad) going into this issue. TONS of users have 3rd party extensions already installed, and they are going to break the moment they upgrade, with no fix available. Then they will have to downgrade to get their working extension back.
I'm not saying I want to update all extensions - I updated those that I personally want to be able to use. So I know a bit what needs to be done.
It's not automatically going to be obvious - many things will be reported by Inkscape, but it can be made easier for people with good instructions.
I'm not fixing bugs in extensions right now.
But I did update the Wiki page yesterday night, waiting for Martin to review. https://wiki.inkscape.org/wiki/index.php?title=Updating_your_Extension_for_1.0
Oh ok. I'll start collecting contact info.
Thanks for helping with this!
Actually, when I can't find contact info, and I'm already on github, and they have Issues available, could I already submit one? Or maybe I should just put this off for another week, until everything is ready?
You can start right away, if the chance opens up to you! The more time people have, the better.
As Martin has mentioned he had also opened some issues, and I have, too - so maybe you could check if there's one already, and add the missing info to it, if there is.
Ok, so this is the link they need: https://wiki.inkscape.org/wiki/index.php?title=Updating_your_Extension_for_1.0
Right?
And.... You mean if there's an open issue in the extension's repo? This would primarily be on github. If there's already an issue, just add to it? Or start a new Issue, if there aren't any open?
I haven't found this yet, but I assume there could theoretically be more than one issue open. What would I do then?
Or are you talking about something in GL?
Edit
You're not suggesting I could edit extensions? Are you?
Yep, that's the link.
And yes, an open issue in the extension's issue tracker, if it has one. I think you know the answer to the adding / opening a new question. In case there are two issues, decide for yourself ;-)
You probably could do some edits, but I've not asked you to, or suggested that you should.
Have a good Sunday!
Ok, thanks.