On Nov 17, 2017, at 9:33 AM, Chip Scheide wrote: > 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. > > 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... > > - how do I find the component database (to create the shortcut/alias) > - I do not have a language reference at hand - is there a command to create > an alias/shortcut?
Chip, The fact of the matter is that when you create a component that uses a plugin, any plugin, installing the component in a host database has an additional step. That’s just how it is. Always been that way. There is really no way to simplify it. It is an install issue. When you develop the component you need the plugin in the component’s Plugins folder. But when you install the component in a host database the component can only access plugins that are in the host databases Plugins folder. Component work has two modes of operation. Development of the component all by itself. Then later component usage in a host database. Each has different considerations. And to use the component in a host requires installation. And that installation has an addition step if you use plugins from the component. You say “then force a restart of the host so the plugin is loaded -- users will love that…”. Users are never involved in any of this. Only a 4D Developer can install a component. And all 4D Developers know about plugins. So your “users” are really 4D Developers. Once the 4D Developer installs the component and installs any necessary plugins in the host Plugins folder all the work is done. It’s a one time thing. The install instructions are this: 1. Put the component in the “Components” folder of the host. 2. Put the plugin in the “Plugins” folder of the host. When you deliver the component it will not have the plugin inside the component. It will be outside all by itself. So that the “user”, the 4D Developer, will see 2 items and your install instructions will tell them what to do. This is not a big deal. I think you are spending too much time trying to automate something that really does not need to be automated. Tim ******************************************** Tim Nevels Innovative Solutions 785-749-3444 timnev...@mac.com ******************************************** ********************************************************************** 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:4d_tech-unsubscr...@lists.4d.com **********************************************************************
