Digital Workshop

Opus v6 which will be available via general release later this month. In the meantime, as a taster, here is a sample publication illustrating a few of the highlights - particularly the new drawing functions.

Paul Harris

Paul

The graph tools look fantastic: are they scriptable? I've been having to use flash to create graphs; I am hoping I can now do data charting from within Opus. Okay I understand you may not want to say more now. After a long hiatus, I may just upgrade and start using Opus again.

looking forward to the release,

Brian

The graphs are examples of the new drawing script functions so, yes, you can script what you need.

We considered a "graphing function" based around these functions but this way it is much more flexible and the program doesn't get too bulky.

These examples use simple hand-filled variables but obviously you can connect to a data source or an array. The publication will be available as an imp file with Opus so you can see how this works.

The DLL support should also help Opus expand in specific directions without imposing too much overhead.


Paul

Hi

Working on a project that would benefit from the drawing tool in V6 (Pro XE), I wondered if

(1) drawn line or object attributes, like size, color, x,y position, angle, etc. can be saved so the line or object can later be reset on the page upon reload?

(2) in the case of circles, square, other shapes, custom shapes/images can be added by the pub author?

(3) these objects can be dragged, dropped or deleted by the user in runtime?

(4) are fully scriptable?

Kind Regards,

Looks great, like new features.

Will the editor support Windows Vista. Currently waiting on Digital Workshop and Adobe to update their software before I make the move over to Vista.

just to let you know. the Mouse cusor is missing on my computer..

running
amd 64 3200 1024mem, windows vista utimate.

mark

turn off Aero and see if the cursor comes back.

Paul

I think this is the more a problem with the default cursor in Vista. I've been having this problem and and found that by using the Vista cursors under XP that they also disappear.

MY work around is to change the cursor that the Opus Pub uses to one from the Windows/cursor folder or better still switch the cursor set in Vista bask to one of the original XP / standard sets.

I'm not sure what it is with the vista cursors as I can't open them into my icon editor program, it just crashes. I'm going to look at them this week in PS and see whats causing the problem.

Mackavi

Vista, will the cursor problem be fixed by the final release of Opus 6.

I understand that it is a Vista issue and Microsoft has changed something with there new antialias aero cursors, but can Opus work around it automatically on build as I do not think my customers will be pleased if I tell them to turn off Vista cursors and use XP non-antialias cursors.

On the topic of Vista will high quality Vista icons be supported in Opus 6, I have long noticed that Opus has never played nice with antialias icons, even under Windows XP. Can we expect support for 256x256 PNG Compressed Icons in Opus 6.


You can download the Windows Aero Cursors here:
http://www.winmatrix.com/forums/index.php?showtopic=9155

Vista Icons:
http://www.vistaicons.com/icon/i124s0/vista_style_icons.htm
http://msdn2.microsoft.com/en-us/library/aa511280.aspx
http://www.axialis.com/tutorials/tutorial-vistaicons.html

The publication runs fine here. No problem with cursors under Aero. I suspect it is a graphics driver issue.

Obviously v5 grew up with XP technology so we can't really expect it to perform flawlessly. Any issues which crop up once v6 is released will be worked through with you on a case by case basis as usual but in my experience it will probably be driver related. Multimedia applications have always pushed the system to it's limits and will always highlight weaknesses in new or legacy drivers and this seems painfully true for Vista at the moment.

Just for the record, if you do need to report Vista problems we will need to know the system details (especially graphics card) and, specifically whether it is a system which has been upgraded to Vista or had Vista factory-installed.

I'm not sure the cursors you link to are actually Aero cursors or graphically similar. Aero elements have an shine/flare to them which these lack. But these work with Opus 6. As do the full Aero cursors and semi-transparent windows work too.

Hope this helps.

Paul Harris

Like most developers, I use high spec computers and have no problem with Vista of any flavour. However, there is a significant (and increasing) proportion of new computer users with mass produced notebooks from the usual large manufacturers.
These manufacturers do not respond quickly to driver issues, sometimes never updating drivers for a particular model because models change frequently, and sub standard video hardware cannot be swapped out of a Notebook. Vista is being pushed aggressively onto these machines.

If a user of a pub complains about a graphics issue, I don't want to have to tell him/her that it's their fault because they purchased a cheap Notebook, especially if none of their other installed applications have any problems.

I think Opus is a great, unique product that is well designed and implemented, but don't make it too "bleeding edge" -- it's not in anyones interest if some pubs have graphics issues, however minor, on the average Notebook being purchased by todays more mobile user.

Paul

I understand what you're saying but that's the whole problem. We're not adding any greater bleeding edge to Opus than it already has but Vista does.

The drivers will support the fundamental calls - hence the fact that most applications work. But Opus allows you to choose options which are used less widely and are therefore a low priority for driver development. For example, chromakey video support under Vista might not be important enough for an OEM of business laptops - as long as Media player works that'll be good enough for most people.

Should we restrict what you can do in Opus because its not yet supported on Vista on some systems when those things work perfectly under XP? We surely don't want to make v6 a downgrade to ensure it is universally Vista compatible and then upgrade again each time there's a step change in the quality of Vista support.

To me the solution is to counsel caution when creating publications for Vista in the short term. Don't do too much and allow for plenty of testing and tweaking. We're highlighting some of the potential difficulties in the documentation for v6.

I may be exaggerating the problem - very few things are simply no longer supported by Vista at all and we've only found a few problems with the rest. I'm just trying to manage people's expectations - Opus already lets you push the envelope. For the time being the Vista envelope may be a little smaller

Paul

Thanks Paul,
A lot of good insight there.
I appreciate your opinion and will follow your advice.

cheers
Paul

It has always been a bone of contention with designers (usually authoring on ultra fast machines, latest hi spec graphics cards and with more memory than you can shake a stick at) producing media rich publications that play beautifully on their machines but come to a shuddering halt on lesser PC's.
We always had a min spec pc for testing - and found that the "lowest common denominator" approach worked best.
As machines got better - we lifted the bar.
For more specific projects - we would test specifically on client machines.
Not ideal - but at least we werent just churning stuff out that didnt work.
I think this is an issue that will never go away and as with the roll out of XP - has raised it's ugly head again with VISTA.
Why dont we all go back to 3.1????

The problem with "lowest common denominator" computers is that it's a moving target.
I've dropped all support for any form of Windows 98/ME, computers older than Pentium lll (that goes next) -- and life got easier with less support hassles and insignificant loss of revenue.
Old computer owners (I mean the computer is old, not the owner ) don't like spending money (or they haven't got it to spend) on computer software.

Paul