- VI Package Manager
-
Ideas
+4
Easy Synch to upgrade Custom Category
Have been playing with the Custom Category and I really like it.
One issue I foresee is the difficulty in updating all packages when there is a change of the Custom Category.
One way could be to allow the Custom Category to be synchronised to the currently installed Category palette with the press of a button:
One way could be to allow the Custom Category to be synchronised to the currently installed Category palette with the press of a button:
Another way, possible better, would be to link to an external file. This way, you update the external file and the next time you load the VIPB it will update:
This file could be as simple as a 32x32.png file or maybe there could be an a GUI option that allows a new VIPM file type to be created.
I am just trying to think of the best of both worlds where your Top Level mnu package is not an external dependency and its really easy to update wrt changes.
Another idea is that it could be a separate package that is included as a sub-package (ties into Expose Sub Package idea. VIPM can upgrade to the latest if not already installed, but the user is only ever distributing/installing one package.
I am just trying to think of the best of both worlds where your Top Level mnu package is not an external dependency and its really easy to update wrt changes.
Another idea is that it could be a separate package that is included as a sub-package (ties into Expose Sub Package idea. VIPM can upgrade to the latest if not already installed, but the user is only ever distributing/installing one package.
Servicio de atención al cliente por UserEcho
