Standalone Building

[Klaus on-rev]

Hallo Wilhelm,

> Richard  wrote:
>
>> For lazy people like myself, the link to that report is:
>> <http://quality.runrev.com/qacenter/show_bug.cgi?id=2217>
>>
>>  The full sentence in which RunRev's Oliver Kenyon suggested the  
>> need for an engine change is worth noting:
>>  To fix the issue, we will need to make an engine change, possibly
>>  the addition of a "repeat for each control" loop form.
>>
>>  So rather than something irritating, it's actually quite cool:  
>> imagine if we had the ease of iterating through controls so simply.  
>> Nice stuff - glad to see they're thinking along those lines.
>
> I did not grasp the meaning of this "engine change" at first, I had  
> been too afraid that we could run into troubles when trying to cope  
> with an engine change.
>
> In the meantime I have used the patched stack  
> "RevStandaloneSettings" along with the additional command "set the  
> cREVKeepDevelopmentProperties of this stack to true".  Standalone  
> building in the Rev IDE with these changes is now nearly as fast as  
> in the MC IDE. The option of decreasing stack size by removing  
> development properties added by the Rev IDE could and should IMO be  
> implemented in the form of a tool separate from the standalone- 
> building process.
>
> For the Metacard IDE this could mean that we integrate command "set  
> the cREVKeepDevelopmentProperties of this stack to true" into our  
> Standalone Builder - possibly in form of a checkbox button - with  
> the default setting to true.

I can add as many checkboxes as you like :-), but what exactly should  
this one be good for?
This property "cREVKeepDevelopmentProperties" has no meaning in MC,  
but maybe I am misunderstanding you?

> I have responded to Oliver Kenyon's comments directly and as a newly  
> added comment to bug report #2217. See the address Richard provided  
> above-
>
> Best regards,
>
> Wilhelm Sanke

Best

Klaus

--
Klaus Major
http://www.major-k.de
klaus at major.on-rev.com