further incompatibilities with Rev

[J. Landman Gay]

On 10/8/04 2:31 PM, Richard Gaskin wrote:

> A new incompatibility has arisen between the 14-year-old MC IDE and the 
> latest version of Rev:  If you've used MC's Resource Mover to copy the 
> answer dialog, ask dialog, etc. into your stack, when you hand that 
> stack to a client to open in Rev they're greeted with an error dialog 
> warning them that stacks with those names are already in memory.

Is this really new? I thought it had been around since Rev 1.0.

> 
> While we've already spent more time than I would prefer accomodating 
> Rev's new behaviors, it may be simpler for us to simply accept being 
> forced into doing the extra work of integrating the Resource Mover with 
> the Standalone Builder as Rev does to accomodate its new behaviors.
> 
> What are the pros and cons of copying resources only into standalones?

If you mean removing the resource mover, then I'm not keen on doing 
this, as it eliminates the control we have that is the main reason we 
use the MC IDE in the first place. I'd prefer to just continue omitting 
these dialog stacks unless I'm building a standalone.

The cons, of course, are that if you move these resources into your own 
stack without building a standalone, then you hit the conflict you 
describe. It requires that we make a copy of our stack and insert the 
resources just before building a standalone, or else that we continue to 
run the stack only in the MC IDE where the conflict doesn't occur for 
some reason.

It's funny that we can have duplicates of the answer dialog in MC but 
not in Rev. Maybe the solution is to figure out why Rev can't do the same.

> 
> Of course the long-term solution is to get rid of the uniquely 
> Transcript limitation of stack name conflicts, as requested in 
> <http://support.runrev.com/bugdatabase/show_bug.cgi?id=1061>.

This would be ideal, for many reasons.

> But in the meantime how can we best accomodate others in our workflow 
> who use Rev?

Well, that's the main problem I guess. I'm not sure. I solve it here 
personally by simply not including those dialog stacks until I am ready 
to build a standalone.


-- 
Jacqueline Landman Gay         |     jacque at hyperactivesw.com
HyperActive Software           |     http://www.hyperactivesw.com