Hello weweb community,
I have an issue regarding the usage of Weweb classes.
Problem 1:
Weweb seems to generate HTML styles for every element off the bat. I can’t seem to find a way to circumvent this.
This bloats the HTML code IMO unnecessarily with repeated and / or unused styles, which reduces the performance of the app.
Problem 2:
Through the usage of Weweb classes, the only thing that I seem to be achieving is that I can implement the styling easier. I cannot find any CSS code that is generated and any class that is applied to the element
I was hoping that this will solve the issue, but this doesn’t seem to be the case.
What I want is to reduce the usage of duplicated HTML styles and start using CSS styles.
Am I missing something? Is there any solution to this?
Hi @borisdonchev 
Yes, that’s the state of the classes in WeWeb at the moment. But this will be improved in the future !
Other than performance, how is your experience using classes in WeWeb?
Hi @jptrinh
Thank you for the info! Do you have a planned release date for this feature? Or something rough? This bloats our HTML quite a bit and is a source of some headaches for us.
And also - is there a way to reduce the amount of generated styles for an element?
As for the Weweb classes - we are not using them. Using the GUI to style elements is fairly simple and the added benefit of the weweb classes is not big enough for us.
In the coming months or so!
The only thing I can think of, is not defining unnecessary properties. For instance, make sure to reset the properties (you can identify that a value is set when the property name has a grey highlight) instead of setting it manually to the default value.
Hey! Has there been any development regarding this?