Dev Diary Ep39 - Introducing Portals for Custom Components

Elements Dev Diary
1

Hey there,

We’re working hard on all your feedback and today we’re pleased to announce, Portals for Custom Components (and no this is not just another random feature). This feature came about because of our need to move elements in the DOM to fix the layering issues you’ve all been experiencing when using menus, modals, and galleries :scream:

Portals will allow us to fix all the layering issues — you can look forward to those new components in the next few betas :crossed_fingers:

This weeks dev diary video is really aimed at those of you that are interested in building custom components, if you’re all about the WYSIWYG, then next weeks dev diary will be for you :wink:

These changes will be available in beta 13, due later today/tomorrow.

Get The Beta

You can sign-up here to be notified when the Elements beta is publicly available.

Thanks

We’re listening to all your feedback and working super-hard to make Elements the perfect website builder :smiling_face:

If you have any thoughts about today’s Dev Dairy please post them below, we really appreciate the feedback.

See you next week :wave:

Thanks,

Dan & Team Realmac.

4 Likes
2

Thanks @Dan - as you say ‘Good stuff’ - is the ‘pageStart’ before the doctype? Keep going.

1 Like
3

Yup, we added it just for you PHP lovers!

2 Likes
4

Dear Dan,
I use Rapidweaver since 2007.
In that year I have build with an inestimable help or your programme the site of AgribusinessWatch, Observatorio do Agronegócio in portuguese (observatoriodoagronegocio.com.br and agribusinesswatch.com). Go there and have a look.
But in 2011, due to others activities, I was obliged to stop it.
At that time I used Rapidweaver 3 or 4.
Now I am afraid to restart its maintenance considering the difference of programme versions.
How to manage this problem?
Thanks for your attention and your time.
Maurício Galinkin
phone number redacted
Brasília, DF.
Brazil

5

Hi @MotlBrazil,

I’d recommend using RapidWeaver Classic for now, and take a look at Elements once it launches as a public beta later this year.

If you need any help with opening your projects, or re-doing them in RW Classic, just start a new thread here on the forum and we’ll do our best to help.

6

I presume the JS/resource libraries for which we are creating IDs are something RM can publish as a list for developers to access, similar to what is shown in the demo. Otherwise, I can see twenty different third-party developers creating their own IDs, which could still result in 20 versions of React.js, for example. Am I missing something?

1 Like
7

BTW: It should be becoming rather obvious to everyone how special this is becoming. The attention to details and efficiencies is outstanding.

1 Like
8

Yup, we’re aware of this and it’s on our list!

1 Like
9

Great stuff (as always) Dan! One thing that I’m curious about is how non-CDN based resources are handled in custom components? With HTTP/2 ‘multiplexing’, the need for sharded domains (to increase the max number of connections) is no longer necessary, and with privacy and performance concerns, more folks are choosing to self-host many of these resources.

Is there the ability for a component to specify the addition of resources in a similar manner to portals in a project? For instance, if I create a number of components using the id com.bryanrieger.* would I be able to ensure that the required resources were only added to the project once (or as required)?

1 Like
10

Yes, for sure!

1 Like
11

Was this week’s beta released yet??

12

Not yet, we wanted to get a couple more fixes in, should be out later today (Thursday).

1 Like