I normally don’t include Youtube videos on my blog. However the below presentation by Mike Hichwa about the Vision, past, present and future of APEX is so imporant, that I just had to include it.
It was recorded at APEX Connect 2016 in Berlin, a great event. If you have the chance to visit APEX Connect, go for it. Lots of APEX experts and a great opportunity to meet up with the good folks that make the APEX community.
In today’s blog post I’ll explain what OData is about and go into details on my reasoning why Oracle in general and APEX in particular should support the OData standard.
NOTE: This is a blog post I prepared before I went to APEX Connect 2016 in Berlin. But I didn’t manage to verify and post in time. I’ve now slightly edited and added some details I learned about while being at APEX Connect.
OData is a new standardized protocol based on REST. It’s platform independent and uses HTTP, REST, JSON, XML. It basically allows you to do all operations you’d normally do in SQL in a transparent way.
So, if you want the short version why I think Oracle should support OData: Because Microsoft and SAP do and because it’s an open standard here to stay.
Microsoft Office 365, Sharepoint, SQL Server, IBM DB2, SAP Netweaver and SAP HANA are a few of the products that either support OData natively or via a plugin.
Imagine defining an APEX Interactive Grid against a SAP HANA table without having to write any PL/SQL code or needing to write separate web-services for each of the operations / tables you work with.
Today, I’d like to talk about the “Model, View, Controller”-Design pattern and how all this is reflected in APEX Page Designer.
This is the first part of a series of blog posts where I’ll share my knowledge on Page Designer internals I gained while working on the Xplug browser add-on.
Perhaps some good advice first: don’t take anything for granted and always double-check yourself.
That being said, I’m a speaker at APEX Connect 2016 and the MVC-topic is part of a presentation I’m currently preparing for the Web Technologies track. It’s called “Lernen vom Page Designer – Auf den Spuren von Jules Vernes” .
Please bare with me. It’s going to be a rather long and somewhat theoretical blog post. I’ll do my very best to keep it interesting.
The release of Xplug v1.2 was quite a success. The possibility to add a “dark” style and customize it via a configuration dialog seems to be something many APEX developers appreciate.
But what if you just want to do a small modification like changing the background color of the properties group header? Until now that was hard -if not -impossible- to do, because the CSS that is injected by Xplug is focussing on a dark style.
One of the things I wanted to do for the Xplug browser plugin, is to check if I can somehow change the Page Designer colors and come up with a custom look-and-feel (style) and
perhaps add some more contrast along the way. In particular I was excited to do a “darker” style. Something you would use at night while you are working on your next fantastic APEX application.
Note that I’m not calling it a theme, because then it could be confused with an APEX theme which definitely is not the case here.
I do am planning on adding a configuration dialog, so you can change colors yourself. Would be cool if these could then be exported as JSON and put online in a gallery.
Anyway, what I find kinda cool is that there’s a button that let you switch between “daylight” and “moonlight” mode.
The daylight/moonlight feature will definitely be part of the next Xplug release (along with some other goodies).
Before that happens I have to refactor the code and work on the “moonlight” mode some more. Adjust colors work on the tabs style, etc.
If you want to take a peek. Here’s a quick Youtube video I did that shows some of the features. Have to apologize for the bad quality. Will need to find a good screen recorder.