Hi friends,
Wilhelm Sanke wrote:
This may have been already noticed here, I just want to make sure:
The Rev Standalone files - necessary to build standalones - of
versions 4 dp3 and dp4 do not work with the Metacard Standalone
Builder. Version 3.5 does.
Mark Waddingham mentioned to me
Klaus Major wrote:
Hi friends,
Wilhelm Sanke wrote:
This may have been already noticed here, I just want to make sure:
The Rev Standalone files - necessary to build standalones - of
versions 4 dp3 and dp4 do not work with the Metacard Standalone
Builder. Version 3.5 does.
Mark Waddingham
Am 07.10.2009 um 09:49 schrieb Richmond Mathewson:
Klaus Major wrote:
Hi friends,
Wilhelm Sanke wrote:
This may have been already noticed here, I just want to make sure:
The Rev Standalone files - necessary to build standalones - of
versions 4 dp3 and dp4 do not work with the Metacard
Klaus Major wrote:
Am 07.10.2009 um 09:49 schrieb Richmond Mathewson:
Klaus Major wrote:
Hi friends,
Wilhelm Sanke wrote:
This may have been already noticed here, I just want to make sure:
The Rev Standalone files - necessary to build standalones - of
versions 4 dp3 and dp4 do not work
Epsecially sic transit gloria mundi.
Love, Richmond.
___
metacard mailing list
metacard@lists.runrev.com
http://lists.runrev.com/mailman/listinfo/metacard
Hi Richmond,
Klaus Major wrote:
Am 07.10.2009 um 09:49 schrieb Richmond Mathewson:
Klaus Major wrote:
Hi friends,
Wilhelm Sanke wrote:
This may have been already noticed here, I just want to make
sure:
The Rev Standalone files - necessary to build standalones -
of versions 4 dp3 and
Thanks for the clarification about a new process for standalone building
in Rev version 4.
From Richard's quote of the v4 engine change log:
In order to achieve this, it has been necessary to implement the core
operation of standalone building in the (ide) engine. This means that
the
An addition to my last post:
I found more detailed data about the creative involvement of Monte
Goulding in 2004 in the Read about Standalone Builder bug (Bugzilla
2217)-text where I quote from a post of mine to the improve-revolution
list on Sept 20th, 2004 (See stack Testcolors 1600 in file
Another additional remark:
I just looked at Bug report 2217 which I sent on Sept 20, 2004, five
years ago.
Report #2217 New troubles with standalone building and players for
multi-fields stacks is still labeled as new
A last commentary from my side had been added two years later
Comment
Wilhelm:
IF the new standAlone builder forces the inclusion of spurious development
properties to each control, I for one shall not be upgrading. At present,
at least we can set the custompropertysets to remove any spurious rev-IDE
crap if migrating a stack from RevIDE to MC-IDE, but if it becomes
Hi Hugh,
Wilhelm:
IF the new standAlone builder forces the inclusion of spurious
development
properties to each control, I for one shall not be upgrading. At
present,
at least we can set the custompropertysets to remove any spurious
rev-IDE
crap if migrating a stack from RevIDE to MC-IDE,
Hugh Senior wrote:
Wilhelm:
IF the new standAlone builder forces the inclusion of spurious development
properties to each control, I for one shall not be upgrading.
Rev doesn't add development properties during the build (unless you
choose to include libraries), it just checks each control to
Hi Wilhelm
I remember the workarounds I did to speed it up. It was interesting to
me at the time to fine the issue was the difference between:
fast - having a stack open (toplevel invisible) and recursively
parsing through it's objects and having the
slow - parsing through the objects of a
13 matches
Mail list logo