Mid and Final term discussion

SmartAuction DAPP - Modularity

SmartAuction DAPP - Modularity

by MICHELE AGOSTINI -
Number of replies: 3
Hello. Just for confirmation, I'd like to know if it is okay for the project purpose to implement the backend and frontend logic for the three actors (seller, auctioneer, bidder) in the same app.
In reply to MICHELE AGOSTINI

Re: SmartAuction DAPP - Modularity

by ANDREA LISI -

Hi,

sorry for the late and sorry, but I do not understand what you mean.

As far as I know, you need to think the Ethereum smart contracts as "backend" of your application (for the project purposes). Then if you would like to add extra backend scripts for additional functionalities then I think it is ok.

In reply to ANDREA LISI

Re: SmartAuction DAPP - Modularity

by MICHELE AGOSTINI -

Yeah I'm sorry it's a bit confusing and probably not a very relevant question - it regards the project structure only.

In short the question is: is it okay to put both frontend (i.e. .html/.css/.js files) and backend (i.e. .sol files) code in subfolders of the same main folder made by truffle init, for the sake of semplicity and for the purpose of the project? Or is a more elegant project organization preferable for DApps?

In reply to MICHELE AGOSTINI

Re: SmartAuction DAPP - Modularity

by ANDREA LISI -

ah ok.
You can do it as you prefer.
I do not think there are rules / suggestions about the project structure.

And in the report you could simply list your files / folders.

I do not know if there is an "elegant" organization. You could place a DApp/ folder inside your Truffle project folder, together with contracts/, tests/ etc etc. For the purposes of the project I think is enough. For bigger projects then I think it is like to structure a complete web application