https://wiki.blender.jp/index.php?action=history&feed=atom&title=Dev%3AWeeklyMeetingAgenda%2F2005-03-13th 2026-05-07T20:07:15Z このウィキのこのページに関する変更履歴 MediaWiki 1.31.0 https://wiki.blender.jp/index.php?title=Dev:WeeklyMeetingAgenda/2005-03-13th&diff=51780&oldid=prev 2018-06-28T17:49:56Z

<p>1版 をインポートしました</p> <table class="diff diff-contentalign-left" data-mw="interface"> <tr class="diff-title" lang="ja"> <td colspan="1" style="background-color: #fff; color: #222; text-align: center;">← 古い版</td> <td colspan="1" style="background-color: #fff; color: #222; text-align: center;">2018年6月28日 (木) 17:49時点における版</td> </tr><tr><td colspan="2" class="diff-notice" lang="ja"><div class="mw-diff-empty">(相違点なし)</div> </td></tr></table>

Yamyam https://wiki.blender.jp/index.php?title=Dev:WeeklyMeetingAgenda/2005-03-13th&diff=51779&oldid=prev 2017-11-14T02:53:00Z

<p>moved <a href="/Dev:SundayMeetingAgenda/2005-03-13th" class="mw-redirect" title="Dev:SundayMeetingAgenda/2005-03-13th">Dev:SundayMeetingAgenda/2005-03-13th</a> to <a href="/Dev:WeeklyMeetingAgenda/2005-03-13th" title="Dev:WeeklyMeetingAgenda/2005-03-13th">Dev:WeeklyMeetingAgenda/2005-03-13th</a>: No longer sunday</p> <p><b>新規ページ</b></p><div>1)Meeting minutes for external sites<br /> Tom Musgrove wanted to know whether it would be acceptable to have the<br /> meeting minutes sent to Linux Weekly News. Ton suggested that<br /> 'Development Digests' like those that were done on a monthly basis by<br /> Nathan Letwory would be more appropriate. Tom volunteered to do start<br /> doing the development digests.<br /> <br /> 2)Requirements for getting code committed in releases<br /> Ton felt that 'new functionality in blender all should be in CMS<br /> before releases' and preferred it be done either the coders submitting<br /> the new functionality, or it being the responsibility of the coders to<br /> find someone to do the documentation. A minimal requirement would be<br /> a text explanation of what it does and how it works, sample images and<br /> screen shots, and a blend file to be used for regression tests.<br /> Martin Poirier stated that the documentation needs to be done earlier<br /> and not at the last minute, 'so we don't wait for release docs when<br /> code is release ready'. Martin also requested that if possible it<br /> would also be nice to have video demonstrations of the new<br /> functionality in action.<br /> For video demonstrations Tom Musgrove suggested wink for usage on windows<br /> http://www.debugmode.com/wink/<br /> which can output to flash videos or png (which can then be turned into<br /> video with blenders sequencer).<br /> Also a brief reminder that developers who have code/projects they are<br /> working on should either update the wiki with their projects status<br /> http://wiki.blender.org/bin/view.pl/Blenderdev/ProjectStatusPage<br /> or contact Chris Burt or JLuc Peuriere with the status of their code<br /> and they will update it for you. Python scripts do not need to be in<br /> the project status page, however Ton emphasized that they DO need<br /> documentation (the py-doc plus screenshots should usually be<br /> adequate.)<br /> <br /> 3)Current Projects – New Transform<br /> According to Martin Poirier the new code has about 90% of the<br /> functionality of the old code. Still missing are shrink/fatten, free<br /> rotate, 'extrude by vector', and moving the camera in camera view, and<br /> assorted api work for exposing constraints, and context. Ton will do<br /> pose mode and dependency update related work, and cameragrab. Ton<br /> stated that new transform code should should now be the default<br /> compile. Emilie Brown will help Martin with the documentation of the<br /> new Transform functionality.<br /> <br /> 4)Current Projects – OpenEXR<br /> Ton stated that while supporting an open hidef image format is<br /> desirable 'it should be properly wrapped in a C library' and that 'we<br /> have to keep all exr dependencies external' - 'it should either work<br /> like quicktime, or as static lib'. For now 'OpenEXR goes back to the<br /> drawing board, to design a good compiling lib for blender first'.<br /> <br /> 5)Current Projects – HEMesh<br /> Joe Eager states that his HEMesh work is going well and is currently<br /> waiting on feedback from JLuc Peuriere on what 'major rewrites' will<br /> be needed. Ton queried whether it was ready for conclusion in<br /> tuhopuu. It was decided that JLuc will review the code this week and<br /> then a decision on suitability for inclusion on tuhopuu will be made<br /> at the next meeting.<br /> <br /> 6)Bug Tracker<br /> It was noted that the majority of bug reports in the tracker (or that<br /> have been moved to a separate tracker) fall in three categories 1)<br /> OpenGL compatibility issues with video accelerator cards both on Linux<br /> and Windows 2) Game Engine 3) Python<br /> <br /> Python – not much was said regarding the python bug count other than<br /> it is of concern to Ton.<br /> <br /> OpenGL - For OpenGL issues there is a need for individuals who are<br /> capable in OpenGL and who have access to the cards that have problems<br /> (ATI on Windows and Linux). Ton stated that OpenGL is 'easy'. Martin<br /> Poirier has the OpenGL Redbook on his Amazon.com wishlist (it was<br /> pointed out that it can be downloaded in PDF or html format here -<br /> http://www.opengl.org/documentation/red_book_1.0/ )<br /> Christ Burt and Emilie Brown will try learning OpenGL to try and<br /> contribute in that respect, but other developers are strongly<br /> encouraged to do so. (Ton claims it is easier to learn and use than<br /> python. Also Blender only uses widely supported OpenGL so just<br /> version 1.2 of the API is sufficient)<br /> <br /> Game Engine- There is really only one active developer of the game<br /> engine, Kester Maddock, and a single part time developer is not<br /> sufficient to maintain the game engine. A number of suggestions were<br /> made about 'what to do about the game engine problem'. Suggestions<br /> ranged from – issue a call for developers, to temporary removal, to<br /> complete removal, to potentially integrating a different open source<br /> engine. Jens Ole Wund noted that 'i don't see much difference between<br /> a good physics driven animation system and a game engine'. Ton<br /> believes that Kester needs to be consulted before any decision is<br /> made.<br /> If separation does happen, sufficient code for doing things like<br /> walkthroughs will be kept in the main blender tree.</div>

wiki>Ideasman42