Code cleanup about hdf5.node HOT 8 CLOSED

@vincent-tr and @rimmartin, thank you for posting these issues on a public channel. I would like to help out the project, and this helps me learn what's going on and how I might contribute. I've worked with HDF for over twenty years, and I am most experienced with C++ and Python. I have some experience with node and have worked on simple HDF5 addon bindings for internal projects. I'm looking to improve my node.js skills and contribute to an open source project. You can see my pi-qmc project for some examples of what I've done with continuous integration and documentation, though the source code and structure is uglier than what I prefer now. Please let me know how I can help.

from hdf5.node.

Yes, very much in agreement. I had rapped this out in standalone cloud9 without good formatting; usually I use netbeans which has set formatting; and can customize it to match formatting everyone likes

Yea the name spacing came from copying examples and I don't like them in headers either.

Wasn't sure if I would eventually template something so started going with hpp with everything in one file for class. Yet a unified style for this project is a good thing

And you are right about faster compile; although I was trying to precompile for some users. yet npm doesn't yet allow for the entire matrix of builds to be published. I never found a way to provide for multiple versions of the native hdf5 libraries

I am very encouraged with more developers!

from hdf5.node.

nodejs/node-gyp#893

Working with node gyp people on defaulting variables yet allowing user to set when the default doesn't work for them

from hdf5.node.

Hi @shumway, pi-qmc is some serious coding:-)

Is there an aspect of hdf5 node that interests you? Besides the core there are some layers to go. There is the image API aspect.

For my own use I have images from scientific instruments and also 3 rank matrices going to http://pointclouds.org/ based applications and 3d fourier transforms

In this interface the intention isn't to replicate the hdf5 API but to map and get the data as directly to javascript style as possible.

from hdf5.node.

Hi @rimmartin. That pi-qmc project is fun, but essentially stalled since I left my professorship a few years ago. I've followed this nodejs hdf5 project for about a year, and I tried to use it recently for a command line utility and to see if it would work with our internal toolsets. I ended up writing some of my own simplified addon wrappers instead, specific to our application, and wrote a script using python/pytables. That said, I think node is very powerful, and hdf5.node is an important project. There isn't anything I need; I just want to give back to the community. It looks like the best way I can be helpful is to work on documentation, so I'm opening that up as a new issue to keep from further hijacking @vincent-tr 's code cleanup thread.

from hdf5.node.

Hi @vincent-tr ,

I've got some fixes and additions for image io that I'm preparing to publish. Is There anything you would like published to npm as well?

from hdf5.node.

Hi,

Sorry, nothing really ready for a publish right now :/

from hdf5.node.

Oh, that's fine. I just wanted to check so I don't publish twice days apart

from hdf5.node.