any reason why model importer doesnt support resources

Why do i have to have physical paths for all my obj and mtl files? i really dont want to deploy dozens of these model files to customers without first emedding them in a library. it appears the code supports physical paths only. After reviewing the code it would appear to be very simple to simply support streams and pulling from assembly resources. has anyone done this already before I add this myself?

agree, it should be possible to provide a mechanism that loads the attached files from streams!
https://helixtoolkit.codeplex.com/workitem/10026