Le 30/03/2015 00:17, Thomas Martitz a écrit : > Am 29.03.2015 um 19:17 schrieb Colomban Wendling: >> Le 29/03/2015 00:23, Thomas Martitz a écrit : >> >>> - New API functions to allow plugins to act as proxy plugins (pluxies). >>> […] >> >> That's the part I'm really fuzzy about. I really don't see why we need >> this specific layer […] > > […] > > As with git master, Geany's core loader scans the plugin folder on > startup and on opening the PM dialog. For each recognized plugin file it > allocates a GeanyPluginPrivate and calls geany_load_module(). > > […] with my new loader (no pluxies) it goes like this, and this is *very* > similar to git master. > > […]
OK, fair enough indeed. And well, proxy plugins are special enough to warrant their own API if it's useful anyway, so okay. > Now, with pluxies, it is completely the same except for: > 2* for each $file in $path, Geany calls is_plugin($file) which matches > additional file extensions (as provided by pluxies), it also calls the > probe() hook to resolve ambiguous files (e.g. .so files, they can be > core or libpeas plugins) As raised on IRC, one small question: do we need a file extension if we have probe()? I don't mind much, but I would imagine probe() could filter extensions itself and simply return the appropriate value. This would also potentially allow for extensionless plugins. But that's a small detail, and apart feeling it a little redundant I don't mind either way. > I hope you better understand my concept now. […] Yep, I do, thanks for these very good clarifications :) Regards, Colomban _______________________________________________ Devel mailing list Devel@lists.geany.org https://lists.geany.org/cgi-bin/mailman/listinfo/devel