Restructure Cadence files

[psiemens]

This PR restructures kitty-items-cadence to be more along the lines of @joshuahannan's proposal here: https://forum.onflow.org/t/typical-dapp-project-structure/814/4?u=pete

This restructure also switches to using filename imports for contracts (instead of placeholders) in preparation for us to integrate the new flow project commands (cc @sideninja).

[joshuahannan]

Is there a plan to include the templates or contracts package? One of the big reasons for structuring it like this was so that we could have packages for different languages that allow people get automatically construct templates from the application code with the correct import addresses with a import and a single method call. Is that still possible here?

[joshuahannan]

Could we import this from the Flow fungible token repo instead of copying it here?

[joshuahannan]

I'd prefer if we could find a way to import contract interfaces without having to copy and paste them to the same repo

[psiemens]

Yeah, agreed. I left my thoughts here, but I think we could make this work with URL imports: onflow/flow-cli#71 (comment)

[psiemens]

Is there a plan to include the templates or contracts package? One of the big reasons for structuring it like this was so that we could have packages for different languages that allow people get automatically construct templates from the application code with the correct import addresses with a import and a single method call. Is that still possible here?

Yep I think this is still possible. This repo didn't have those packages to begin with, but I hope to add them in.

The main change now is the fact that the placeholders (e.g. 0xFUNGIBLETOKEN) don't exist, making it a bit harder to do those address replacements. However, I was thinking we could generalize the code here to handle that.

[10thfloor]

Is there a plan to include the templates or contracts package? One of the big reasons for structuring it like this was so that we could have packages for different languages that allow people get automatically construct templates from the application code with the correct import addresses with a import and a single method call. Is that still possible here?

Yep I think this is still possible. This repo didn't have those packages to begin with, but I hope to add them in.

The main change now is the fact that the placeholders (e.g. 0xFUNGIBLETOKEN) don't exist, making it a bit harder to do those address replacements. However, I was thinking we could generalize the code here to handle that.

Ok, will merge this for now.
@sideninja Is there an issue in the CLI repo for Josh's suggestions?