compileIt for revolution?
Dan Shafer
revdan at danshafer.com
Wed Jun 22 01:27:30 EDT 2005
Xavier....
I guess we'll just have to agree to disagree about this.
How in the world would you expect a compiled script or handler -- if
such a thing were possible -- to then be smoothly integrated into a
stand-alone app?
We needed CompileIt! in HyperCard *far* less for performance than for
code protection and the ability to deliver stuff that didn't require
the player to be around. Neither of those is an issue today in
Revolution.
As for performance, tuning for such situations has produced
staggering results. I was blown away in Monterey last weekend to
watch a dynamically populated menu that was pulling its contents from
100 text files appear in under a second. I've never heard much here
in the way of complaints about slow programs written in Rev.
Dan
On Jun 21, 2005, at 9:31 PM, MisterX wrote:
> Dan,
>
> Creating apps with rev has NOTHING to do with compileIt.
>
> I really would like to speed up some scripts to manipulate
> arrays (where rev has some serious limitations) and the best
> possible way to do that would be to have something like
> CompileIt.
>
> I cannot create DLL to create externals in Rev can i? ;)
>
> There's an apparent fan group of CompileIT who would pay
> dearly to get this functionality back. And I'd rather shell
> out credits to rev than to Moft or MW for a dll compiler for
> externals.
>
> Meanwhile, in the jungle, any rev app without this and
> manipulating many lists or very long is definitely a dog
> compared to any real-compiled application. Rev will never
> compete in that "segment" compared to a real compiled app.
> Although this is apparent, it is not when all of your
> application runs smooth and fast, until the user enters
> his real data.
>
> Example: The HotKeyN2O stack stores all properties of all
> controls in a card when the user opens the card. The props
> are all in array form which cannot be stored into another
> array (time based array of object changes). So for each
> object i have to translate array[key]=data to <key>data</key>.
>
> This in turn is stored into a time-based array. So if i need
> to restore the property (any) for any object and at any time,
> it's ultra easy - except that the translation process is so
> slow after 10 controls trasnlated that it's USELESS if i dont
> write that into a real-compiled external.
>
> So CompileIt is needed - and very much so i would say - we
> all have these uses for it where Rev just doesn't can't
> perform fast enough.
>
> cheers
> Xavier
>
>
>> -----Original Message-----
>> From: use-revolution-bounces at lists.runrev.com
>> [mailto:use-revolution-bounces at lists.runrev.com] On Behalf Of
>> Dan Shafer
>> Sent: Wednesday, June 22, 2005 06:10
>> To: How to use Revolution
>> Subject: Re: compileIt for revolution?
>>
>> I think perhaps you haven't yet understood Revolution very well.
>> That's cool; it takes a while.
>>
>> With Rev, we don't need CompileIt! because Rev produces
>> stand-alone, compiled applications for multiple platforms as
>> part of its way of doing business.
>>
>>
>> On Jun 21, 2005, at 6:48 PM, Eric Engle wrote:
>>
>>
>>> Is there any chance that Heizer/Royalsoft (or anyone else for that
>>> matter) will
>>> make a script compiler for revolution like compileIt?
>>>
>>>
>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> Dan Shafer, Revolution Consultant and Author
>> http://www.shafermedia.com Get my book, "Revolution: Software
>> at the Speed of Thought"
>> From RunRev Store
>>
>>
>>
>>
>> _______________________________________________
>> 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
>>
>>
>
> _______________________________________________
> 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