P4
I'm not sure which component this would be. It affects all versions. I didn't know if I should list it as a bug or an improvement.
When working with javafx.concurrent.Service, both the title and message properties of the service will return empty strings whenever the service state is READY. This is because, when the Service is started, both properties are temporarily bound to matching properties in an underlying Task. When the Service is reset both properties are unbound and set to "" (empty). The explicit calls to set happen in the reset() method of Service.
This makes it difficult to build a control that shows a list of Services that can be managed (started, cancelled, etc.) by the user. The title and message properties aren't usable because, assuming all Services are added to the list with a state of READY, all of the titles and messages are blank.
I can think of a couple options to make the API a little more usable...
1) Add something like readyTitle and readyMessage properties to Service. Alternate names could be idleTitle, unboundTitle, emptyTitle.
2) Add protected methods that would allow sub-classes to supply values that are used when the title and message are unbound.
Personally, I would prefer to set the title for a Service directly rather than having it bind to underlying task. Using either of the above suggestions I would have to ensure both the Service and underlying Task(s) are using the same title if I don't ever want the title to change.
When working with javafx.concurrent.Service, both the title and message properties of the service will return empty strings whenever the service state is READY. This is because, when the Service is started, both properties are temporarily bound to matching properties in an underlying Task. When the Service is reset both properties are unbound and set to "" (empty). The explicit calls to set happen in the reset() method of Service.
This makes it difficult to build a control that shows a list of Services that can be managed (started, cancelled, etc.) by the user. The title and message properties aren't usable because, assuming all Services are added to the list with a state of READY, all of the titles and messages are blank.
I can think of a couple options to make the API a little more usable...
1) Add something like readyTitle and readyMessage properties to Service. Alternate names could be idleTitle, unboundTitle, emptyTitle.
2) Add protected methods that would allow sub-classes to supply values that are used when the title and message are unbound.
Personally, I would prefer to set the title for a Service directly rather than having it bind to underlying task. Using either of the above suggestions I would have to ensure both the Service and underlying Task(s) are using the same title if I don't ever want the title to change.