search

asticode / go-astilectron-demo

Discover the power of Astilectron through a demo app
MIT License
404 stars 83 forks source link

How should I debug a project during its development?Does the command "astilectron-bundler -v" need to be used every time? #47

Closed ghost closed 5 years ago

ghost commented 5 years ago

How to debug a project during the development process? Do you need to use the "astilectron-bundler -v" command every time? If this is the case, it may take me a lot of time. Is there any good solution?

asticode commented 5 years ago

Once you have executed astilectron-bundler -v for the first time (and if neither electron or astilectron versions change) you don't need to use the bundler to test things out.

All you need to do is go run *.go -v and that should be enough.

Let me know if that works.

ndawg commented 5 years ago

For me, changes in HTML files are only being rendered when the bundler is run. I'm using the bootstrapper with my BaseDirectoryPath set to deps. If I edit the files within deps that are generated, all I need to do is refresh the page. Editing from resources requires re-bundling.

If I don't specify a BaseDirectoryPath, editing within the resources still doesn't make a difference until re-bundling. I'm running with go run *.go -v

asticode commented 5 years ago

@ndawg you're definitely right.

My next idea would be not to use the bundler for development purposes. Would that make sense?

ghost commented 5 years ago

@asticode Problem solved! thank you