Re: Startup question

2009-08-11 Thread Joe F.
The easy way to do this in Leopard is just drag any item to the Dock,  
right click on it and choose "Open at Login..." from the popup.


To make it open in a specific (non default) application: select the  
file in a window or on the desktop; press command-I or right-click>"  
Get Info". Set "Open with" to whatever you like. You can also choose a  
new default app to open all documents of that file type there.


Joe F.

On Aug 10, 2009, at 2:05 PM, Joe Lewis Wilkins wrote:


Colin, we thank you.

Joe Wilkins

On Aug 10, 2009, at 10:57 AM, Colin Holgate wrote:



On Aug 10, 2009, at 1:51 PM, Joe Lewis Wilkins wrote:

However, this still doesn't allow me to stipulate a "document" as  
in the past; just the application. Bummer.


Thats not true. Click the +, add in a document, and away you go.

Now, having it open a document using an application that is not the  
normal application for that document type, can't be expressed in  
one line, but you could add in an AppleScript standalone instead,  
and that could do whatever you want it to do.


___
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your  
subscription preferences:

http://lists.runrev.com/mailman/listinfo/use-revolution


___
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution


Re: Startup question

2009-08-10 Thread Joe Lewis Wilkins

Colin, we thank you.

Joe Wilkins

On Aug 10, 2009, at 10:57 AM, Colin Holgate wrote:



On Aug 10, 2009, at 1:51 PM, Joe Lewis Wilkins wrote:

However, this still doesn't allow me to stipulate a "document" as  
in the past; just the application. Bummer.


Thats not true. Click the +, add in a document, and away you go.

Now, having it open a document using an application that is not the  
normal application for that document type, can't be expressed in one  
line, but you could add in an AppleScript standalone instead, and  
that could do whatever you want it to do.


___
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution


Re: Startup question

2009-08-10 Thread Colin Holgate


On Aug 10, 2009, at 1:51 PM, Joe Lewis Wilkins wrote:

However, this still doesn't allow me to stipulate a "document" as in  
the past; just the application. Bummer.


Thats not true. Click the +, add in a document, and away you go.

Now, having it open a document using an application that is not the  
normal application for that document type, can't be expressed in one  
line, but you could add in an AppleScript standalone instead, and that  
could do whatever you want it to do.



___
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution


Re: Startup question

2009-08-10 Thread Edward D Lavieri Jr

Thanks for posting this, Colin.

I am a relatively new Mac user and love these knowledge bites.

Ed


On Aug 10, 2009, at 12:38 PM, Colin Holgate wrote:



On Aug 10, 2009, at 1:28 PM, Joe Lewis Wilkins wrote:


Sorry, I should have asked Finder Help the same question.


Indeed. And for anyone who wanted to know the answer:

System Preferences/Accounts/Your Account/Login Items.


___
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your  
subscription preferences:

http://lists.runrev.com/mailman/listinfo/use-revolution


___
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution


Re: Startup question

2009-08-10 Thread Joe Lewis Wilkins

Thanks, Colin,

However, this still doesn't allow me to stipulate a "document" as in  
the past; just the application. Bummer.


Joe Wilkins


On Aug 10, 2009, at 10:38 AM, Colin Holgate wrote:



On Aug 10, 2009, at 1:28 PM, Joe Lewis Wilkins wrote:


Sorry, I should have asked Finder Help the same question.


Indeed. And for anyone who wanted to know the answer:

System Preferences/Accounts/Your Account/Login Items.



___
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution


Re: Startup question

2009-08-10 Thread Colin Holgate


On Aug 10, 2009, at 1:28 PM, Joe Lewis Wilkins wrote:


Sorry, I should have asked Finder Help the same question.


Indeed. And for anyone who wanted to know the answer:

System Preferences/Accounts/Your Account/Login Items.


___
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution


Re: Startup question

2009-08-10 Thread Joe Lewis Wilkins

Sorry, I should have asked Finder Help the same question.
Joe Wilkins

___
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution


Re: startup question

2006-04-15 Thread Rob Cozens

Hi Stephen,

I just used preOpenStack for all the stuff that has to happen on 
startup...


works like a champ. Nothing can even see or touch the stack until 
everything is loaded.




Just so you and anyone else who might go this route knows:

Any reference to menus and menuItems in preOpenStack will not produce 
the desired result.


One can reference a menu button by name, id, or number, and change the 
menuItems by changing the button's text.  But references to "menu 
'File'" or "menuItem 'Save'", etc. made prior to preOpenCard will fail.


Rob Cozens
CCW, Serendipity Software Company

"And I, which was two fooles, do so grow three;
Who are a little wise, the best fooles bee."

from "The Triple Foole" by John Donne (1572-1631)

___
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution


Re: startup question

2006-04-14 Thread Stephen Barncard

A word of thanks goes out to all who suggested solutions to my startup problem;
Jim Ault, Chipp Walters, David Burgun, Dave Cragg, and Rob Cozens.

I just used preOpenStack for all the stuff that has to happen on startup...

works like a champ. Nothing can even see or touch the stack until 
everything is loaded.



All I can say is  duh... and thanks.

sqb
--
stephen barncard
s a n  f r a n c i s c o
- - -  - - - - - - - - -
___
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution


Re: startup question

2006-04-13 Thread Rob Cozens

Hi Stephen,


I have a chicken-and-egg situation..

I have a stack startup handler that works fine until it does a 'start 
using' for a library stack, and then immediately needs to use a 
handler in that stack just included.


What happens is that the code keeps marching along, the lib isn't 
active yet... and --- error.


I've put a 'wait 30 ticks' then a 'wait 60 ticks' before continuing. 
Not long enough? I know, I know, cheesy too.


What's the best way to allow the lib to load.. and how do I wait or 
hold for it?

I know there's an 'librarystack' message..



If this is the standard response from Revolution, my Foole's luck has 
kept me from experiencing it: I have not checked all my stacks this 
morning; however all but one I checked starts using the Library on 
preOpenStack but doesn't call a Library handler until openStack.


Suppose you started using the library stack in preOpenStack and 
transferred the library calls to the preOpenCard handler for the first 
card opened in your main stack?


I said "all but one" because sdbTools plugIn contains:

on preopenStack
  startLibrary "Serendipity_Library.rev"
  if the result then
beep
answer warning sdbNoLibraryWarning
close this stack
exit preopenStack
  end if
  put field "Source Database" of card "Translation" into 
translationSource

  get the sdbFile of this stack
  put it into savedDatabase
  put char 1 to -5 of item -1 it into referenceSource
  if referenceSource <> translationSource then
put referenceSource into field "Source Database" of card 
"Translation"

put empty into field "Destination Database" of card "Translation"
get empty -- trigger db save
  end if
  if it is not savedDatabase then save this stack
  set the icon of button "Serendipity" of card 1 to 103010
  try
revGoToFramePaused "GrowBook",1
  catch anyError
set the rect of image "Closed book.gif" to 380,45,765,508
  end try
  getSDBClientId mainStackClientId -- library call
  getSDBDbId mainStackDbId -- library call
  logInSDBClient (the platform),(the rIPCMode of this stack) -- library 
call

  checkSDBResult (the result) -- library call
  get the result
  if word 1 of it then
close this stack
exit preopenStack
  end if
  put word 2 of it into referenceClientId
  put the sdbFile of this stack into savedDatabase
  openSDBFile sdbBuffer,false,true,,"None",false,empty -- library call
  checkSDBResult (the result) -- library call
  get the result
  if word 1 of it then
close this stack
exit preopenStack
  end if
  if the sdbFile of this stack is not savedDatabase then save this stack
  put word 2 of it into referenceDbId
  put referenceDbId into field "Source Db Id" of card "Translation"
  loadToolTips
end preopenStack

This logic has always worked for moi.  Perhaps because it isn't 
preOpenStack that contains the start using statement, but rather the 
startLibrary handler called by preOpenStack.  So you might try:


on preOpenStack
...
...
startLibrary "My Library"
callLibraryHandler
...
...
end preOpenStack

startLibrary could be as simple as...

on startLibrary libraryName
start using stack libraryName
return the result
end startLibrary

Mine is more complex:

on startLibrary libraryName
  set the itemDelimiter to "/"
  put the effective fileName of this stack into libraryPath
  put libraryName into item -1 of libraryPath
  if there is a stack libraryPath then
start using stack libraryPath
return empty
  end if
  put "PlugIns" into item -1 of libraryPath
  put "/"&libraryName after libraryPath
  if there is a stack libraryPath then
start using stack libraryPath
return empty
  end if
  switch (the platform)
  case "Win32"
get specialFolderPath("Documents")&"/"&libraryName
if there is a stack it then
  start using stack it
  return empty
end if
break
  case "MacOS"
if char 1 of the systemVersion < 7 then
  delete item -5 to -3 of libraryPath
  if there is a stack libraryPath then
start using stack libraryPath
return empty
  end if
  delete item -2 of libraryPath
  if there is a stack libraryPath then
start using stack libraryPath
return empty
  end if
end if
break
  end switch
  return true -- = error
end startLibrary

This is because I want developers who use Serendipity Library to have 
multiple optional locations for library placement when bundling it with 
their apps.



Rob Cozens
CCW, Serendipity Software Company

"And I, which was two fooles, do so grow three;
Who are a little wise, the best fooles bee."

from "The Triple Foole" by John Donne (1572-1631)

___
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution


Re: startup question

2006-04-13 Thread Dave Cragg


On 13 Apr 2006, at 02:32, Stephen Barncard wrote:


I have a chicken-and-egg situation..

I have a stack startup handler that works fine until it does a  
'start using' for a library stack, and then immediately needs to  
use a handler in that stack just included.


What happens is that the code keeps marching along, the lib isn't  
active yet... and --- error.


I've put a 'wait 30 ticks' then a 'wait 60 ticks' before  
continuing. Not long enough? I know, I know, cheesy too.


What's the best way to allow the lib to load.. and how do I wait or  
hold for it?

I know there's an 'librarystack' message..


I don't have a solution, but I'm surprised at the behavior.  
Generally, libraries called in this way are available immediately.  
(I'm thinking of cgi scripts that start using a library in the  
startup handler.) Do you know of anything in the library itself that  
might be causing this? Right now, the only thing I can think of is  
the library calling one of the Rev library handlers (commands  
beginning with rev, or a url request requiring liburl), as the Rev  
libraries don't load until after startup.


Cheers
Dave
___
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution


Re: startup question

2006-04-13 Thread David Burgun

Hi,

One way of doing it is like this:



  put "stack " & quote & myStackFilePath & "LibStack.rev" & quote  
into myTempStackFilePathName
  get value("LibStartUsing(" & theParam1 & "," & theParam2 &  
")",myTempStackFilePathName)


Then in LibStack:

function LibStartUsing theParam1, theParam2
start using me
end LibStartUsing

That way the Stack is loaded before the start using is actually run.

Hope this helps
All the Best
Dave


On 13 Apr 2006, at 02:32, Stephen Barncard wrote:


I have a chicken-and-egg situation..

I have a stack startup handler that works fine until it does a  
'start using' for a library stack, and then immediately needs to  
use a handler in that stack just included.


What happens is that the code keeps marching along, the lib isn't  
active yet... and --- error.


I've put a 'wait 30 ticks' then a 'wait 60 ticks' before  
continuing. Not long enough? I know, I know, cheesy too.


What's the best way to allow the lib to load.. and how do I wait or  
hold for it?

I know there's an 'librarystack' message..

thanks.

sqb
--
stephen barncard
s a n  f r a n c i s c o
- - -  - - - - - - - - -
___
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your  
subscription preferences:

http://lists.runrev.com/mailman/listinfo/use-revolution


___
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution


Re: startup question

2006-04-12 Thread Chipp Walters

Stephen,

Regarding my last comment, I may have addressed a problem you didn't have.

You could have a callback message sent after the library has loaded, and 
trap it in the stack, then resume your startup code there, of course 
your openStack and other handlers would've already run.


You might try 'wait 30 ticks with messages' and see if it doesn't help.
Just an idea.

best,

Chipp

Stephen Barncard wrote:

I have a chicken-and-egg situation..

I have a stack startup handler that works fine until it does a 'start 
using' for a library stack, and then immediately needs to use a handler 
in that stack just included.


What happens is that the code keeps marching along, the lib isn't active 
yet... and --- error.


I've put a 'wait 30 ticks' then a 'wait 60 ticks' before continuing. Not 
long enough? I know, I know, cheesy too.


What's the best way to allow the lib to load.. and how do I wait or hold 
for it?

I know there's an 'librarystack' message..

thanks.

sqb


___
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution


Re: startup question

2006-04-12 Thread Jim Ault
I did not say this, but of course, in the repeat loop you need to

get tEchoFromLib()
wait 60 ticks with messages
if tEchoFromLib <> "" then exit repeat


to allow the call back from the library handler to take effect.

function echoFromLib
   return "true"
end echoFromLib


Jim Ault
Las Vegas


On 4/12/06 7:16 PM, "Jim Ault" <[EMAIL PROTECTED]> wrote:

> I have not done this kind of event looping yet, but couldn't you add a
> handler in the library that would call back that it was ready?  Then in your
> code, do a repeat until it echoed a response?
> 
> HTH
> Jim Ault
> Las Vegas
> 
> 
> On 4/12/06 6:32 PM, "Stephen Barncard" <[EMAIL PROTECTED]>
> wrote:
> 
>> I have a chicken-and-egg situation..
>> 
>> I have a stack startup handler that works fine until it does a 'start
>> using' for a library stack, and then immediately needs to use a
>> handler in that stack just included.
>> 
>> What happens is that the code keeps marching along, the lib isn't
>> active yet... and --- error.
>> 
>> I've put a 'wait 30 ticks' then a 'wait 60 ticks' before continuing.
>> Not long enough? I know, I know, cheesy too.
>> 
>> What's the best way to allow the lib to load.. and how do I wait or
>> hold for it?
>> I know there's an 'librarystack' message..
>> 
>> thanks.
>> 
>> sqb
> 
> 
> ___
> use-revolution mailing list
> use-revolution@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription
> preferences:
> http://lists.runrev.com/mailman/listinfo/use-revolution


___
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution


Re: startup question

2006-04-12 Thread Chipp Walters



Stephen Barncard wrote:

I have a stack startup handler that works fine until it does a 'start 
using' for a library stack, and then immediately needs to use a handler 
in that stack just included.


What's the best way to allow the lib to load.. and how do I wait or hold 
for it?


Stephen,

I use preOpenStack and openStack handlers in THE CARD SCRIPT of the 
stack to effectively handle startup stuff. If you put your start using 
code there it should work fine. Startup, for me, is only a necessary 
handler when setting the externals of a stack BEFORE the stack loads..as 
they can't be set (and used) AFTER the stack loads.


best,

Chipp

___
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution


Re: startup question

2006-04-12 Thread Jim Ault
I have not done this kind of event looping yet, but couldn't you add a
handler in the library that would call back that it was ready?  Then in your
code, do a repeat until it echoed a response?

HTH
Jim Ault
Las Vegas


On 4/12/06 6:32 PM, "Stephen Barncard" <[EMAIL PROTECTED]>
wrote:

> I have a chicken-and-egg situation..
> 
> I have a stack startup handler that works fine until it does a 'start
> using' for a library stack, and then immediately needs to use a
> handler in that stack just included.
> 
> What happens is that the code keeps marching along, the lib isn't
> active yet... and --- error.
> 
> I've put a 'wait 30 ticks' then a 'wait 60 ticks' before continuing.
> Not long enough? I know, I know, cheesy too.
> 
> What's the best way to allow the lib to load.. and how do I wait or
> hold for it?
> I know there's an 'librarystack' message..
> 
> thanks.
> 
> sqb


___
use-revolution mailing list
use-revolution@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution