Re: 4D Structure Export...

Thanks for the response Lutz. This is very helpful and increases my confidence that we will be able to provide a solution. Tom Benedict > On Jan 11, 2019, at 01:14, Epperlein, Lutz (agendo) via 4D_Tech > <4d_tech@lists.4d.com> wrote: > > Hi Tom, > > The use of the VC_Framework component is

RE: 4D Structure Export...

Hi Tom, The use of the VC_Framework component is completely independent of the version control system. I don't know much about the Team Foundation Server, but in AFAIK it has means to manage the source code. But again, the approach works with 4D and the import functionality of the VC_Framewor

Re: 4D Structure Export...

Hi Lutz, Sorry to bug you again, but we’re moving forward on a project where we are consulting with a client who is setting up an agile development team to use 4D. They will be managing this team with Microsoft Team Foundation Server. I’m thinking that TFS should be able to serve as a repositor

Re: 4D Structure Export...

Hi Lutz, I also need support for Release Management, so I need a way to track version numbers. In the past I have initially written a major version number to a List object in the structure file, then incremented a minor version number every time I run Compile & Build, creating a file copy of

Re: 4D Structure Export...

Thanks for posting the link Lutz. I will dig into it deeper. It looks encouraging. Tom Benedict > On Dec 10, 2018, at 01:26, Epperlein, Lutz (agendo) via 4D_Tech > <4d_tech@lists.4d.com> wrote: > >> Maybe we need to consider moving team development from the centralized 4D >> Team >> Develop

RE: 4D Structure Export...

> Maybe we need to consider moving team development from the centralized 4D Team > Developer model to a distributed model using individual copies of 4D. That > would > match the classic development model and practice which non-4D developers have > enjoyed for decades Is anyone doing > this ye

Re: 4D Structure Export...

> Le 7 déc. 2018 à 23:11, Tom Benedict via 4D_Tech <4d_tech@lists.4d.com> a > écrit : > >> [...] > I see how one would get the modified date for the method using METHOD GET > MODIFICATION DATE, but I don’t see a METHOD GET MODIFIED BY. Thinking that Current user works already on server side…

Re: 4D Structure Export...

Thanks for your comments Kirk. > On Dec 7, 2018, at 11:07, Kirk Brooks via 4D_Tech <4d_tech@lists.4d.com> > wrote: > I'm not familiar with VC_Framework but the big improvement in R3 is the > addition of Form convert to dynamic. This allows you to export all the > forms - not just the object and

Re: 4D Structure Export...

> > On Dec 7, 2018, at 1:07 PM, Kirk Brooks via 4D_Tech <4d_tech@lists.4d.com> > wrote: > > I'm not familiar with VC_Framework but the big improvement in R3 is the > addition of Form convert to dynamic. This allows you to export all the > forms - not just the object and form methods. The object

Re: 4D Structure Export...

Tom, On Fri, Dec 7, 2018 at 10:14 AM Tom Benedict via 4D_Tech < 4d_tech@lists.4d.com> wrote: > if this feature does more than the export we’ve been able to do since > v12/14 via various versions of VC_Framework. Is this simply a higher level > of integration with the app or does it actually offe

4D Structure Export...

There are a couple of recent posts on the 4D Blog related to exporting 4D methods and forms as text as a new feature in v17R3: https://blog.4d.com/text-files-from-your-structure-file/ and https://blog.4d.com/a-component-to-export-the-st