Skip to main content

Collaborate 2011 - Day 1

Travelling to Orlando went smooth. Very smooth even. The first leg to Boston arrived about a half hour early and as I was sitting right in front of the Economy class, I could leave the plane as one of the first. So I arrived at the border securty as the third non-US citizen. So checkin in the US costed about two minutes. I even arrived at the luggage belt before it actually started running - usually my bag is already off the belt when I arrive there. After an almost two hour layover, in the second plane I managed to get two seats at the exit row. So I could move wherever I liked. And at Orlando airport a taxi was immediately available so I arrived at the hotel around 6:30 AM. After some real American food (burger, beer & fries) I hit the sack around 10. 
The next morning I managed to stay more or less asleep until 7. From 9 to 12 I sat at the pool until it was getting too hot and went to the registration of Collaborate.The conference is in the Orlando Conference Centre. I thought Moscone in San Francisco was a big place, but this is way bigger. The staff rides around on Segways...
Today there was only one session on my schedule : "Fusion, Soup to Nuts". The whole idea was to show all the technical details that's used for building Fusion Apps, by a number of different presenters. I think the idea is quite good, but the operation could be better. Alongside that, the projector screen was way too small for that big room. And one of the speakers couldn't resize his resolution, so his demo was unreadable for everyone who wasn't at the front row. The sequel ended with a presentation of Fusion Applications (by Debra, who else). It even contained a semi-live demo - a.k.a. a viewlet. As Fusion Apps isn't available yet, they weren't allowed to do a live demo. But, I have to admit, the user interface looks very, very slick!
This first day of Collaborate ended with a reception, with some food (pizza slices etc) and drinks. I bumped into Borkur and his colleague Peter (from RittmanMead) and also met Gwen and a colleague of hers (from Pythian).
All in all a nice first day - looking forward to tomorrow as the "real" conference starts!

Comments

Popular posts from this blog

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

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...

Refresh selected row(s) in an Interactive Grid

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...

Stop using validations for checking constraints !

 If you run your APEX application - like a Form based on the EMP table - and test if you can change the value of Department to something else then the standard values of 10, 20, 30 or 40, you'll get a nice error message like this: But it isn't really nice, is it? So what do a lot of developers do? They create a validation (just) in order to show a nicer, better worded, error message like "This is not a valid department".  And what you then just did is writing code twice : Once in the database as a (foreign key) check constraint and once as a sql statement in your validation. And we all know : writing code twice is usually not a good idea - and executing the same query twice is not enhancing your performance! So how can we transform that ugly error message into something nice? By combining two APEX features: the Error Handling Function and the Text Messages! Start with copying the example of an Error Handling Function from the APEX documentation. Create this function ...