Re: FlowStudio
Posted: Tue Oct 15, 2019 3:50 pm
The Cross-Platform Multimedia Application Layer
https://forums.hollywood-mal.com/
I use APPBuilder to compile HW apps, but I do run my scripts from FlowStudio. After creating Project and adding a script file to it, go to Workspace --> Project Settings. In the Build tab, write this as Build Command: Hollywood:System/Hollywood -debugdevice @stdout yourscript.hws. I have Makefile Creation "None" and selected "Quiet build" and "Automatically save modified files before building" boxes.
If you plan on developing for AmigaOS 4.1 and AROS as well as MorphOS, use CubicIDE. If you're developing on MorphOS for MorphOS, use FlowStudio because it comes from the MorphOS team and works well on MorphOS. If you are developing on Windows, Linux or Mac and don't mind using VS Code, download the Hollywood plugin for that instead. Of all of the above the auto-code-complete feature of VS Code and its open source counterparts puts it well ahead of the others.amigadave wrote: ↑Thu Sep 10, 2020 7:24 pm I'm currently only using Windows to play with Hollywood programming, but my original intentions have always been to do my programming on MorphOS, using Cubic IDE, which I purchased at full price years ago. (edit: I'm the kind of person who likes to use things that I have paid for, if they are still useful, even if better, or different solutions become available to me in the present. I'd like to use Cubic IDE, just because I paid for it, unless Flow Studio is significantly better, or because Flow Studio is still under development, it will be better for me to learn using it now, instead of learning Cubic IDE, and later needing to switch, and learn Flow Studio in the future)
Is Flow Studio a better choice now, or is Cubic IDE still a good choice for programming in Hollywood on MorphOS? Can anyone with experience using both on MorphOS please describe the Pros and Cons of both Flow Studio and Cubic IDE on MorphOS to me?
That works, for running the project.emeck wrote: ↑Mon Sep 20, 2021 10:43 pm After creating Project and adding a script file to it, go to Workspace --> Project Settings. In the Build tab, write this as Build Command: Hollywood:System/Hollywood -debugdevice @stdout yourscript.hws. I have Makefile Creation "None" and selected "Quiet build" and "Automatically save modified files before building" boxes.
You would make the build command: Hollywood:System/Hollywood yourscript.hws -debugdevice @stdout -compile yourscriptGMKai wrote: ↑Sun Sep 26, 2021 11:00 amThat works, for running the project.emeck wrote: ↑Mon Sep 20, 2021 10:43 pm After creating Project and adding a script file to it, go to Workspace --> Project Settings. In the Build tab, write this as Build Command: Hollywood:System/Hollywood -debugdevice @stdout yourscript.hws. I have Makefile Creation "None" and selected "Quiet build" and "Automatically save modified files before building" boxes.
Any hints on the "blue play"-button, that maybe starts a created executable, how can that be used in a Hollywood-context?