mudlet-makers team mailing list archive

[Stephen Lyons <1357786@xxxxxxxxxxxxxxxxxx>]

Just that it is in the resource file but nothing uses it from there, it
is inaccessible to the end-user in that place.

-- 
You received this bug notification because you are a member of Mudlet
Makers, which is subscribed to Mudlet.
https://bugs.launchpad.net/bugs/1357786

Title:
  Embedded Vyzor package is a couple of years old!

Status in Mudlet the MUD client:
  Confirmed

Bug description:
  Just checking the vyzor.mpackage file that is included in the source
  code and EMBEDDED into the Mudlet executable via the resource file  I
  find it contains files the latest of which has a date-stamp of 30
  November 2012!  Given that at the time of writing Oneymus's latest
  master Github version is dated 22 July 2014 we really ought to update
  the bundled version.  As it turns out the Mudlet executable does NOT
  use/load and the source code does not mention it anywhere (unlike the
  Geyser framework that is implicitly loaded at profile start-up) I
  suggest it may be best to remove this resource from the bundle at this
  time, if that is not felt appropriate then we should at least update
  it.

  Assuming that Vyzor and Geyser are mutually exclusive (I do not know
  that this IS the case) do we need to provide a way for the user to
  select between them and provide a load from resource file mechanism
  for it to be actually used; or, if they ARE capable of running side by
  side, we still need to provide a loading mechanism.  And have an
  update method!  So perhaps we should un-package it and instead install
  the individual files in a <mudlet-lue>/lua/vyzor directory alongside
  the corresponding <mudlet-lue>/lua/geyser one.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mudlet/+bug/1357786/+subscriptions