How to properly share your project's source code
Quote from luishp on March 4, 2021, 1:34 pmWhen working with very simple projects, with no dependencies, images or any other files, you can just share your .neoapp file to anyone you want to be able to edit it within VisualNEO Web.
But for most projects, you will need to share quite more files if you want your app to to work properly. In this case it's not enough just compress all of them in a .zip file, because once uncompressed the paths may vary in the target computer.Then, how do we properly share our project's source code?
Just go to "Project > Archive/Backup > Arhive to .zip file" menu and let VisualNEO Web do the job for you.
All necessary files (images, icons, css, js...) will be copied to a .zip file and the paths will be modified so they can be used in any other computer once unzipped.Did you know about this useful functionality? :)
When working with very simple projects, with no dependencies, images or any other files, you can just share your .neoapp file to anyone you want to be able to edit it within VisualNEO Web.
But for most projects, you will need to share quite more files if you want your app to to work properly. In this case it's not enough just compress all of them in a .zip file, because once uncompressed the paths may vary in the target computer.
Then, how do we properly share our project's source code?
Just go to "Project > Archive/Backup > Arhive to .zip file" menu and let VisualNEO Web do the job for you.
All necessary files (images, icons, css, js...) will be copied to a .zip file and the paths will be modified so they can be used in any other computer once unzipped.
Did you know about this useful functionality? :)
Quote from Gaev on March 4, 2021, 11:25 pm@luishp
Thanks for the tip.
Can the archived (.zip) file be uploaded to our website, unzipped and then run (test) the App from there ? ... if so, it would save a few steps when testing Apps from the C: drive hit the CORS wall.
Even better, if the .zip could be uploaded to the Google Drive.
Thanks for the tip.
Can the archived (.zip) file be uploaded to our website, unzipped and then run (test) the App from there ? ... if so, it would save a few steps when testing Apps from the C: drive hit the CORS wall.
Even better, if the .zip could be uploaded to the Google Drive.
Quote from luishp on March 5, 2021, 1:36 pmCan the archived (.zip) file be uploaded to our website, unzipped and then run (test) the App from there ? ... if so, it would save a few steps when testing Apps from the C: drive hit the CORS wall.
No @gaev, this is for sharing the source code not the compiled app. For testing you can just zip and upload to your web server the compiled app. Or perhaps I'm not understanding you very well, sorry.
Can the archived (.zip) file be uploaded to our website, unzipped and then run (test) the App from there ? ... if so, it would save a few steps when testing Apps from the C: drive hit the CORS wall.
No @gaev, this is for sharing the source code not the compiled app. For testing you can just zip and upload to your web server the compiled app. Or perhaps I'm not understanding you very well, sorry.