development cycle

anybody have any recommendations as to the quickest way to develop jitter externals?
i’ve noticed that as i’m working on different versions of a jitter external,
if i want to switch out the object in max for the new version,
i have to quit max & restart it in order for the new external to take place.
it’s not the end of the world, but i’m sure there must be an easier way…
i’m using max 4.6.2 / jitter 1.6.2, xcode 2.4.1 if that matters.

Unfortunately there’s no way around the fact that once an external is
loaded in Max, a new version of it can only be used by restarting the
app. You could rename it and use it, but that might be more trouble
than it’s worth.

wes

On 12/9/06, m. cera wrote:
>
> anybody have any recommendations as to the quickest way to develop jitter externals?
> i’ve noticed that as i’m working on different versions of a jitter external,
> if i want to switch out the object in max for the new version,
> i have to quit max & restart it in order for the new external to take place.
> it’s not the end of the world, but i’m sure there must be an easier way…
> i’m using max 4.6.2 / jitter 1.6.2, xcode 2.4.1 if that matters.
>
> thx in adavance,
> -mark
>
>

right on, so i guess the better way to go is working through the openGL stuff either with jit.gl.sketch, maybe jitter java (?) or just developing it for carbon standalone apps & then porting it over when everything’s sort of locked down.
the constant back & forth really makes it too time-consuming to be a fluid development cycle otherwise.
at any rate, thanks for the heads up.