> 2017/11/17 9:58、Chip Scheide <[email protected]> のメール： > > The host after completion of the component will not be in my control. > > to install a plugin... > the component will need to have a table - with a blob. In the blob will need > to be the plugin.
that sounds like overkill. just use COPY DOCUMENT which works for folders since v13. a plugin is a folder, so you would need means to archive and extract the folder if you were to use BLOB. besides, local tables are totally inaccessible in a component's execution context, so you would need to use some kind of external DB to store the BLOB. technically you could use Get 4D folder(Database folder)+"Plugins"+Folder separator to locate the host's plugins folder, but injecting a plugin to host feels very violent and wrong. but if you do, there is no need to create an alias. see previous post. but you would have to restart the host. If you can instruct users to install your component in their host, I can't see why you can't also tell them to install the plugin too. > upon initialization of the component I can: > check to see if the plugin is already installed > if not blob to document into the plugins folder for the host (creating the > plugins folder for the host if needed) > then create a shortcut/alias to the newly installed plugin inside the > component's plugin folder (which I will have to create as it will not be > there in a compiled/built component) > then force a restart of the host so the plugin is loaded -- users will love > that... ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: http://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
