You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The scoring algorithm assign a CONTAINER_AREA_BONUS to figures based on their minH - the idea seems to be that bigger figures (usually pictures) are more important and so should go first. Am I right?
If this is the case why use minH and not the area (something like Math.sqrt(mapped_container.figureSize.minH * mapped_container.figureSize.minW)? Using only the height privileges vertical pictures.
Wouldn't be better to have a bonus based on the position of the figures in the article instead of the size? Presumably whoever is creating the content knows what is more imporant and could place it at the beginning of the article.
Thanks
The text was updated successfully, but these errors were encountered:
In my local builds I use the area, the square root is probably a better idea (same order of magnitude as one side).
I don't really see a real disadvantage to this change; depending on the content, it will change the "best grid" for someone, but that's a given.
I will clean it up and send a pull request.
The scoring algorithm assign a
CONTAINER_AREA_BONUS
to figures based on theirminH
- the idea seems to be that bigger figures (usually pictures) are more important and so should go first. Am I right?If this is the case why use
minH
and not the area (something likeMath.sqrt(mapped_container.figureSize.minH * mapped_container.figureSize.minW
)? Using only the height privileges vertical pictures.Wouldn't be better to have a bonus based on the position of the figures in the article instead of the size? Presumably whoever is creating the content knows what is more imporant and could place it at the beginning of the article.
Thanks
The text was updated successfully, but these errors were encountered: