You guys rocks!
I'd like to test it, too, but download link leads to a dead end...
Sorry Enri,
I've renamed it to hubg as said in the last page, so the link changed as well
https://github.com/ducasp/MSX-Development/tree/master/UNAPI/...
Just tested, it works like a charm! Some suggestions:
- as Manuel said, tab to navigate across frames, cursors Left & Right to change page, and Up & Down to select entry with a reverse colour bar; or function keys to apply operations instead of normal keys;
- some packages contain big files, for example the PDF manual of WDW; and so, is it possible to avoid the download of some files? (a filter on file extension).
- some packages contain big files, for example the PDF manual of WDW; and so, is it possible to avoid the download of some files? (a filter on file extension).
About these big files every time I'm creating a new package I'm wondering what to do with them... Of course the PDF cannot be opened with the MSX, but that's also the only documentation available for some applications (WDW is a good example)...
What should be done in that cases? Include the (relatively) big PDF or package the application with no documentation at all?
What should be done in that cases? Include the (relatively) big PDF or package the application with no documentation at all?
I think you could include a small text file with the URL of the PDF.
I think you could include a small text file with the URL of the PDF.
Yeah, that's a good idea and it would work in some cases, but in WDW specifically I could not find the PDF where it could be directly linked... And converting the whole PDF to TXT is probably too much work...
I think you could include a small text file with the URL of the PDF.
Yeah, that's a good idea and it would work in some cases, but in WDW specifically I could not find the PDF where it could be directly linked... And converting the whole PDF to TXT is probably too much work...
But you are hosting the PDF now as well somewhere, or does HUB download packages from original locations?
Anyway you could also offer a ‘light’ version of each package, so you could download wdw or wdw-lite. Alternatively package s could mark optional heavy files and these are not doenloaded if you pass an argument to hub.com, e.g. /L.
I think you could include a small text file with the URL of the PDF.
Yeah, that's a good idea and it would work in some cases, but in WDW specifically I could not find the PDF where it could be directly linked... And converting the whole PDF to TXT is probably too much work...
But you are hosting the PDF now as well somewhere, or does HUB download packages from original locations?
Anyway you could also offer a ‘light’ version of each package, so you could download wdw or wdw-lite. Alternatively package s could mark optional heavy files and these are not doenloaded if you pass an argument to hub.com, e.g. /L.
I really don't like the idea of two packages, this might lead to confusion about what is lite and most people don't read information anyway and would get the regular version fearing it wouldn't fatten... oops, wouldn't have some feature that the non light version has... But I like the idea of not downloading any files our MSX is going to be able to handle, adds up to install time and occupies disk space that goes to waste... A text file with the URL to access the full package on the internet, or, the manual if that can be directly linked, seems like a great idea
nm