Fork me on GitHub

I'm looking to start a new project that hopefully eventually makes it to production. I'm pretty familiar with the basics of Fulcro, but definitely not all of it, and I haven't tried RAD at all. Is there some guideline for which parts of Fulcro one should be familiar with prior to starting with RAD? I see this mention in the fulcro-template: > Fulcro also has a Rapid Application Development add-on that makes building a production application faster and easier; however, a beginner should not start with RAD except to satisfy surface-level curiosity. RAD requires that you understand the core library

Jakub Holý (HolyJak)18:10:55

My first prod Fulcro app (not counting a small PoC) used RAD. You need to understand the basics covered in the minim. f. tutorial. Other than that, knowing about forms and a little about UISM will be useful, I think. Also you will likely want to user routing.

Jakub Holý (HolyJak)18:10:01

If you understand how RAD reports and forms work and that they are basically nothing more than defsc + a custom uism then you are good to go. Look at fulcro-rad-demo. Do you feel comfortable building on that?


I have studied uism and have implemented a bit of it, but eventually decided I didn't quite need it yet for my form state handling. I'll have to take a closer look into what's in the RAD demo and maybe give it a spin before deciding whether to go with RAD or vanilla Fulcro. I usually try to limit my use of abstractions until I'm very familiar with the basics, but it sounds like I might know enough to be able to leverage RAD to get stuff done more quickly.

Jakub Holý (HolyJak)18:10:46

It sounds to me like you do. Being you, I would not hesitate reaching out for RAD. But yes, play with it. Good luck! (And keep us posted :))

Jakub Holý (HolyJak)18:10:13

BTW I am going to help Tony improve the RAD docs so please make notes of what is confusing/missing/... 🙏


You definitely need to know the core basics, but it would be a mistake to overlook the time savings that RAD will bring you if you're really spinning up something to use in the long-run...but yeah, the docs need love


Thanks. I'll start familiarizing myself with RAD this week and will note anything I find unclear.


So, RAD needs refinement...but the core structure is really helpful IMO, as are the autogenerated things. Even if you don't find the autogenerated code/UI helpful, having your model in attribute form, and seeing the patterns and automation this enables is a huge win.

💯 1
👍 1

Ah, nice to see that RAD has a mechanism for avoiding the issue I had here with the way vars are mapped to keyword: > which helps you ensure that you’re using a key that has not been mis-typed, and also gives you docstring access in your IDE.