Skip to main content

Less is More

Spent a few minutes yesterday building my schedule for OOW.  Lots of sessions, and unfortunately, some of the good ones are already booked.  That didn't matter, as there were plenty more to choose from.

There's not a whole lot of APEX sessions this year - or at least ones that I have not already seen.  Thus, I'm going to focus more on other database technologies, such as security & performance.  Lots of sessions under that category.

My only gripe is that the Schedule Builder UI needs a major overhaul.  First off, you need a 30" monitor just to view all of the content on one screen - especially when you have the Advanced Search option enabled.   Also, I kept getting a "Search Timeout" error when I tried to search for sessions.  The only way to resolve this is to log out and log back in again.  Such basic functionality for a database conference should NEVER break, at least in my opinion...

The Schedule Builder also tries to use a lot of Ajax-type controls; lots of popup boxes and asynchronous stuff going on.  Maybe it works better in IE, but in Safari, it's a bit clunky.

This is part of the danger of using jQuery or similar Ajax-based technologies - without thorough testing on multiple browsers, the user experience may vary greatly.  This can often be mitigated when building applications that are used internally, as most organizations can lock down which browsers are allowed.  However, this is obviously not the case on the public Internet.

While the Advanced Search is more sophisticated and allows you to search by day, for instance, there is no Google-like interface to search all fields for a specific string.  There are two text fields - Speaker/Company & Free Text - that each search different parts of the content.  But if you're searching for a string, the system will AND these two fields together, producing a different set of results than you may expect.

It seems like too much attention was paid to adding features vs. thinking of a logical design for this site.  Some common things - such as the aforementioned Google-like search, a weekly view of the agenda, and a map of where each session takes place - all seem to be left out.

Hopefully this tool will be enhanced for future events and be made simpler and better at the same time.

Comments

Roel said…
Why not build a cool APEX demo for this Schedule Builder and show that to the Oracle people? Must not be too hard for you ;-)
Then maybe we can use a proper working APEX version next year...
Cheers and see you in SF,
Roel
PS: Hope you added my session to your schedule as one of the few APEX sessions (and you haven't seen it yet!).
Scott said…
Roel,

It doesn't HAVE to be APEX - but I think that from Oracle, we should get something a bit more intuitive and easy to use. Oh, and once OOW starts, something that doesn't go down every 5 minutes like it has in the past.

APEX is a perfect technology for this type of application, as you can easily and quickly design most of the site, and then scale it up with RAC the week of OOW.

I wish I could make your session - because I have not yet seen it - but I'll be flying home Thursday AM. :(

- Scott -
John Flack said…
Gee, Scott, I liked this year's schedule builder a lot better than last year's. Compare it to the Collaborate or Kaleidoscope schedule builder - those two make it easier to compare what's happening at the same time, but with so many concurrent sessions I'm constantly panning right and left. But I do admit that I had to use it on IE - my favored Firefox browser wouldn't show it.
Scott said…
JCFlack,

I don't remember much difference between this and last year's application.

While scheduling sessions is not a terribly hard task, it seems that most sites - at least in the Oracle community - do struggle with it.

I wonder if it's any easier or more intuitive for, say, Microsoft related conferences?

- Scott -

Popular posts from this blog

Custom Export to CSV

It's been a while since I've updated my blog. I've been quite busy lately, and just have not had the time that I used to. We're expecting our 1st child in just a few short weeks now, so most of my free time has been spent learning Lamaze breathing, making the weekly run to Babies R Us, and relocating my office from the larger room upstairs to the smaller one downstairs - which I do happen to like MUCH more than I had anticipated. I have everything I need within a short walk - a bathroom, beer fridge, and 52" HD TV. I only need to go upstairs to eat and sleep now, but alas, this will all change soon... Recently, I was asked if you could change the way Export to CSV in ApEx works. The short answer is, of course, no. But it's not too difficult to "roll your own" CSV export procedure. Why would you want to do this? Well, the customer's requirement was to manipulate some data when the Export link was clicked, and then export it to CSV in a forma

Refreshing PL/SQL Regions in APEX

If you've been using APEX long enough, you've probably used a PL/SQL Region to render some sort of HTML that the APEX built-in components simply can't handle. Perhaps a complex chart or region that has a lot of custom content and/or layout. While best practices may be to use an APEX component, or if not, build a plugin, we all know that sometimes reality doesn't give us that kind of time or flexibility. While the PL/SQL Region is quite powerful, it still lacks a key feature: the ability to be refreshed by a Dynamic Action. This is true even in APEX 5. Fortunately, there's a simple workaround that only requires a small change to your code: change your procedure to a function and call it from a Classic Report region. In changing your procedure to a function, you'll likely only need to make one type of change: converting and htp.prn calls to instead populate and return a variable at the end of the function. Most, if not all of the rest of the code can rem

Logging APEX Report Downloads

A customer recently asked how APEX could track who clicked “download” from an Interactive Grid.  After some quick searching of the logs, I realized that APEX simply does not record this type of activity, aside from a simple page view type of “AJAX” entry.  This was not specific enough, and of course, led to the next question - can we prevent users from downloading data from a grid entirely? I knew that any Javascript-based solution would fall short of their security requirements, since it is trivial to reconstruct the URL pattern required to initiate a download, even if the Javascript had removed the option from the menu.  Thus, I had to consider a PL/SQL-based approach - one that could not be bypassed by a malicious end user. To solve this problem, I turned to APEX’s Initialization PL/SQL Code parameter.  Any PL/SQL code entered in this region will be executed before any other APEX-related process.  Thus, it is literally the first place that a developer can interact with an APEX p