It works, thanks!
I'll probably use it only for navigating the tree, so here's my feedback so far.
More -> About JPortsUI… seems to trigger connections to the update sites for
requested ports. This also happens when clicking on a row in the main pane for
a port to show below it. Is that necessa
JPortsUI has been updated due to an error when loading a file://
hosted port index (ex. GitHib) and an error when uninstalling ports
has been corrected. This version, 2017-04-10, can be downloaded from
https://sourceforge.net/projects/jportsui/files/
Feel free to submit a ticket or feature request
> On Apr 9, 2017, at 8:03 AM, db wrote:
>
> On 8 Apr 2017, at 02:28, Stephen Baber wrote:
>> JPortsUI has been updated due to an error when loading the port index.
>
> I get an error when launching it from systems almost identical: OS X 10.8.5,
> Java 1.6.0_65, port 2.4.1.
>
> One uses rsync
On 8 Apr 2017, at 02:28, Stephen Baber wrote:
> JPortsUI has been updated due to an error when loading the port index.
I get an error when launching it from systems almost identical: OS X 10.8.5,
Java 1.6.0_65, port 2.4.1.
One uses rsync for the tree, another uses github and shows this error me
Thanks! I think I was the one (or one of the ones, at least) who expressed
surprise at the old default behaviour, so thanks very much for changing that.
Mostly, it was unexpected...
I really like your GUI interface, and appreciate the effort you've put into it
to make the less-obvious parts of
I won't debate what default behavior might be desirable, but is the behavior
configurable regarding inactive ports? If so, there are options some might
desire between keep all and keep none. I for instance would always want to
keep any that still had a dependency on them (it happens, occasiona
