Re: Help->v11 to v17 Upgrade or New?

On Oct 23, 2018, at 2:00 PM, Tom Benedict wrote: > Dani Beaubien writes: >> >> I use the external git client for diffs against historical commits and I use >> the >> Code Analysis component for diffs between what is in the 4D structure >> compares against the last export to the external folder.

Re: Help->v11 to v17 Upgrade or New?

Dani Beaubien writes: > >I use the external git client for diffs against historical commits and I use >the >Code Analysis component for diffs between what is in the 4D structure >compares against the last export to the external folder. We did a similar thing based on Thomas Maul's MethodHistory

Re: Help->v11 to v17 Upgrade or New?

4D Tech mailing list wrote > I am not uploading directly from 4D. I thought about implementing that but > decided against it since 4D is going that direction them selves. Waiting > to see what they come up with. I understood the same from teh Summit. Anyway, there is an existing module in

Re: Help->v11 to v17 Upgrade or New?

Folks, I would like to suggest you (if you haven’t already) check out a paid product from the Foundation Shell App Store by Robert Livingston for a 4D database solution to storing the text from all your methods and object methods automatically. ArchiveMethod

Re: Help->v11 to v17 Upgrade or New?

I am not uploading directly from 4D. I thought about implementing that but decided against it since 4D is going that direction them selves. Waiting to see what they come up with. My workflow is to use the Code Analysis component to export all my code, 4D Structure and form properties (gathered

Re: Help->v11 to v17 Upgrade or New?

Robert, What I was dropping not-so-subtle hints about is working out the interface for the GitHub API, which I found - unwelcoming, to support exporting directly to GitHub from 4D and allowing me to pull from it as well. All the tools for this are already in 4D, it's just a matter of working out

Re: Help->v11 to v17 Upgrade or New?

Kirk, I think any mechanism that can export 4D code as text (plain text, JSON, XML, etc) can be used via GitHub to at least manage method changes. So, with the new v17r3 we have a native way to share the entire structure which will allow us to use version control. However, the limitations seem

Re: Help->v11 to v17 Upgrade or New?

Hi Kirk, 4D Tech mailing list wrote > Did I just hear you say something about uploading direct from 4D into > GitHub...  It is not what I understood. He used GitHub to manage his version. But, if you're right, I'm also very interested by this ;-) - Patrick EMANUEL

Re: Help->v11 to v17 Upgrade or New?

Dani, On Fri, Oct 19, 2018 at 8:22 AM Dani Beaubien via 4D_Tech < 4d_tech@lists.4d.com> wrote: > I have been using GitHub to track changes on the exported code. I have > projects that go back years that are in GitHub. Did I just hear you say something about uploading direct from 4D into

Re: Help->v11 to v17 Upgrade or New?

In this situation, I use Code Analysis is to find out what code has changed due to the upgrade to a newer version of 4D. Here is an example. I am moving a structure from v16 to v17 and I want to know all the changes that occur. In v16, I use the Code Analysis component to export all the

Re: Help->v11 to v17 Upgrade or New?

About QS_Toolbox, the one I really know, there is a bunch of tools in the Structure Analysis part. It works from V15 to V17, but nothing has been added since V16R6. QS_Toolbox performed very few update for you. Its goal is to identify

Re: Help->v11 to v17 Upgrade or New?

Patrick or Dani, how might your tool help identify what needs to change? R Sent from my iPhone > On Oct 19, 2018, at 2:09 AM, Patrick Emanuel via 4D_Tech > <4d_tech@lists.4d.com> wrote: > > Some tools can help you like QS_Toolbox from me or CodeAnalysis from Dani > Beaubien for example, and

Re: Help->v11 to v17 Upgrade or New?

4D Tech mailing list wrote > So, there are more than 700 lines of code with the deprecated “_o_” > prefix. Perhaps I could make a lot of that go away via Search/Replace (a > feature that I normally don’t use). Some tools can help you like QS_Toolbox from me or CodeAnalysis from Dani Beaubien for

Re: Help->v11 to v17 Upgrade or New?

It was Dani! Yeah, 4D is awesome at this stuff. We get upgrades old, old versions all the time and our current structure just opens these old data files, and 4d does its magic to uid them, unicode them, de'subtable them. no problem. > On Oct 18, 2018, at 2:19 PM, Robert ListMail via

Re: Help->v11 to v17 Upgrade or New?

Okay, I can’t find it now but someone said, "hey pop it into v17 and see if it works…" or something like that. Well, I did just that and without any changes it compiled (after toggling unicode on) and I created a built server and client and ran a few tests. Yes, as I recall, I did fix all of

Re: Help->v11 to v17 Upgrade or New?

Robert, I am just taking on a project for a similar situation: v11 to v17. I haven't had a chance to really dive into the code yet so I'm not really sure what's there but at this point the client's intention is to essentially keep the database on 'palliative care' for the next 1 to 2 years when

Re: Help->v11 to v17 Upgrade or New?

> Le 17 oct. 2018 à 21:45, Robert ListMail via 4D_Tech <4d_tech@lists.4d.com> a > écrit : > > [...] > > Also, the client originally said the new database would not have to migrate > data forward from the old system and now they are wanting to have the data > too. Most of the I write the new

RE: Help->v11 to v17 Upgrade or New?

If in doubt I would vote for a rewrite, even more if the old application is poor designed. We struggle from time to time with problems caused by using legacy 4D code. E.g. sometimes there were assumptions made in the past regarding performance they are nowadays simply wrong and are causing now

Re: Help->v11 to v17 Upgrade or New?

sdale > via 4D_Tech > Sent: Wednesday, October 17, 2018 1:11 PM > To: 4D iNug Technical <4d_tech@lists.4d.com> > Cc: Spencer Hinsdale > Subject: Re: Help->v11 to v17 Upgrade or New? > > > 4D automatically converts Subtables. This should not be a problem. > **

Re: Help->v11 to v17 Upgrade or New?

At some point, v18(?), 4D will completely drop support for subtables. as I understand: a simple conversion to the current version will allow all the functions of existing subtables to continue working -- without -- any change to code. As noted by Tim Penner, but typo-ed :), this applies to a

RE: Help->v11 to v17 Upgrade or New?

> The rest of the conversion needs to be done by the developer and consists of > replacing the subtable commands and redrawing the relationship line. This is > not automatic. See more here: http://livedoc.4d.com/4Dv17/help/Title/en/page3607.html#1693868 What we mean by “change the code

RE: Help->v11 to v17 Upgrade or New?

ts.4d.com> Cc: Spencer Hinsdale Subject: Re: Help->v11 to v17 Upgrade or New? 4D automatically converts Subtables. This should not be a problem. ** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html

Re: Help->v11 to v17 Upgrade or New?

4D automatically converts Subtables. This should not be a problem. > On Oct 17, 2018, at 12:45 PM, Robert ListMail via 4D_Tech > <4d_tech@lists.4d.com> wrote: > > I have an old v11 database running on Windows that’s not particularly > well-designed and where there are more than a few

Re: Help->v11 to v17 Upgrade or New?

This is a very hard question to give any advice on. There are a lot of factors that could affect the decision. Things to consider: - Complexity of the structure (# of tables, forms, methods, etc) - Are there any old style 4D extensions used? - Are there any plugins that are no longer supported?

Help->v11 to v17 Upgrade or New?

I have an old v11 database running on Windows that’s not particularly well-designed and where there are more than a few subtables to deal with. Assuming that there is no additional budget for writing a new clean app, would you likely upgrade or re-write in v17 with the old v11 structure as