Hi Aaron
It's not so much that App Central is lacking as it is some certain
organizations do not want any scripts (encrypted or not) outside of
their own locations. Giving the package a custom bit at the end of the
name works well enough, but though that prevents conflicts, it doesn't
give the auto update functionality that could be useful in some
situations. Still, I know what I need to now and can work around it if
it becomes necessary. Thanks.
On 5/9/2011 05:38, Aaron Smith wrote:
On 5/8/2011 8:20 PM, Jacob Schmude wrote:
Ouch. Why would that be hard-coded like this?
Because App Central is the official Window-Eyes app distribution center.
What happens then if, for example, I make an app for a certain piece
of software and need to host it somewhere else, then another
individual makes an app for the same software, uses different
techniques and version numbers, and puts it on app central or visa
versa? Couldn't that cause a conflict?
Unless they give it the exact same name, it shouldn't be an issue. You
can already install multiple apps for a single piece of software.
That's actually, I would argue, one of the selling points of
Window-Eyes apps.
Why not use app central by default but allow packages to override
this if necessary?
An off site location would have to conform to the XML specifications
and URL naming conventions of App Central. It would seem, if one were
going to go through the trouble of maintaining that kind of setup, one
would just use App Central. If App Central is lacking in some way that
would make someone not want to use it, that's something we need to
address.
Aaron
--
Aaron Smith
Web Development * App Development * Product Support Specialist
GW Micro, Inc. * 725 Airport North Office Park, Fort Wayne, IN 46825
260-489-3671 * gwmicro.com
To insure that you receive proper support, please include all past
correspondence (where applicable), and any relevant information
pertinent to your situation when submitting a problem report to the GW
Micro Technical Support Team.
