This new version introduces two major changes:
Big thanks to all contributors, including issue reports.
Here is the changelog:
The Pharo team.
Thanks for this. Its nice to be able to easily reference this info.
Is "last update" the date the VM was changed on the local system, or the build date reported by the VM?
Seeing this new interface sparks a ideas (you probably already considered some of them):
- show the commit hash of each VM
- have a history log tab - so if an Image stops working between last week and now, I can review to
be confident it wasn't a VM update behind the scenes and if there was I can identify the old VM and
be able to test against it to isolate a problem.
- be able to edit the Download URL
- be able to add additional custom VMs, e.g for latest VM snapshots
Love this!! especially sorting by it.
Also the Template column is cool. I used to include the number in the name of the image but this is so much more informative.
The Arch column is cool. The VM Name would be useful in addition, or as a replacement for Arch. might e.g. 70-x86.
And dreaming of this being a pulldown menu to select from custom VMs defined in the VM-management window.
It is the build date reported by the system (modificationTime of the vm binary).
It could be better by providing the VM version but it is a start. To provide VM version, we should probably add metadata for each VMs.
This one is redundant with the next one, no? Or do you just want to override the default VM download?
If so, it will be a bit difficult because we expect to find vms with specific names / folders, dependening on your OS, Pharo version.
yes, all this is nice. You could add feature requests for them to PL issue tracker.
It is in the plan but we need to change a lot of logic in PL so that each image has its own metadata, including the VM to run it that you could customize.
Thanks for the feedback,
On Mon, 11 Feb 2019 at 18:19, Christophe Demarey <[hidden email]> wrote:
|Free forum by Nabble||Edit this page|