
Quote from rocote on March 13, 2020, 11:14 pmHi everyone...
I have done it! This is my first application with VisualNeo Web.
It is not too complicated, but I'm still proud of the result.
Since I'm doing lots of Music Videos, it was logical to created a Video Application for my needs.
In this video, I show the process to compiled my application to a standalone desktop application with VisualNeo Web.
I would say this... I didn't accomplish this without any help. But any programmer knows that patience and discipline is needed.
By asking questions, I did receive the information I needed to know so I could do what I needed to build. :)
In the video, I show what the application can do. It is not much, but it is nice even if it is not finished because it will grow up with time.
Thanks!
Hi everyone...
I have done it! This is my first application with VisualNeo Web.
It is not too complicated, but I'm still proud of the result.
Since I'm doing lots of Music Videos, it was logical to created a Video Application for my needs.
In this video, I show the process to compiled my application to a standalone desktop application with VisualNeo Web.
I would say this... I didn't accomplish this without any help. But any programmer knows that patience and discipline is needed.
By asking questions, I did receive the information I needed to know so I could do what I needed to build. :)
In the video, I show what the application can do. It is not much, but it is nice even if it is not finished because it will grow up with time.
Thanks!

Quote from rocote on March 13, 2020, 11:23 pmLuis, I don't understand why after compiled my application and running it with NWJS.App, the screen app is very large. Actually, it takes all the screen instead of only showing the application screen.
Take a look of this video.
Luis, I don't understand why after compiled my application and running it with NWJS.App, the screen app is very large. Actually, it takes all the screen instead of only showing the application screen.
Take a look of this video.

Quote from luishp on March 14, 2020, 11:19 amCongratulations @rocote !
About window size you may need to do some manual adjustments depending on your target operating system.
Just open the generated package.json file in a plain text or code editor and change the width and height values until you are satisfied with the result. I don't have any Mac or Linux system so I have not noticed the problem.
Thank you!
Congratulations @rocote !
About window size you may need to do some manual adjustments depending on your target operating system.
Just open the generated package.json file in a plain text or code editor and change the width and height values until you are satisfied with the result. I don't have any Mac or Linux system so I have not noticed the problem.
Thank you!

Quote from rocote on March 14, 2020, 2:51 pmNice, I will look after this for sure. You know, it only happening when compile for Mac but for windows, it works good.
I will let you know if I find a fix for it.
Thanks Luis!
Nice, I will look after this for sure. You know, it only happening when compile for Mac but for windows, it works good.
I will let you know if I find a fix for it.
Thanks Luis!

Quote from rocote on March 14, 2020, 11:52 pmHi Luis, you wrote this: Just open the generated package.json file in a plain text or code editor and change the width and height values until you are satisfied with the result.
I did what you offered me. I edited the package.json file with a text editor for Mac, and despite the changes I made, nothing happened. The window was always the same size.
On the other hand, I was successful in changing the coordinates in VisiualNeo Web and subsequently I made another "compile" of my application.
Was i doing something wrong? I do not know. But what counts Luis is that I practically solve my problem anyway.
I still have to work on the coordinates of the main "container" and the parent "container".
Thank you
Hi Luis, you wrote this: Just open the generated package.json file in a plain text or code editor and change the width and height values until you are satisfied with the result.
I did what you offered me. I edited the package.json file with a text editor for Mac, and despite the changes I made, nothing happened. The window was always the same size.
On the other hand, I was successful in changing the coordinates in VisiualNeo Web and subsequently I made another "compile" of my application.
Was i doing something wrong? I do not know. But what counts Luis is that I practically solve my problem anyway.
I still have to work on the coordinates of the main "container" and the parent "container".
Thank you

Quote from luishp on March 15, 2020, 12:06 pmI did what you offered me. I edited the package.json file with a text editor for Mac, and despite the changes I made, nothing happened. The window was always the same size.
That's not possible. The way NWjs works is loading that file first to know how to open your app in a window. Are you sure you saved the changes in the correct path (package.nw)?
On the other hand, I was successful in changing the coordinates in VisiualNeo Web and subsequently I made another "compile" of my application.
VisualNEO Web just write the options to package.json. It's just the same, there is not any magic.
I did what you offered me. I edited the package.json file with a text editor for Mac, and despite the changes I made, nothing happened. The window was always the same size.
That's not possible. The way NWjs works is loading that file first to know how to open your app in a window. Are you sure you saved the changes in the correct path (package.nw)?
On the other hand, I was successful in changing the coordinates in VisiualNeo Web and subsequently I made another "compile" of my application.
VisualNEO Web just write the options to package.json. It's just the same, there is not any magic.

Quote from rocote on March 15, 2020, 5:39 pmHi Luis, here is the result when editing package.json (see video)
This is what I understood you asked me to do.
Roger
Hi Luis, here is the result when editing package.json (see video)
This is what I understood you asked me to do.
Roger
Uploaded files:

Quote from luishp on March 15, 2020, 9:27 pmHi @rocote,
You are doing it right. The only explanation I can think on, is the previous value being cached.
Anyway this is a NWjs related issue more than a VisualNEO Web one.
VisualNEO Web just provides a convenient way to generate the package.json file and adds a small script to the end of the index.html file to allow AngularJS to work properly under NWjs. That's all.
Sorry.
Hi @rocote,
You are doing it right. The only explanation I can think on, is the previous value being cached.
Anyway this is a NWjs related issue more than a VisualNEO Web one.
VisualNEO Web just provides a convenient way to generate the package.json file and adds a small script to the end of the index.html file to allow AngularJS to work properly under NWjs. That's all.
Sorry.

Quote from rocote on March 16, 2020, 12:03 amSo when I modify the H and W values of the package.json file, they do not really affect the software because these new values are not found in the script at the end of "index.html"? But you did really think they would find their way around?
Right?
However, these values could be changed in VisualNeo Web because during compilation, the software builds a new file "index.html". And because of this, the values take effect as such. Right?
And that's what happened with me. Right?
It's ok Luis. I knew there was no magic but that there was something that was not working well. Now I understand why.
So when I modify the H and W values of the package.json file, they do not really affect the software because these new values are not found in the script at the end of "index.html"? But you did really think they would find their way around?
Right?
However, these values could be changed in VisualNeo Web because during compilation, the software builds a new file "index.html". And because of this, the values take effect as such. Right?
And that's what happened with me. Right?
It's ok Luis. I knew there was no magic but that there was something that was not working well. Now I understand why.