Embedded Vyzor package is a couple of years old!

[Stephen Lyons]

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.

[Vadim Peretokin (vperetokin)]

Vyzor has been updated: http://forums.mudlet.org/viewtopic.php?f=6&t=2647&view=unread#p21255

Need to update it in Mudlet. I think it should stay as an mpackage, we don't need admin overhead of unpackaging it.

[Stephen Lyons (slysven)]

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

[Vadim Peretokin (vperetokin)]

The mpackage was supposed to be installed into a new profile from the resource file when it is created.

[Chris (chrismudlet)]

We should make use of the new https download support and just point to the github/etc. URL with a fallback package.

[Vadim Peretokin (vperetokin)]

That would be a nice feature. Would be a fair bit of work to make it work
nicely though. I'm imagining some kind of a small progress dialog for the
downloads with an option to cancel the download if you don't want it and so
on.

On Wed, Sep 17, 2014 at 12:59 AM, Chris <email address hidden> wrote:

> We should make use of the new https download support and just point to
> the github/etc. URL with a fallback package.
>
> --
> 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
>
> _______________________________________________
> Mailing list: https://launchpad.net/~mudlet-makers
> Post to : <email address hidden>
> Unsubscribe : https://launchpad.net/~mudlet-makers
> More help : https://help.launchpad.net/ListHelp
>

[Vadim Peretokin (vperetokin)]

Migrating issues to Github, please follow the new discussion here: https://github.com/Mudlet/Mudlet/issues/569

This issue needs to be closed and there is no appropriate status, so will set it to "Opinion" just for migration purposes.