Welcome to swing-modal-dialog Discussions!

[DJ-Raven]

👋 Welcome!

We’re using Discussions as a place to connect with other members of our community. We hope that you:

• Ask questions you’re wondering about.
• Share ideas.
• Engage with other community members.
• Welcome others and are open-minded. Remember that this is a community we
  build together 💪.

To get started, comment below with an introduction of yourself and tell us about what you do with this community.

[Janix520]

Your framework looks great, and when combined with my packaging tool, it provides a great desktop experience, https://github.com/Janix520/EasyPackage

[DJ-Raven]

@Janix520 Thank for that tool. but my project just demo application it's not complete app. so I thing we no need to package it.

[SilverD3]

Hi @DJ-Raven . Please how to customize the Drawer? Like refreshing, changing look and feel?

[DJ-Raven]

Hi @SilverD3 I'm don't understand the question.

Like refreshing

You want to change the menu item or set new header name value ... ?

changing look and feel?

This mean you want to change the menu background, foreground or font ... ?

I'm recommend to open another discussions.

[harshaindunil]

I'm using your UI framework in my app, and it's fantastic

[DJ-Raven]

@harshaindunil Thank for using :)

[suntana]

Hi DJ-Raven,
if select menu in Drawer menu, the form not reload form as New Form
the problem is: when i set Input Form and Data Form in Drawer, Data Form not Refresh when opened;
hopely my question clear...

[DJ-Raven]

Data Form not Refresh when opened

Yes, the method formRefresh() not execute when the form open or init. it's work only click button refresh at the header menu.

So to load your data you can call from method formInit().
here example to create form:

import raven.modal.demo.system.Form;
import raven.modal.demo.utils.SystemForm;

@SystemForm(name = "Form Input", description = "input form not yet update")
public class FormInput extends Form {

    public FormInput() {
        init();
    }

    private void init() {
        // init some component
    }

    @Override
    public void formInit() {
        System.out.println("do form init");
    }

    @Override
    public void formOpen() {
        System.out.println("do form open");
    }

    @Override
    public void formRefresh() {
        System.out.println("do form refresh");
    }
}

[suntana]

nice....
it's work..
thank you...

[suntana]

hai raven,

i'm not clear in part validation menu for 3 user with different access...

[DJ-Raven]

We has talk in this discussions #34 and this for example code test-validation

[SeifEdI]

Hello, When comparing the source code of the modal-dialog repository and the demo repository, I noticed that the demo application contains significantly more code and effort, even though it already relies on the modal-dialog library. I understand that modal-dialog is a utility module, but I would like to better understand the practical benefit of having so much additional code in demo, when some parts seem like they could be simplified or shared. Furthermore, I question the architectural choices: why not use a more structured and "cleaner code" approach, for example, by following an MVC architecture or a more modular design? I would be grateful if you could clarify these points or explain the reasons behind these choices. Thank you in advance for your feedback.

[DJ-Raven]

@SeifEdI The demo project is not only for showing the modal-dialog library. It also includes many other example components that can be used with FlatLaf. My goal was to create a small dashboard that shows how different components can work together and how they might look in a real project.

The modal-dialog library itself stays simple and independent, while the demo provides a richer, more practical showcase.