Plugin system
Locked
 
|
Hello!
There is number of "connectors and plugs" in Amber now. I am talking about Debugger, ErrorHandler, PlatformInterface, progress-bar displayer, ... They are all used to plug an implementation to open connector. It reminds me of a plugin system that is implemented in Eclipse. Any part can define named connectors, any part can connect to that named connector and will be thus called to perform a service (Eclipse can allow more things to be connected to a single plug and all are called, just for info). Maybe this would be good for Amber as well. First, it would institionalize existing connectors and plug; and second, it would allow to easily create other ones, allowing for example various plugins to Helios. Herby -- You received this message because you are subscribed to the Google Groups "amber-lang" group. To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email]. For more options, visit https://groups.google.com/d/optout. |
|
Personally I like the idea of a Plugin system. My favorite IDE is Delphi and it has a very capable system called Components , its so capable that the entire environment based on tons of components making up VLC (Visual Component Library) . Its called Visual because unlike other plugin system its visual meaning if you want to add a capability to your app you simple drag the VCL element ( a small icon) corresponding to the feature you want added to your app and drop it on the form of you app. Delphi then automagically adds the code to make the plugin available to your app.
For example lets say you wanted to add connection and support for MySQL in your app, you just picked up the MySQL icon and dropped it on your app's form (canvas) , and there were separate components for various MySQL functionalities
Because VLC has been a huge success to Delphi and because Delphi is heavily inspired by smalltalk IDE wise, I think a plugin system even one much less sophisticated than the one I described would be a good addition to amber, because for me its just a plain good reason to having something like that in a visual coding environment which what the Smalltalk IDE is.
Braking down the existing system into components makes total sense too. The important thing is to keep the system as simple as possible and not introduce heavy dependencies. Cause if the plugin itself is very complex to use, then users will prefer doing things the manual way.
On Tue, Mar 11, 2014 at 2:46 PM, Herby Vojčík <[hidden email]> wrote: Hello! You received this message because you are subscribed to the Google Groups "amber-lang" group. To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email]. For more options, visit https://groups.google.com/d/optout. |
«
Return to Amber Smalltalk
|
1 view|%1 views
| Free forum by Nabble | Edit this page |