mostaphaRoudsari
commented
5 years ago @theo-armour, we have a very short time between now and the workshop so and I totally agree with your comments to find the most important ones first to address. Here are my comments.
- Repo Should this code move into its own repo and become a proper issue-driven development project?
I think it should happen sooner than later. It is a very interesting project and I think keep it separate and small can be very helpful both as a viewer and a learning resource (for getting started with THREE.js). I'm being selfish here and want to use this project to learn THREE.js
- Geometry RAD files may contain spheres, cones and other types of geometry. The current version of this viewer only supports polygons. It would be a good thing to decide the priority for the addition of support for other types of geometry. Should support for these geometries be added ASAP or are these types infrequently used and their inclusion might even be a distraction in a AEC domain-specific environment?
We can add a couple of commonly used geometries such as sphere, cone and Cylinder and we will cover most of the cases. I assume are easy to support these primitive geometries in THREE.js. I can add them to parser later today/tonight.
- Materials RAD files support a variety of materials and colors but gbXML and Honeybee are only likely to used a small number of these. It would be a good thing to decide the priority for the addition of support for other types of materials. Should the viewer be able to parse all Radiance material types ASAP or is it sufficient for the time being to have a simple hard-wired lookup table for 50 or so commonly used materials?
There are several type of materials in Radiance and I propose that for now parse all of them with a generic structure. All we need is that all the geometries with the same material name to be colored the same in the viewer. Also it would be very nice if material definition shows up on mouse hover.
I will add more info in rad_2_json repository.
- File Size The current viewer is setup for files up 1 to 2 MB in size. It can be updated to handle files of much larger size but this would come at cost of greater complexity and more safeguards. Would this effort be worthwhile in the near term of not?
For now and as a prototype I think this is all we need. Once moved to its own repository we can start thinking about heavier files.
- More Permalinks, drag and drop and so on. Many of these little feature will just drop in organically as revisions keep coming out.
I would keep these cool feature for later and after the basic viewer works but you know better if we should implement them sooner than later. In my list they will be down there in the bottom.
Access to more RAD files created using Ladybug tools or by frequently used energy analysis programs
I can gradually add more radiance sample files but in reality the structure is always the same. Only the size will change.
Ok. Let me add more geometry support and separate materials and then I will add a new post here.
theo-armour
whale has cones at nose and tail
zati89
@mostaphaRoudsari
It would be a nice thing if we could get this script ready for you to show at The 17th International Radiance Workshop
Radiance RAD to Three.js R3
Radiance RAD to Three.js Read Me
Where do we go from here?
Everything in the to do list will get done eventually. The following some questions that could use some answers prior to the Radiance Workshop
Are there others? The main thing is this: what should be just the next two or three priority items to be tackled in the next few days/next release or two?
Help Wanted