Ticket #841 (closed bug: wontfix)

Opened 3 years ago

Last modified 22 months ago

textConfiguration in text add-on

Reported by: mitar Owned by: matija
Milestone: 2.6 Component: other
Severity: minor Keywords:
Cc: ales, marko, matija Blocking:
Blocked By:


There is also textConfiguration in text mining add-on. Should we move also this to orangerc.cfg? So configuration for add-ons? Probably we could define section for each add-on?

Change History

comment:1 Changed 3 years ago by marko

  • Status changed from new to assigned
  • Owner changed from marko to matija
  • Cc marko, matija added

Matija, have you considered where should be/are add-on settings saved? See Orange.misc.environ documentation for Orange settings.

comment:2 Changed 3 years ago by matija

I like Mitar's idea. Configuration for an add-on will be stored in orangerc.cfg under section, named after add-on's GUID. Also, Orange.misc.environ will additionally parse orangerc.cfg files under add-on directories, so that, for instance, Text's installation routines don't have to modify Orange's orangerc.cfg file, but it can have its own. When having more than one instance of the same add-on (which should happen only to a developer), each add-on will see the settings overridden by its local orangerc.cfg (unless the one in the user's home directory overrides it).

Values from the configuration will be accessible through Orange.misc.addons module. Configuration files in add-on directories will be unable to override anything out of their scope (ie. any other section than the one with add-on's GUID). If anyone has any objections, raise them today, not after I start working on the implementation. :)

comment:3 Changed 22 months ago by matija

  • Status changed from assigned to closed
  • Resolution set to wontfix

Add-on packaging has changed completely in the meantime, and Text is very outdated; hopefully someone will take care of it and make it up-to-date. Since that's the only add-on in need of any configuration (if at all), I'm leaving this decision to that person.

Note: See TracTickets for help on using tickets.