Application Express Best Practices

It doesn’t seem 5 minutes since I was presenting at UKOUG and I’m already starting to prepare for the next set of conferences.

So far this year I’m going to be presenting at IOUG Collaborate in Denver (April) and also at ODTUG in New Orleans (June).

At both conferences I’m going to be presenting on the same topic:

  • Application Express Hints, Tips & Best Practices.

No, I’m not doing the same one twice because I’m lazy ;), it’s because it’s a topic I hear people mention again and again (coincidentally mentioned only last week on H.TonguΓ§ YILMAZ’s blog)

It can be difficult when you’re starting out in any development environment to know the ‘best’ ways of doing things, so lots of newbies to APEX will hopefully find this topic interesting. For the more seasoned APEX developers, I’m throwing in some hints and tips that not everyone may be aware of (in other words I’m hoping to show something that will be useful to APEX developers of any skill level).

For those of you not attending either the Collaborate or ODTUG events, I am writing a Whitepaper on the topic which I hope to be able to make public.

Of course, the first people to get to see this topic, will be the people attending the APEX Evangelists European Training event in London (March), there are still a few places left so if you’re looking for some advanced APEX training then sign-up here!

3 thoughts on “Application Express Best Practices

  1. Doug Gault

    Whether you cover it in detail or not, it would also be good to point to PL/SQL best practices too. I know that there are a number of quick introductions out there, and Mr Feuerstien has written extensively on the topic.

    In short, you can do everything right in APEX, but if your back in PL/SQL sucks, so will your ability to troubleshoot, debug, and support the system.

    Just my 2 pence!



  2. Bill Ferguson

    I’m hoping we have enough money in budget this year so I can attend Collaborate, since it’s here in town.

    One thing that’s always bugged me when looking over the sample apps, etc., is how the pages are generally scattered and intermixed. When I create my apps, I try to think everything through first, then I ‘generally’ leave pages 1-200 for typical ‘basic’ screens, like the login/logout, access control, introduction/welcome, etc. My ‘data’ pages I generally don’t start until 300, and I always try to increment succeeding page numbers by at least 2. I also try to ‘group’ my pages in the same set, where the pages in one group (like ‘General info’) would fall in the range of 300 -330, then the next group would begin at 340 or 350. A minor complaint, but especially when trying to follow somebody else’s logic in app design and implementation, it makes it easier trying to see how the pages ‘flow’.



Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s