Thanks Peter.
I've moved the calls to Active 4D into the host. I'll just finish the
job and wrap the component calls in host methods for calling from
Active 4D scripts.
On a more reflective note, if I were Aparajita, I'd think twice before
promoting the idea that people should move away from implementing
Active4D in components.
Since v11, component solutions are a lot more portable than they were
before and are a great way of dumping Active4D-based business
functionality straight into someone's database without the kind of
"arm-wrestling" with the host that went on before (variable conflicts
etc).
On the other hand, non-component based code modules are a lot *less*
portable - we no longer have Insider code libraries and we have to use
4D's extremely buggy teleportation system between 2 open applications.
We also have to use folders to get any kind of reasonable delineation
of modules (can't search on prefixes any more).
On the face of it, there doesn't appear to be much problem with Active
4D supporting components directly. The only 3 issues I can see are:
[1] Callbacks to 4D have to be to host methods (easily liveable with
- a 'set callbacks' command has already been thoughtfully provided
for this). There is only 1 callback at the moment.
[2] If Active 4D is started from within a component, it seems to look
for it's resources relative to the component folder, not the host
(Hopefully this is manageable in the same way as the 'Structure File'
function - optionally uses the component or host as a reference)
[3] Support calls to component methods in the scripts (Not so
essential - they can be wrapped in host methods if it's a problem)
i.e. - it's even less of a deal than opening a host dialog from a
component which is a regular occurence
With all the stuff that we now 'can't' do in components, they are
turning out to be good for writing math libraries :)
Just my thoughts - I speak non-authoritatively because I'm not an
expert in the plugin API and readily accept that my assessment of the
problem may be far too superficial.
Best Regards
Peter
On 16 Jun 2010, at 10:51, Peter Schumacher wrote:
Active4D is using callbacks, they don't work in components reliable.
You have to install the A4D shell into your structure. It's a
problem with 4D's API.
_______________________________________________
Active4D-dev mailing list
[email protected]
http://mailman.aparajitaworld.com/mailman/listinfo/active4d-dev
Archives: http://mailman.aparajitaworld.com/archive/active4d-dev/
