I like this a lot (only with the signature features), but if you have a nice shiny GUI program (which PAR is GREAT at bundling), I'm wondering how easy it would be to funnel PAR connection errors up into happy-shiny-GUI land...as well as whether one could produce "do want to upgrade, etc" type GUI's...
If you wanted to upgrade a whole application this way, it would be fairly easy to have a simple shell with a go() method and have PAR download the entire application, then invoke the "go()". That way you would be free to completely rearchitect your app rather than fixing yourself to certain unbrekable interfaces.
I'd probably just implement my own system though, with the launch.exe and a seperate goforthanddostuff.par ... and code my update interfaces around that. (preferably sftp with public keys that ship with the product, or something like that?)
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
