Some Basic Misunderstandings/Problems with RunRev
Thomas McGrath III
3mcgrath at adelphia.net
Wed Apr 14 18:32:59 EDT 2004
Marian,
Yeah, i know :-)
I too have issues with the E-docs (I have the printed docs to help me
there). So asking questions is a good thing and I encourage that. But
again, 'Some' reading (perusing) is always going to be necessary
especially coming from another language.
I hope I wasn't rude but rather just trying to point him in that
direction. I think he came from C(C++) and Rev has an intro that
describes just what he wanted to do for C(C++) programmers new to REV.
In His and my defense, there are a lot of things that are not clear in
the docs no matter how much we read them. And for that I empathize with
Dave, completely.
Tom
On Apr 14, 2004, at 4:18 PM, Marian Petrides wrote:
> Tom
>
> In Dave's defense, I too have trouble finding what I need in the dox
> sometimes. Lack of an index is one issue, lack of a comprehensive
> book like Danny Goodman's that takes you from start to finish in words
> of one phoneme is another. Dan's book may eventually address the
> second issue, but we only have part 1 right now. The material may be
> there, but if you don't know where to look, it might as well not be
> there.
>
> This is NOT a flame about the dox. It is a statement that the blind
> (me) sometimes need some direction in finding the correct door to
> enter--which is a vital function of this list.
>
> And, I for one am very glad Dave asked his questions because I learned
> about things I never would have thought to explore --in the form of
> suggested solutions to the problem he posed.
>
> Marian
>
>
>
>
> On Apr 14, 2004, at 4:04 PM, Thomas McGrath III wrote:
>
>> Dave,
>>
>> This is all written down in the docs. Creating a standalone and then
>> how to save it is using a splash screen app is documented.
>>
>> You have to do 'some' reading to get up to speed in any new
>> programming tool and the same applies here with REV. I too am
>> learning and have been pointed to the docs time and again 'until' I
>> too started reading them.
>>
>> I only say this because it will cut down on your frustration and make
>> your questions easier to answer on the list.
>>
>> HTH
>>
>> Tom
>>
>> On Apr 14, 2004, at 2:37 PM, David Burgun wrote:
>>
>>> Hi All,
>>>
>>>> You could have a two stack system: the app. stack and the interface
>>>> stack.
>>>> If the user clicks on the app., it goes to the interface stack.
>>>> If the user clicks on the interface stack it "starts using" the
>>>> app. stack.
>>>> No matter what the user does he/she ends up in the interface stack,
>>>> which can
>>>> be changed and saved.
>>>> Paul Looney
>>>
>>> Ahhhh, this sounds more like what I want!
>>>
>>> But how do I set this up? At the moment I have a "Stack" that
>>> contains all my GUI elements. From what you are saying I assume
>>> that's I'd need a shell that forms the standalone, this could just
>>> display a Splash Screen and then issue the "start using" command on
>>> the Main GUI.
>>>
>>> Question:
>>> Do I just locate the GUI stack in the same folder as the Standalone
>>> and if so can I use the "Copy Files" panel of the "Standalone
>>> Application Settings" to do this or do I have to move/copy it
>>> manually each time?
>>>
>>> However they get there, I am assuming that I will have the following
>>> files in the Standalone folder:
>>>
>>> StandaloneApp
>>> InitialGUI.rev
>>>
>>> So the user double clicks the Standalone which displays it's splash
>>> screen and then checks for a file called "NewGUI.rev" (which won't
>>> exist the first time) and if the file doesn't exist, copies the file
>>> "InitialGUI.rev" into "NewGUI.rev".
>>>
>>> Either way, it then issues a "start using NewGUI.rev" command".
>>>
>>> The copy code is to allow the user to reset back to the factory
>>> settings if need be, all that need be done is for the "NewGUI.rev"
>>> to be moved or renamed or deleted and upon the next launch, the
>>> factory defaults are back in place.
>>>
>>> More questions:
>>>
>>> Does the NewGUI.rev Stack I create have a main stack and sub-stacks
>>> as normal?
>>>
>>> If not, how do I set it up?
>>>
>>> If so, when I issue a "save this stack" command does it save all
>>> stacks and the mainStack?
>>>
>>> Thanks a lot for your time, this looks like the best approach for
>>> what I want to do. I just want to be sure it can do what I want
>>> before I start re-arranging my stack files again!
>>>
>>> All the Best
>>> Dave
>>> _______________________________________________
>>> use-revolution mailing list
>>> use-revolution at lists.runrev.com
>>> http://lists.runrev.com/mailman/listinfo/use-revolution
>>>
>>>
>>
>> Thomas J. McGrath III
>> SCS
>> 1000 Killarney Dr.
>> Pittsburgh, PA 15234
>> 412-885-8541
>>
>> _______________________________________________
>> use-revolution mailing list
>> use-revolution at lists.runrev.com
>> http://lists.runrev.com/mailman/listinfo/use-revolution
>>
>
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> http://lists.runrev.com/mailman/listinfo/use-revolution
>
>
Thomas J. McGrath III
SCS
1000 Killarney Dr.
Pittsburgh, PA 15234
412-885-8541
More information about the use-livecode
mailing list