Hi Maren,

Yes, I am referring to the html documentation; specifically the 'tutorial.html 
and 'examples.html' pages. The viewBox... extension files, together with the 
readMe file will be downloadable. The structure that I have made, seems to work 
OK, and I would like to keep links in the readMe.html file for the example.html 
and tutorial.html pages, so ideally these pages need to be hosted, but not by 
me.

I have considered building a local structure, and adding the said supporting 
docs to the zip file. Indeed, this had been my initial approach, but as the 
supporting documentation grew, I began to have doubts, and to ask, why do it 
this way?  Including them in the zip file would no doubt 'work', but it is not 
the approach that I would like to take. 

Further, why should anyone have, or want to download files that a) they may not 
want, and/or b) simply in order to access, and/or peruse them? I am not against 
anyone downloading them per-se (e.g. if they chose to do so) and, I am less 
worried about users breaking any relative links. I guess, I am simply not 
intending the supporting documents to be downloadable. 

I don't think requesting more space is an answer.

Thanks for considering matters. 

Kind regards.

-u

---- On Sat, 23 Jul 2016 23:59:28 +0000 <ma...@goos-habermann.de> wrote 
---- 

Hi u, 
 
I'm not entirely sure which specific documents you are referring to. 
 
If you mean external documents, that you don't control (the manual, for 
example), then you could just add a link into the README file and / or 
into the description text for the extension. 
 
If you mean your own html documents, why don't you just add them to the 
zip file? You could make a subfolder 'documentation' or similar, if you 
like. 
 
If you need more space for uploading everything, this list is the place to 
request it. 
 
Kind Regards, 
 Maren 
 
> 
> I have been working on a new extension called viewBox..., which is 
> awaiting upload to the Inkscape addons gallery. It is available for 
> preview here: 
> http://ugajin.co.uk/sketchbooks/viewBox/viewBox/viewBox.html, with a bunch 
> of supporting documents. 
> 
> The problem is what to do with the supporting documents (I do not want to 
> host them on ugajin.co.uk). Whilst, I may upload the extension files, 
> without the supporting documents and/or providing a link to them, this 
> seems to me to be the wrong approach. 
> 
> The viewBox and its sibling attributes are one of those things, which are 
> not be easily accessed in Inkscape, and those cutting their teeth writing 
> SVG using Inkscape may benefit from the supporting documentation. 
> 
> Thank you for considering matters. 
> 
> -u 
> 
> 
------------------------------------------------------------------------------ 
> What NetFlow Analyzer can do for you? Monitors network bandwidth and 
> traffic 
> patterns at an interface-level. Reveals which users, apps, and protocols 
> are 
> consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
> J-Flow, sFlow and other flows. Make informed decisions using capacity 
> planning 
> 
reports.http://sdm.link/zohodev2dev_______________________________________________
 
> Inkscape-docs mailing list 
> Inkscape-docs@lists.sourceforge.net 
> https://lists.sourceforge.net/lists/listinfo/inkscape-docs 
> 
 
 





------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are 
consuming the most bandwidth. Provides multi-vendor support for NetFlow, 
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports.http://sdm.link/zohodev2dev
_______________________________________________
Inkscape-docs mailing list
Inkscape-docs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/inkscape-docs

Reply via email to