MMF2 HWA Beta 2c

[nivram]

I think Jeff mentioned something about removing the Updater all together, because of all the issues.

[BrandonC]

I think Jeff mentioned something about removing the Updater all together, because of all the issues .

There really aren't any major issues though. The extension list is just out of date. Yeah, this completely defeats the whole idea of having an extension updater that updates extensions, but the program itself is a very solid piece of software and just need someone to keep it up to date. :sleep:

[nivram]

Makes sense to me.
Thanks

[Crash86]

Why does the program not run from the Neatwares Extension list database so that when a new extension is released the Updater knows about it?

The idea of an Updater that needs updating itself rather than running automatically from a pre-existing self-updating resource is crazy.

[Nifflas]

Well, we kind of need a dedicated extension distribution system though, one place where the latest versions always is. Either as an integrated part of MMF2, or as a portable stand-alone application... and if a such system is created, the other ones must be removed from clickteam.com (e.g. extension download board, and links to other extension download pages) so that Clickteam points out that there's only one standardized way to obtain extensions, and that it's the place to always get the latest versions.

I propose an extension download page AND an extension updater client. The extension updater should however connect to the very same database as the extension download page to retrieve the latest versions. This way, if an extension is updated on the extension site, the updater software will also retrieve that extension.

I know a few great programmers skilled in both php and c++, who might be interested in creating something like this if they get enough money.

I think the main problem with Fusion Updater is it's lack of support for including other files, such as extension example mfa's, and it's by some reason really slow too, a lot more than it should have to be to carry out the task it does.

[Crash86]

That is exactly what I mean.

It should be like "Right, if you want your extension published, or if you update it - This is how you do it". This is so that I can visit one definitive location and view every extension and be sure of obtaining the latest version. I think we've nearly got that with the Neatware's Extension List. There used to be an even bigger one I used but it was removed from the Community Links box (-->)

We need an app that compares the extensions on your machine and their version numbers to those in the database (and if there is a newer version available downloads said file).

Any other approach is seriously over-complicated.

[Dynasoft]

That reminds me, I really need to prod LIJI into giving me the ability to update the version of the "select object" on the neatwares list. The version on there doesn't work with the current MMF build.

I can provide code for retrieving an extension's version number (and a lot of other details) from C++ (via the Windows API for loading DLLs) if anyone wants to use it in an updater.

[MechatheSlag]

I can provide code for retrieving an extension's version number (and a lot of other details) from C++ (via the Windows API for loading DLLs) if anyone wants to use it in an updater.

I am interested.

[uprize]

Well, we kind of need a dedicated extension distribution system though, one place where the latest versions always is. Either as an integrated part of MMF2, or as a portable stand-alone application... and if a such system is created, the other ones must be removed from clickteam.com (e.g. extension download board, and links to other extension download pages) so that Clickteam points out that there's only one standardized way to obtain extensions, and that it's the place to always get the latest versions.

I propose an extension download page AND an extension updater client. The extension updater should however connect to the very same database as the extension download page to retrieve the latest versions. This way, if an extension is updated on the extension site, the updater software will also retrieve that extension.

I know a few great programmers skilled in both php and c++, who might be interested in creating something like this if they get enough money.

I think the main problem with Fusion Updater is it's lack of support for including other files, such as extension example mfa's, and it's by some reason really slow too, a lot more than it should have to be to carry out the task it does.

that would be awesome

[Jacob]

Seconded.