Skip to main content

Why do I attend Kscope?

Kscope14 will be my 6th Kscope event. After New Orleans, Monterey, Washington, Long Beach and New Orleans again (yes, I missed San Antonio), this year Seattle will be the place to be at the end of June.

So why do I spent quite a lot of time and money to visit this event? That's because of two reasons: the content and the fellow attendees. Without any doubt the content of Kscope is best you can get in one conference. And it doesn't matter whether your interested in database development, APEX or Hyperion, there's only one conference with that much awesome presentations. And that draws a certain type of people: your fellow attendees. The size of the event and the location (usually) offers an unique opportunity to meet and greet whoever you want. You don't have to make an appointment to talk to someone, as there is a huge chance you'll run into each other at a presentation, during lunch or at the bar. Speaking of lunch ... there is no conference or event that serves better food than Kscope!

During Kscope14 I will do two presentations myself. One in the beginners track about "Starting mobile development with APEX" and one about "Creating hybrid APEX applications".

As the APEX Content Lead, I am looking forward to all (APEX) presentations. Especially all the planned APEX 5 presentations will have my attention. Apart from those I planned to attend the "Pins, Polygons, and Perspectives: Visualizing Geographic Data in APEX" by Christoph Ruepprich and "Oracle APEX + Node.JS A Primer" by John Scott.
Another thing I also like (and has been requested during previous conferences), is the "intro track". So the first two days of the conference we do have one (out of three) complete track 100% dedicated to APEX beginners. And another thing I'm fond of are our "newbie slots". In order to prevent an unequal competition between newbie presenters and well known APEX rock stars, we planned the presentations of the Kscope newbies against each other. So they all get an equal chance to get a full room!

So, right now you understand I am looking forward to Kscope14 a lot. And I hope I'll meet you there in June. Visit http://kscope14.com for all details, abstracts, location and registration.

Post a Comment

Popular posts from this blog

Showing a success message after closing a modal dialog

APEX 5 comes with Modal Dialogs out of the box. Very neat. Especially for adding and changing data. And to minimise the number of time a user has to click, it could be useful to add a "Close Dialog" process after the actual data processing. When the data processing fails, the Dialog stays on top showing the error. When data processing runs fine, the Dialog is closed ... without any confirmation. And this might be scary for a shaky user.

So how can we provide the user some feedback? On Page 4 of the Sample Dialog Application you can see one solution: up on a Dialog Closed Event on the parent page it does a redirect to refresh the parent page appending the success message of the "Close Dialog" process. This has two drawbacks. First, it probably refreshes more than necessary. And second, if you're using multiple layers of dialogs (dialogs that open other dialogs) the message appears in the "parent dialog".
As an alternative you could follow these steps: 1…

APEX 5 New Static File Features

In APEX 4 you could upload files - like CSS files, JavaScript files, Images and whatever else you like - into the APEX Repository. When you navigate to Shared Components, there is a Files section that offers three different options:
CSS Files are always uploaded (and changed !) for the whole Workspace. For Images and Static Files (usually JavaScript) you could choose whether they should be available for the whole Workspace or for a specific Application only. And if you had a lot of files - e.g. a lot of images - then you had to go through the upload process one-by-one. But that's usually a one time only thing. If you make changes to the CSS and JavaScript files - and that's a continuous process in development - then you had to delete the existing file and upload the new one. Over and over again. And meanwhile fighting the cache of the webserver and your browser.  And another irritating issue: You couldn't use relative references in your CSS or JavaScript files as they just…

Using LDAP for Authentication and Authorization within APEX

One of my current customers would like to use their LDAP (Microsoft Active Directory) server for authentication and authorization of APEX applications. Of course we tried to set up a standard LDAP Authenication that's available within APEX. But we couldn't get that to work. Maybe it has to do with the fact that the client stored their Users within Groups within Groups within .... . Or maybe it doesn't do a full tree walk in the directory. Or maybe it is just because it is Microsoft - and not Oracle Internet Directory (OID). So we moved to a custom Authentication using the DBMS_LDAP functions (and some examples from the Pro Oracle Application Express book and Tim Hall - a.k.a. Oracle Base).

One of the issues we encountered that we wanted to use the user's login name, like "jdoe" and not his full name ("John Doe"). And the login name is stored in the "sAMAccountName" attribute. But authenticating using just "jdoe" didn't work. …