利用者・トーク:Mindrones

Mensaje de Next or Right

Hola DifferentSmoke y mindrones mi nombre es Next or Right y soy un usuario bastante nuevo. Me comunico con ustedes porque tengo la idea de seguir traduciendo algunos capítulos sin traducir sobre el tema de Blender Summer of Documentation, en parte por mi y en parte por apoyar a la comunidad hispana.

Intente comunicarme con bf-docboard-es-cvs pero no se porqué no pude (al parecer un problema de contraseña o no se, ya que no entiendo el problema si estoy en linea...). En una, intente mandar mensajes a todos los usuarios.

Bueno, entonces el tema es así, para simplificarme la vida, traducí alguno capitulos del manual 2.5 y son los siguientes (las cuales necesitan revisión)

- http://wiki.blender.org/index.php/Doc:ES/2.5/Manual/3D_interaction/Manipulation/Basics

- http://wiki.blender.org/index.php/Doc:ES/2.5/Manual/Modeling

- http://wiki.blender.org/index.php/Doc:ES/2.5/Manual/Your_First_Animation/1.A_static_Gingerbread_Man (este ultimo no tiene traducido gran parte del tema "materiales")

Si ustedes no pueden hacer algo (y si quieren, y pueden..), tal vez por que no quieran o no tengan tiempo, estaría bueno que lo comunicaran a los demás usuarios, tal vez alguno pueda. A demás quisiera saber como procedo para usar el "sandbox"; ¿simplemente hay que crear una pagina con el nombre "sandbox" en su dirección?. He editado algunos articulos hace mucho tiempo en wikipedia y no recuerdo si se hacia igual.

Bueno, Saludos, espero su pronta respuesta y .. Suerte!

DokuWiki

Hi Mindrones. Here's where you can try DokuWiki:

wiki.watchmike.ca

Thanks, don't work too hard!

--Mikahl

Thanks a lot for syntax highligthing! works like a charm! --Skadge 18:25, 28 March 2010 (UTC)

Re: Proposed Section - Classes and Functions: specifications, diagrams, and test cases

Hey Mindrones,

Thank you for such a soon reply to my discussion on adding code specifications. About your edits, you add structure to the specification I listed, and your link system would be beneficial to programmers’ mental organization of the code and allow a quick reference from looking at the code to seeing documentation.

I would have gotten back sooner, however, I wanted to know more about you. To my surprise, I see, I'm dealing with someone who attends Blender conferences, gives presentations (that Ton attends), and knows people that can just borrow a Milo camera in spare time. I've read your Blender wiki user page, and visited your blender sites. First, I’ll get some chit chat out of the way (your proposed collapsible wiki, my long-term Blender goal), then I’ll cover the documentation stuff (docboard, my free time, how I can begin).

Collapsible information: Browsing your proposals, you were talking about collapsable wiki. I had just been thinking almost the same thing just two days ago, but I was going to use it for a Blender 2.5a2 CMake Building tutorial. I was going to put detailed information, for the people that need understanding of the instructions. Its interesting to think of the audience of a tutorial. Sometimes its programmers that want facts and jargon, and sometimes its beginners that may have a problem (i.e. they chose a different installation path and didn’t realize the instructions were variable depending on that path) or simply want understanding to the process. Since it is a developers wiki, I’d say make the target audience, programmers, therefore, collapse the understanding parts leaving just the process and jargon for letting the programmer get what is needed fast. On the other hand, if the page was inside the Blender user guide, I’d put technical stuff collapsed. The collapsed table would then be used for people that understand the jargon and want a fast/specific read of instructions.

My long term goal with Blender: Understand blender enough to contribute code and usable documentation, have the acceptance of 3 board members (or whatever the requirement is) to get subversion commit privileges, and gain resume experience - working with groups on a major project, practicing software engineering, and programming. Beyond resume experience I'd like the ability to say I contributed a piece, allowing extra enjoyment to that shared by the thousands that use or will use Blender.

Docboard: By going to the “get involved” link I see that there is an entire board devoted to the documentation for the end-user. I’ve submitted a request to be added to the docboard list. I think I might be able to contribute a block of time every week to documenting.

Time: I’m currently attending a university, and will be crunching for finals starting...mmm... now. So, at first, the block I spend per week will be limited, but I at least want to get something started.

My documentation start: I’ve been debating on a pipeline, and formatting information has been a concern. I really wanted to create Class diagrams and test cases as another approach to the documentation, but finding a way to present links within diagrams inside a wiki has been challenging, and I’d also like to keep diagram image file size down (possibly using gif format where the boxes and texts are a readable color and the background is ignored?)

For now, I’m going to stick with the tables. Also, I see that the way for new Blender developers to get involved is with documentation, and there is suggestion to start on the developer’s user page first, so it can be moved to a main page. There is also a way to officially start a project, but for now I guess I better stick with my user page since I don’t know how much time I’m going to be able to put into it. That’s my plan.

Later,

Double_dose