Tempel
Active Member
I've just uploaded a bugfix to the repo. PXML parsing should now be just about as robust as possible. peelie, stouffa, let me know if you get any more problems.
Had that one too some times (but now I deleted chromium-dev because it was that annoying).pndstore not liking chrome-dev whenupdating list
see attached screenshot
I've just uploaded a bugfix to the repo. PXML parsing should now be just about as robust as possible. peelie, stouffa, let me know if you get any more problems.
I've just posted a beta of version 0.3 on my own site. There are only two new features (I've been busy):
- Checkboxes alongside upgrades allow you to select which to skip.
- Basic GUI threading.
I've just uploaded a bugfix to the repo. PXML parsing should now be just about as robust as possible. peelie, stouffa, let me know if you get any more problems.
hi
unfortunately still getting same error message with chorme-dev with your bugfix release
I've just posted a beta of version 0.3 on my own site. There are only two new features (I've been busy):
- Checkboxes alongside upgrades allow you to select which to skip.
- Basic GUI threading.
Hmm, strange. I updated to version 0.2.3 via PNDstore, but I can't recognize any of the new features :blink:
PNDstore is still busy during the update procedure and I can't find any checkboxes anywere. Any hints ?
While you still have time to do things How about an easy filter for the list, to show only the new apps from the last x (= 3) days ?
Thanks for still working on it - highly appreciated.
meandu's right. 0.2.3 was only a bugfix release; the 0.3 beta has the new features. I just want confirmation that they work before I make an official 0.3 release.Hmm, strange. I updated to version 0.2.3 via PNDstore, but I can't recognize any of the new features :blink:
That might be a challenge. The repository spec does not include upload dates, so they can't be sorted that way. I could potentially allow it to track changes between list updates, but it doesn't do that now and would require some serious work in the backend. So sorry, I can't promise that in the near future, but I'll see what milkshake and others think about adding upload dates to a future version of the spec. Also, I'll first need to implement sorting, which should happen next.While you still have time to do things How about an easy filter for the list, to show only the new apps from the last x (= 3) days ?
It might worth adding it to the spec, all you need is milkshake to publish information he already have...The repository spec does not include upload dates, so they can't be sorted that way.
I've just uploaded a bugfix to the repo. PXML parsing should now be just about as robust as possible. peelie, stouffa, let me know if you get any more problems.
meandu's right. 0.2.3 was only a bugfix release; the 0.3 beta has the new features. I just want confirmation that they work before I make an official 0.3 release.
I've just posted a beta of version 0.3 on my own site.
Hmm, well as it seems I didn't thought that to the end. So im guessing milkshake is using an additional mechanism on his repo then. Maybe a temporary solution could be that it shows the new additions to the repo since the last list update. But I agree that sorting should have a higher priority.That might be a challenge. The repository spec does not include upload dates, so they can't be sorted that way. I could potentially allow it to track changes between list updates, but it doesn't do that now and would require some serious work in the backend. So sorry, I can't promise that in the near future, but I'll see what milkshake and others think about adding upload dates to a future version of the spec. Also, I'll first need to implement sorting, which should happen next.
One thing I encountered during testing (no real bug, just unexpected behaviour on one side - choose which one ): When a installing/update process is already in progress and you try to start a additional install/update - the GUI is not responding, but both tasks are carried out without any problem.
Only one action can happen at a time; if you try to trigger a second action while the first is running, the GUI will become unresponsive until the first action completes and the second action starts.
Those who can read have a clear advantage - sorry :unsure:
There actually is a command-line interface to it already, though it's not accessible from within the PND; the whole thing would need to be installed to NAND to access it. It might be possible for me to use some PND tricks to make it accessible, though it still wouldn't be easy to run. But I guess it doesn't have to be if you're putting it in a cron job.One thing that came to my mind just seconds ago:
How about splitting PNDstore into two modules, that aren't directly depending on each other? A cli binary that has only the purpose to connect to the repo and update the local list. So this could be used to make a cron job to update the list on a more regular basis. The second module houses all the gui stuff (which still keeps the ability to update the list).
Yeah, I only just recently learned about that mmenu folder. For whatever reasons, libpnd doesn't report it as a searchpath, so PNDstore doesn't look there. I'll see what I can do.The first is trivial and not a bug as such, simply that PND's stored in pandora/mmenu are ignored by PNDStore and cant be upgraded. Skeezix mentions that this is a sneaky method minimenu employs, so if you want to only display PND files in minimenu you stick em in there.
That doesn't seem right. The worst PNDstore should be able to do is remove your PNDs. It doesn't even have functionality to remove appdata directories. Even if it did, it runs with user privileges, so it would need to seriously exploit the system to be able to delete everything from your root directory. So I can only conclude that you downloaded the secret possessed version of PNDstore, that is doomed to unleash the Apocalypse upon the Earth. Or maybe you should try HF5. The beta pnd_run.sh isn't necessary, but doesn't hurt. I wish I could be more helpful here, but thanks for testing.The second problem appears to be more serious in my case and has happened for a 3rd time now when using PNDStore (making me now believe it is the culprit) and hence bringing it to your attention now.
Basically it has totally wiped out my system on 3 occasions. I'm not bothered, just surprised. i also suspect it must be something odd with my setup but each time i've used PNDstore my system has been wiped.
[holy cow]