|
From: Robert M. <rob...@gm...> - 2006-02-21 18:33:54
|
Glenn, Gerd: Just a thought: The standard and optional plugins are all available in the installer now. However, we don't currently have any inter-dependencies between plugins. If we introduce one, we'll probably want to update the installer to not allow the user to install one plugin without the plugin that it depends on. In a related topic, functionality that is common to multiple plugins might best be moved to core, no? So, if scripting support is required by multipl= e plugins, would it make sense to work out a generic API and relocate it to FW? Rob On 2/21/06, Glenn Griffin < gw...@co...> wrote: > > Hi Gerd, > I would suggest that the Designer function not be included in the SQL > Script plugin. My reasoning is that the Designer could become a major > functionality on its own, and putting it in the Script plugin would have > two negative effects. One is that people who want the Scripts plugin > may not want the Designer and all of its complexity, and the other is > that the potentially huge amount of Designer code could make it > difficult to maintain the Scripts plugin. > > |
