Re: Relative Paths in Property Inspector
PR submitted: https://github.com/livecode/livecode-ide/pull/1817 For bug: http://quality.livecode.com/show_bug.cgi?id=17287 Not sure how it will be received, but it uses the pref to always use absolute path names for images to decide whether to convert a path to relative. On Sun, Oct 29, 2017 at 2:02 PM, Sannyasin Brahmanathaswami via use-livecodewrote: > Backstory: > > Sometime back in a round with HQ we got the engine to "remember" relative > path settings for the filenames of images/players etc.. such that it would > not default to full path from root on the drive which makes the path unique > to that user and no longer portable… so "relativity" go supported/sticky in > different dev scenarios… > > so far so good… if you set the filename in an image in a stack that lives > here: > > User/MyDrive/myProject/coolAnimals.livecode > > with images here to: > > User/MyDrive/myProject/img/thumbs/little-rooster.jpg > > # it, obviously works But, now you can > > a) manually chop of the lead down to this in the property inspector > > img/thumbs/little-rooster.jpg > > # and it works… this is also portable if you include "img/*" in the > stackfiles when create your standalone and the filename is saved relative > to the stack, and, assuming you keep the folder structure intact you don't > have to even mess with defaultfolder or even specialFolderPath("engine") > because the "relativity" of the path is respected in any and all contexts > (I think…) > > so you can also programatically do this > > set the filename of img "myPet" to "img/thumbs/little-rooster.jpg" > > and that also works though you do need to use "specialFolderPath" > functions on mobile. > > Again, so far so good… > > End backstory (please correct anything you see that is wrong) > > So, why can't we just a relative path in the Property Inspector itself? > The browser tool will always return full path from User down to the > "asset.jpg"… if I send that stack to someone else, or use a GIT work flow > where these stacks are "pure views" (i.e. no actual imported images > anywhere) along with the images. the paths are broken. So, long way of > asking: > > Do we need an enhancement request for a check box in the PI to set the > path as relative to the stack? Seems like that would be super usefu > > Mikey has this request in since May '16… which feels related > > http://quality.livecode.com/show_bug.cgi?id=17705 > > but the suggestion for having this in the PI seems a bit different, and > might not actually solve his issue for using a cloud instance of his > project. > > Brahmanathaswami > > > > > > ___ > 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
Re: Relative Paths in Property Inspector
This is called a Watch Folder approach and any cloud based system that uses it (nextcloud does sort of, icloud does as well) will work the same way. Pretty slick. Bob S > On Oct 31, 2017, at 11:43 , J. Landman Gay via use-livecode >wrote: > > On 10/31/17 11:57 AM, Mike Kerner via use-livecode wrote: >> no I'm referring to the usernames on the machine. I'm using google drive >> (backup and sync and file stream). I use dropbox for app data storage and >> transfer. > > Here is my setup: I created a folder in Dropbox named "Application Support". > I put the LC folder in there as well as BBEdit's preferences and a few other > things I want to share among machines. > > On Mac #1, the path in the LC prefs is: > /Users/Username1/Dropbox/Application Support/My LiveCode > > Mac #2: > /Users/username2/Dropbox/Application Support/My LiveCode > > And so forth. Dropbox keeps the folders in sync and because it's a local > folder on each drive, LC has no problem accessing it. > > -- > 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: Relative Paths in Property Inspector
On 10/31/17 11:57 AM, Mike Kerner via use-livecode wrote: no I'm referring to the usernames on the machine. I'm using google drive (backup and sync and file stream). I use dropbox for app data storage and transfer. Here is my setup: I created a folder in Dropbox named "Application Support". I put the LC folder in there as well as BBEdit's preferences and a few other things I want to share among machines. On Mac #1, the path in the LC prefs is: /Users/Username1/Dropbox/Application Support/My LiveCode Mac #2: /Users/username2/Dropbox/Application Support/My LiveCode And so forth. Dropbox keeps the folders in sync and because it's a local folder on each drive, LC has no problem accessing it. -- 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: Relative Paths in Property Inspector
no I'm referring to the usernames on the machine. I'm using google drive (backup and sync and file stream). I use dropbox for app data storage and transfer. On Tue, Oct 31, 2017 at 11:17 AM, Mark Wieder via use-livecode < use-livecode@lists.runrev.com> wrote: > On 10/30/2017 07:55 PM, Mike Kerner via use-livecode wrote: > >> So what do you have for your paths? Are your usernames the same? For me, >> I run into the issue because my usernames aren't the same on every box, so >> the absolute path varies. >> > > Are you referring to the *dropbox* usernames being different? If that's > the case, you can share a folder between dropbox users and still use a > common repository. > > > -- > 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 > -- 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: Relative Paths in Property Inspector
On 10/30/2017 07:55 PM, Mike Kerner via use-livecode wrote: So what do you have for your paths? Are your usernames the same? For me, I run into the issue because my usernames aren't the same on every box, so the absolute path varies. Are you referring to the *dropbox* usernames being different? If that's the case, you can share a folder between dropbox users and still use a common repository. -- 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: Relative Paths in Property Inspector
Hmm. I wonder why I've run into trouble with this. Now I don't remember. On Mon, Oct 30, 2017 at 11:19 PM, J. Landman Gay via use-livecode < use-livecode@lists.runrev.com> wrote: > I have different user names on each machine too. Just set the appropriate > path in the LC prefs on each machine. You only have to do it once, and > going forward it just works for any other LC versions you install since all > versions on a machine share the same prefs file. > > > On 10/30/17 9:55 PM, Mike Kerner via use-livecode wrote: > >> So what do you have for your paths? Are your usernames the same? For me, >> I run into the issue because my usernames aren't the same on every box, so >> the absolute path varies. >> >> On Mon, Oct 30, 2017 at 6:49 PM, Mark Wieder via use-livecode < >> use-livecode@lists.runrev.com> wrote: >> >> On 10/30/2017 01:51 PM, J. Landman Gay via use-livecode wrote: >>> >>> I've got my extensionos folder in Dropbox. All my machines have Dropbox installed and it syncs to all of them. On 10/30/17 3:20 PM, Mike Kerner via use-livecode wrote: All I'm trying to "Get" is a simpler way to store the extensions folder > on > a network/sync so I get the exact same environment on every box. > > Same here. Trick learned from Andre Garzia. >>> >>> +1 for 'extensionos'. >>> >>> >>> -- >>> 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 >>> >>> >> >> >> > > -- > 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 > -- 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: Relative Paths in Property Inspector
I have different user names on each machine too. Just set the appropriate path in the LC prefs on each machine. You only have to do it once, and going forward it just works for any other LC versions you install since all versions on a machine share the same prefs file. On 10/30/17 9:55 PM, Mike Kerner via use-livecode wrote: So what do you have for your paths? Are your usernames the same? For me, I run into the issue because my usernames aren't the same on every box, so the absolute path varies. On Mon, Oct 30, 2017 at 6:49 PM, Mark Wieder via use-livecode < use-livecode@lists.runrev.com> wrote: On 10/30/2017 01:51 PM, J. Landman Gay via use-livecode wrote: I've got my extensionos folder in Dropbox. All my machines have Dropbox installed and it syncs to all of them. On 10/30/17 3:20 PM, Mike Kerner via use-livecode wrote: All I'm trying to "Get" is a simpler way to store the extensions folder on a network/sync so I get the exact same environment on every box. Same here. Trick learned from Andre Garzia. +1 for 'extensionos'. -- 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 -- 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: Relative Paths in Property Inspector
So what do you have for your paths? Are your usernames the same? For me, I run into the issue because my usernames aren't the same on every box, so the absolute path varies. On Mon, Oct 30, 2017 at 6:49 PM, Mark Wieder via use-livecode < use-livecode@lists.runrev.com> wrote: > On 10/30/2017 01:51 PM, J. Landman Gay via use-livecode wrote: > >> I've got my extensionos folder in Dropbox. All my machines have Dropbox >> installed and it syncs to all of them. >> >> On 10/30/17 3:20 PM, Mike Kerner via use-livecode wrote: >> >>> All I'm trying to "Get" is a simpler way to store the extensions folder >>> on >>> a network/sync so I get the exact same environment on every box. >>> >> > Same here. Trick learned from Andre Garzia. > > +1 for 'extensionos'. > > > -- > 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 > -- 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: Relative Paths in Property Inspector
On 10/30/2017 01:51 PM, J. Landman Gay via use-livecode wrote: I've got my extensionos folder in Dropbox. All my machines have Dropbox installed and it syncs to all of them. On 10/30/17 3:20 PM, Mike Kerner via use-livecode wrote: All I'm trying to "Get" is a simpler way to store the extensions folder on a network/sync so I get the exact same environment on every box. Same here. Trick learned from Andre Garzia. +1 for 'extensionos'. -- 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: Relative Paths in Property Inspector
I've got my extensionos folder in Dropbox. All my machines have Dropbox installed and it syncs to all of them. On 10/30/17 3:20 PM, Mike Kerner via use-livecode wrote: All I'm trying to "Get" is a simpler way to store the extensions folder on a network/sync so I get the exact same environment on every box. On Mon, Oct 30, 2017 at 4:11 PM, Mark Wieder via use-livecode < use-livecode@lists.runrev.com> wrote: On 10/30/2017 12:45 PM, Mike Kerner via use-livecode wrote: One of the cases where it would be nice is the location of the plugins folder ("User Extensions"), which is why I mentioned ~ to begin with. A better way to get that would be revEnvironmentUserExtensionsPath() -- 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 -- 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: Relative Paths in Property Inspector
All I'm trying to "Get" is a simpler way to store the extensions folder on a network/sync so I get the exact same environment on every box. On Mon, Oct 30, 2017 at 4:11 PM, Mark Wieder via use-livecode < use-livecode@lists.runrev.com> wrote: > On 10/30/2017 12:45 PM, Mike Kerner via use-livecode wrote: > >> One of the cases where it would be nice is the location of the plugins >> folder ("User Extensions"), which is why I mentioned ~ to begin with. >> > > A better way to get that would be > revEnvironmentUserExtensionsPath() > > -- > 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 > -- 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: Relative Paths in Property Inspector
Oh right my point was that I am not sure the tilde would work in a Windows standalone, but maybe the engine interprets it either way. And yes, the tilde means user home folder sorry for the misinformation. Bob S > On Oct 30, 2017, at 11:58 , Mike Kerner via use-livecode >wrote: > > Actually the ~ is a unix convention, so it is also used in Linux. ___ 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: Relative Paths in Property Inspector
Oh right you are. Bob S ___ 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: Relative Paths in Property Inspector
On 10/30/2017 12:45 PM, Mike Kerner via use-livecode wrote: One of the cases where it would be nice is the location of the plugins folder ("User Extensions"), which is why I mentioned ~ to begin with. A better way to get that would be revEnvironmentUserExtensionsPath() -- 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: Relative Paths in Property Inspector
http://forums.livecode.com/viewtopic.php?f=6=30074 Richmond. ___ 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: Relative Paths in Property Inspector
One of the cases where it would be nice is the location of the plugins folder ("User Extensions"), which is why I mentioned ~ to begin with. On Mon, Oct 30, 2017 at 3:22 PM, Brian Milby via use-livecode < use-livecode@lists.runrev.com> wrote: > Just clarifying that the two are not interchangeable. From the OP, I don’t > think ~/ links would be used at all. I am not saying that we should include > the ./ but that when discussing relative links for assets that the fixed > point should be the stack location and not something anchored to the > profile location. This would mean that all of the Dropbox/Google > Drive/network share stuff would work as expected. You could also zip a > stack with the associated assets and as long as the structure was preserved > another user could unzip and use the stack. > On Mon, Oct 30, 2017 at 2:12 PM Mike Kerner via use-livecode < > use-livecode@lists.runrev.com> wrote: > > > Yes, Brian. So I'm not sure what you're getting at. > > > > On Mon, Oct 30, 2017 at 3:07 PM, Brian Milby via use-livecode < > > use-livecode@lists.runrev.com> wrote: > > > > > ./ is current directory. ~/ is the user home directory. > > > On Mon, Oct 30, 2017 at 2:00 PM Mike Kerner via use-livecode < > > > use-livecode@lists.runrev.com> wrote: > > > > > > > Actually the ~ is a unix convention, so it is also used in Linux. > > > > > > > > On Mon, Oct 30, 2017 at 2:24 PM, Bob Sneidar via use-livecode < > > > > use-livecode@lists.runrev.com> wrote: > > > > > > > > > The tilde is a MacOS convention. The period should be universal. ./ > > as > > > > > opposed to ~/ > > > > > > > > > > Bob S > > > > > > > > > > > > > > > > On Oct 30, 2017, at 10:48 , Mike Kerner via use-livecode < > > > > > use-livecode@lists.runrev.com> wrote: > > > > > > > > > > > > If you use Backup and Sync (the old "Drive"), your folder is > > ~/Google > > > > > Drive/ > > > > > > If you use Drive Stream and do not map the mount point to an > alias > > in > > > > the > > > > > > documents folder, the mount point will be a volume. > > > > > > > > > > > > Git was not amused when I switched on the one machine. > > > > > > > > > > > > On Mon, Oct 30, 2017 at 1:39 PM, Sannyasin Brahmanathaswami via > > > > > > use-livecodewrote: > > > > > > > > > > > >> @Mike I tried to duplicate your 3rd case. Are you on Mac OS X? > > > > > >> > > > > > >> if I create a stack, place and img in an adjacent image folder > and > > > > move > > > > > to > > > > > >> the server ("Chola") in the next room… set the img filename to > > > > > >> > > > > > >> img/tiger.jpg > > > > > >> > > > > > >> it works @brian ./img/tiger.jpg also works… but really doesn't > > get > > > us > > > > > >> anything… we have to manually enter either way > > > > > >> > > > > > >> So from terminal if you do "cd /" and you look under Volumes… > the > > > > > >> DriveFileStream is not there? > > > > > >> > > > > > >> in this if I do > > > > > >> > > > > > >> cd /Volumes > > > > > >> I will see > > > > > >> > > > > > >> MyDrive HD > > > > > >> Chola > > > > > >> BR Back ups (USB for local Time machine backups) > > > > > >> > > > > > >> But "Chola" is a "network store"… I guess I don’t understand the > > > > nature > > > > > of > > > > > >> the connection/Mount context to Googles Drive File Stream… how > > that > > > is > > > > > >> different? > > > > > >> > > > > > >> At any rate you do seem to have a different, though obviously > > > related > > > > > >> issue. > > > > > >> > > > > > >> > > > > > >> > > > > > >> > > > > > >> On 10/30/17, 6:09 AM, "use-livecode on behalf of Mike Kerner via > > > > > >> use-livecode" of > > > > > >> use-livecode@lists.runrev.com> wrote: > > > > > >> > > > > > >>On "b", I have three machines that I use. Two of them use > > > Google's > > > > > >> Backup > > > > > >>and Sync service, and the other uses Google's Drive File > > Stream. > > > > So > > > > > >> in for > > > > > >>two of the machines, the answer is "mostly yes" - the > > difference > > > is > > > > > the > > > > > >>username, as the "Drive" folder is in the user folder. For > the > > > the > > > > > >> third, > > > > > >>the answer is "no", because in that case, the access is > treated > > > as > > > > a > > > > > >>network store, i.e. its own drive. > > > > > >> > > > > > >> ___ > > > > > >> 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. > > >
Re: Relative Paths in Property Inspector
Just clarifying that the two are not interchangeable. From the OP, I don’t think ~/ links would be used at all. I am not saying that we should include the ./ but that when discussing relative links for assets that the fixed point should be the stack location and not something anchored to the profile location. This would mean that all of the Dropbox/Google Drive/network share stuff would work as expected. You could also zip a stack with the associated assets and as long as the structure was preserved another user could unzip and use the stack. On Mon, Oct 30, 2017 at 2:12 PM Mike Kerner via use-livecode < use-livecode@lists.runrev.com> wrote: > Yes, Brian. So I'm not sure what you're getting at. > > On Mon, Oct 30, 2017 at 3:07 PM, Brian Milby via use-livecode < > use-livecode@lists.runrev.com> wrote: > > > ./ is current directory. ~/ is the user home directory. > > On Mon, Oct 30, 2017 at 2:00 PM Mike Kerner via use-livecode < > > use-livecode@lists.runrev.com> wrote: > > > > > Actually the ~ is a unix convention, so it is also used in Linux. > > > > > > On Mon, Oct 30, 2017 at 2:24 PM, Bob Sneidar via use-livecode < > > > use-livecode@lists.runrev.com> wrote: > > > > > > > The tilde is a MacOS convention. The period should be universal. ./ > as > > > > opposed to ~/ > > > > > > > > Bob S > > > > > > > > > > > > > On Oct 30, 2017, at 10:48 , Mike Kerner via use-livecode < > > > > use-livecode@lists.runrev.com> wrote: > > > > > > > > > > If you use Backup and Sync (the old "Drive"), your folder is > ~/Google > > > > Drive/ > > > > > If you use Drive Stream and do not map the mount point to an alias > in > > > the > > > > > documents folder, the mount point will be a volume. > > > > > > > > > > Git was not amused when I switched on the one machine. > > > > > > > > > > On Mon, Oct 30, 2017 at 1:39 PM, Sannyasin Brahmanathaswami via > > > > > use-livecodewrote: > > > > > > > > > >> @Mike I tried to duplicate your 3rd case. Are you on Mac OS X? > > > > >> > > > > >> if I create a stack, place and img in an adjacent image folder and > > > move > > > > to > > > > >> the server ("Chola") in the next room… set the img filename to > > > > >> > > > > >> img/tiger.jpg > > > > >> > > > > >> it works @brian ./img/tiger.jpg also works… but really doesn't > get > > us > > > > >> anything… we have to manually enter either way > > > > >> > > > > >> So from terminal if you do "cd /" and you look under Volumes… the > > > > >> DriveFileStream is not there? > > > > >> > > > > >> in this if I do > > > > >> > > > > >> cd /Volumes > > > > >> I will see > > > > >> > > > > >> MyDrive HD > > > > >> Chola > > > > >> BR Back ups (USB for local Time machine backups) > > > > >> > > > > >> But "Chola" is a "network store"… I guess I don’t understand the > > > nature > > > > of > > > > >> the connection/Mount context to Googles Drive File Stream… how > that > > is > > > > >> different? > > > > >> > > > > >> At any rate you do seem to have a different, though obviously > > related > > > > >> issue. > > > > >> > > > > >> > > > > >> > > > > >> > > > > >> On 10/30/17, 6:09 AM, "use-livecode on behalf of Mike Kerner via > > > > >> use-livecode" > > > >> use-livecode@lists.runrev.com> wrote: > > > > >> > > > > >>On "b", I have three machines that I use. Two of them use > > Google's > > > > >> Backup > > > > >>and Sync service, and the other uses Google's Drive File > Stream. > > > So > > > > >> in for > > > > >>two of the machines, the answer is "mostly yes" - the > difference > > is > > > > the > > > > >>username, as the "Drive" folder is in the user folder. For the > > the > > > > >> third, > > > > >>the answer is "no", because in that case, the access is treated > > as > > > a > > > > >>network store, i.e. its own drive. > > > > >> > > > > >> ___ > > > > >> 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 > > > > > > > > ___ > > > > use-livecode mailing list > > > > use-livecode@lists.runrev.com > > > > Please visit this url to
Re: Relative Paths in Property Inspector
Yes, Brian. So I'm not sure what you're getting at. On Mon, Oct 30, 2017 at 3:07 PM, Brian Milby via use-livecode < use-livecode@lists.runrev.com> wrote: > ./ is current directory. ~/ is the user home directory. > On Mon, Oct 30, 2017 at 2:00 PM Mike Kerner via use-livecode < > use-livecode@lists.runrev.com> wrote: > > > Actually the ~ is a unix convention, so it is also used in Linux. > > > > On Mon, Oct 30, 2017 at 2:24 PM, Bob Sneidar via use-livecode < > > use-livecode@lists.runrev.com> wrote: > > > > > The tilde is a MacOS convention. The period should be universal. ./ as > > > opposed to ~/ > > > > > > Bob S > > > > > > > > > > On Oct 30, 2017, at 10:48 , Mike Kerner via use-livecode < > > > use-livecode@lists.runrev.com> wrote: > > > > > > > > If you use Backup and Sync (the old "Drive"), your folder is ~/Google > > > Drive/ > > > > If you use Drive Stream and do not map the mount point to an alias in > > the > > > > documents folder, the mount point will be a volume. > > > > > > > > Git was not amused when I switched on the one machine. > > > > > > > > On Mon, Oct 30, 2017 at 1:39 PM, Sannyasin Brahmanathaswami via > > > > use-livecodewrote: > > > > > > > >> @Mike I tried to duplicate your 3rd case. Are you on Mac OS X? > > > >> > > > >> if I create a stack, place and img in an adjacent image folder and > > move > > > to > > > >> the server ("Chola") in the next room… set the img filename to > > > >> > > > >> img/tiger.jpg > > > >> > > > >> it works @brian ./img/tiger.jpg also works… but really doesn't get > us > > > >> anything… we have to manually enter either way > > > >> > > > >> So from terminal if you do "cd /" and you look under Volumes… the > > > >> DriveFileStream is not there? > > > >> > > > >> in this if I do > > > >> > > > >> cd /Volumes > > > >> I will see > > > >> > > > >> MyDrive HD > > > >> Chola > > > >> BR Back ups (USB for local Time machine backups) > > > >> > > > >> But "Chola" is a "network store"… I guess I don’t understand the > > nature > > > of > > > >> the connection/Mount context to Googles Drive File Stream… how that > is > > > >> different? > > > >> > > > >> At any rate you do seem to have a different, though obviously > related > > > >> issue. > > > >> > > > >> > > > >> > > > >> > > > >> On 10/30/17, 6:09 AM, "use-livecode on behalf of Mike Kerner via > > > >> use-livecode" > > >> use-livecode@lists.runrev.com> wrote: > > > >> > > > >>On "b", I have three machines that I use. Two of them use > Google's > > > >> Backup > > > >>and Sync service, and the other uses Google's Drive File Stream. > > So > > > >> in for > > > >>two of the machines, the answer is "mostly yes" - the difference > is > > > the > > > >>username, as the "Drive" folder is in the user folder. For the > the > > > >> third, > > > >>the answer is "no", because in that case, the access is treated > as > > a > > > >>network store, i.e. its own drive. > > > >> > > > >> ___ > > > >> 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 > > > > > > ___ > > > 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 > ___ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your > subscription preferences: >
Re: Relative Paths in Property Inspector
./ is current directory. ~/ is the user home directory. On Mon, Oct 30, 2017 at 2:00 PM Mike Kerner via use-livecode < use-livecode@lists.runrev.com> wrote: > Actually the ~ is a unix convention, so it is also used in Linux. > > On Mon, Oct 30, 2017 at 2:24 PM, Bob Sneidar via use-livecode < > use-livecode@lists.runrev.com> wrote: > > > The tilde is a MacOS convention. The period should be universal. ./ as > > opposed to ~/ > > > > Bob S > > > > > > > On Oct 30, 2017, at 10:48 , Mike Kerner via use-livecode < > > use-livecode@lists.runrev.com> wrote: > > > > > > If you use Backup and Sync (the old "Drive"), your folder is ~/Google > > Drive/ > > > If you use Drive Stream and do not map the mount point to an alias in > the > > > documents folder, the mount point will be a volume. > > > > > > Git was not amused when I switched on the one machine. > > > > > > On Mon, Oct 30, 2017 at 1:39 PM, Sannyasin Brahmanathaswami via > > > use-livecodewrote: > > > > > >> @Mike I tried to duplicate your 3rd case. Are you on Mac OS X? > > >> > > >> if I create a stack, place and img in an adjacent image folder and > move > > to > > >> the server ("Chola") in the next room… set the img filename to > > >> > > >> img/tiger.jpg > > >> > > >> it works @brian ./img/tiger.jpg also works… but really doesn't get us > > >> anything… we have to manually enter either way > > >> > > >> So from terminal if you do "cd /" and you look under Volumes… the > > >> DriveFileStream is not there? > > >> > > >> in this if I do > > >> > > >> cd /Volumes > > >> I will see > > >> > > >> MyDrive HD > > >> Chola > > >> BR Back ups (USB for local Time machine backups) > > >> > > >> But "Chola" is a "network store"… I guess I don’t understand the > nature > > of > > >> the connection/Mount context to Googles Drive File Stream… how that is > > >> different? > > >> > > >> At any rate you do seem to have a different, though obviously related > > >> issue. > > >> > > >> > > >> > > >> > > >> On 10/30/17, 6:09 AM, "use-livecode on behalf of Mike Kerner via > > >> use-livecode" > >> use-livecode@lists.runrev.com> wrote: > > >> > > >>On "b", I have three machines that I use. Two of them use Google's > > >> Backup > > >>and Sync service, and the other uses Google's Drive File Stream. > So > > >> in for > > >>two of the machines, the answer is "mostly yes" - the difference is > > the > > >>username, as the "Drive" folder is in the user folder. For the the > > >> third, > > >>the answer is "no", because in that case, the access is treated as > a > > >>network store, i.e. its own drive. > > >> > > >> ___ > > >> 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 > > > > ___ > > 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 ___ 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: Relative Paths in Property Inspector
Actually the ~ is a unix convention, so it is also used in Linux. On Mon, Oct 30, 2017 at 2:24 PM, Bob Sneidar via use-livecode < use-livecode@lists.runrev.com> wrote: > The tilde is a MacOS convention. The period should be universal. ./ as > opposed to ~/ > > Bob S > > > > On Oct 30, 2017, at 10:48 , Mike Kerner via use-livecode < > use-livecode@lists.runrev.com> wrote: > > > > If you use Backup and Sync (the old "Drive"), your folder is ~/Google > Drive/ > > If you use Drive Stream and do not map the mount point to an alias in the > > documents folder, the mount point will be a volume. > > > > Git was not amused when I switched on the one machine. > > > > On Mon, Oct 30, 2017 at 1:39 PM, Sannyasin Brahmanathaswami via > > use-livecodewrote: > > > >> @Mike I tried to duplicate your 3rd case. Are you on Mac OS X? > >> > >> if I create a stack, place and img in an adjacent image folder and move > to > >> the server ("Chola") in the next room… set the img filename to > >> > >> img/tiger.jpg > >> > >> it works @brian ./img/tiger.jpg also works… but really doesn't get us > >> anything… we have to manually enter either way > >> > >> So from terminal if you do "cd /" and you look under Volumes… the > >> DriveFileStream is not there? > >> > >> in this if I do > >> > >> cd /Volumes > >> I will see > >> > >> MyDrive HD > >> Chola > >> BR Back ups (USB for local Time machine backups) > >> > >> But "Chola" is a "network store"… I guess I don’t understand the nature > of > >> the connection/Mount context to Googles Drive File Stream… how that is > >> different? > >> > >> At any rate you do seem to have a different, though obviously related > >> issue. > >> > >> > >> > >> > >> On 10/30/17, 6:09 AM, "use-livecode on behalf of Mike Kerner via > >> use-livecode" >> use-livecode@lists.runrev.com> wrote: > >> > >>On "b", I have three machines that I use. Two of them use Google's > >> Backup > >>and Sync service, and the other uses Google's Drive File Stream. So > >> in for > >>two of the machines, the answer is "mostly yes" - the difference is > the > >>username, as the "Drive" folder is in the user folder. For the the > >> third, > >>the answer is "no", because in that case, the access is treated as a > >>network store, i.e. its own drive. > >> > >> ___ > >> 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 > > ___ > 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: Relative Paths in Property Inspector
The tilde is a MacOS convention. The period should be universal. ./ as opposed to ~/ Bob S > On Oct 30, 2017, at 10:48 , Mike Kerner via use-livecode >wrote: > > If you use Backup and Sync (the old "Drive"), your folder is ~/Google Drive/ > If you use Drive Stream and do not map the mount point to an alias in the > documents folder, the mount point will be a volume. > > Git was not amused when I switched on the one machine. > > On Mon, Oct 30, 2017 at 1:39 PM, Sannyasin Brahmanathaswami via > use-livecode wrote: > >> @Mike I tried to duplicate your 3rd case. Are you on Mac OS X? >> >> if I create a stack, place and img in an adjacent image folder and move to >> the server ("Chola") in the next room… set the img filename to >> >> img/tiger.jpg >> >> it works @brian ./img/tiger.jpg also works… but really doesn't get us >> anything… we have to manually enter either way >> >> So from terminal if you do "cd /" and you look under Volumes… the >> DriveFileStream is not there? >> >> in this if I do >> >> cd /Volumes >> I will see >> >> MyDrive HD >> Chola >> BR Back ups (USB for local Time machine backups) >> >> But "Chola" is a "network store"… I guess I don’t understand the nature of >> the connection/Mount context to Googles Drive File Stream… how that is >> different? >> >> At any rate you do seem to have a different, though obviously related >> issue. >> >> >> >> >> On 10/30/17, 6:09 AM, "use-livecode on behalf of Mike Kerner via >> use-livecode" > use-livecode@lists.runrev.com> wrote: >> >>On "b", I have three machines that I use. Two of them use Google's >> Backup >>and Sync service, and the other uses Google's Drive File Stream. So >> in for >>two of the machines, the answer is "mostly yes" - the difference is the >>username, as the "Drive" folder is in the user folder. For the the >> third, >>the answer is "no", because in that case, the access is treated as a >>network store, i.e. its own drive. >> >> ___ >> 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 ___ 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: Relative Paths in Property Inspector
If you use Backup and Sync (the old "Drive"), your folder is ~/Google Drive/ If you use Drive Stream and do not map the mount point to an alias in the documents folder, the mount point will be a volume. Git was not amused when I switched on the one machine. On Mon, Oct 30, 2017 at 1:39 PM, Sannyasin Brahmanathaswami via use-livecodewrote: > @Mike I tried to duplicate your 3rd case. Are you on Mac OS X? > > if I create a stack, place and img in an adjacent image folder and move to > the server ("Chola") in the next room… set the img filename to > > img/tiger.jpg > > it works @brian ./img/tiger.jpg also works… but really doesn't get us > anything… we have to manually enter either way > > So from terminal if you do "cd /" and you look under Volumes… the > DriveFileStream is not there? > > in this if I do > > cd /Volumes > I will see > > MyDrive HD > Chola > BR Back ups (USB for local Time machine backups) > > But "Chola" is a "network store"… I guess I don’t understand the nature of > the connection/Mount context to Googles Drive File Stream… how that is > different? > > At any rate you do seem to have a different, though obviously related > issue. > > > > > On 10/30/17, 6:09 AM, "use-livecode on behalf of Mike Kerner via > use-livecode" use-livecode@lists.runrev.com> wrote: > > On "b", I have three machines that I use. Two of them use Google's > Backup > and Sync service, and the other uses Google's Drive File Stream. So > in for > two of the machines, the answer is "mostly yes" - the difference is the > username, as the "Drive" folder is in the user folder. For the the > third, > the answer is "no", because in that case, the access is treated as a > network store, i.e. its own drive. > > ___ > 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: Relative Paths in Property Inspector
@Mike I tried to duplicate your 3rd case. Are you on Mac OS X? if I create a stack, place and img in an adjacent image folder and move to the server ("Chola") in the next room… set the img filename to img/tiger.jpg it works @brian ./img/tiger.jpg also works… but really doesn't get us anything… we have to manually enter either way So from terminal if you do "cd /" and you look under Volumes… the DriveFileStream is not there? in this if I do cd /Volumes I will see MyDrive HD Chola BR Back ups (USB for local Time machine backups) But "Chola" is a "network store"… I guess I don’t understand the nature of the connection/Mount context to Googles Drive File Stream… how that is different? At any rate you do seem to have a different, though obviously related issue. On 10/30/17, 6:09 AM, "use-livecode on behalf of Mike Kerner via use-livecode"wrote: On "b", I have three machines that I use. Two of them use Google's Backup and Sync service, and the other uses Google's Drive File Stream. So in for two of the machines, the answer is "mostly yes" - the difference is the username, as the "Drive" folder is in the user folder. For the the third, the answer is "no", because in that case, the access is treated as a network store, i.e. its own drive. ___ 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: Relative Paths in Property Inspector
On "b", I have three machines that I use. Two of them use Google's Backup and Sync service, and the other uses Google's Drive File Stream. So in for two of the machines, the answer is "mostly yes" - the difference is the username, as the "Drive" folder is in the user folder. For the the third, the answer is "no", because in that case, the access is treated as a network store, i.e. its own drive. On Mon, Oct 30, 2017 at 11:26 AM, Sannyasin Brahmanathaswami via use-livecodewrote: > @ Brian: good question. Now that I think of it… maybe both would be good? > > Option 1: If the pref is on, then the check box is checked by default in > the PI; otherwise it's not. This allows the user to use full path. Option > 2: no check box in PI, just a pref because: assumes no use cases there are > that would "break" if the path was always relative. But I don't know if > that assumption is correct, and option 1 seems to be "no skin off the IDE" > to implement. > > Possibly in some secure situation a stack wants to only able to access > local resources and would fail to find them, by design, if ported as a > package elsewhere. Seems very rare use case to me. One faces this same > issue every day in our team… with DTPublishing with doc + links to images, > and we all just wish Adobe would make relative paths work "out of the box, > everywhere, all the time." > > @ Mikey > a) we understand your use cases… in fact I have the exact same set right > here; GIT is in effect the net storage case you describe, and albeit > instead of a mounted drive you have your cloned project folder on disk… on > another project we used Dropbox. > b) Sorry to be tedious, but you did not confirm: if you keep the stack and > the image in the same folder on the "cloud" drive that appears as a mount > point on your system… > > ~/Dropbox/Pet Project/animals.livecode > ~/Dropbox/Pet Project/img/dangerous-pets/tiger.jpg > > do relative paths work? of course I could test here, but just want to be > sure your context is the same. > > c) Yes, I will file an QR enhancement request… and agreed they should be > considered together, > > But first: if your answer to b) above is "No" that the relative path on a > mounted instance of your cloud drive doesn't work then we have a different > problem, > > OR > > if the answer is "Yes" it does work… then we do indeed have the > same/parallel request and I can just append your QR > > BR > > > Brian wrote: > > So the ask is for a check box in the PI (near the source field with a > label > like “Relative path”)? And when checked, the PI would automatically > trim > the path to be relative to the stack file (probably with the assumption > that it only goes down the hierarchy). > > Or are you asking for a preference that would default to relative path > names when choosing files in the PI? > > ___ > 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: Relative Paths in Property Inspector
@ Brian: good question. Now that I think of it… maybe both would be good? Option 1: If the pref is on, then the check box is checked by default in the PI; otherwise it's not. This allows the user to use full path. Option 2: no check box in PI, just a pref because: assumes no use cases there are that would "break" if the path was always relative. But I don't know if that assumption is correct, and option 1 seems to be "no skin off the IDE" to implement. Possibly in some secure situation a stack wants to only able to access local resources and would fail to find them, by design, if ported as a package elsewhere. Seems very rare use case to me. One faces this same issue every day in our team… with DTPublishing with doc + links to images, and we all just wish Adobe would make relative paths work "out of the box, everywhere, all the time." @ Mikey a) we understand your use cases… in fact I have the exact same set right here; GIT is in effect the net storage case you describe, and albeit instead of a mounted drive you have your cloned project folder on disk… on another project we used Dropbox. b) Sorry to be tedious, but you did not confirm: if you keep the stack and the image in the same folder on the "cloud" drive that appears as a mount point on your system… ~/Dropbox/Pet Project/animals.livecode ~/Dropbox/Pet Project/img/dangerous-pets/tiger.jpg do relative paths work? of course I could test here, but just want to be sure your context is the same. c) Yes, I will file an QR enhancement request… and agreed they should be considered together, But first: if your answer to b) above is "No" that the relative path on a mounted instance of your cloud drive doesn't work then we have a different problem, OR if the answer is "Yes" it does work… then we do indeed have the same/parallel request and I can just append your QR BR Brian wrote: So the ask is for a check box in the PI (near the source field with a label like “Relative path”)? And when checked, the PI would automatically trim the path to be relative to the stack file (probably with the assumption that it only goes down the hierarchy). Or are you asking for a preference that would default to relative path names when choosing files in the PI? ___ 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: Relative Paths in Property Inspector
I think you can. Preface the path with ./ which will refer to the path of the executable. And if I am not mistaken, ../ will refer to the parent folder of the application folder. Bob S > On Oct 29, 2017, at 12:02 , Sannyasin Brahmanathaswami via use-livecode >wrote: > > End backstory (please correct anything you see that is wrong) > > So, why can't we just a relative path in the Property Inspector itself? The > browser tool will always return full path from User down to the "asset.jpg"… > if I send that stack to someone else, or use a GIT work flow where these > stacks are "pure views" (i.e. no actual imported images anywhere) along with > the images. the paths are broken. So, long way of asking: ___ 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: Relative Paths in Property Inspector
Sure, but if you were to do that, then I should have an LC-wide preference that I can set so that I don't have to fix it for every project. ___ 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: Relative Paths in Property Inspector
What I meant was not that you shouldn't file a QR, but that I think that all the requests for relative paths should be combined because I think relative paths across LC would be beneficial. Sorry for not being clear about that. I have four obvious cases, where I see a benefit: 1) Using multiple machines - unless usernames are the same, absolute paths won't be the same 2) Using multiple platforms. 3) Using network syncing tools. If I use a syncing tool, the absolute paths won't match, either, unless both the username and the os are the same 4) Using network file storage. The path for syncing and storage won't be the same - for example, if on a lappie you use a network file storage tool to save disk space, the path will start with a network drive letter. If you use a syncing tool for the same service on a desktop, the path will start with some local drive and will be at least one level deeper. On Sun, Oct 29, 2017 at 10:30 PM, Sannyasin Brahmanathaswami via use-livecodewrote: > BR: are you keeping your stacks next to the images? > > like this > > ~/Dropbox/Pet Project/animals.livecode > ~/Dropbox/Pet Project/img/dangerous-pets/tiger.jpg > > and if you set the image filename to "img/dangerous-pets/tiger.jpg" > > it fails? > > -- > > Mike Kerner wrote: > > it is related. As soon as I saw your post I said "gee, that looks > familiar". > > Brahmanathaswami wrote: > > [snip] now you can > > > > a) manually chop of the lead down to this in the property inspector > > > > img/thumbs/little-rooster.jpg > > > > # and it works… this is also portable if you include "img/*" in the > > stackfiles when create your standalone and the filename is saved > relative > > to the stack, and, assuming you keep the folder structure intact you > don't > > have to even mess with defaultfolder or even > specialFolderPath("engine") > > because the "relativity" of the path is respected in any and all > contexts > > (I think…) > > > > so you can also programatically do this > > > > set the filename of img "myPet" to "img/thumbs/little-rooster.jpg" > > > So, why can't we just a relative path in the Property Inspector > itself? > > The browser tool will always return full path from User down to the > > "asset.jpg"… if I send that stack to someone else, or use a GIT work > flow > > where these stacks are "pure views" (i.e. no actual imported images > > anywhere) along with the images. the paths are broken. So, long > way of > > asking: > > > > Do we need an enhancement request for a check box in the PI to set > the > > path as relative to the stack? Seems like that would be super usefu > > > > Mikey has this request in since May '16… which feels related > > > > http://quality.livecode.com/show_bug.cgi?id=17705 > > > > but the suggestion for having this in the PI seems a bit different, > and > > might not actually solve his issue for using a cloud instance of his > > project. > > > > Brahmanathaswami > > > > > > > > > > > > ___ > > 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 > > ___ > 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: Relative Paths in Property Inspector
So the ask is for a check box in the PI (near the source field with a label like “Relative path”)? And when checked, the PI would automatically trim the path to be relative to the stack file (probably with the assumption that it only goes down the hierarchy). Or are you asking for a preference that would default to relative path names when choosing files in the PI? I think I know the behavior script that would need to trim the file name (for images). Not quite sure how to get the path of the stack file in that context yet. On Sun, Oct 29, 2017 at 8:02 PM Mike Kerner via use-livecode < use-livecode@lists.runrev.com> wrote: > it is related. As soon as I saw your post I said "gee, that looks > familiar". > > On Sun, Oct 29, 2017 at 3:02 PM, Sannyasin Brahmanathaswami via > use-livecodewrote: > > > Backstory: > > > > Sometime back in a round with HQ we got the engine to "remember" relative > > path settings for the filenames of images/players etc.. such that it > would > > not default to full path from root on the drive which makes the path > unique > > to that user and no longer portable… so "relativity" go supported/sticky > in > > different dev scenarios… > > > > so far so good… if you set the filename in an image in a stack that lives > > here: > > > > User/MyDrive/myProject/coolAnimals.livecode > > > > with images here to: > > > > User/MyDrive/myProject/img/thumbs/little-rooster.jpg > > > > # it, obviously works But, now you can > > > > a) manually chop of the lead down to this in the property inspector > > > > img/thumbs/little-rooster.jpg > > > > # and it works… this is also portable if you include "img/*" in the > > stackfiles when create your standalone and the filename is saved relative > > to the stack, and, assuming you keep the folder structure intact you > don't > > have to even mess with defaultfolder or even specialFolderPath("engine") > > because the "relativity" of the path is respected in any and all contexts > > (I think…) > > > > so you can also programatically do this > > > > set the filename of img "myPet" to "img/thumbs/little-rooster.jpg" > > > > and that also works though you do need to use "specialFolderPath" > > functions on mobile. > > > > Again, so far so good… > > > > End backstory (please correct anything you see that is wrong) > > > > So, why can't we just a relative path in the Property Inspector itself? > > The browser tool will always return full path from User down to the > > "asset.jpg"… if I send that stack to someone else, or use a GIT work flow > > where these stacks are "pure views" (i.e. no actual imported images > > anywhere) along with the images. the paths are broken. So, long way of > > asking: > > > > Do we need an enhancement request for a check box in the PI to set the > > path as relative to the stack? Seems like that would be super usefu > > > > Mikey has this request in since May '16… which feels related > > > > http://quality.livecode.com/show_bug.cgi?id=17705 > > > > but the suggestion for having this in the PI seems a bit different, and > > might not actually solve his issue for using a cloud instance of his > > project. > > > > Brahmanathaswami > > > > > > > > > > > > ___ > > 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 ___ 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: Relative Paths in Property Inspector
BR: are you keeping your stacks next to the images? like this ~/Dropbox/Pet Project/animals.livecode ~/Dropbox/Pet Project/img/dangerous-pets/tiger.jpg and if you set the image filename to "img/dangerous-pets/tiger.jpg" it fails? -- Mike Kerner wrote: it is related. As soon as I saw your post I said "gee, that looks familiar". Brahmanathaswami wrote: [snip] now you can > > a) manually chop of the lead down to this in the property inspector > > img/thumbs/little-rooster.jpg > > # and it works… this is also portable if you include "img/*" in the > stackfiles when create your standalone and the filename is saved relative > to the stack, and, assuming you keep the folder structure intact you don't > have to even mess with defaultfolder or even specialFolderPath("engine") > because the "relativity" of the path is respected in any and all contexts > (I think…) > > so you can also programatically do this > > set the filename of img "myPet" to "img/thumbs/little-rooster.jpg" > So, why can't we just a relative path in the Property Inspector itself? > The browser tool will always return full path from User down to the > "asset.jpg"… if I send that stack to someone else, or use a GIT work flow > where these stacks are "pure views" (i.e. no actual imported images > anywhere) along with the images. the paths are broken. So, long way of > asking: > > Do we need an enhancement request for a check box in the PI to set the > path as relative to the stack? Seems like that would be super usefu > > Mikey has this request in since May '16… which feels related > > http://quality.livecode.com/show_bug.cgi?id=17705 > > but the suggestion for having this in the PI seems a bit different, and > might not actually solve his issue for using a cloud instance of his > project. > > Brahmanathaswami > > > > > > ___ > 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 ___ 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: Relative Paths in Property Inspector
it is related. As soon as I saw your post I said "gee, that looks familiar". On Sun, Oct 29, 2017 at 3:02 PM, Sannyasin Brahmanathaswami via use-livecodewrote: > Backstory: > > Sometime back in a round with HQ we got the engine to "remember" relative > path settings for the filenames of images/players etc.. such that it would > not default to full path from root on the drive which makes the path unique > to that user and no longer portable… so "relativity" go supported/sticky in > different dev scenarios… > > so far so good… if you set the filename in an image in a stack that lives > here: > > User/MyDrive/myProject/coolAnimals.livecode > > with images here to: > > User/MyDrive/myProject/img/thumbs/little-rooster.jpg > > # it, obviously works But, now you can > > a) manually chop of the lead down to this in the property inspector > > img/thumbs/little-rooster.jpg > > # and it works… this is also portable if you include "img/*" in the > stackfiles when create your standalone and the filename is saved relative > to the stack, and, assuming you keep the folder structure intact you don't > have to even mess with defaultfolder or even specialFolderPath("engine") > because the "relativity" of the path is respected in any and all contexts > (I think…) > > so you can also programatically do this > > set the filename of img "myPet" to "img/thumbs/little-rooster.jpg" > > and that also works though you do need to use "specialFolderPath" > functions on mobile. > > Again, so far so good… > > End backstory (please correct anything you see that is wrong) > > So, why can't we just a relative path in the Property Inspector itself? > The browser tool will always return full path from User down to the > "asset.jpg"… if I send that stack to someone else, or use a GIT work flow > where these stacks are "pure views" (i.e. no actual imported images > anywhere) along with the images. the paths are broken. So, long way of > asking: > > Do we need an enhancement request for a check box in the PI to set the > path as relative to the stack? Seems like that would be super usefu > > Mikey has this request in since May '16… which feels related > > http://quality.livecode.com/show_bug.cgi?id=17705 > > but the suggestion for having this in the PI seems a bit different, and > might not actually solve his issue for using a cloud instance of his > project. > > Brahmanathaswami > > > > > > ___ > 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
Relative Paths in Property Inspector
Backstory: Sometime back in a round with HQ we got the engine to "remember" relative path settings for the filenames of images/players etc.. such that it would not default to full path from root on the drive which makes the path unique to that user and no longer portable… so "relativity" go supported/sticky in different dev scenarios… so far so good… if you set the filename in an image in a stack that lives here: User/MyDrive/myProject/coolAnimals.livecode with images here to: User/MyDrive/myProject/img/thumbs/little-rooster.jpg # it, obviously works But, now you can a) manually chop of the lead down to this in the property inspector img/thumbs/little-rooster.jpg # and it works… this is also portable if you include "img/*" in the stackfiles when create your standalone and the filename is saved relative to the stack, and, assuming you keep the folder structure intact you don't have to even mess with defaultfolder or even specialFolderPath("engine") because the "relativity" of the path is respected in any and all contexts (I think…) so you can also programatically do this set the filename of img "myPet" to "img/thumbs/little-rooster.jpg" and that also works though you do need to use "specialFolderPath" functions on mobile. Again, so far so good… End backstory (please correct anything you see that is wrong) So, why can't we just a relative path in the Property Inspector itself? The browser tool will always return full path from User down to the "asset.jpg"… if I send that stack to someone else, or use a GIT work flow where these stacks are "pure views" (i.e. no actual imported images anywhere) along with the images. the paths are broken. So, long way of asking: Do we need an enhancement request for a check box in the PI to set the path as relative to the stack? Seems like that would be super usefu Mikey has this request in since May '16… which feels related http://quality.livecode.com/show_bug.cgi?id=17705 but the suggestion for having this in the PI seems a bit different, and might not actually solve his issue for using a cloud instance of his project. Brahmanathaswami ___ 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