Add functions to accept more RGB-D input formats (different resolution, different view, etc) about open3d HOT 5 CLOSED

@syncle Should explain this in the ReadRGBD tutorial page. Also mention we don't have a solution for un-registered RGB-D image pair yet. This is TBD and we welcome PR to address it.

from open3d.

Sure. Will do. I am merging rgbd examples from test_py3d to ReadRGBD. The new tutorial will demonstrate I/O of different types of RGBD images, and its point cloud form.

from open3d.

This is a bit off the topic. But lately I have started using libigl. I really don't like its documentation: http://libigl.github.io/libigl/tutorial/tutorial.html
But I like its python tutorial a lot: https://github.com/libigl/libigl/tree/master/python/tutorial

When I am engineering, I don't want to touch any C++ code at all. So the documentation is useless for me. But I managed to engineer lots of stuff based on the Python tutorial.

Spend half an hour, download it, and engineer something, e.g., read/write a mesh, and render it. It is and educational experience to let you know which is important in our documentation which is not.

Our plan is correct: we write good python tutorials, and write a documentation page for each of it. I also had a principle regarding Open3D that I had set a very long time ago but I want to bring it up now. It is important:

For developers

Do only when necessary. If a functionality is not necessary, do not implement it. If an external tool/library is not necessary, do not use it. Considering the scale of the project and the cross-platform nature, the cost of adding something to the project can be very high. For individual source file or project, do not include header file or link libraries if they are not needed. Keep things organized.

from open3d.

@yxlao Can please guide me what needs to be done in documentation part ??

from open3d.

@sk9331657 please redirect the docs discussion to a new github issue or through discord, thanks

from open3d.