The development with the new page designer feels different.
Before you can say if it is good or not. You will have to make a whole APEX project and force yourself to only use the new "Page Designer" instead of the old "Component View".
So in this post I will show you where everything ended up when you compare the old dropped "Tree View" with the new "Page Designer".
First we take a look at the old "Tree View":
I like the newest blog post from Joel Kallman and especially his rule of thumb:
"My rule of thumb - when you're editing code in a text area/code editor in the Application Builder of APEX and you see the scroll bar, it's time to consider putting it into a PL/SQL package."
I would go further and say that even the smallest application you create should have at least one package for all the PL/SQL code you write.
This time I will show you the small changes which will appear in every migrated APEX application.
For the better understanding I show you an old and a new example (all tested with Mac and Firefox):
Date Picker - Icon:
The real title of this post should be "What I Really Meant to Say Was....".
Next days / weeks I will post from my experiences with the new APEX 5 EA. Today I will show a common mistake in current APEX applications. Because APEX 4 has not the newest versions of jQuery or jQuery UI included. Even so the development continued and some developers just added newer version of jQuery (UI) into their page templates or headers. Unfortunately APEX 5 is not so happy about it. :)
Example of wrong page template implementations:
Last week, I participated in my first Little League draft for my son's baseball team. This was new territory, as up until now, play has been non-competitive. This year we will actually have to keep score, and there will be winners and losers.
If you are working with interactive reports you will for sure be faced with a problem of wide reports. If you are taking care of the page layout and eventually have more than just an interactive report on the page, you will want to limit it's size to something making sense.
In einem meiner Projekte habe ich etwas intensiver auf Tabular Forms gesetzt.
In gewissen Konstellationen habe ich immer wieder folgende Meldung nach einem Validierungsfehler erhalten:
Aktuelle Daten für tabulare Forms sind zu alt; die Quelldaten wurden geändert.
Klicken Sie hier, um Ihre Änderungen zu verwerfen und die Daten aus der Datenbank neu zu laden.
Eventuell auch in Englisch:
Current tabular form data is too old; the source data has been modified.
Click here to discard your changes and reload the data from the database.