Hi, it would be nice if the following was implemented in the package manager
- the possibility to open packages for compilers not installed, and extract files from those packages. Needed for e.g. mB users that want to use mP libraries and vice versa. Of course "install package" should be disabled in these cases.
- the possibility (in addition to the above) to "open" files in the package manager with the standard executable according to the file extension. This permits looking in .zip files, viewing .txt, .mpas, .htm files etc... while in the package manager. Should not be so difficult to make.
Thanks in advance! Great work!
v2.30 improvement suggestions
v2.30 improvement suggestions
Kind regards, Dany.
Forget your perfect offering. There is a crack in everything, that's how the light gets in... (L. Cohen)
Remember when we were young? We shone like the sun. (David Gilmour)
Forget your perfect offering. There is a crack in everything, that's how the light gets in... (L. Cohen)
Remember when we were young? We shone like the sun. (David Gilmour)
Re: v2.30 improvement suggestions
I'm not sure blocking package installation is necessary. Actually, possibility to install packages to compilers other than the one the package was prepared for could save library designer some work. Assuming all needed mcl files are present in package, there's no difference in their operation in mB and mP (some mP/mB libs may even work in mC).Dany wrote:- the possibility to open packages for compilers not installed, and extract files from those packages. Needed for e.g. mB users that want to use mP libraries and vice versa. Of course "install package" should be disabled in these cases.
Presently one always has to prepare separate packages for separate compilers, even for libs that contain only mcl files .
A warning that package was prepared for uninstalled compiler should be enough - next step could be an option to install the package in any compiler present, or simply to unpack it to indicated directory.
Re: v2.30 improvement suggestions
Indeed, I fully agree.janni wrote:I'm not sure blocking package installation is necessary. Actually, possibility to install packages to compilers other than the one the package was prepared for could save library designer some work. Assuming all needed mcl files are present in package, there's no difference in their operation in mB and mP (some mP/mB libs may even work in mC).Dany wrote:- the possibility to open packages for compilers not installed, and extract files from those packages. Needed for e.g. mB users that want to use mP libraries and vice versa. Of course "install package" should be disabled in these cases.
Indeed. That would provide maximum flexibility.janni wrote:Presently one always has to prepare separate packages for separate compilers, even for libs that contain only mcl files .
A warning that package was prepared for uninstalled compiler should be enough - next step could be an option to install the package in any compiler present, or simply to unpack it to indicated directory.
Kind regards, Dany.
Forget your perfect offering. There is a crack in everything, that's how the light gets in... (L. Cohen)
Remember when we were young? We shone like the sun. (David Gilmour)
Forget your perfect offering. There is a crack in everything, that's how the light gets in... (L. Cohen)
Remember when we were young? We shone like the sun. (David Gilmour)
Re: v2.30 improvement suggestions
Ok, added to the wish list.
Re: v2.30 improvement suggestions
Move to beta test forum
Kind regards, Dany.
Forget your perfect offering. There is a crack in everything, that's how the light gets in... (L. Cohen)
Remember when we were young? We shone like the sun. (David Gilmour)
Forget your perfect offering. There is a crack in everything, that's how the light gets in... (L. Cohen)
Remember when we were young? We shone like the sun. (David Gilmour)