From: Nando D. <na...@de...> - 2005-07-24 07:17:30
|
Milan, M> "Open in web browser" would need a file saved somewhere, so we have same M> problems as with "Save as HTML file". Probably solvable. Since we have M> both "save" and "print", I'm not sure this options is even needed? I'd say let's skip it for the time being. M> "Duplicate window" is open for discussion. The idea is that you can, for M> example, open both "dependencies" and "fields" page on some table M> simultaniously. what if you add a context menu with the "Open in new window" command to hyperlinks instead? M> Currently we have code in framemanager that constraints M> each object to one page. Now do we: M> - circumvent framemanager and open new independent window when M> "Duplicate window" is shown M> or M> - extend framemanager to allow multiple instances ? I'm not terribly familiar with the frame manager; we really need to put some comments in to document stuff. :-) AFAICT that code serves the purpose (among others) of finding an existing window and bring it to the foreground instead of creating another instance as required. This is the current rule. I'd advise against circumventing a rule, let's change the rule to reflect our new requirements instead. To do that, you'd perhaps have to add a "bool forceNewFrame = false" parameter to FrameManager::showMetadataPropertyFrame, but I'm not sure it's the way to go. Then, your popup menu item could add a param like "target=new" to the URL and let the URI handler figure out what that means. The particular handler is PropertiesHandler; in PropertiesHandler::handleURI you test for the target param and set forceNewFrame accordingly. Alternatively, we could also automate everything at the metadata frame / frame manager level: add the page type to the set of criteria that the manager uses to find an existing window and the window will be foind only if it is displaying the same page type (i.e. summary), otherwise (i.e. triggers) a new page is created. Ciao -- Nando Dessena http://www.flamerobin.org |