Tuesday, April 9, 2013

Enkitec Navbar Plug-in for APEX in the Wild

I'm excited to announce the first plug-in released under the Enkitec brand: Enkitec Navbar! It's basically a wrapper plug-in for the Navbar and Dropdown pieces of the Twitter Bootstrap framework so most of the credit must go to the developers and contributors of that framework. The goal of this plug-in for APEX was to make it as easy as possible to add these components to your applications. The result is a fantastic looking, easy to use navigation bar that could be used as a replacement for tabs or elsewhere. Here's a preview:



If you're interested in learning more go to http://www.enkitec.com/products/plugins/navbar and click on help or demo on the right.

I hope you enjoy it! More plug-ins are under development! :)
Posted by at

8 comments:

  1. Jeff HolomanApril 9, 2013 at 7:18 PM

    Awesome, looks cool!

    ReplyDelete
  2. Guido LeducApril 10, 2013 at 1:40 AM

    Hi,

    Is it possible to add/set Authorization to the menu options/levels like you can do on a List Entry making menu options disabled or invisible depending on the logged on user/role for example ?

    Regards,
    Guido

    ReplyDelete
  3. StewApril 10, 2013 at 7:35 AM

    Looks very nice!

    ReplyDelete
  4. Dan McGhanApril 10, 2013 at 8:13 AM

    @Guido

    Yes, authorizations, conditions, and build options are supported with static lists. With dynamic lists the WHERE clause will need to handle that.

    Regards,
    Dan on

    ReplyDelete
  5. UnknownApril 11, 2013 at 8:18 AM

    Nice work!! Can you use an image for branding like a company logo? Keep up the great work!!

    ReplyDelete
  6. Dan McGhanApril 11, 2013 at 9:53 AM

    Hi Dave,

    Thanks!

    You know, I've not tried. In theory it should work but it would have to be a small image. Let me know if you have trouble with this...

    Regards,
    Dan

    ReplyDelete
  7. Scott WesleyApril 24, 2013 at 4:53 AM

    Very nice, and I'm learning a few things reading through the render PL/SQL.

    I found an issue with dynamic lists using page alias instead of page_id at this line (took me a while to isolate!)
    l_retval := l_page = apex_application.g_flow_step_id;
    Can you suggest a workaround beyond avoiding page aliases, or do you think this is another place in APEX where we'll always get resistance?

    Widespread support for page aliasing is one of my APEX bugbears...

    ReplyDelete
  8. Dan McGhanApril 24, 2013 at 9:39 AM

    Hi Scott,

    Goot catch. Unfortunately, I literally just released 1.1.0 and I was unaware of this issue at that time. This is an issue I can address in the future but there's no way to say when that would be.

    For now, I guess page aliases are not supported.

    Regards,
    Dan

    ReplyDelete

Subscribe to: Post Comments (Atom)