compileIt for revolution?

Dan Shafer revdan at danshafer.com
Wed Jun 22 23:38:36 EDT 2005


Mark....

I have a hard time seeing where you and I disagree here. I think  
we're saying the same thing differently.

Dan

On Jun 22, 2005, at 3:52 PM, Mark Wieder wrote:

> Dan-
>
> Wednesday, June 22, 2005, 3:05:06 PM, you wrote:
>
> DS> The way rev implements the OS X-specific stuff is right. On  
> Windows,
> DS> it is just ignored. It doesn't break and the app still runs.
>
> Here's where I think you're off base on this, Dan.
>
> I'd like to see runrev spend their time fixing bugs and working on new
> enhancements rather than chasing after the latest new features in
> <enter name of OS here>. The "shell" command and being able to run
> AppleScript scripts are examples of being able to extend the language
> without relying on runrev to add more things to the engine.
>
> It's a winning situation for all if a) the runrev team doesn't have to
> go implementing new solutions every time a particular OS changes; b)
> developers don't have to wait around for runrev to implement new
> things; and c) there's an easy way to do these things from Transcript
> without needing to spawn non-cross-platform external libraries.
>
> Sometimes you need to get out of the sandbox (QuickTime, for example)
> and I don't think it should be the responsibility of the runrev team
> to keep extending the engine's capabilities. If runrev provides the
> hooks to allow us to do this then the onus is on us (got kind of a
> ring to it, doesn't it?) as developers to do what we need. I don't see
> this as interfering with your, or anyone else's, ability to code. If
> you need the capability, use it; otherwise just ignore it.
>
> -- 
> -Mark Wieder
>  mwieder at ahsoftware.net
>
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your  
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-revolution
>
>



More information about the use-livecode mailing list