From gaia.clary at machinimatrix.org Tue Aug 19 17:07:35 2014 From: gaia.clary at machinimatrix.org (Gaia) Date: Tue, 19 Aug 2014 17:07:35 +0200 Subject: [Bf-docboard] What is the method used by "Preserve Volume" in the Armature modifier ? Message-ID: <53F36837.6060501@machinimatrix.org> I suspect that "Preserve Volume" based on this paper: http://www.tara.tcd.ie/handle/2262/64125 can anybody confirm this, or correct me please ? thanks, Gaia From gaia.clary at machinimatrix.org Tue Aug 19 17:21:08 2014 From: gaia.clary at machinimatrix.org (Gaia) Date: Tue, 19 Aug 2014 17:21:08 +0200 Subject: [Bf-docboard] about Armature based animation: is the correct term for this "Skeletal animation" ? Message-ID: <53F36B64.5090407@machinimatrix.org> Actually i often stumble over the term "Rigged Mesh" as well. In fact i thought for a while that this was the official term. But now i tend to believe that "Rigged Mesh" is a fuzzy term. So, is "Skeletal animation" the correct term to use use when documenting anything in the are of armature based animation ? cheers, Gaia From italic.rendezvous at gmail.com Tue Aug 19 18:01:13 2014 From: italic.rendezvous at gmail.com (Jeffrey H) Date: Tue, 19 Aug 2014 09:01:13 -0700 Subject: [Bf-docboard] about Armature based animation: is the correct term for this "Skeletal animation" ? In-Reply-To: <53F36B64.5090407@machinimatrix.org> References: <53F36B64.5090407@machinimatrix.org> Message-ID: I'm inclined to call armature animation "armature animation" over "skeletal animation." For me, skeleton means bones of a character, but that's only one use for an armature. I feel it's better to use a general term rather than a mis-used specific term. I have not looked at the docs to see where this comes up, though. I've seen "skin" used in place of "rigged mesh" while in conversation. I understand why this is so, but Blender does not use the word "skin" in the interface; skins come from maya. As a generic term, "rigged mesh" would fit into most parts of the docs well enough without introducing terms not see in the UI (ie, skin). Unless you're talking about something very specific like character/creature rigging/animation, generic naming should be the way to go. These are my opinions, of course. My only wish is for consistency. On Tue, Aug 19, 2014 at 8:21 AM, Gaia wrote: > Actually i often stumble over the term "Rigged Mesh" as well. > In fact i thought for a while that this was the official term. > But now i tend to believe that "Rigged Mesh" is a fuzzy term. > > So, is "Skeletal animation" the correct term to use use when > documenting anything in the are of armature based animation ? > > cheers, > Gaia > _______________________________________________ > Bf-docboard mailing list > Bf-docboard at blender.org > http://lists.blender.org/mailman/listinfo/bf-docboard > -- Jeffrey "Italic_" Hoover -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.blender.org/pipermail/bf-docboard/attachments/20140819/e472fb09/attachment.htm From danmcgrath.ca at gmail.com Thu Aug 21 22:40:45 2014 From: danmcgrath.ca at gmail.com (Dan McGrath) Date: Thu, 21 Aug 2014 16:40:45 -0400 Subject: [Bf-docboard] Wiki outage and login issues today/yesterday Message-ID: Hey, Just a heads up that last night the lighttpd process when into a tailspin again and forced a restart. It would also appear that something killed the memcached process that holds the sessions for login which was the cause of people not being able to log in to the wiki. Memcached and lighttpd have been restarted now and logins should be working again. Sorry for the outage and happy wiki'ing! :) Dan -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.blender.org/pipermail/bf-docboard/attachments/20140821/0271418b/attachment.htm From ardito at apiform.to.it Tue Aug 26 13:15:04 2014 From: ardito at apiform.to.it (marco ardito) Date: Tue, 26 Aug 2014 13:15:04 +0200 Subject: [Bf-docboard] Review Request In-Reply-To: References: <53D5F605.7010004@apiform.to.it> <53D61830.1000602@apiform.to.it> <53D62C0E.7040707@apiform.to.it> Message-ID: <53FC6C38.2010108@apiform.to.it> Il 28/07/2014 13:20, Johannes Stoye ha scritto: > Yes this was me, but I had to change a bit more: > There were some dashes ("|") used before, which now separate the > columns " TOC HEADER | LEFT COL | RIGHT COL | ". > I'm sure, you will see the difference ;) > > 2014-07-28 12:57 GMT+02:00 Francesco Siddi: >> Hi Marco, >> I was actually checking out the German version, and it seems fixed. >> >> Francesco sorry to be late (I had a terrible august...), I just fixed wiki manual TOC (IT version). hope it works well along with all the wiki stuff in the next days I'll check if other versions need same tratement Marco ------------------- [Ai sensi e per gli effetti della Legge sulla tutela della privacy (L. 196/2003), questa mail ? destinata unicamente alle persone sopra indicate e le informazioni in essa contenute sono da considerarsi strettamente riservate. E' proibito leggere, copiare, usare o diffondere il contenuto della presente mail senza autorizzazione. Se avete ricevuto questo messaggio per errore, siete pregati di rispedire la stessa al mittente. Grazie] From ardito at apiform.to.it Tue Aug 26 15:26:37 2014 From: ardito at apiform.to.it (marco ardito) Date: Tue, 26 Aug 2014 15:26:37 +0200 Subject: [Bf-docboard] Review Request In-Reply-To: <53FC6C38.2010108@apiform.to.it> References: <53D5F605.7010004@apiform.to.it> <53D61830.1000602@apiform.to.it> <53D62C0E.7040707@apiform.to.it> <53FC6C38.2010108@apiform.to.it> Message-ID: <53FC8B0D.3060704@apiform.to.it> in a rush, i (hopefully) fixed also TOCs of versions: RO, PL, PT, LT, KO, ID, TR that were in need. later, I'll check if more versions TOCs are in the need of being fixed hth Il 26/08/2014 13:15, marco ardito ha scritto: > Il 28/07/2014 13:20, Johannes Stoye ha scritto: >> Yes this was me, but I had to change a bit more: >> There were some dashes ("|") used before, which now separate the >> columns " TOC HEADER | LEFT COL | RIGHT COL | ". >> I'm sure, you will see the difference ;) >> >> 2014-07-28 12:57 GMT+02:00 Francesco Siddi: >>> Hi Marco, >>> I was actually checking out the German version, and it seems fixed. >>> >>> Francesco > > sorry to be late (I had a terrible august...), I just fixed wiki > manual TOC (IT version). > hope it works well along with all the wiki stuff > > in the next days I'll check if other versions need same tratement > > Marco ------------------- [Ai sensi e per gli effetti della Legge sulla tutela della privacy (L. 196/2003), questa mail ? destinata unicamente alle persone sopra indicate e le informazioni in essa contenute sono da considerarsi strettamente riservate. E' proibito leggere, copiare, usare o diffondere il contenuto della presente mail senza autorizzazione. Se avete ricevuto questo messaggio per errore, siete pregati di rispedire la stessa al mittente. Grazie] From mkucera66 at seznam.cz Thu Aug 28 10:32:09 2014 From: mkucera66 at seznam.cz (=?utf-8?q?Mirek_Ku=C4=8Dera_Quark66?=) Date: Thu, 28 Aug 2014 10:32:09 +0200 (CEST) Subject: [Bf-docboard] =?utf-8?q?Bf-docboard=255D=2520Review=2520Request?= =?utf-8?q?=26In-Reply-To=3D53FC6C38=2E2010108=2540apiform=2Eto=2Ei?= =?utf-8?q?t=3E?= Message-ID: <9Qc.1Vc2f.QEwGaRC8mY.1J}ka9@seznam.cz> Hello, so I will check TOC pages translated into CZ(ech). I broke my translation activity durin summer but now I am on the boat again. -- Mirek Ku?era, Quark66,??? Czech Republic -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.blender.org/pipermail/bf-docboard/attachments/20140828/a6e2e242/attachment.htm From francesco.siddi at gmail.com Fri Aug 29 12:31:04 2014 From: francesco.siddi at gmail.com (Francesco Siddi) Date: Fri, 29 Aug 2014 12:31:04 +0200 Subject: [Bf-docboard] Update on Wiki to RestructuredText conversion In-Reply-To: References: <53B50AA8.5090101@apiform.to.it> Message-ID: Hello everyone, an important update on the documentation migration: - we created a project on?https://developer.blender.org/project/view/53/? - the new sphinx-based documentation is available here?https://developer.blender.org/diffusion/BM/ The project is now open for contribution, so we welcome any volunteer willing to check out the documentation and do content edits and structure refactoring for basically any section. General instructions on how to do this are available in the project description. At the moment, in order to contribute, there are a few requirements: - basic knowledge of GIT (checkout, commit, diff) - basic knowledge of Sphinx and reST (the documentation system) - an account on developer.blender.org (so you can write comments in the project tasks or raise issues there) About translations and versioning: - currently we are trying to set up this documentation in English (many sections are unmaintained and some are outdated back to 2.4x) - if this migration succeeds, we will support other languages in parallel repos - currently we are working for the 2.7x series, and the idea is to use git-tags for greater versions - older documentation will stay on wiki.blender.org until this documentation fully functional We are happy to hear feedback and comments! Also, we are working on trying to make this infrastructure simpler, to easily allow casual contribution. Reminder: this project is about the User Manual. Everything else (developers docs, proposals, release logs, module owners list, etc) will stay on the wiki. Thanks, Francesco On 3 Jul 2014 at 10:35:13, Campbell Barton (ideasman42 at gmail.com) wrote: On Thu, Jul 3, 2014 at 5:47 PM, marco ardito wrote: > Hi, campbell, > > nice clean look! but... a TOC should be, well, a TOC, not a full index! :) > look at the TOC page source. Something like that, with links... :) but > that will be tuned later, I'm sure. Yep, this needs cleaning up, basic structure is there but need to change how top-level categories show. Attempting to do this automatic isnt that valuable IMHO, once we do final conversion re-arranging TOC isn't so hard. > about the look, it's clean but it needs some tweaking. Great job, anyway > for an automatic conversion! > > I'm doing a wiki > pdf conversion since a while, updated each month. atm > I stopped to see how the sphinx-doc trial went on, hoping that soon the > old pdf could be no more needed!! great! converting the wiki in pdf is > fun but also a pain :) With sphinx we can provide the HTML as a downloadable archive, IMHO this is more usable then the PDF, I generated a PDF for our sphinx python reference for a while but it wasnt that great, I removed and dont think anyone noticed. > Do you have any pdf conversion test? I did do one, but cant recall if I uploaded- It does an OK job, but image layout sometimes doesn't look right. Heres sphinx generated PDF, though there aren't any images. http://www.blender.org/documentation/blender_python_api_2_59_0/blender_python_reference_2_59_0.pdf To summarize we can have PDF book if we want, but I always found the output inferior to the HTML docs. > Thanks, Marco > > Il 02/07/2014 23:29, Campbell Barton ha scritto: >> Hi, quick update on the progress migrating the wiki, > > > > > ------------------- > [Ai sensi e per gli effetti della Legge sulla tutela della privacy > (L. 196/2003), questa mail ? destinata unicamente alle persone sopra > indicate e le informazioni in essa contenute sono da considerarsi > strettamente riservate. E' proibito leggere, copiare, usare o > diffondere il contenuto della presente mail senza autorizzazione. > Se avete ricevuto questo messaggio per errore, siete pregati di > rispedire la stessa al mittente. Grazie] > > _______________________________________________ > Bf-docboard mailing list > Bf-docboard at blender.org > http://lists.blender.org/mailman/listinfo/bf-docboard -- - Campbell _______________________________________________ Bf-docboard mailing list Bf-docboard at blender.org http://lists.blender.org/mailman/listinfo/bf-docboard -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.blender.org/pipermail/bf-docboard/attachments/20140829/9893ed8c/attachment.htm From ideasman42 at gmail.com Sat Aug 30 16:59:29 2014 From: ideasman42 at gmail.com (Campbell Barton) Date: Sun, 31 Aug 2014 00:59:29 +1000 Subject: [Bf-docboard] Update on Wiki to RestructuredText conversion In-Reply-To: References: <53B50AA8.5090101@apiform.to.it> Message-ID: Did anyone try get the docs and build them? so far this has been me and Francesco, but if the project is to be a success, we will need others to become involved. For the migration and for ongoing improvements. We realize the barrier of entry is high (using git for technical writers), and may eventually have a way to avoid writings having to use git or sphinx (directly) at all. (We're keeping an eye on possible solutions). But for now its important that we can see if the system is usable. That the team who writes docs even is able to use it effectively, or finds it better then the wiki. On Fri, Aug 29, 2014 at 8:31 PM, Francesco Siddi wrote: > Hello everyone, > an important update on the documentation migration: > > - we created a project on https://developer.blender.org/project/view/53/ > - the new sphinx-based documentation is available here > https://developer.blender.org/diffusion/BM/ > > The project is now open for contribution, so we welcome any volunteer > willing to check out the documentation and do content edits and structure > refactoring for basically any section. General instructions on how to do > this are available in the project description. At the moment, in order to > contribute, there are a few requirements: > > - basic knowledge of GIT (checkout, commit, diff) > - basic knowledge of Sphinx and reST (the documentation system) > - an account on developer.blender.org (so you can write comments in the > project tasks or raise issues there) > > About translations and versioning: > > - currently we are trying to set up this documentation in English (many > sections are unmaintained and some are outdated back to 2.4x) > - if this migration succeeds, we will support other languages in parallel > repos > - currently we are working for the 2.7x series, and the idea is to use > git-tags for greater versions > - older documentation will stay on wiki.blender.org until this documentation > fully functional > > We are happy to hear feedback and comments! Also, we are working on trying > to make this infrastructure simpler, to easily allow casual contribution. > > Reminder: this project is about the User Manual. Everything else (developers > docs, proposals, release logs, module owners list, etc) will stay on the > wiki. > > Thanks, > Francesco > > > On 3 Jul 2014 at 10:35:13, Campbell Barton (ideasman42 at gmail.com) wrote: > > On Thu, Jul 3, 2014 at 5:47 PM, marco ardito wrote: >> Hi, campbell, >> >> nice clean look! but... a TOC should be, well, a TOC, not a full index! :) >> look at the TOC page source. Something like that, with links... :) but >> that will be tuned later, I'm sure. > > Yep, this needs cleaning up, basic structure is there but need to > change how top-level categories show. > > Attempting to do this automatic isnt that valuable IMHO, once we do > final conversion re-arranging TOC isn't so hard. > >> about the look, it's clean but it needs some tweaking. Great job, anyway >> for an automatic conversion! >> >> I'm doing a wiki > pdf conversion since a while, updated each month. atm >> I stopped to see how the sphinx-doc trial went on, hoping that soon the >> old pdf could be no more needed!! great! converting the wiki in pdf is >> fun but also a pain :) > > With sphinx we can provide the HTML as a downloadable archive, IMHO > this is more usable then the PDF, > I generated a PDF for our sphinx python reference for a while but it > wasnt that great, I removed and dont think anyone noticed. > >> Do you have any pdf conversion test? > > I did do one, but cant recall if I uploaded- It does an OK job, but > image layout sometimes doesn't look right. > > Heres sphinx generated PDF, though there aren't any images. > http://www.blender.org/documentation/blender_python_api_2_59_0/blender_python_reference_2_59_0.pdf > > To summarize we can have PDF book if we want, but I always found the > output inferior to the HTML docs. > >> Thanks, Marco >> >> Il 02/07/2014 23:29, Campbell Barton ha scritto: >>> Hi, quick update on the progress migrating the wiki, >> >> >> >> >> ------------------- >> [Ai sensi e per gli effetti della Legge sulla tutela della privacy >> (L. 196/2003), questa mail ? destinata unicamente alle persone sopra >> indicate e le informazioni in essa contenute sono da considerarsi >> strettamente riservate. E' proibito leggere, copiare, usare o >> diffondere il contenuto della presente mail senza autorizzazione. >> Se avete ricevuto questo messaggio per errore, siete pregati di >> rispedire la stessa al mittente. Grazie] >> >> _______________________________________________ >> Bf-docboard mailing list >> Bf-docboard at blender.org >> http://lists.blender.org/mailman/listinfo/bf-docboard > > > > -- > - Campbell > _______________________________________________ > Bf-docboard mailing list > Bf-docboard at blender.org > http://lists.blender.org/mailman/listinfo/bf-docboard > > > _______________________________________________ > Bf-docboard mailing list > Bf-docboard at blender.org > http://lists.blender.org/mailman/listinfo/bf-docboard > -- - Campbell From gaia.clary at machinimatrix.org Sun Aug 31 13:15:20 2014 From: gaia.clary at machinimatrix.org (Gaia) Date: Sun, 31 Aug 2014 13:15:20 +0200 Subject: [Bf-docboard] Update on Wiki to RestructuredText conversion In-Reply-To: References: <53B50AA8.5090101@apiform.to.it> Message-ID: <540303C8.2000608@machinimatrix.org> Hi, Campbell, Francesco ; I will take a look at the section modeling/meshes/vertex_groups and try to make this pretty and working nicely. cheers, Gaia On 30.08.2014 16:59, Campbell Barton wrote: > Did anyone try get the docs and build them? so far this has been me > and Francesco, but if the project is to be a success, we will need > others to become involved. > For the migration and for ongoing improvements. > > We realize the barrier of entry is high (using git for technical > writers), and may eventually have a way to avoid writings having to > use git or sphinx (directly) at all. (We're keeping an eye on possible > solutions). > > But for now its important that we can see if the system is usable. > That the team who writes docs even is able to use it effectively, or > finds it better then the wiki. > > > > On Fri, Aug 29, 2014 at 8:31 PM, Francesco Siddi > wrote: >> Hello everyone, >> an important update on the documentation migration: >> >> - we created a project on https://developer.blender.org/project/view/53/ >> - the new sphinx-based documentation is available here >> https://developer.blender.org/diffusion/BM/ >> >> The project is now open for contribution, so we welcome any volunteer >> willing to check out the documentation and do content edits and structure >> refactoring for basically any section. General instructions on how to do >> this are available in the project description. At the moment, in order to >> contribute, there are a few requirements: >> >> - basic knowledge of GIT (checkout, commit, diff) >> - basic knowledge of Sphinx and reST (the documentation system) >> - an account on developer.blender.org (so you can write comments in the >> project tasks or raise issues there) >> >> About translations and versioning: >> >> - currently we are trying to set up this documentation in English (many >> sections are unmaintained and some are outdated back to 2.4x) >> - if this migration succeeds, we will support other languages in parallel >> repos >> - currently we are working for the 2.7x series, and the idea is to use >> git-tags for greater versions >> - older documentation will stay on wiki.blender.org until this documentation >> fully functional >> >> We are happy to hear feedback and comments! Also, we are working on trying >> to make this infrastructure simpler, to easily allow casual contribution. >> >> Reminder: this project is about the User Manual. Everything else (developers >> docs, proposals, release logs, module owners list, etc) will stay on the >> wiki. >> >> Thanks, >> Francesco >> >> >> On 3 Jul 2014 at 10:35:13, Campbell Barton (ideasman42 at gmail.com) wrote: >> >> On Thu, Jul 3, 2014 at 5:47 PM, marco ardito wrote: >>> Hi, campbell, >>> >>> nice clean look! but... a TOC should be, well, a TOC, not a full index! :) >>> look at the TOC page source. Something like that, with links... :) but >>> that will be tuned later, I'm sure. >> Yep, this needs cleaning up, basic structure is there but need to >> change how top-level categories show. >> >> Attempting to do this automatic isnt that valuable IMHO, once we do >> final conversion re-arranging TOC isn't so hard. >> >>> about the look, it's clean but it needs some tweaking. Great job, anyway >>> for an automatic conversion! >>> >>> I'm doing a wiki > pdf conversion since a while, updated each month. atm >>> I stopped to see how the sphinx-doc trial went on, hoping that soon the >>> old pdf could be no more needed!! great! converting the wiki in pdf is >>> fun but also a pain :) >> With sphinx we can provide the HTML as a downloadable archive, IMHO >> this is more usable then the PDF, >> I generated a PDF for our sphinx python reference for a while but it >> wasnt that great, I removed and dont think anyone noticed. >> >>> Do you have any pdf conversion test? >> I did do one, but cant recall if I uploaded- It does an OK job, but >> image layout sometimes doesn't look right. >> >> Heres sphinx generated PDF, though there aren't any images. >> http://www.blender.org/documentation/blender_python_api_2_59_0/blender_python_reference_2_59_0.pdf >> >> To summarize we can have PDF book if we want, but I always found the >> output inferior to the HTML docs. >> >>> Thanks, Marco >>> >>> Il 02/07/2014 23:29, Campbell Barton ha scritto: >>>> Hi, quick update on the progress migrating the wiki, >>> >>> >>> >>> ------------------- >>> [Ai sensi e per gli effetti della Legge sulla tutela della privacy >>> (L. 196/2003), questa mail ? destinata unicamente alle persone sopra >>> indicate e le informazioni in essa contenute sono da considerarsi >>> strettamente riservate. E' proibito leggere, copiare, usare o >>> diffondere il contenuto della presente mail senza autorizzazione. >>> Se avete ricevuto questo messaggio per errore, siete pregati di >>> rispedire la stessa al mittente. Grazie] >>> >>> _______________________________________________ >>> Bf-docboard mailing list >>> Bf-docboard at blender.org >>> http://lists.blender.org/mailman/listinfo/bf-docboard >> >> >> -- >> - Campbell >> _______________________________________________ >> Bf-docboard mailing list >> Bf-docboard at blender.org >> http://lists.blender.org/mailman/listinfo/bf-docboard >> >> >> _______________________________________________ >> Bf-docboard mailing list >> Bf-docboard at blender.org >> http://lists.blender.org/mailman/listinfo/bf-docboard >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.blender.org/pipermail/bf-docboard/attachments/20140831/2cdc8035/attachment.htm From nils.kelleter at googlemail.com Sun Aug 31 23:38:15 2014 From: nils.kelleter at googlemail.com (nils.kelleter at googlemail.com) Date: Sun, 31 Aug 2014 21:38:15 +0000 Subject: [Bf-docboard] =?utf-8?q?_Re=3A__Update_on_Wiki_to_RestructuredTex?= =?utf-8?q?t_conversion?= In-Reply-To: References: <53B50AA8.5090101@apiform.to.it> , Message-ID: <95ae2f21e653497e9fb3cd863cb3dc0b@googlemail.com> Hi, I have tried it under Windows 8.1 and use the instructions on your project site. I got an error during pip installation of wsgiref. Below you can find the debug output. For information, I have no experience with git or python, I have installed both today the first time. I have downloaded the latest version of the git and python installation package for Windows and installed it. I hope someone can help me. If the setup is running on my computer, I will write an installation guide for Windows users and can provide it here. Regards, Nils Here the Output of the debug log file: >>> Downloading/unpacking wsgiref==0.1.2 (from -r requirements.txt (line 7)) Getting page https://pypi.python.org/simple/wsgiref/ URLs to search for versions for wsgiref==0.1.2 (from -r requirements.txt (line 7)): * https://pypi.python.org/simple/wsgiref/0.1.2 * https://pypi.python.org/simple/wsgiref/ Getting page https://pypi.python.org/simple/wsgiref/0.1.2 Could not fetch URL https://pypi.python.org/simple/wsgiref/0.1.2: 404 Client Error: Not Found Will skip URL https://pypi.python.org/simple/wsgiref/0.1.2 when looking for download links for wsgiref==0.1.2 (from -r requirements.txt (line 7)) Analyzing links from page https://pypi.python.org/simple/wsgiref/ Skipping link https://pypi.python.org/packages/2.3/w/wsgiref/wsgiref-0.1-py2.3.egg#md5=102c28c347907758ef83006e7fd4bc60 (from https://pypi.python.org/simple/wsgiref/); unknown archive format: .egg Skipping link https://pypi.python.org/packages/2.3/w/wsgiref/wsgiref-0.1.1-py2.3.egg#md5=d87f9e63c6a83d798730c2c74dc5c455 (from https://pypi.python.org/simple/wsgiref/); unknown archive format: .egg Skipping link https://pypi.python.org/packages/2.3/w/wsgiref/wsgiref-0.1.2-py2.3.egg#md5=6afff05ff3bd529123b1b987677d08a1 (from https://pypi.python.org/simple/wsgiref/); unknown archive format: .egg Skipping link https://pypi.python.org/packages/2.4/w/wsgiref/wsgiref-0.1-py2.4.egg#md5=8e46b55129b21a5dfdedd120ad13b8e3 (from https://pypi.python.org/simple/wsgiref/); unknown archive format: .egg Skipping link https://pypi.python.org/packages/2.4/w/wsgiref/wsgiref-0.1.1-py2.4.egg#md5=e63f109ff92ec1bc4c3d9755f3c4ff73 (from https://pypi.python.org/simple/wsgiref/); unknown archive format: .egg Skipping link https://pypi.python.org/packages/2.4/w/wsgiref/wsgiref-0.1.2-py2.4.egg#md5=8376d1cde46a101877687c041f46f02d (from https://pypi.python.org/simple/wsgiref/); unknown archive format: .egg Found link https://pypi.python.org/packages/source/w/wsgiref/wsgiref-0.1.1.zip#md5=95b91a109b7e4bebe5bcf5ae3fdaf853 (from https://pypi.python.org/simple/wsgiref/), version: 0.1.1 Found link https://pypi.python.org/packages/source/w/wsgiref/wsgiref-0.1.2.zip#md5=29b146e6ebd0f9fb119fe321f7bcf6cb (from https://pypi.python.org/simple/wsgiref/), version: 0.1.2 Found link https://pypi.python.org/packages/source/w/wsgiref/wsgiref-0.1.zip#md5=156193401dc7b068ec1dd1f8bac99555 (from https://pypi.python.org/simple/wsgiref/), version: 0.1 Skipping link http://peak.telecommunity.com/wsgiref.pdf (from https://pypi.python.org/simple/wsgiref/); unknown archive format: .pdf Skipping link http://peak.telecommunity.com/wsgiref_docs/ (from https://pypi.python.org/simple/wsgiref/); not a file Skipping svn://svn.eby-sarna.com/svnroot/wsgiref#egg=wsgiref-dev (from https://pypi.python.org/simple/wsgiref/) because it is externally hosted. Ignoring link https://pypi.python.org/packages/source/w/wsgiref/wsgiref-0.1.1.zip#md5=95b91a109b7e4bebe5bcf5ae3fdaf853 (from https://pypi.python.org/simple/wsgiref/), version 0.1.1 doesn't match ==0.1.2 Ignoring link https://pypi.python.org/packages/source/w/wsgiref/wsgiref-0.1.zip#md5=156193401dc7b068ec1dd1f8bac99555 (from https://pypi.python.org/simple/wsgiref/), version 0.1 doesn't match ==0.1.2 Downloading wsgiref-0.1.2.zip Downloading from URL https://pypi.python.org/packages/source/w/wsgiref/wsgiref-0.1.2.zip#md5=29b146e6ebd0f9fb119fe321f7bcf6cb (from https://pypi.python.org/simple/wsgiref/) Running setup.py (path:C:\Users\Nils\AppData\Local\Temp\pip_build_Nils\wsgiref\setup.py) egg_info for package wsgiref Traceback (most recent call last): File "", line 17, in File "C:\Users\Nils\AppData\Local\Temp\pip_build_Nils\wsgiref\setup.py", line 5, in import ez_setup File "C:\Users\Nils\AppData\Local\Temp\pip_build_Nils\wsgiref\ez_setup\__init__.py", line 170 print "Setuptools version",version,"or greater has been installed." ^ SyntaxError: invalid syntax Complete output from command python setup.py egg_info: Traceback (most recent call last): File "", line 17, in File "C:\Users\Nils\AppData\Local\Temp\pip_build_Nils\wsgiref\setup.py", line 5, in import ez_setup File "C:\Users\Nils\AppData\Local\Temp\pip_build_Nils\wsgiref\ez_setup\__init__.py", line 170 print "Setuptools version",version,"or greater has been installed." ^ SyntaxError: invalid syntax <<< Von: Campbell Barton Gesendet: ?Samstag?, ?30?. ?August? ?2014 ?16?:?59 An: Blender Documentation Project Did anyone try get the docs and build them? so far this has been me and Francesco, but if the project is to be a success, we will need others to become involved. For the migration and for ongoing improvements. We realize the barrier of entry is high (using git for technical writers), and may eventually have a way to avoid writings having to use git or sphinx (directly) at all. (We're keeping an eye on possible solutions). But for now its important that we can see if the system is usable. That the team who writes docs even is able to use it effectively, or finds it better then the wiki. On Fri, Aug 29, 2014 at 8:31 PM, Francesco Siddi wrote: > Hello everyone, > an important update on the documentation migration: > > - we created a project on https://developer.blender.org/project/view/53/ > - the new sphinx-based documentation is available here > https://developer.blender.org/diffusion/BM/ > > The project is now open for contribution, so we welcome any volunteer > willing to check out the documentation and do content edits and structure > refactoring for basically any section. General instructions on how to do > this are available in the project description. At the moment, in order to > contribute, there are a few requirements: > > - basic knowledge of GIT (checkout, commit, diff) > - basic knowledge of Sphinx and reST (the documentation system) > - an account on developer.blender.org (so you can write comments in the > project tasks or raise issues there) > > About translations and versioning: > > - currently we are trying to set up this documentation in English (many > sections are unmaintained and some are outdated back to 2.4x) > - if this migration succeeds, we will support other languages in parallel > repos > - currently we are working for the 2.7x series, and the idea is to use > git-tags for greater versions > - older documentation will stay on wiki.blender.org until this documentation > fully functional > > We are happy to hear feedback and comments! Also, we are working on trying > to make this infrastructure simpler, to easily allow casual contribution. > > Reminder: this project is about the User Manual. Everything else (developers > docs, proposals, release logs, module owners list, etc) will stay on the > wiki. > > Thanks, > Francesco > > > On 3 Jul 2014 at 10:35:13, Campbell Barton (ideasman42 at gmail.com) wrote: > > On Thu, Jul 3, 2014 at 5:47 PM, marco ardito wrote: >> Hi, campbell, >> >> nice clean look! but... a TOC should be, well, a TOC, not a full index! :) >> look at the TOC page source. Something like that, with links... :) but >> that will be tuned later, I'm sure. > > Yep, this needs cleaning up, basic structure is there but need to > change how top-level categories show. > > Attempting to do this automatic isnt that valuable IMHO, once we do > final conversion re-arranging TOC isn't so hard. > >> about the look, it's clean but it needs some tweaking. Great job, anyway >> for an automatic conversion! >> >> I'm doing a wiki > pdf conversion since a while, updated each month. atm >> I stopped to see how the sphinx-doc trial went on, hoping that soon the >> old pdf could be no more needed!! great! converting the wiki in pdf is >> fun but also a pain :) > > With sphinx we can provide the HTML as a downloadable archive, IMHO > this is more usable then the PDF, > I generated a PDF for our sphinx python reference for a while but it > wasnt that great, I removed and dont think anyone noticed. > >> Do you have any pdf conversion test? > > I did do one, but cant recall if I uploaded- It does an OK job, but > image layout sometimes doesn't look right. > > Heres sphinx generated PDF, though there aren't any images. > http://www.blender.org/documentation/blender_python_api_2_59_0/blender_python_reference_2_59_0.pdf > > To summarize we can have PDF book if we want, but I always found the > output inferior to the HTML docs. > >> Thanks, Marco >> >> Il 02/07/2014 23:29, Campbell Barton ha scritto: >>> Hi, quick update on the progress migrating the wiki, >> >> >> >> >> ------------------- >> [Ai sensi e per gli effetti della Legge sulla tutela della privacy >> (L. 196/2003), questa mail ? destinata unicamente alle persone sopra >> indicate e le informazioni in essa contenute sono da considerarsi >> strettamente riservate. E' proibito leggere, copiare, usare o >> diffondere il contenuto della presente mail senza autorizzazione. >> Se avete ricevuto questo messaggio per errore, siete pregati di >> rispedire la stessa al mittente. Grazie] >> >> _______________________________________________ >> Bf-docboard mailing list >> Bf-docboard at blender.org >> http://lists.blender.org/mailman/listinfo/bf-docboard > > > > -- > - Campbell > _______________________________________________ > Bf-docboard mailing list > Bf-docboard at blender.org > http://lists.blender.org/mailman/listinfo/bf-docboard > > > _______________________________________________ > Bf-docboard mailing list > Bf-docboard at blender.org > http://lists.blender.org/mailman/listinfo/bf-docboard > -- - Campbell -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.blender.org/pipermail/bf-docboard/attachments/20140831/5c45c9b4/attachment.htm