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 the API
interface. Or so it seems. The inner workings of GitHub are still a bit
mysterious to me and and the API docs didn't do anything to clarify it for
me. But it seems like something that's doable.

On Sat, Oct 20, 2018 at 1:47 PM Robert ListMail via 4D_Tech <
4d_tech@lists.4d.com> wrote:

> 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
> to be that we can not pull a version from a Git repository and integrate
> that back into 4D. I assume that’s coming to a 4D version near you, but as
> I understand it, we don’t have that ability just yet. It’s a one way street
> although a very welcome one.
>
> FWIW,
>
> Robert
>
> > On Oct 19, 2018, at 6:28 PM, Kirk Brooks via 4D_Tech <
> 4d_tech@lists.4d.com> wrote:
> >
> > Did I just hear you say something about uploading direct from 4D into
> > GitHub... 🙄
>
> **********************************************************************
> 4D Internet Users Group (4D iNUG)
> Archive:  http://lists.4d.com/archives.html
> Options: https://lists.4d.com/mailman/options/4d_tech
> Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
> **********************************************************************



-- 
Kirk Brooks
San Francisco, CA
=======================

*We go vote - they go home*
**********************************************************************
4D Internet Users Group (4D iNUG)
Archive:  http://lists.4d.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Unsub:  mailto:4d_tech-unsubscr...@lists.4d.com
**********************************************************************

Reply via email to