Code Monkey home page Code Monkey logo

Comments (3)

sebinside avatar sebinside commented on July 18, 2024 1

Some ideas / notes on this:

  • keep all pluggable meta data in a required xml file
  • rework the PluginFramework to load this xml file (e.g. called plugin.xml) before loading the Plugin file
  • only allow one xml and one plugin class per jar
  • rework the create task (see issue #20) to automatically create the proposed structure with the given choice for java or scala, already containing a require for e.g. the sample connector to show the usage
  • rework the fetch task, to only add a plugin to the plugins.sbt if the plugin xml file exists. Its currently a pain in the ass to delete plugins because of this
  • think about other usefull (optional) fields in the xml file, e.g. a support website / source github repo or license. Maybe npm does have other usefull examples
  • deprecate all other approaches. this is main reason we still call it pre-alpha

I hope this answers all your questions. Another spontanious idea: the plugin version could be also embeeded into the xml. Minimal sbt file changes, minimal framework reloads...

from chatoverflow.

hlxid avatar hlxid commented on July 18, 2024

I would like to start working on this, but still have some questions:

  1. What file format should be used? Propably xml?
  2. Should multiple plugins in one jar be supported? The current code just complains, but allows it:
    pluggableObjects.length match {
    case 0 => logger warn "No pluggable classes found."
    case 1 =>
    case _ => logger warn "More than one pluggable class found."
    }
  3. Should pluggable be directly removed with pre-alpha 3 or be deprecated and slowly removed?

from chatoverflow.

sebinside avatar sebinside commented on July 18, 2024

Just an idea...

<plugin>
  <name>sampel</name>
  <author>sebinside</author>
  <description>Just a test</description>
  <api>
    <major>3</major>
    <minor>0</minor>
  </api>
  <version>0.4.2</version>
  <website>codeoverflow.org</website>
  <license>MIT</license>
</plugin>

from chatoverflow.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.