How could ADF Faces RC be made simpler/easier?
Chris Muir
vpGmZj) on how could ADF BC be made simpler/easier, and it generated
considerable debate. While we can't guarantee Oracle was listening
and will make any substantial change, the exercise should be valuable
to both beginners and experienced members in that it will hopefully
show the pain points in learning & using ADF BC, which can assist in
reading more about the tricky areas or writing more blogs/papers/
presentations to help others.
Today I'd like to pose the same question for ADF Faces RC.
For those who didn't read the original thread, the goal here is not to
identify new features (though it may happen as a result) but rather
discuss how ADF Faces RC could be made easier to use and learn. The
question has a subtle nuance, but as we've done the new features
question several times before I really wanted to take the conversation
in a new direction.
Please note this post will at this stage not consider the ADF
Controller, I'll post a separate thread on that later. As a result
ideas on task flows, the JSF/ADF Lifecycle and other controller
concepts aren't appropriate for this post. Please save them for
later, we're considering ADF Faces RC here.
So in taking this post forward, I'll post one of my minor ADF Faces RC
bugbears. Some components like the af:showDetailItem have "double-
negative" properties such as "disclosed". Simply put the property
should have been "open". It makes it much easier when you write EL
Boolean expressions for this property if you don't have to translate
the double-negative in your head & I bet none-native English speakers
would appreciate this too.
That's my idea (small) idea to get the ball rolling. What's yours?
CM.
Luc Bors
Two points that come to mind immediate (to start with);
1) I really think layout components (stretchable / not stretchable) should be made easier to understand/use. I know Oracle is working on that.
2) (Model based) List of values should have a property to set the width of the popup. Now this cannot be defined.
regards Luc
Jernej Kaše
BC, but it could be fixed in the View)
2. Shuttles require some coding to use, should use the same drag-and-drop
principle as everything else
3. Table. Need I say more? It's slow, it doesn't scale well and
_it_has_no_paging_ (how many times has this issue been raised?)
4. More layout control in PanelFormLayout
5. Bind images to blobs directly
6. Bind RichTextEditor to blob directly (some time ago it didn't work out of
the box IIRC, but I could be wrong)
7. Out of the box customizable panelDashboard, a light version of
pageCustomizable
8. It should include some kind of reporting
Not so much "simpler/easier" category, but still related
9. Not W3C HTML compliant (some end customers actually require that)
10. Does not use current trends (like jquery), but comes with its own
JavaScript API; developers can't laverage ther existing knowledge but have
to learn a new platform
11. My personal favorite - improve performance
Jernej
CM.
--
You received this message because you are subscribed to the ADF Enterprise
Methodology Group (http://groups.google.com/group/adf-methodology). To
unsubscribe send email to adf-methodolo...@googlegroups.com
All content to the ADF EMG lies under the Creative Commons Attribution 3.0
Unported License (http://creativecommons.org/licenses/by/3.0/). Any content
sourced must be attributed back to the ADF EMG with a link to the Google
Group (http://groups.google.com/group/adf-methodology).