No reason not to eventually allow them both. With what I've done so far
with the plugin code, it could easily handle any language if someone wraps
the interpreter in Java using the PluginInterpreter interface. I was more
concerned that I might end up spending time written this Python plugin code
and find out we could have just gone with a Java-only model, which is
infinitely easier since it doesn't require introducing interpreters, etc.
On Fri, Jun 26, 2020 at 11:01 PM bareheiny <dmarc-noreply@xxxxxxxxxxxxx>
wrote:
...but then in the spirit of the taco girl, “Why not both?”.
On 27/06/2020, at 09:17, Arturo Pérez Mulas <theotocopulitos@xxxxxxxxx>
wrote:
I vote for python, I find it much easier to use and learn than Java...
Also, CR used python... Knowing next to nothing I was able to create the
first version of the Comicrack Comicvine scraper way back when... and it
was a success ;) ...
On Fri, Jun 26, 2020 at 10:17 PM bareheiny <dmarc-noreply@xxxxxxxxxxxxx>
wrote:
CR plug-ins are python as far as I’m aware - so for ease of migration I’d
go with python.
I’ve also found python a lot easier to come to grips with as somebody
with very minimal programming skills.
So python gets my vote.
On 27/06/2020, at 03:17, Darryl L. Pierce <mcpierce@xxxxxxxxx> wrote:
Working on the python plugin feature for CX, I'm now wondering if it's
the right solution, to have them be written in Python. Would it be better
to have them be written in Java so they can just be dropped into the lib
directory and loaded?
What're your thoughts?
--
Darryl L. Pierce <mcpierce@xxxxxxxxx>
"Le centre du monde est partout." - Blaise Pascal
"Let's try and find some point of transcendence and leap together." -
Gord Downie
