NewsArchive
09-21-2012, 05:41 AM
I have recently begun to find a huge flaw with Windows 8 brought about by
their policy - as I understand it. Maybe I have got it wrong.
As I understand it Windows 8 should really only ever have one icon
associated with an application, that being the shortcut to launch the
application.
However I am now finding myself having to write a utility application to run
various things in the software accessed from my server as that is the only
way I can see how to get round these "rules". For example, I use Armadillo
to protect and register my application. The demo runs for 30 days and if
that period runs out the user can register the software manually. Previously
I provided a shortcut for that. Now I having to do that via my utility.
Otherwise the user has to go through a convoluted process to do it via the
RUN menu which is prone to significant errors.
In short I am finding that Microsoft is forcing us to use the internet which
I prefer not to do for many reasons.
The point of this discussion is that as I understand it Friedrich recommends
us NOT to create more than one icon. I could have got that wrong. What I
think we need to be able to do is to create a group in the APP area. If you
install SB7 on Windows 8 now you see a group created (see attached). However
Friedrich has said he is moving away from this and I understand why - to
comply with the rules. Of course the installer on the version I installed as
a test was NOT Windows 8 aware hence the group appearing.
Another feature I feel we need is to be able to run FM3 (the file manager
utility) independently of the application. Hence another requirement for a
shortcut.
So my point is this ... surely the best way is to create the groups within
the APPS area. But that seems against the "rules". So how do we get around
this issue?
I absolutely love Windows 8 but I feel to comply with the rules (which I
would prefer to do) I am imposing severe limitations on how I provide basic
support for my applications.
Of course I might have misunderstood this and if these groups are allowed
then there is no problem. After all Microsoft has their own set of "groups"
such as Windows Accessories, System etc. as show attached.
Thanks
John
their policy - as I understand it. Maybe I have got it wrong.
As I understand it Windows 8 should really only ever have one icon
associated with an application, that being the shortcut to launch the
application.
However I am now finding myself having to write a utility application to run
various things in the software accessed from my server as that is the only
way I can see how to get round these "rules". For example, I use Armadillo
to protect and register my application. The demo runs for 30 days and if
that period runs out the user can register the software manually. Previously
I provided a shortcut for that. Now I having to do that via my utility.
Otherwise the user has to go through a convoluted process to do it via the
RUN menu which is prone to significant errors.
In short I am finding that Microsoft is forcing us to use the internet which
I prefer not to do for many reasons.
The point of this discussion is that as I understand it Friedrich recommends
us NOT to create more than one icon. I could have got that wrong. What I
think we need to be able to do is to create a group in the APP area. If you
install SB7 on Windows 8 now you see a group created (see attached). However
Friedrich has said he is moving away from this and I understand why - to
comply with the rules. Of course the installer on the version I installed as
a test was NOT Windows 8 aware hence the group appearing.
Another feature I feel we need is to be able to run FM3 (the file manager
utility) independently of the application. Hence another requirement for a
shortcut.
So my point is this ... surely the best way is to create the groups within
the APPS area. But that seems against the "rules". So how do we get around
this issue?
I absolutely love Windows 8 but I feel to comply with the rules (which I
would prefer to do) I am imposing severe limitations on how I provide basic
support for my applications.
Of course I might have misunderstood this and if these groups are allowed
then there is no problem. After all Microsoft has their own set of "groups"
such as Windows Accessories, System etc. as show attached.
Thanks
John