[Chameleon-dev] [Bug 451] New: Some shared resources are cached from template initialized with chameleon. Subsequent templates do not have their shared resources loaded (ie..separate languages) .

[bugzilla-daemon at www.maptools.org]

http://www.maptools.org/bugzilla/show_bug.cgi?id=451

           Summary: Some shared resources are cached from template
                    initialized with chameleon.   Subsequent templates do
                    not have their shared resources loaded (ie..separate
                    languages) .
           Product: Chameleon
           Version: 1.99
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Core
        AssignedTo: chameleon-dev at lists.maptools.org
        ReportedBy: godwinl at agr.gc.ca


>From chameleon user list correspondence:

> I have another question about language template handling, and shared 
> resources.  The wait image is declared as many times as there are 
> languages in all templates.  If you change something in one template, 
> it affects that template.  But when it comes to styling (text buttons, 
> nav
> buttons) only those resources defined in the initial template are
> loaded.  So...if you start the session in English, the style shared
> resoures defined in english apply.  Styling defined differently in other
> language templates has no effect. BUT  it is possible to change a
> stylesheet between languages.  

Um .... I see the problem.  I think the caching mechanism is perhaps a 
little too aggressive.  Right now, it caches the actual generated images 
on a per-template basis, but it will actually only load a shared 
resource once per session if caching is used.  I think it can be made to 
work on a per-template basis, but this will cause the session to grow a 
little bigger and reduce performance (perhaps).

> 
> I guess I'm saying that this is inconsistent and hard to follow.  It 
> would be my preference to have chameleon accept all shared resources 
> as they are in a template, regardless of when they are loaded.  Is 
> something that can be changed easily, say by me?  Is it interesting 
> enough to others to hope for a change in a future release?

I would actually classify this as a bug. I'll try to address it in one 
of the beta releases.



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.