In general it's important that you know the new portlet specification as its vital for our decision. But i will neverthelesse answer your points as you made the effort to answer mine :-)
> If all developers use your library & at one point all widgets go through > your library, then you can guarantee the div gets the namespace somehow > added to the ID. That "somehow" is what im interested in :-) I can overwrite a component and implement my own naming, where i try to respect my own conventions. But, as im not in the portlet code but much more in my GWT-extended Class, there's no way how i can reach the portlet specific information. > I'm not familiar with the JSR (wonder how many people here are). Can you > expand on the requirement? You can create URL's by tag's that can be called from any portlet that causes a call of an internal portlet function...like doing a POST on the doPost of a servlet. The same goes for RenderURL's...if i create a Render URL and call a specific page, all portlets on this page are getting their doView method called, so that they can do their render operations. > Please clarify the requirement here. It's possible to do some level of > communication between GWT modules that are on 1 page. Not trivial, but > possible (but I believe they would have to expose some kind of > non-conflicting interface, in terms of the function name), but these apps > would have to be created to begin with with the expectation of being used as > a JS library. However, making a GWT-"enabled"-Portlet can just be a simple > <inherits> away. My concern is not a GWT-specific communicaton (which could come handy for sure) but more a JSR 286 supported way. Only this can ensure, that we can integrate external portlets, which are supporting this standard. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
