Bonjour Thierry,
Why don't you store directly your text files into custom properties,
the name of which would be the path?
Of course you have to replace spaces and slashes with some string
that will not break the name of the custom prop into several parts :-)
BTW note that custom props names
Wholy moly... The file system was definately NOT made to be a live data store.
For one, disc IO is several orders of magnitude slower than memory IO. Maybe
soon a memory/file system meld will revolutionize computing, be we are about 30
years behind this. Retrieve your data from disc and unpac
. Be good to your
disc.
-Original Message-
From: "Randall Lee Reetz" <[EMAIL PROTECTED]>
To: "How to use Revolution"
Sent: 1/16/2008 9:38 AM
Subject: RE: importing a bunch of files
Wholy moly... The file system was definately NOT made to be a live data store
Le 16 janv. 08 à 17:39, Eric Chatonet a écrit :
Bonjour Thierry,
Why don't you store directly your text files into custom
properties, the name of which would be the path?
Why not
Ok, it's a mix solution from the 2 I exposed :-)
Of course you have to replace spaces and slashes with so
Well :-)
You can also set a specific custom property set with custom
properties the name of which does not matter and parse it:
In each custom property, line 1 will be the path and line 2 to -1
contents :-)
Le 16 janv. 08 à 18:51, Thierry a écrit :
Le 16 janv. 08 à 17:39, Eric Chatonet a
Hi Randall,
Not only that but using your disc files as dat fields or even
record will seriously overburden your file system's day to day
efficiency. You could easily add orders of magnitude to the number
of files and directories on disc.. Seriously slowing down a lot of
OS (and finder)
Thierry wrote:
Of course you have to replace spaces and slashes with some string
that will not break the name of the custom prop into several parts :-)
Yes, I'm aware of that.
I think such failure depends on how it's done.
I just ran this test:
on mouseUp
put "some/thing" into v1
put
I posted the mail below but it did not appear in the list: so I
apologize if it should appear twice.
Well :-)
You can also set a specific custom property set with custom
properties the name of which does not matter and parse it:
In each custom property, line 1 will be the path and line 2 to -
If you follow shuch a scheme, you will have to keep your internal data in
lockstep with your stored data structure. Choose one as master and let the
other slave to it (always sticking to this heirarchy). Either way, you will
have to navigate some form of object tree... And translate that out t
This 256 char path limit... who's is it... File system? Rev?
-Original Message-
From: "Thierry" <[EMAIL PROTECTED]>
To: "How to use Revolution"
Sent: 1/16/2008 9:51 AM
Subject: Re: importing a bunch of files
Le 16 janv. 08 à 17:39, Eric Chatonet a écri
Richard,
In your script, it appears that a custom prop is dynamically declared
just by setting it's value? Is this all you have to do? In
SuperCard, one has to specifically declare a "user" property with a
"define" statement before ever setting it's value. Otherwise it
doesn't know if
At 10:18 AM -0800 1/16/2008, Richard Gaskin wrote:
Thierry wrote:
Of course you have to replace spaces and slashes with some string
that will not break the name of the custom prop into several parts
:-)
I just ran this test:
on mouseUp
put "some/thing" into v1
put "some thing" into v2
Hi Randall,
Le 16 janv. 08 à 19:41, Randall Lee Reetz a écrit :
This 256 char path limit... who's is it... File system? Rev?
Obviously a Rev choice about used variables.
See 'Documentation/rev/Memory and Limits Reference.rev'
Best regards from Paris,
Eric Chatonet.
-
Randall Lee Reetz wrote:
In your script, it appears that a custom prop is dynamically declared
just by setting it's value? Is this all you have to do? In
SuperCard, one has to specifically declare a "user" property with a
"define" statement before ever setting it's value.
Yeah, and that
set the uTest["some\thing"] of this stack to "test"
cautioning against naming custom properties anything that
wouldn't be legal for variables, on the grounds that it may work
now but might not work forever.
Where can we see more about: "be legal for variables" ?
Regards,
Thierr
Hi Randall,
If you follow shuch a scheme, <...>
All of this points to why it makes sense at times to interface your
stack to a professional data base and let it do all of this
structural efficiency heavylifting (that is what it is there for).
I like to build my own cause i like to
On Jan 17, 2008, at 5:56 AM, Thierry wrote:
set the uTest["some\thing"] of this stack to "test"
cautioning against naming custom properties anything that
wouldn't be legal for variables, on the grounds that it may work
now but might not work forever.
Where can we see more about
On Jan 17, 2008, at 9:29 AM, Devin Asay wrote:
On Jan 17, 2008, at 5:56 AM, Thierry wrote:
Where can we see more about: "be legal for variables" ?
From our tutorials at http://revolution.byu.edu/transcript/
Transcript1.php
A Revolution variable name:
May be any single string (no spac
Have you written a file tree spider?
-Original Message-
From: "Thierry" <[EMAIL PROTECTED]>
To: "How to use Revolution"
Sent: 1/17/2008 4:54 AM
Subject: Re: importing a bunch of files
Hi Randall,
> If you follow shuch a scheme, <...>
> All o
Where can we see more about: "be legal for variables" ?
Regards,
Thierry
The 'rules' for this might not be documented.
I've had problems with custom properties that are named like this:
1 a number or begin with a number can be a problem
2 spaces in the name doesn't always work
3 use on
Hi Devin,
On Jan 17, 2008, at 5:56 AM, Thierry wrote:
Where can we see more about: "be legal for variables" ?
Ah, found it: The Revolution User Guide PDF, section 5.5.5 -
Variable Names. (Open Documentation, click User Guide, then launch
PDF.)
Ok, read it again, and there one can re
Where can we see more about: "be legal for variables" ?
The 'rules' for this might not be documented.
I've had problems with custom properties that are named like this:
1 a number or begin with a number can be a problem
2 spaces in the name doesn't always work
3 use only alphanumeric charac
Le 17 janv. 08 à 19:31, Randall Lee Reetz a écrit :
Have you written a file tree spider?
Not at all :-)
It's only a kind of administration tool to embed in *one* file
everything we need to run a complex application.
Interesting for Quality and Ease of deployment
I promess to show you t
On Jan 18, 2008, at 3:58 AM, Thierry wrote:
Hi Devin,
On Jan 17, 2008, at 5:56 AM, Thierry wrote:
Where can we see more about: "be legal for variables" ?
Ah, found it: The Revolution User Guide PDF, section 5.5.5 -
Variable Names. (Open Documentation, click User Guide, then launch
On Wed, 16 Jan 2008 12:19:44 -0800, Randall Lee Reetz wrote:
> Richard,
>
> In your script, it appears that a custom prop is dynamically declared
> just by setting it's value? Is this all you have to do? In
> SuperCard, one has to specifically declare a "user" property with a
> "define" stat
Randall Lee Reetz wrote:
> Looks like rev does lots of things SC doesnt, what about the
> other way around?
Glad you asked. I'd made myself somewhat tiresome to some here over the
last several years with my constant nagging about the two issues below,
but since you asked I'll make this my now-o
On Fri, 18 Jan 2008 11:51:13 -0800, Randall Lee Reetz wrote:
> Thanks richard. I would have thnked you off line but this samsung
> blackjack of mine is a minefield of hopelessness... It stuck me here
> so here i am. Looks like rev does lots of things SC doesnt, what
> about the other way arou
27 matches
Mail list logo