Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 372255

Summary:	Make branding more flexible to support alternative clients
Product:	[RT] RAP	Reporter:	Ralf Sternberg <rsternberg>
Component:	RWT	Assignee:	Project Inbox <rap-inbox>
Status:	RESOLVED FIXED	QA Contact:
Severity:	enhancement
Priority:	P3	CC:	holger.staudacher
Version:	1.5
Target Milestone:	1.5 M6
Hardware:	PC
OS:	Linux
Whiteboard:

Description Ralf Sternberg

2012-02-22 12:10:35 EST

Some of the methods in the class AbstractBranding make sense only for the web client, but are useless for mobile clients:

* getFavIcon
* getHeaders
* getBody

Alternative clients may need different branding parameters. Before we finalize the ApplicationConfigurator API, we should think about replacing AbstractBranding in this API with a more general interface.

@Holger: Are there any requirement from the mobile prototypes already?

Comment 1 Ralf Sternberg

2012-03-16 07:38:25 EDT

This requirement has been addressed in bug 372257. Instead of brandings, we now have entrypoint properties. These properties are key-value maps. Every client can define its own keys. The default web client provides constants in the new class WebClient.