Change name of RaspberryPiGateway to Gateway?

[SorraTheOrc]

There is nothing specific, other than startup scripts, to the RaspberryPi within the Gateway. In fact during testing it is easier to use a Windows machine. Some folks might even prefer to use a Windows machine as the gateway.

For example, I have a Dell Windows 8 Tablet as a controller for my Hue lights in some of my rooms. Rather than install a Pi in these rooms I'd rather use the existing tablet as the Gateway.

It therefore seems to make sense to separate out the startup scripts from the Gateway code. THis would give us both a "RaspberryPiGateway" and a "Gateway" artifact.

Thoughts?

[luisrudge]

👍

[olivierbloch]

That's a good point. we are actually planning to add some additional Gateway samples with other hardware platforms that will certainly use the same code. We could then make this piece of code more generic...
Maybe we could call it CSharpGateway so that when we add a JavaScript version we can call this other one JSGateway...
Thoughts on this?

[olivierbloch]

Based on Issue #16 we will break the solution into several individual ones. The name of the project should still be RaspberryPiGateway as the device targeted will be a Pi, however we could move the C# code into a shared code folder (per language) that other device projects could reuse.
Makes sense?

[olivierbloch]

We just updated the project architecture to ease the addition of more devices but for now we are keeping the code for the Raspberry Pi Gateway project under this name. Once we have several devices using the same piece of code we will consider having a generic code folder added that several devices projects can use code from.