Skip to main content

New APEX Item Type Plugin : BetterGrow Textarea

By
Using the jQuery BetterGrow Plugin, I created a BetterGrow APEX Plugin. The APEX part is just a simple wrapper of the jQuery Plugin - so all the credits go to "The Product Guy" who came up with that one.
It just does this:
You can see it in action on the demo site. And download it from apex-plugin.com. There already was an similar plugin, created by Martin. On the demo page you can see both, so pick the one you like most!
Labels:
Location: Arnhem, The Netherlands

Comments

Patrick Wolf said…
Hi Roel,

looks nice. But wouldn't it be useful to have some kind of maximum size? Because now the textarea grows forever which also doesn't look good if you have a long text.

Regards
Patrick
1:40 pm
Roel said…
You're right, but the (original) jQuery Plugin doesn't support a maxsize setting. So in order to achieve that we have to adapt the js code. I'll put this on my to-do list ;-)
1:50 pm
Johannes de Jong said…
Definitely a plug in I will use.
7:19 am
style said…
here is how you can add Facebook LIKE to a blog http://stylishfirst.com/how-to-add-facebook-like-to-blogger/
1:48 pm
Stefan said…
Hi,

Your Plugin is fine in Firefox, but it is not working in IE8. On each keystroke the height of the textarea is set to the initial value!

The jQuery BetterGrow Plugin is working fine in IE8.

regards
Stefan
4:08 pm
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