Wouter Vernaillen 10 Years Ago Thanks a lot for putting this code online. IT was a great session at DevCon! Please sign in to reply. Reply as... Cancel James Falkner Wouter Vernaillen 10 Years Ago Thanks Wouter! Let me know if you have any follow-up questions. One thing I forgot to add, there are several improvements that could be made to the Expando browser, such as handling field types like dates, etc, and configuring the AUI datatable to use a cool date picker when double-clicking on dates. Or, providing better "helper links" for other types of objects that may be in Expando. Cheers! Please sign in to reply. Reply as... Cancel
James Falkner Wouter Vernaillen 10 Years Ago Thanks Wouter! Let me know if you have any follow-up questions. One thing I forgot to add, there are several improvements that could be made to the Expando browser, such as handling field types like dates, etc, and configuring the AUI datatable to use a cool date picker when double-clicking on dates. Or, providing better "helper links" for other types of objects that may be in Expando. Cheers! Please sign in to reply. Reply as... Cancel
s s 8 Years Ago Hi, this is very good\interesting information. Well done. I tried a simple example and got the render\response working with one issue. When using "<form action="${request['resource-url']}" method="POST">" the resource-phase results get rendered on a blank page (not in the portlet). The resource-url seems to be formed properly. Any ideas on how to fix that? Second question; when doing a parameters and response sort of solution, would you be better off using two portlets (web-content-display in my case) and establishing some sort of communication between them? Don't know if that makes things harder or easier or if even feasible but may add extra flexibility\reusability (something like what CatNav and AssetPub do). Please sign in to reply. Reply as... Cancel s s s s 8 Years Ago Skip the first one, (it's probably in your stuff above; was intimidated by volume of code); got something rough working with a bit of AJAX and checking request lifecycle.. Please sign in to reply. Reply as... Cancel James Falkner s s 8 Years Ago @s s - you could do it with two portlets, but I don't think you could use traditional portlet IPC eventing or render parameter mechanisms to do it. You'd have to do it with a client-side solution (using Liferay.fire() and Liferay.on() APIs or perhaps something more robust like OpenAJAX pub/sub). So yeah it would probably add some reusability! Good question! Please sign in to reply. Reply as... Cancel
s s s s 8 Years Ago Skip the first one, (it's probably in your stuff above; was intimidated by volume of code); got something rough working with a bit of AJAX and checking request lifecycle.. Please sign in to reply. Reply as... Cancel
James Falkner s s 8 Years Ago @s s - you could do it with two portlets, but I don't think you could use traditional portlet IPC eventing or render parameter mechanisms to do it. You'd have to do it with a client-side solution (using Liferay.fire() and Liferay.on() APIs or perhaps something more robust like OpenAJAX pub/sub). So yeah it would probably add some reusability! Good question! Please sign in to reply. Reply as... Cancel