Skip to main content

APEX Plugin Directory

By
For all you APEX Plugin developers: There is already an operational APEX Plugin Directory available at http://www.apex-plugin.com/. You can add your own Plugins there and view and download the ones your co-APEX developers came up with.
Looks pretty slick, with just one drawback: It is not built in APEX (at this moment).
Oracle also has one under construction at http://www.oracle.com/technology/products/database/application_express/html/plugins.html.
Labels:

Comments

Buzz Killington said…
I've already seen no less than like 5 different bloggers setting up various sites, groups, google things for plugins.

Personally it should really just be handled through Oracle sort of how Apple handles the App Store or how jquery indexes plugins. Not as rigid for submission, but if you want an app, you go one place. Everyone makes sure the most up-to-date plugin is on Oracle's site, and then everyone is happy.

What I think will inevitably happen is you'll get a graveyard of sites that started out storing all these plugins, but people will get other jobs, or whatever and will never update the sites. So you'll get outdated plugins and that doesn't help anyone.

Just look at what happened with the slew of wikis, blogs and sourceforge projects...etc - haven't been updated in years. This it the fate of disparate plugin registries too.

That's just my 2 cents anyway.
2:11 pm
Johannes de Jong said…
Though I think apex-plugin.com is a fantastic initiative I'm afraid I have to agree with Buzz.

Personally however I feel that it won’t be a bad idea if Oracle would let a 3rd party "manage" the plug-ins, something like what IBM did with Eclipse. Creativity works best for developers if they feel that their efforts are “managed” by an independent party.

I do however feel that the plug-ins that are Oracle “certified” should be clearly indicated.

Johannes
7:15 am
Post a Comment

Popular posts from this blog

Fix Interactive Report headers issue when using a Region Display Selector

By
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.
Post a Comment
Read more

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

By
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...
21 comments
Read more

Refresh selected row(s) in an Interactive Grid

By
In my previous post I blogged about pushing changed rows from the dabatase into an Interactive Grid . The use case I'll cover right here is probably more common - and therefore more useful! Until we had the IG, we showed the data in a report (Interactive or Classic). Changes to the data where made by popping up a form page, making changes, saving and refreshing the report upon closing the dialog. Or by clicking an icon / button / link in your report that makes some changes to the data (like changing a status) and ... refresh the report.  That all works fine, but the downsides are: The whole dataset is returned from the server to the client - again and again. And if your pagination size is large, that does lead to more and more network traffic, more interpretation by the browser and more waiting time for the end user. The "current record" might be out of focus after the refresh, especially by larger pagination sizes, as the first rows will be shown. Or (even wors...
Post a Comment
Read more