I don't see how this can help maintaining the projects. Maybe I didn't explain myself, basically, the configuration is like:" Every client has 2 projects: style project and locales project.
If I have 2 clients, both would have, for the simplicty, these 2 files: Client A's style project: -------- .myCoolButton { color: #FF0000; } Client B's style project: -------- .myCoolButton { color: #0000FF; } Now, all I have to do is to compile each client style and dynamically load it, leaving the main up ignorant of the client. However, lets say I need to add new screen with some new kind of button, I'll need to add a new class selector all clients' style projects, one by one, that's the maintenance issue I have - I don't want to go through N projects just because I need to ass new text/style... Thanks, Almog Kurtser --- In flexcoders@yahoogroups.com, "Mayur Bais" <[EMAIL PROTECTED]> wrote: > > can u not keep the styles and text file..in once folder.. > and add that folder as a external source path ..to all ur locale project.. > and there by only one copy gets used across all projects... > > > On 5/13/08, mydarkspoon <[EMAIL PROTECTED]> wrote: > > > > Hi, > > I'm currently working on a project where both styles and language > > content are externalized and loaded at runtime. > > The same application is supplied to all clients from the same code > > base, and the changes are only made on the locales/styles. > > > > As the styles and the locales are compiled for every client > > differently, they're located on separated projects: > > -Main application project (Same code base for all clients) > > -Styles flex project (per client) > > -Locale project (per client) > > > > Since the main app is rapidly being developed, new styles and texts > > are added. > > Whenever new text is added to the app, it needs to be added to each > > and every locale project, even if all clients share the same text. > > same goes with styles. > > > > This is a quite maintenance issue and I'm looking for ways to make > > this proccess easier. > > > > I'll be really glad to get get some advices regarding maintenance of > > such architecture. > > > > Thanks in advance, > > > > Almog Kurtser. > > > > > > >