LostGrid, the new Darcy Release

LostGrid releases new version called Darcy

July 1, 2016

LostGrid, the Darcy Release

Tonight I released the latest version of the open source project, LostGrid I maintain. The main focus of this release was to fix some bugs that caused some breaking changes, start a new version naming strategy, add a feature for lost-row and to also ensure that there was movement on the project.

#306 [FEATURE] lost-row: none; was added to reset the element back to default settings.

#297 [BUGFIX] Updates the clear: left; to be clear: both; for lost-column/waffle rule.

#299 [BUGFIX] Changes the size from 99.99/999999% to 99.9% within lost-column, lost-masonry-column, lost-move, lost-offset, lost-row and lost-waffle. This is because in Edge and IE there were some rounding errors causing stacking of columns instead of allowing them to sit side-by-side.

#251 [REFACTOR] Minor refactor to add in cloneAllBefore function to make readability easier.

In order to add the clearing in a more standard way by using “both” it required that the preferred method of clear: both; be the default. A global setting was added to set this back to left if your project needs it. @lost clearing left; will keep you going if your project is affected by this change.

Thanks to Jon LostGrid now has a math based approach to the 99% rounding. This might cause issues in your project but after testing in a number of different browsers it appears to be a non-issue. It’s recommended that you just peruse your project with the oldest version of IE that you support to ensure there isn’t an edge case that you’re caught in.

What’s with Darcy? Why not just Version 7?

Great question! To answer it we need to understand the importance of semver. In order to progress LostGrid there are going to have to be breaking changes. The nature of how LostGrid was initially written means that as it matures there is going to be a phase of breaking changes. So V8 and V9 will be coming because I just don’t have time to bunch all those breaking changes into one version without holding back needed features and bug fixes.

So, Darcy release will be here for a while. Darcy will probably be around for several major version numbers. When a new set of features come out and it starts to not feel like the Darcy release anymore then it’ll change. But it’s just for marketing. As the plugin progresses we’ll be able to talk about it using these terms.