Skip to main content ↑ ↓

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: fooweb2020: reworked components website (Read 7762 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Re: fooweb2020: reworked components website

Reply #25 –
With fb2k 1.5.3 beta 4, component auto update dialog is now resizable and can present multilevel bullet lists in change logs - two spaces before the asterisk to create a nested list.
Microsoft Windows: We can't script here, this is bat country.

Re: fooweb2020: reworked components website

Reply #26 –
Quote from: Peter on
With fb2k 1.5.3 beta 4, component auto update dialog is now resizable and can present multilevel bullet lists in change logs - two spaces before the asterisk to create a nested list.
Thanks!
Regretfully, it seems that something is bugged with bullet lists. The following layout is displayed incorrectly:

Plain text
  • Item
    • Sub-Item
Plain text 2
  • Item
Plain text 3

`Plain text 2` and `Plain Text 3` indentation will be borked (see https://www.foobar2000.org/components/view/foo_spider_monkey_panel for example).

Re: fooweb2020: reworked components website

Reply #27 –
Another small suggestion: add a Changelog header before or after the Current version. Currently it's not very obvious that the release text is a changelog (without reading said text).

[EDIT] Another small bug, there is an empty new line appended to the beginning of the changelog when Previewed.

Re: fooweb2020: reworked components website

Reply #28 –
Change log formatting updated. Added 'change log:' header before the change log.
Microsoft Windows: We can't script here, this is bat country.

Re: fooweb2020: reworked components website

Reply #30 –
Not sure if this is a proper place to report this but: a few fb2k versions back there was the following change "Made possible to check for updates of components listed but not hosted on foobar2000.org.". But no matter what I've tried I couldn't force my fb2k instance to produce any notification about an available update.
Are there any specific steps required to enable this feature?

Re: fooweb2020: reworked components website

Reply #31 –
Indeed, checking for updates of components without downloads does not appear to be functional. Investigating.

Edit: Fixed
Microsoft Windows: We can't script here, this is bat country.

Re: fooweb2020: reworked components website

Reply #32 –
Yep, works now =)
v1.5.3 b5 has the same indentation bug in change log as `fooweb` though :P

Re: fooweb2020: reworked components website

Reply #33 –
Lines with no asterisk were meant to continue the previous change log line (like, additional notes for a change), rather than present headers. I'm getting that changed, so spaces before text are used to determine what the content is (two or four spaces for extra info, no space for header).
Microsoft Windows: We can't script here, this is bat country.

Re: fooweb2020: reworked components website

Reply #34 –
It would be a good moment to report any pending bugs with 1.5.3 change log formatting. I'd like to prepare 1.5.3 final, which means finalizing the change log bullet list spec.
Microsoft Windows: We can't script here, this is bat country.

Re: fooweb2020: reworked components website

Reply #35 –
Changelogs (of components that I've checked) display correctly in 1.5.3b6.
Url support (even a basic one, without aliasing) would be really appreciated though =)

Re: fooweb2020: reworked components website

Reply #36 –
I was using the component website tonight with a component which had been in beta with version 0.4.5b4, and I tried to officially release version 0.4.5. After publishing that version, foobar told me the component did not need an update. It was only when I bumped the version to 0.4.6 in the component registry that I could update through foobar.

Is there specific formatting I need to use for semvar comparisons, or is this currently bugged?

Re: fooweb2020: reworked components website

Reply #37 –
From foobar2000\SDK\componentversion.h:

Code: [Select]
//! Please keep your version numbers formatted as: N[.N[.N....]][ alpha|beta|RC[ N[.N...]] \n
//! Sample version numbers, in ascending order: 0.9 < 0.10 < 1.0 alpha 1 < 1.0 alpha 2 < 1.0 beta 1 < 1.0 RC < 1.0 RC1 < 1.0 < 1.1 < 1.10 \n
//! For a working sample of how foobar2000 sorts version numbers, see http://www.foobar2000.org/versionator.php \n

P.S. Probably the link should be changed from http to https (current browsers aren't happy when they see plain http).

Re: fooweb2020: reworked components website

Reply #38 –
Quote from: lvqcl on
From foobar2000\SDK\componentversion.h:

Code: [Select]
//! Please keep your version numbers formatted as: N[.N[.N....]][ alpha|beta|RC[ N[.N...]] \n
//! Sample version numbers, in ascending order: 0.9 < 0.10 < 1.0 alpha 1 < 1.0 alpha 2 < 1.0 beta 1 < 1.0 RC < 1.0 RC1 < 1.0 < 1.1 < 1.10 \n
//! For a working sample of how foobar2000 sorts version numbers, see http://www.foobar2000.org/versionator.php \n

P.S. Probably the link should be changed from http to https (current browsers aren't happy when they see plain http).
Thanks, I'll keep that in mind next time I need to do a beta release.

Re: fooweb2020: reworked components website

Reply #40 –
By the way,  the default example was sorted as:

0.9.6.9
0.9.6.10
1.0 alpha 1
1.0 alpha 2
1.0 beta 1
1.0 beta 2
1.0 beta 2a
1.0
1.0.2 beta
1.0.2 beta 1
1.0.2
1.0.2.1
1.0 RC
1.0 RC55
1.1

???

Re: fooweb2020: reworked components website

Reply #41 –
Looks like the script is broken now. Sorry for linking to it.

Re: fooweb2020: reworked components website

Reply #42 –
Regression has been fixed, release candidates are again between betas and stable.
The versionator.php link is OK to use - it references same code as site's code matching updates so it exposes any bugs present in it.
Microsoft Windows: We can't script here, this is bat country.

Re: fooweb2020: reworked components website

Reply #43 –
Assume its an oversight on part of the author/developer, and I apologize in advance for this probably being the wrong thread to post it, but new, week-old component here w/newest version here (tag type "album art")
Neither an audiophile, nor album snob. Why do ratings threads always have someone saying they don't believe in rating music?
Record Label Icons: 600x600 pngs appropriate for any color background:
freeimage.host/johnbuck/?list=images&sort=name_asc&page=1

Re: fooweb2020: reworked components website

Reply #44 –
Quote from: JohnBuckWLD on
Assume its an oversight on part of the author/developer, and I apologize in advance for this probably being the wrong thread to post it, but new, week-old component here w/newest version here (tag type "album art")
Marc/snotlicker does not publish his components in the registry.
 

Re: fooweb2020: reworked components website

Reply #45 –
@Peter: a small bug/formatting issue - additional new lines are ignored.
Example:

Source code for the changelog:
Code: [Select]
Hotfix for 1.3.0.  

Fixed

Result (mind the missing double new-line after `Hotfix for 1.3.0.`):

https://www.foobar2000.org/components/view/foo_spider_monkey_panel