On Sun, Jan 18, 2015 at 3:43 AM, Richmond
wrote:
I can imagine a scenario where somebody uses an app both at work and at
> home and for
> security reasons carries the app around in their pocket on a USB
> flash-drive or an SD card
> and wants the data to ride with it.
>
Not sure that makes sense
It wouldn’t occur to me to save data within the executable code (UI) area. For
my purposes, I’d only save data in a separate file, mysql light db, or online
mysql db. Apple has a folder in the Library folder called “Application
Support”. That’s where I put preferences, licenses, and stuff that d
On Jan 16, 2015, at 7:22 PM, Richard Gaskin wrote:
> Among those who've never used HyperCard, how many people would think of
> saving data bound to the UI?
Harumph. Programs go in the card reader and data goes on the tape drive.
___
use-livecode mai
Richard-
Saturday, January 17, 2015, 11:40:48 AM, you wrote:
> Mark Rauterkus wrote:
>> Q asked: Among those who've never used HyperCard, how many people would
>> think of saving data bound to the UI?
>>
>> My $.02: LOTS and LOTS of mere mortals.
> I can see the attraction to it, esp. in cases w
On 17/01/15 21:40, Richard Gaskin wrote:
Mark Rauterkus wrote:
Q asked: Among those who've never used HyperCard, how many people would
think of saving data bound to the UI?
My $.02: LOTS and LOTS of mere mortals.
I can see the attraction to it, esp. in cases where you're building a
quickie a
Mark Rauterkus wrote:
Q asked: Among those who've never used HyperCard, how many people would
think of saving data bound to the UI?
My $.02: LOTS and LOTS of mere mortals.
I can see the attraction to it, esp. in cases where you're building a
quickie ad hoc solution with no vision for later ve
Hi,
Q asked: Among those who've never used HyperCard, how many people would
think of
saving data bound to the UI?
My $.02: LOTS and LOTS of mere mortals.
--
Ta.
Mark Rauterkus mark.rauter...@gmail.com
PPS Summer Dreamers' Swim and Water Polo Camp Head Coach
Varsity Boys Swim Coach, Pit
Count 1 for me. Never considered saving user data in the application
folder. Just seems weird.
On Jan 16, 2015 7:23 PM, "Richard Gaskin"
wrote:
> This thread about "splash stacks" has me wondering:
>
> Among those who've never used HyperCard, how many people would think of
> saving data bound to
Kay:
The following won’t address the issue of the RunRev article you cite needing to
be updated, which clearly needs to happen. But it might help you to know that
there are really two different issues being addressed here: saving stack data,
and making an updatable stack. While the splash scr
This thread about "splash stacks" has me wondering:
Among those who've never used HyperCard, how many people would think of
saving data bound to the UI?
--
Richard Gaskin
Fourth World Systems
Software Design and Development for Desktop, Mobile, and Web
_
Jacque,
it's more likely I'm confused. You and Richard are the experts here so I
tend to be wary if I'm going against the flow.
The original post simply asked about Saving User preferences. Unfortunately
there was no mention of OS, nor was there any mention that it used to
'working for ages up un
Kay C Lan wrote:
This problem comes up when those new to programming and/or LC follow an
example How-To that doesn't work for all platforms and/or goes against OS
guidelines. Saving User Data is a basic app requirement, the example given
should work on ALL platforms.
IMO if the How-To example u
simple but full featured under cursor colour picker /
finder.
http://www.pointandsee.co.uk - made with LiveCode
--
View this message in context:
http://runtime-revolution.278305.n4.nabble.com/Storing-and-saving-a-setting-in-a-stand-alone-tp4687858p4687895.html
Sent from the Revolution - User mailin
On 1/15/2015 9:31 PM, Kay C Lan wrote:
Yes Scott,you are right it's still a valid method, but it's not a method
that works for all platforms and for a product who's key feature is that it
is cross platform, desktop and mobile, I see it being counter productive to
provide an example that isn't.
On Fri, Jan 16, 2015 at 8:40 AM, Richard Gaskin
wrote:
On the contrary, as the rest of your post points out, it's increasingly
> useful as OS file system permissions get ever more restrictive.
>
Yes Scott,you are right it's still a valid method, but it's not a method
that works for all platforms
Kay C Lan wrote:
* It would probably be wise for RunRev to remove any mention of the Splash
Stack method on their how-to site as it is clearly not an approach that
should be used any more.
On the contrary, as the rest of your post points out, it's increasingly
useful as OS file system permissi
RunRev may need to edit the description of the method but why remove it? What
is preventing developers from placing their primary stacks in the Documents
folder or any other writable folder?
AFAICT, using the splash stack technique is still valid, but you may not be
able to save the stack in a
On Fri, Jan 16, 2015 at 3:57 AM, Richard Gaskin
wrote:
>
> Why do you suppose this has survived so long with no one discovering it
> until now?
>
Whilst I may be a Mac fanboy, I'm definitely anti-iOSing of OS X. That
said, one of the few side effects may be the herding of LCers to store User
dat
On 1/15/2015 2:54 PM, J. Landman Gay wrote:
my main project is still done in LC 6.5.x
Oops, that should be 6.6.5. I'm not THAT far behind. ;)
--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
On 1/15/2015 1:57 PM, Richard Gaskin wrote:
J. Landman Gay wrote:
> On 1/15/2015 10:05 AM, Richard Gaskin wrote:
>> While the absence of reports related to general file access in the
>> bundle would seem to suggest this change was implemented well in the
>> engine, René's report shows this w
J. Landman Gay wrote:
> On 1/15/2015 10:05 AM, Richard Gaskin wrote:
>> While the absence of reports related to general file access in the
>> bundle would seem to suggest this change was implemented well in the
>> engine, René's report shows this workaround for Apple's new security
>> policy need
On 1/15/2015 10:05 AM, Richard Gaskin wrote:
While the absence of reports related to general file access in the
bundle would seem to suggest this change was implemented well in the
engine, René's report shows this workaround for Apple's new security
policy needs to be added to the SQLite external
On Thu, Jan 15, 2015 at 8:05 AM, Richard Gaskin
wrote:
> Hanson's confirmation there suggests they're working on it now, and given
> how widely SQLite is used I'd be surprised if the fix isn't in the next
> build.
Hopefully they will take the opportunity to get the SQLite library up to
date. C
René Micout wrote:
>> Le 15 janv. 2015 à 15:17, dunbarx at aol.com a écrit :
>>
>> You know, recently I tried to make a "splash" standalone in 6.7,
>> the first I needed to in a while (the last was in 5.x) and it
>> would not work. I thought it was something I was doing wrong,
>> but was not on m
> Le 15 janv. 2015 à 15:17, dunb...@aol.com a écrit :
>
> Rene.
>
>
> OOOH.
>
>
> You know, recently I tried to make a "splash" standalone in 6.7, the first I
> needed to in a while (the last was in 5.x) and it would not work. I thought
> it was something I was doing wrong, but was not on m
Shawn Blc wrote:
Can someone point me in the right direction?
I want to save a setting in stand alone application. This setting will be
different for each person (name).
Once it's set, the user won't be prompted to enter again.
OSes don't allow applications to modify themselves. Back in the
e, but how could it have gone unnoticed?
Craig
-Original Message-
From: René Micout
To: How to use LiveCode
Sent: Thu, Jan 15, 2015 9:14 am
Subject: Re: Storing and saving a setting in a stand alone
> Le 15 janv. 2015 à 15:08, dunb...@aol.com a écrit :
>
> Hi.
>
>
> Le 15 janv. 2015 à 15:08, dunb...@aol.com a écrit :
>
> Hi.
>
>
> Are you talking about the fact that a single stack, which is the executable
> if you save it as a standalone, cannot save to itself? If so, there are
> several threads on the forums that address this. My favorite is the "spla
on
Craig Newman
-Original Message-
From: Shawn Blc
To: How to use LiveCode
Sent: Thu, Jan 15, 2015 8:28 am
Subject: Storing and saving a setting in a stand alone
Can someone point me in the right direction?
I want to save a setting in stand alone application. This setting will be
dif
Can someone point me in the right direction?
I want to save a setting in stand alone application. This setting will be
different for each person (name).
Once it's set, the user won't be prompted to enter again.
___
use-livecode mailing list
use-livecode@
30 matches
Mail list logo
