Polishing the MonologFX API

Guest Author

Earlier this week, I released "into the wild" a new JavaFX 2.x dialog library, MonologFX, that incorporated some elements of DialogFX and new features I'd been working on over time. While I did try to get the API to a point of reasonable completion (nothing is ever truly "finished", of course!), there was one bit of functionality that I'd included without providing any real "polish": that of the button icons.

Good friend and fellow JFXtras teammate José Pereda Llamas suggested I fix that oversight and provide an update (thanks much, José!), thus this post. If you'd like to take a peek at the new streamlined syntax, I've updated the earlier post; please click here if you'd like to review it. If you want to give MonologFX a try, just point your browser to GitHub to download the updated code and/or .jar.

All the best,

Join the discussion

Comments ( 2 )
  • guest Tuesday, November 19, 2013

    I have been using the JFXtras library since 2.2Snapshot something early. Been using it for about a year, and I'd like to get the new MonologFX functionality. What refactoring is necessary to replace the DialogFX functionality with MonologFX?

  • Mark Heckler Tuesday, November 19, 2013

    Hi Kevin,

    Very little, actually. I'm guessing that taking a quick look at the examples I posted in previous articles here for MonologFX would give you everything you need to swap out the two in a few minutes. I improved (or would like to think I did!) the functionality and i18n, plus added a few extras along the way...but my primary goal was a dead-simple dialog capability. Who wants to spend a lot of time doing dialogs in the middle of their "real" app? :-D

    The big change externally from DialogFX was probably the return values...but again, I think those are actually simpler in the end.

    Please let me know what you think, and if you do hit any walls, ping me!

    All the best,


Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.