Skip to main content

APEX 4.0 PlugIn for Google Wave

Better late than never...
I am also happily playing around with APEX 4.0 and busy creating some PlugIns. The first one is rather simple (once you get the hang of it). It can show you a Google Wave by just entering the Wave ID (ok, and a width and height for your convenience).
If you have a Google Wave account you can see the results and download the PlugIn on : http://tryapexnow.com/apex/f?p=PLUGINS:GOOGLEWAVE.

More to come ... : as you can see in the Wave, there are lots of good ideas on PlugIns!!

Comments

Patrick Wolf said…
Looks like the URL doesn't work.
Roel said…
What URL? This one: http://tryapexnow.com/apex/f?p=PLUGINS:GOOGLEWAVE
?? Seems to work for me (FF & Safari)...
Martin D'Souza said…
Hi Roel,

I just tried and the link doesn't work.

Martin
Roel said…
otherwise try 9872:2 instead of PLUGINS:GOOGLEWAVE in the URL
Surachart Opun said…
nice -)
work on http://tryapexnow.com/apex/f?p=9872:2:2516381878495629
Hi Roel

In order to make the wave plugin to run on apex 4.0 production i had to change the code to this

function render_wave (
p_region in apex_plugin.t_region,
p_plugin in apex_plugin.t_plugin,
p_is_printer_friendly in boolean )
return apex_plugin.t_region_render_result

and at the end:

return null;
end render_wave;


It is great and i am using it in a prototype to one offer we are working with :-)

Popular posts from this blog

Fix Interactive Report headers issue when using a Region Display Selector

When you have multiple Interactive Reports (IR) on your page and use a Region Display Selector to mimic tabs, you might notice some weird behaviour in the IR headings if you switch tabs. The headings are not positioned correctly and you get an extra empty row under the headings. It just looks weird and ugly. But if you resize your browser window, it all looks fine again (until you switch to another tab..) So can we fix this by creating a Dynamic Action that mimics that "browser window resize" event? Yes we can! Create a Dynamic Action that fires on Click of the jQuery selector li.apex-rds-item a . That should fire a JavaScript snippet :  apex.event.trigger(this.triggeringElement, "apexwindowresized"); So now a click on a tab not only switches from one IR to another but also fires that event that will "autofix" the IR headers. A simple solution for an annoying problem. This applies to APEX 5.0, I assume it will be solved in 5.1.

How to create neatly formatted Excel documents using PL/SQL?

If there is a requirement to produce output from an application into Excel, you would probably create a CSV (Comma Separated File) with the data and start Excel to show the data - at least that's what I did...until now. The drawback of this solution is that you could only produce data and no nice layout. But Excel is also capable of opening HTML-files and using this you could create Excel files with data and magnificent layout! Let me give an example: 1. Create a procedure to show the data in formatted in an HTML table. CREATE OR REPLACE PROCEDURE display_emp_list IS v_emp_count NUMBER(5); v_empno NUMBER(8); v_ename VARCHAR2(50); v_job emp.job%TYPE; v_sal emp.sal%TYPE; v_bg_color VARCHAR2(10) := ''; CURSOR c_emp IS SELECT empno, initcap(ename), job, sal FROM emp ORDER BY ename; BEGIN SELECT COUNT(*) INTO v_emp_count FROM emp; owa_util.mime_header('application/ms-excel', FALSE); htp.p('Content...

Transform ORA-xxxx messages into something more user friendly in APEX

When you delete a record that is referenced using a foreign key constraint you get a rather ugly error like this: Of course you can prevent such a thing from happening by creating a Page process that checks if your delete is "Ok". But that's double coding...and dangerous when you have to maintain your database structure: You'll probably forget to update the processes as well. Wouldn't it be nice if you can 'catch' that error an present it to the end user in a more friendly way (and with a somewhat more understandable text)? I guess your users will be more enthusiastic about your application (and you) when you show them something like this: So how do we achieve that? 1. Edit the "Error Page Template Control" region of your Application Default Page Template, because that's the one that is used for presenting errors. Set it to : <script type="text/javascript">$(document).ready(function(){raiseErrorHandler();});</script> ...