Fixed - thank yousmokey01 wrote:1. It couldn't find the ripper and streamer icons for the menus as Fatdog doesn't have the /usr/share/pixmaps/puppy directory.
pMusic 6.0.0
Added to todo-listsmokey01 wrote:3. Ripping the CD did work but initially I didn't think it did. Popup GUI wipes out the GUI behind. Could you use the modal setting to fix this or is it deliberate so that all GUI close together.
Yes it can. pMusic rip/export whatever is in the playqueue. It can be a variety of cd-tracks, local files and streams. If only one cd-track in the playqueue - it rip this single track.smokey01 wrote:4. I couldn't find a way to rip a single track, is this possible? If not it might be a nice addition.
Please do - thank yousmokey01 wrote:I will let you know if I find any more issues.
OK for the new 505
>Bugfix: update gui after edit
Does not refreshes, without closing and restarting the window.
What I wish to see is for the podcast to have something such as with gPodder, see screenshot attachment.
Without being able to know which author and title, one is lost
>Bugfix: update gui after edit
Does not refreshes, without closing and restarting the window.
What I wish to see is for the podcast to have something such as with gPodder, see screenshot attachment.
Without being able to know which author and title, one is lost
- Attachments
-
- gPodder_frCulture2.png
- (179.68 KiB) Downloaded 147 times
live
5.2 will be next stable release. Next development release will be 5.1.2, which can be released without any further testing. I don't know your interest or coding skills, but if you would like to work on /usr/local/func_podcast (all podcast code), I can send you the very latest code. - You can can work on this file, while I continue to work on other stuff.
Else, you have to wait for me to do my round of coding on the podcast grabber. In this case, your feedback is very important to bring podcast support further. I do not use this function myself, so without feedback it will be status quo.
5.2 will be next stable release. Next development release will be 5.1.2, which can be released without any further testing. I don't know your interest or coding skills, but if you would like to work on /usr/local/func_podcast (all podcast code), I can send you the very latest code. - You can can work on this file, while I continue to work on other stuff.
Else, you have to wait for me to do my round of coding on the podcast grabber. In this case, your feedback is very important to bring podcast support further. I do not use this function myself, so without feedback it will be status quo.
Haha you got a new pupil. Remember pwidgets days?zigbert wrote:live
5.2 will be next stable release. Next development release will be 5.1.2, which can be released without any further testing. I don't know your interest or coding skills, but if you would like to work on /usr/local/func_podcast (all podcast code), I can send you the very latest code. - You can can work on this file, while I continue to work on other stuff.
Else, you have to wait for me to do my round of coding on the podcast grabber. In this case, your feedback is very important to bring podcast support further. I do not use this function myself, so without feedback it will be status quo.
Ok, here's a draft.
Looking at the code, it is clear that this module of pMusic hasn't got priority.
Any input are welcome. I am a newbie to podcasts, and if we gonna reach a better user experience, I need help.
Some new features and it now follows the new gui standard for the upcoming 5.2.0
This release is to be considered as a draft for discussion. It's not heavily tested and is probably more unstable than the previous releases.
I have deactivated visualization because it conflicts with many podcast formats. I will look at that later...
Looking at the code, it is clear that this module of pMusic hasn't got priority.
Any input are welcome. I am a newbie to podcasts, and if we gonna reach a better user experience, I need help.
Some new features and it now follows the new gui standard for the upcoming 5.2.0
This release is to be considered as a draft for discussion. It's not heavily tested and is probably more unstable than the previous releases.
I have deactivated visualization because it conflicts with many podcast formats. I will look at that later...
- Attachments
-
- forum.png
- (99.26 KiB) Downloaded 368 times
-
- pmusic-5.1.2.pet
- (113.07 KiB) Downloaded 252 times
Thanks
OK, let's start by explaning what one does with podcasts.
As with music, for each podcast entry/title one needs to see:
1. to which channel/album it belongs, some podcast channels may have hundreds of titles.
2. its description, hopefully split into author, title, duration, track date, downloaded date
One is interested (= subscribes) to some channels, in doing so, one distinguishes 3 status (flags => different appearance styles):
1. new podcasts (that will need to be downloaded, possibly with a filter - typically a limiting number)
2. already downloaded podcast, that will be deleted (often automatically with some user set rule, typically after a period of time)
3. already downloaded podcast, that one wants to archive, keep and NOT delete.
Now, with pMusic.
I think podcast grabber window should be limited to manage subscriptions and possibly if you want display the new released podcats, since last download.
All the rest ought to be in the main window, as for music.
With the present version 512, it appears to me as extra work to have a list both in the grabber window and the main window.
A good test can be http://radiofrance-podcast.net/podcast09/rss_10351.xml
As previously said, for podcast its useful to know played track, from none.
Some styling suggestions:
* I would make the sliders button <> a bit bigger (one day everyting will be with touchscreen)
* the current played track in the play list, I would use another background color to make it more visible
OK, let's start by explaning what one does with podcasts.
As with music, for each podcast entry/title one needs to see:
1. to which channel/album it belongs, some podcast channels may have hundreds of titles.
2. its description, hopefully split into author, title, duration, track date, downloaded date
One is interested (= subscribes) to some channels, in doing so, one distinguishes 3 status (flags => different appearance styles):
1. new podcasts (that will need to be downloaded, possibly with a filter - typically a limiting number)
2. already downloaded podcast, that will be deleted (often automatically with some user set rule, typically after a period of time)
3. already downloaded podcast, that one wants to archive, keep and NOT delete.
Now, with pMusic.
I think podcast grabber window should be limited to manage subscriptions and possibly if you want display the new released podcats, since last download.
All the rest ought to be in the main window, as for music.
With the present version 512, it appears to me as extra work to have a list both in the grabber window and the main window.
A good test can be http://radiofrance-podcast.net/podcast09/rss_10351.xml
As previously said, for podcast its useful to know played track, from none.
Some styling suggestions:
* I would make the sliders button <> a bit bigger (one day everyting will be with touchscreen)
* the current played track in the play list, I would use another background color to make it more visible
Tested pMusic 5.0.5 in Slacko, Precise and Xenial. I was unable to generate a .pot file with all GUI strings, the file contains about fifty strings and it should contain over five hundred. This is because only the main pmusic script has the required gettext header:
Then Momanager only gets gettext strings from that single script. That is why most of the GUI remains in English.
After editing manually all the scripts that contain gettext to include the TEXDOMAIN and OUTPUT_CHARSET, I finally got a .pot file with 554 strings.
Bellow are the edited scripts.
*EDIT
After updating the translations for pMusic, everything still remains in English. Will post again later if I find out why.
Code: Select all
export TEXTDOMAIN=pmusic
export OUTPUT_CHARSET=UTF-8
After editing manually all the scripts that contain gettext to include the TEXDOMAIN and OUTPUT_CHARSET, I finally got a .pot file with 554 strings.
Bellow are the edited scripts.
*EDIT
After updating the translations for pMusic, everything still remains in English. Will post again later if I find out why.
- Attachments
-
- Screenshot_2016-07-16_19.53.24.jpg
- (192.7 KiB) Downloaded 233 times
-
- pmusic.mo.gz
- remove false .gz and copy to /usr/share/locale/es/LC_MESSAGES
- (52.81 KiB) Downloaded 234 times
-
- pmusic.tar.gz
- pMusic 5.0.5 scripts now include TEXTDOMAIN to make translations properly.
- (104.07 KiB) Downloaded 231 times
[url=http://murga-linux.com/puppy/viewtopic.php?t=76948]Puppy Linux en español[/url]
vicmz
I wonder where the bug is....
To get it work with Spanish (choose es in the preferences), I had to restart the X server. Now I had to go to the preferences once more and press OK to rebuild gui files (since it didn't build Spanish at first attempt).
Even without setting $LANG to es, pmusic reports a gtk error. I checked Gimp and pFind as well, and got the same error. Inkscape on the other hand went straight to Spanish.
???
I wonder where the bug is....
To get it work with Spanish (choose es in the preferences), I had to restart the X server. Now I had to go to the preferences once more and press OK to rebuild gui files (since it didn't build Spanish at first attempt).
Even without setting $LANG to es, pmusic reports a gtk error. I checked Gimp and pFind as well, and got the same error. Inkscape on the other hand went straight to Spanish.
???
Code: Select all
# pmusic --debug
/usr/local/pmusic/pmusic: line 454: kill: (11754) - No such process
(process:19684): Gtk-WARNING **: Locale not supported by C library.
Using the fallback 'C' locale.
- Attachments
-
- forum.png
- (79.54 KiB) Downloaded 314 times
Thank you for the feedback
A different color on the playing track in the playlist would have been nice, but afaik, this is not possible with gtkdialog.
To be considered. Though, I think it is possible to use the same code for browsing the podcast channels in both the setup dialog and in the main gui.live wrote:Now, with pMusic.
I think podcast grabber window should be limited to manage subscriptions and possibly if you want display the new released podcats, since last download.
All the rest ought to be in the main window, as for music.
With the present version 512, it appears to me as extra work to have a list both in the grabber window and the main window.
The latest version of pMusic does so... The icon color switches from yellow to green when played.live wrote:As previously said, for podcast its useful to know played track, from none.
Regarding touchscreen, I believe a unique theme is the best way. Graphical theming in pMusic is gtk-based, and we have tested touchscreen theming in Slacko 6.3.x. and it works well. See pTheme in the Desktop menu.live wrote:Some styling suggestions:
* I would make the sliders button <> a bit bigger (one day everyting will be with touchscreen)
* the current played track in the play list, I would use another background color to make it more visible
A different color on the playing track in the playlist would have been nice, but afaik, this is not possible with gtkdialog.
Apparently, after setting the system language there is a directory that should be created but is missing.zigbert wrote:vicmz
I wonder where the bug is....
To get it work with Spanish (choose es in the preferences), I had to restart the X server. Now I had to go to the preferences once more and press OK to rebuild gui files (since it didn't build Spanish at first attempt).
Even without setting $LANG to es, pmusic reports a gtk error. I checked Gimp and pFind as well, and got the same error. Inkscape on the other hand went straight to Spanish.
???Code: Select all
# pmusic --debug /usr/local/pmusic/pmusic: line 454: kill: (11754) - No such process (process:19684): Gtk-WARNING **: Locale not supported by C library. Using the fallback 'C' locale.
Following the advice of Wow, I made a symlink to es_AR.utf8 with the name es_AR in /usr/lib/locale (see the screenshot below). Then, I deleted /root/.pmusic and started pMusic, now in full Spanish language using the original scripts of the pet (without TEXTDOMAIN).
There is still the doubt about why Momanager did not create a .pot with all the 500+ lines until I included the TEXTDOMAIN in all scripts, but that is for the Momanager thread.
*EDIT* actually Momanager does require TEXTDOMAIN to be in all gui scripts, it is the only way to create a working .mo
Thank you, Zigbert.
- Attachments
-
- Shot_2016-07-18_23.28.02.png
- (151.13 KiB) Downloaded 264 times
[url=http://murga-linux.com/puppy/viewtopic.php?t=76948]Puppy Linux en español[/url]