Apple, Developer Certificates, Provisioning Profiles
Required reading. There's a lot to read here, and for once, the comments (also written by AgileBits devs) are at least as informative as the original message. https://blog.agilebits.com/2017/02/21/certificates-provisioning-profiles-and-expiration-dates-the-perfect-storm/ -- Mark Wieder ahsoftw...@gmail.com ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Script Editor fixable? (was: Configuring a Sublime Text project to notify LiveCode IDE about updates to script only stacks)
Dr. Hawkins wrote: > More commonly, until and unless livecode can save such that such > standard tools or comparable can be applied, multi-person development > will remain a fantasy and/or novelty. And yet here we are, using an IDE written in LiveCode by a team comprised of dozens of company and community developers working together on a single code base. > I've come to accept that the next major rewrite of my software is > going to have to be in something else (Swift?) so that I can add > developers, as well as the inability to actually put a pdf or eps > on a card (just a bitmap of it won't do); livecode just doesn't > seem to me doing towards such a direction. The Business Edition has already gone that direction: https://livecode.com/products/livecode-platform/pdf-viewer/ Probably at least an order of magnitude cheaper to upgrade to Business than to rewrite the whole thing in Swift from scratch. And with LC you get a cross-platform solution, while even if you did find a GUI framework for Swift for Windows you'd likely be writing a lot of forked code for each platform. -- Richard Gaskin Fourth World Systems Software Design and Development for the Desktop, Mobile, and the Web ambassa...@fourthworld.comhttp://www.FourthWorld.com ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Script Editor fixable? (was: Configuring a Sublime Text project to notify LiveCode IDE about updates to script only stacks)
On Sat, Feb 25, 2017 at 5:05 PM, Mike Kerner via use-livecode < use-livecode@lists.runrev.com> wrote: > I don't think SOS is the main future. I think it gives us another option. I don't think it will *ever* be a full-fledged option until stacks themselves can be saved as text files for use with standard revision control and patching. The most it can due is take a chink out of the corner. And on the value of those . . . As I was nearing the end of my dissertation, and had a visiting spot for the following year lined up, with a $10k difference between waiting for paperwork (assistant prof) and ABD (instructor), my wife had to go to California to help her sister's family during her first cancer. I had to drive out to pick them up, and lost my transmission in Omaha (really, It *does* happen outside of country songs). I had a laptop with an older version of my dissertation with me, and hard-copy of the current version with advisor comments (between two majors in my Ph.D. and working outside the departments, I had three advisors). Because (and only because) LyX and LaTeX are text format, I was able to simply edit the obsolete copy and use diff to make a comparison, and apply patch to the most recent copy, and actually get two days work out of the two days I spent stranded. More commonly, until and unless livecode can save such that such standard tools or comparable can be applied, multi-person development will remain a fantasy and/or novelty. I've come to accept that the next major rewrite of my software is going to have to be in something else (Swift?) so that I can add developers, as well as the inability to actually put a pdf or eps on a card (just a bitmap of it won't do); livecode just doesn't seem to me doing towards such a direction. Yes, I understand the desire to stay true to the hypercard model, but as-is, I don't see livecode as a viable solution to a project larger than the indy limits. -- Dr. Richard E. Hawkins, Esq. (702) 508-8462 ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Script Editor fixable? (was: Configuring a Sublime Text project to notify LiveCode IDE about updates to script only stacks)
Abbreviations that come up in this thread: LC - livecode SE - script editor IDE - Integrated Development Environment OSS - open source software SOS - script-only stack On Sun, Feb 26, 2017 at 8:24 AM, Simon Knight via use-livecode < use-livecode@lists.runrev.com> wrote: > Hi, as someone who came to Livecode attracted by the hook that it could be > used by Subject Matter Experts (SMEs) I try and follow these threads but > please take care with the use of abbreviations / acronyms. Some I’ve > worked out others I’ve no idea : OSS open source S?, SOS ??? or > generally morse code dot dot dot dash dash dash dot dot dot “Save Our > Souls” however it doesn’t read well below ;-) > > My concern with external editors is based on my use of the tRev editor in > the past, which while having some nice features often lost the edits I > made. I have no idea how it communicated with the IDE. > > I agree with your comments re GIT. As a one man band it seems like over > kill in my situation. So I am creating an AutoSave plugin that makes a > backup every few minutes if the scripts have been modified (it has no > knowledge of changes to the UI). It also produces a simple log file that > describes the delta between backups. I am happy to share if it is of any > interest. > > best wishes > > Skids > > Simon Knight > s...@anvic.net > Telephone : 01427 325911 > Mobile : 07963 077071 > Skype : jtidsskids > > > > > On 26 Feb 2017, at 01:05, Mike Kerner via use-livecode < > use-livecode@lists.runrev.com> wrote: > > > > I don't think SOS is the main future. I think it gives us another > option. > > Long before someone learns that technique, they should have the > traditional > > method down, cold, and understand why they would use one or the other. > SOS > > definitely make working on the IDE easier, and they make complicated > > projects easier, but I wouldn't even think of teaching someone who isn't > > already a LC expert about doing it this way. > > > > The one thing to remember about the SOS technique is that Git isn't the > > only option. Git is hard core, and it is hard. I still don't like it, > but > > I am trying to tolerate it. If you're using any cloud syncing tool that > > can keep track of versions (Office365, Gsuite, and Dropbox come to mind), > > you have simple version control/rollbacks/archiving/etc. > > ___ > > use-livecode mailing list > > use-livecode@lists.runrev.com > > Please visit this url to subscribe, unsubscribe and manage your > subscription preferences: > > http://lists.runrev.com/mailman/listinfo/use-livecode > > ___ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your > subscription preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode > -- On the first day, God created the heavens and the Earth On the second day, God created the oceans. On the third day, God put the animals on hold for a few hours, and did a little diving. And God said, "This is good." ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
Re: Script Editor fixable? (was: Configuring a Sublime Text project to notify LiveCode IDE about updates to script only stacks)
Hi, as someone who came to Livecode attracted by the hook that it could be used by Subject Matter Experts (SMEs) I try and follow these threads but please take care with the use of abbreviations / acronyms. Some I’ve worked out others I’ve no idea : OSS open source S?, SOS ??? or generally morse code dot dot dot dash dash dash dot dot dot “Save Our Souls” however it doesn’t read well below ;-) My concern with external editors is based on my use of the tRev editor in the past, which while having some nice features often lost the edits I made. I have no idea how it communicated with the IDE. I agree with your comments re GIT. As a one man band it seems like over kill in my situation. So I am creating an AutoSave plugin that makes a backup every few minutes if the scripts have been modified (it has no knowledge of changes to the UI). It also produces a simple log file that describes the delta between backups. I am happy to share if it is of any interest. best wishes Skids Simon Knight s...@anvic.net Telephone : 01427 325911 Mobile : 07963 077071 Skype : jtidsskids > On 26 Feb 2017, at 01:05, Mike Kerner via use-livecode >wrote: > > I don't think SOS is the main future. I think it gives us another option. > Long before someone learns that technique, they should have the traditional > method down, cold, and understand why they would use one or the other. SOS > definitely make working on the IDE easier, and they make complicated > projects easier, but I wouldn't even think of teaching someone who isn't > already a LC expert about doing it this way. > > The one thing to remember about the SOS technique is that Git isn't the > only option. Git is hard core, and it is hard. I still don't like it, but > I am trying to tolerate it. If you're using any cloud syncing tool that > can keep track of versions (Office365, Gsuite, and Dropbox come to mind), > you have simple version control/rollbacks/archiving/etc. > ___ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode ___ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode