> On Apr 21, 2017, at 9:59 AM, Chip Scheide <4d_o...@pghrepository.org> wrote:
>
> What does this project method look like?
>
> Case of
> :(form event=)
> case of
> :(Last object = )
> do stuff
Example below. All calls to Form event in the database are replaced with a
wrapper
What does this project method look like?
Case of
:(form event=)
case of
:(Last object = )
do stuff
On Fri, 21 Apr 2017 07:49:11 -0500, John DeSoi via 4D_Tech wrote:
> I recently embarked on an automated testing project and implemented
> the advantages you mention by
I have asked for - repeatedly -
4D to give us an automated means to "fix" this.
http://forums.4d.fr/Post/EN/8282868/1/8282870#8282870
(15 votes from 2012)
Basically - a means to change unchanged object names (variable1, Field3
etc) to AT LEAST the variable name,
but with an option to pre/post
I recently embarked on an automated testing project and implemented the
advantages you mention by automatically generating *one* project method per
form that contains all of the object method and form method code. The only
other task was to create wrappers for Form event and OBJECT Get pointer
Kirk,
Interesting approach. And your remark about deleted methods rings a bell ...
> Something this won't catch that Josh's VC did is deleted methods...
Yes, the vc-framework handles deleted methods for export. It means if I delete
a method in 4D the former exported text file with the code is
Tom
I handle forms in my version control. I use a method to get all form objects
into an object-its an object of my own format…here is a sample below. Pretty
extensive. I have code to pack and unpack the form objects so i can compare
current version of a form with the last one (not using diff)
> Do your apps use 4D forms? If so, how do you deal with them with respect to
> version
> control?
No, our approach doesn't cover forms, it is usable only for methods like
project methods, object methods, form methods, short: all methods editable in
the method editor of 4D.
Since our
Lutz writes:
>we use a modified version of the mentioned vc-framework component. It saves
>all changes in the code to text files
>immediately and keeps track of the timestamps of the changes in an external
>database. The text files can be
>committed to a source code versioning tool like svn,
Hi Nigel,
basically I'm interested, we are following a similar approach. I should explain
it a bit.
At first we use a modified version of the mentioned vc-framework component. It
saves all changes in the code to text files immediately and keeps track of the
timestamps of the changes in an
Actually there is
code analysis component free
Dani Beaubien
And
Archive Method(?) commercial it's foundation App Store
Robert Livingston
You should be able to find them with those details.
I've used both but I prefer Code Analysis component. .
Cheers
Wayne
On Thu, 20 Apr 2017 at 20:37,
> how does one get access to the 4D source code outside of 4D? Is there a
magic command to get 4D
> to regurgitate its code into plain text?
I was talking about the code in your database, which is accessible (read
and write) using the commands described here:
Luiz
I have a nice set of code that exports the code, including the forms(as
objects),and all the database settings including table structure, and
maintains a history(in an external database) of everything using a modified
DIFF . I would be happy to give you a copy of my component(including
> 1 - how does one get access to the 4D source code outside of 4D? Is there a
> magic
> command to get 4D to regurgitate its code into plain text?
METHOD GET CODE
Since V13
Than you can do what you want with the text. An example is the VC-Framework
component by J. Fletcher:
David -
On Apr 20, 2017, at 3:42 AM, David Adams wrote:
> From: David Adams >
>
> Forgot to say specificallyyou can do a whole lot of Very Good Things
> with an integrated code scanner. Things that the 4D compiler does not do,
> and much more:
Forgot to say specificallyyou can do a whole lot of Very Good Things
with an integrated code scanner. Things that the 4D compiler does not do,
and much more:
* Check that method names passed as strings are valid.
* Check that parameter lists are not too long or too short.
* Confirm that
First up, thanks to Wayne for starting this thread and for being a Good
Citizen and providing code to match. Also thanks to Bruno for expanding the
context for talking about automatic documentation. As it turns out, this is
all related to one of my more recent proof-of-concept pieces. (For the
Oops!
I forgot this bit:
// Threadsafe?
METHOD GET ATTRIBUTES($MethodNames_at{$CurrentMethod_i};$Attributes_o)
$ThreadSafe_t:=OB Get($Attributes_o;"preemptive")
Case of
: ($ThreadSafe_t="capable")
$ThreadSafeSection_t:="\rPREEMPTIVE\r"
: ($ThreadSafe_t="incapable")
17 matches
Mail list logo