I’ve created this topic to provide an area where you can feedback any suggestions you may have for improving the new SAFE Network - DevHub. We’re working on making it as good as it can be and we’d like your input.
Please feel free to suggest anything (within reason ) but please have a little read of any existing suggestions first to avoid duplication. I’m not going to say that we’ll implement everything but we’ll certainly consider all reasonable ideas.
hmhmmm - i would love to have a link to the newest peruse release on the front page …
…i literally just spent ~5 minutes looking for the right link to the latest version (okay - a laggy internet did slow me down a bit too … but still … i do exactly know what i’m looking for … new people won’t …) … on maidsafe.net there is just the safe browser linked and in this forum there are a lot of mentions of peruse but it’s not always linked …
First I should say that I think the existing lesson is very good, and most ‘real’ devs would not find too many problems, but for us lesser mortals, there are still a few pitfalls.
So first, how about providing a simple ‘hello world’ type example as suggested in this thread?
Second, it would be helpful to beginners for the tutorial to be a little more instructional. There are lots of places where mistakes can be made, an obvious one being a failure to set the NODE_ENV to dev in the correct consoles (easily done if you start the browser from the file manager rather than the CLI too…). Also, there is the ever-present problem with node and npm versions, with different Linux distros seemingly having different requirements. Some of these issues could be avoided by spelling out the procedure and noting down where errors might occur.
For the SAFE Desktop App Tutorial, after a beefed up prerequisites section, I would suggest something like this (these are only partial instructions obviously):
Open three console windows or tabs in the folder where you want to build the app (e.g. /home/user in Linux ).
Download SAFE Browser Mock Routing zip file into that folder and unzip to extract the contents. We now need to do three different operations, one from each of the consoles.
Start the browser and set up an account.
First set the node environment to dev: $ export NODE_ENV=dev
or in Windows
$ set NODE_ENV=dev
Now start SAFE Browser in Console 1 with:
$ safe_browser.../safe_browser [or Windows equivalent]
[Instructions on setting up an account etc etc]
[What to do if you get stuck here]
In Console 2 we will clone the repo which contains the boilerplate using git onto a local folder named safe_examples :
I’v tried the ‘SAFE Web App Tutorial’ and I think it is a good introduction!
Feedback (nitpicks) I didn’t see in the posts above:
Maybe describe somewhere how to test with a seperate local webserver (e.g. ‘python3 -m http.server 5000’ on Linux) -> more freedom in testing self made examples in my opinion.
Is there a use case of the mockup SAFE Browser without the NODE_ENV variable set to ‘dev’, which is the default setting now? And if yes: is the estimated use case bigger than with NODE_ENV=dev? Because if not, maybe an idea to change the default setting of the mockup SAFE Browser, if possible.