externals

Brian Yennie briany at qldlearning.com
Mon Jan 19 21:19:50 EST 2009


I think it's probably two of those things - the OS doesn't like to  
expose certain things as much as others, and also programs like Rev  
have to pick and choose what they support. Why not do the OS level  
research, and find out how hard it would be to create an external?

> Yes, I want it all!  And I want it easy.  Things like this can be  
> attacked at the application level... which would help ME... but it  
> will only help the whole rev community when it is an integral part  
> of the rev native event and command loop.  This is why I talk of  
> these things on this and other lists... to garner interest... to  
> plant seeds... to grow memes in the heads of others.
>
> Maybe Rev and programs like it just chase the low hanging fruit...  
> maybe this is an OS problem... maybe we live in a world where the  
> computer is a static device that waits for our commands... and maybe  
> that precludes the kinds of event driven automation that I seek.  We  
> have no experience with it so we don't ask for it.
>
> Randall
>
>
> On Jan 19, 2009, at 1:17 PM, Brian Yennie wrote:
>
>> Randall,
>>
>> Unfortunately it seems you are looking for a high-level API to take  
>> care of a very low level job. There simply isn't an API for  
>> everything. You are probably going to have to get your hands dirty  
>> in C if this is your goal. If you know the OS APIs you want to tap  
>> into, you could work on building externals in C. If you don't, time  
>> to do some research =). You will definitely need to build separate  
>> externals for each operating system as well.
>>
>> Maybe not what you were hoping for, but I hope that helps.
>>
>>> QuickKeys is cool... but it doesn't offer finder events as  
>>> triggers for the execution of macros.  There is no way, for  
>>> instance, to tell it:
>>>
>>> When a user saves any file, from any application, and the name  
>>> contains "Entropy", then save an alias at "Hard Drive: My Entropy  
>>> Docs:"






More information about the Use-livecode mailing list