Re: Your installer is broken

2014-12-29 Thread Sean Cole (Pi)
Roger, Make a backup of 6.7 first just in case. I doubt that it would
remove 6.7 (RR and LC never delete older versions from your machine when
installing - I've still got every version right back to 5.5) but keep one
safe anyway. And make backups of your projects while you're at it.

All the best

Sean Cole


On 28 December 2014 at 15:12, Roger Eller roger.e.el...@sealedair.com
wrote:

 I launched 6.7 and the updater offered to install 7.0.1 for OS X.  I
 allowed it to download, but then the wording on screen scared me.  It said
 this will replace your current installation of 6.7, so I bailed.

 ~Roger
 On Dec 28, 2014 3:17 AM, J. Landman Gay jac...@hyperactivesw.com
 wrote:

  On Windows the installer will create a folder inside the location you
  select, so that's why you saw two LiveCode folders (the one you made and
  the one the installer made.) Also, all file paths use forward slashes in
  LiveCode so that's why those were there.
 
  I'm not sure why you'd get the first installation failure. I can only
  guess that the OS was doing some housekeeping on the download when the
  installer was supposed to launch. After a brief delay it was ready.
 
  It's normal to see the contents of a folder when you choose it in the
 file
  selector. You should be able to just choose the one that is currently
  selected and install there, regardless of what you see in the content
 area.
 
  On December 26, 2014 5:53:16 PM CST, Paul D. DeRocco 
  pdero...@ix.netcom.com wrote:
  While I was using LiveCode, I was informed of a 7.0.1 update. The text
  box
  showed the following text:
  
  Stable: The release has been through a full
  testing cycle and is deemed stable.
  Maintenance: The release is the previous stable
  release with fixes ready for testing.
  Beta: The release contains new features which
  are complete and ready for testing.
  Development: The release contains untested
  new features.
  
  My initial reaction was, So, which is it? It was a moment before I
  realized I was looking at the end of a long update description, and had
  to
  scroll all the way back to the top to find out that it's a stable
  release.
  The text box really ought to positioned at the beginning, not the end.
  That's just a very minor issue. But then...
  
  I closed LiveCode and selected Update Now, and it began to download
  rather
  slowly. When it was done, it said Installation Failed, with the
  explanation, Could not launch downloaded installer: not opened. I
  clicked Retry, and it switched to Ready to Install, saying that it
  will
  Install LiveCode to: C:/Program Files (x86)/RunRev/LiveCode Community
  6.6.3 etc.
  
  First of all, if it downloaded the installer, why did it say that it
  had
  failed? Second of all, why is it offering to install it in the LiveCode
  Community 6.6.3 folder, when it's LiveCode 7.0.1? (And third, why is it
  using forward slashes on Windows?)
  
  Rather than click Install, I clicked Back. Rather than go back,
  it
  went to Select Installation Type, so I clicked Custom and
  Continue,
  and it switched to Customize. I clicked the magnifying glass icon
  next
  to the installation folder name (still 6.6.3), and it popped up
  Libraries\Documents. That's not a valid place to install anything, so
  I
  had to navigate to my C: drive and drill down to where I wanted to put
  it.
  I tried selecting C:\Program Files (x86)\RunRev as the installation
  directory, and it simply opened that folder, showing me LiveCode
  Community 6.6.3. Why can't I just put it into C:\Program Files
  (x86)\RunRev?
  
  So I created a LiveCode folder under RunRev and selected it, and it
  went
  back to Customize, showing C:/Program Files
  (x86)/RunRev/LiveCode/LiveCode. Why two LiveCode folders? Where did
  that come from?
  
  I clicked the magnifying glass again, deleted the LiveCode folder that
  I
  had created, and created a LiveCode Community 7.0.1 folder under
  RunRev
  and selected it. It switched back to Customize, showing C:/Program
  Files (x86)/RunRev/LiveCode Community. What happened to the 7.0.1?
  
  I figured, this is the best I could do so I clicked Continue. It
  switched to Ready to Install, and said that it would install in
  C:/Program Files (x86)/RunRev/LiveCode Community 7.0.1/LiveCode
  Community
  6.6.3. At this point, I decided to stick with the 6.6.3 installation
  I've
  already got. Please let us know when you have a stable release of the
  installer, because this one barely qualifies as a beta.
 
  --
  Jacqueline Landman Gay | jac...@hyperactivesw.com
  HyperActive Software   | http://www.hyperactivesw.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
 
 ___
 use-livecode 

Re: Your installer is broken

2014-12-29 Thread Richard Gaskin

Sean Cole wrote:

 Roger, Make a backup of 6.7 first just in case. I doubt that it would
 remove 6.7 (RR and LC never delete older versions from your machine
 when installing - I've still got every version right back to 5.5) but
 keep one safe anyway.

LiveCode always installs each version into its own folder, so your older 
versions will remain in place.


Perhaps what the installer was referring to is the OS file type 
association.  On Windows this is governed by the Registry, and IIRC is 
updated with each LC install.  On Mac it's governed by voodoo using 
unknowable rules in the Finder, so that sometimes it'll use the most 
recently-installed version of an app but sometimes it'll decide to 
fixate on one particular version.


But that only governs what happens when you double-click a stack in the 
file manager.


As long as you open the version you want to work with and then use 
File-Open in the IDE you'll always have complete control over which 
version you're using.



 And make backups of your projects while you're at it.

Excellent advice for all data made with all applications.

Hard drives fail, file systems get corrupted, systems get hacked, and 
then there are fires, floods, earthquakes, etc.  Merde happens.


At a minimum everyone should have at least three copies of any data they 
consider non-disposable, with one of those copies rotated off-site.


Here I maintain 5 copies of everything.  Storage is cheap, and time is 
precious.



Worth taking 5 minutes to read up on rsync to quickly back up folders:
https://www.digitalocean.com/community/tutorials/how-to-use-rsync-to-sync-local-and-remote-directories-on-a-vps

Like many good programs rsync has a lot of options, but for simple 
one-way syncing the -av flags are usually sufficient when working with 
local volumes:


rsync -av /volume/sourcefolder/   /backup/destfolder/

Across networks it's helpful to add -z for compression:

rsync -avz /volume/sourcefolder/  user@domain:/backup/destfolder/


--
 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: Your installer is broken

2014-12-28 Thread J. Landman Gay
On Windows the installer will create a folder inside the location you select, 
so that's why you saw two LiveCode folders (the one you made and the one the 
installer made.) Also, all file paths use forward slashes in LiveCode so that's 
why those were there. 

I'm not sure why you'd get the first installation failure. I can only guess 
that the OS was doing some housekeeping on the download when the installer was 
supposed to launch. After a brief delay it was ready. 

It's normal to see the contents of a folder when you choose it in the file 
selector. You should be able to just choose the one that is currently selected 
and install there, regardless of what you see in the content area. 

On December 26, 2014 5:53:16 PM CST, Paul D. DeRocco pdero...@ix.netcom.com 
wrote:
While I was using LiveCode, I was informed of a 7.0.1 update. The text
box
showed the following text:

Stable: The release has been through a full
testing cycle and is deemed stable.
Maintenance: The release is the previous stable
release with fixes ready for testing.
Beta: The release contains new features which
are complete and ready for testing.
Development: The release contains untested
new features.

My initial reaction was, So, which is it? It was a moment before I
realized I was looking at the end of a long update description, and had
to
scroll all the way back to the top to find out that it's a stable
release.
The text box really ought to positioned at the beginning, not the end.
That's just a very minor issue. But then...

I closed LiveCode and selected Update Now, and it began to download
rather
slowly. When it was done, it said Installation Failed, with the
explanation, Could not launch downloaded installer: not opened. I
clicked Retry, and it switched to Ready to Install, saying that it
will
Install LiveCode to: C:/Program Files (x86)/RunRev/LiveCode Community
6.6.3 etc.

First of all, if it downloaded the installer, why did it say that it
had
failed? Second of all, why is it offering to install it in the LiveCode
Community 6.6.3 folder, when it's LiveCode 7.0.1? (And third, why is it
using forward slashes on Windows?)
 
Rather than click Install, I clicked Back. Rather than go back,
it
went to Select Installation Type, so I clicked Custom and
Continue,
and it switched to Customize. I clicked the magnifying glass icon
next
to the installation folder name (still 6.6.3), and it popped up
Libraries\Documents. That's not a valid place to install anything, so
I
had to navigate to my C: drive and drill down to where I wanted to put
it.
I tried selecting C:\Program Files (x86)\RunRev as the installation
directory, and it simply opened that folder, showing me LiveCode
Community 6.6.3. Why can't I just put it into C:\Program Files
(x86)\RunRev?

So I created a LiveCode folder under RunRev and selected it, and it
went
back to Customize, showing C:/Program Files
(x86)/RunRev/LiveCode/LiveCode. Why two LiveCode folders? Where did
that come from?

I clicked the magnifying glass again, deleted the LiveCode folder that
I
had created, and created a LiveCode Community 7.0.1 folder under
RunRev
and selected it. It switched back to Customize, showing C:/Program
Files (x86)/RunRev/LiveCode Community. What happened to the 7.0.1?

I figured, this is the best I could do so I clicked Continue. It
switched to Ready to Install, and said that it would install in
C:/Program Files (x86)/RunRev/LiveCode Community 7.0.1/LiveCode
Community
6.6.3. At this point, I decided to stick with the 6.6.3 installation
I've
already got. Please let us know when you have a stable release of the
installer, because this one barely qualifies as a beta.

-- 
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software   | http://www.hyperactivesw.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: Your installer is broken

2014-12-28 Thread Roger Eller
I launched 6.7 and the updater offered to install 7.0.1 for OS X.  I
allowed it to download, but then the wording on screen scared me.  It said
this will replace your current installation of 6.7, so I bailed.

~Roger
On Dec 28, 2014 3:17 AM, J. Landman Gay jac...@hyperactivesw.com wrote:

 On Windows the installer will create a folder inside the location you
 select, so that's why you saw two LiveCode folders (the one you made and
 the one the installer made.) Also, all file paths use forward slashes in
 LiveCode so that's why those were there.

 I'm not sure why you'd get the first installation failure. I can only
 guess that the OS was doing some housekeeping on the download when the
 installer was supposed to launch. After a brief delay it was ready.

 It's normal to see the contents of a folder when you choose it in the file
 selector. You should be able to just choose the one that is currently
 selected and install there, regardless of what you see in the content area.

 On December 26, 2014 5:53:16 PM CST, Paul D. DeRocco 
 pdero...@ix.netcom.com wrote:
 While I was using LiveCode, I was informed of a 7.0.1 update. The text
 box
 showed the following text:
 
 Stable: The release has been through a full
 testing cycle and is deemed stable.
 Maintenance: The release is the previous stable
 release with fixes ready for testing.
 Beta: The release contains new features which
 are complete and ready for testing.
 Development: The release contains untested
 new features.
 
 My initial reaction was, So, which is it? It was a moment before I
 realized I was looking at the end of a long update description, and had
 to
 scroll all the way back to the top to find out that it's a stable
 release.
 The text box really ought to positioned at the beginning, not the end.
 That's just a very minor issue. But then...
 
 I closed LiveCode and selected Update Now, and it began to download
 rather
 slowly. When it was done, it said Installation Failed, with the
 explanation, Could not launch downloaded installer: not opened. I
 clicked Retry, and it switched to Ready to Install, saying that it
 will
 Install LiveCode to: C:/Program Files (x86)/RunRev/LiveCode Community
 6.6.3 etc.
 
 First of all, if it downloaded the installer, why did it say that it
 had
 failed? Second of all, why is it offering to install it in the LiveCode
 Community 6.6.3 folder, when it's LiveCode 7.0.1? (And third, why is it
 using forward slashes on Windows?)
 
 Rather than click Install, I clicked Back. Rather than go back,
 it
 went to Select Installation Type, so I clicked Custom and
 Continue,
 and it switched to Customize. I clicked the magnifying glass icon
 next
 to the installation folder name (still 6.6.3), and it popped up
 Libraries\Documents. That's not a valid place to install anything, so
 I
 had to navigate to my C: drive and drill down to where I wanted to put
 it.
 I tried selecting C:\Program Files (x86)\RunRev as the installation
 directory, and it simply opened that folder, showing me LiveCode
 Community 6.6.3. Why can't I just put it into C:\Program Files
 (x86)\RunRev?
 
 So I created a LiveCode folder under RunRev and selected it, and it
 went
 back to Customize, showing C:/Program Files
 (x86)/RunRev/LiveCode/LiveCode. Why two LiveCode folders? Where did
 that come from?
 
 I clicked the magnifying glass again, deleted the LiveCode folder that
 I
 had created, and created a LiveCode Community 7.0.1 folder under
 RunRev
 and selected it. It switched back to Customize, showing C:/Program
 Files (x86)/RunRev/LiveCode Community. What happened to the 7.0.1?
 
 I figured, this is the best I could do so I clicked Continue. It
 switched to Ready to Install, and said that it would install in
 C:/Program Files (x86)/RunRev/LiveCode Community 7.0.1/LiveCode
 Community
 6.6.3. At this point, I decided to stick with the 6.6.3 installation
 I've
 already got. Please let us know when you have a stable release of the
 installer, because this one barely qualifies as a beta.

 --
 Jacqueline Landman Gay | jac...@hyperactivesw.com
 HyperActive Software   | http://www.hyperactivesw.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

___
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