Digital Workshop

I rest my case, the program has been hijacked by the code junkies who have absolutely no comprehension of the needs of the core multimedia application builders - educational or otherwise. Opus is a tool to be used to produce a product which can be sold. It is not our hobby or a way of demonstrating our superior technical knowledge.

(I just want to drive my car, I don't want to know how it's built or to get involved in building it myself. I dont even want manual transmission anymore the world has moved on to automatic transmission and air-conditioning).

Opus is by far the best platform available today to design and produce multimedia content. Only the output format requirement has changed. When the demand moved from exe files to HTML5 Opus was quick to respond and the program is now so close to being user friendly enough to capture an enormous no-code market who are looking for a way of producing auto-resizing content for web use or as the content for Apps.

Please Opus don't listen to the vocal minority who think that we don't need the facility to edit all header content within the program, easy favicon implementation, output to HTML instead of HTM, App-caching for web-app offline content and so forth.

Wow.

Perhaps you'll explain a couple of points...

1. How does a no-code market fit with an application that allows editing header content which surely in itself requires technical knowledge?

2. How simple do you want to make Opus with the easy favicon when either the unofficial put it in the folder method or adding a single line of code to Opus' head includes box is too complicated for a professional application.

3. What does .html have to do with my Opus applications?

4. How is App Caching basic HTML5 functionality?

I'm not objecting, I'm happy to have any features that make Opus more usable to a wider audience but you appear to be criticising Opus for its choice of advanced functionality and my understanding of it - and yet requesting your own.

Mack - the code junkie sat in the corner waiting to dance

The original Opus customer-base were developers of applications designed to impart information in an interactive visual and audio format. Educators and Windows exe program producers loved the program and embraced it in a big way. They still do.

Now that the world has moved it's emphasis from Windows desktop PC's (exe files) to mobile devices running various other operating systems. Developers are now using HTML5 to present their interactive content either online as a web page or online as a webapp which downloads and stores the content to your device so it runs as a native (installed) app when the internet is not available. Or porting the HTML5 content to an Android or Apple App maker which packages the interactive content as a native app for distribution via any of the app stores.

Opus does amazingly simple to produce interactive content without the need to learn coding and also has the facility to add script to allow programmers to add features that are not basic Opus drag and drop functions. Multimedia program developers want to be able to produce usable HTML5 with the same ease as the rest of the Opus platform. This would mean adding simple tabs to the publish options for things like page title, generator, description, analytics code, favicon, add to desktop, copyright, App-caching offline content, HTML or HTM etc.

This would bring Opus back to centre stage, this time as the world's best program for producing 'APPS' and 'Interactive Internet Content'. Multimedia which is sensitive to the device screen size and resizes itself accordingly.

Nothing else currently does this - without the need for employing an IT professional to bring the project content and the distribution package together.

Mallette,

How were you able to combine the Opus email code with the code mackavi sent you? Thanks