https://github.com/Ciuntuc-BIM-Studio/lapin

Modelling - Storeys between two levels. A storey runs from a base level to a top level, above or below ±0.00. Its height is the difference between them. - New projects start with three storeys: Foundations (−1.50), Ground floor and First floor. The ground floor is active. - Strip footings at L corners. The outer layers are always mitred, and the cores join as the chosen style says. The Structure tab offers Mitre, Butt and Swap for footings and beams. Plans and views - Each plan shows only its own storey by default. In View → Storeys shown, or in the plan view's properties, you can choose to show selected storeys or all of them, optionally in halftone. Sheets print what the screen shows. - Reference level (underlay). Another level's plan can show faded under the current one. It can be snapped to, but it is never picked or printed. It is saved with the plan view. - View styles: - Architectural (all layers), Structural (cores only) and MEP, plus any style you make; - each style sets which layers are drawn, whether materials join and whether overhead elements are drawn; - a view takes its discipline's style, and any field can be overridden; - styles are edited in Manage → View styles. - Complete visual joins. Where one core runs through another element's corner, no boundary line is drawn. Joins can be turned off per material (Draw joints) or per view (Join materials). - Finishes by material category. Each material has a category, set in Manage → Materials, which tells the view styles which layers are finishes. - A drawing's settings in the properties panel. When a view or sheet is selected in the browser, the panel shows: - its discipline and style; - the view range and reference level; - Visibility/Graphics and the storeys shown. With nothing selected, the panel shows the view in front. - Disciplines. Each view or sheet has a discipline, set in its properties, and the browser files it under that discipline. Annotation

Hi everyone, Some of you used the first Lapin in the browser, and some of you noticed it went quiet for a while. That pause was on purpose. Lapin has been rewritten from the ground up. Today the first test builds are out for Windows, macOS and Linux, and a web version runs the very same engine right in your browser. Here is what changed, why, and how it works under the hood. Why I rewrote it The first Lapin was built on a fork of ifc-lite by accident. I've miss-understood the requirements for ifcsheets given by @Petru Conduraru , and distiled and exposed into the UI editing functions in ifc-lite. The project only needed documenting ifc models, so I split the project. I wasn't expecting the popularity jump that in got in only 3 days. It was a great place to start. It let me prove that a modelling tool on the IFC schema, with layered walls, joins, roofs and drawings, could feel fast and simple. But a fork is a borrowed house, and I had three reasons to build my own. 1. One engine, my engine. For a while I've been building BubbleBIM Pro, a C# engine with its own geometry kernel, session, undo and module system. Running Lapin on a different core meant maintaining two worlds and solving the same problems twice. I wanted Lapin's ideas, workflows and test cases re-linked onto the BubbleBIM Pro core, written in one language, with one architecture I understand end to end. 2. A modelling tool, not a coordination platform. ifc-lite is rich in tooling for BIM management and coordination: viewing, federating and checking models, and working with them across a project. That is valuable work, but it's not my field, and I'm honestly not the right person to carry it. Lapin has one job: authoring a model. Forking a large toolkit meant carrying a lot of code I didn't need, didn't fully understand, and couldn't maintain well. 3. Less friction with a community I respect. I admire the ifc-lite project and the people behind it. A fork that keeps diverging creates confusion: whose code is this, which licence applies where, and what should flow back upstream? I'd rather each project be clean and fully itself. Lapin and ifc-lite now meet where they should, at IFC files, with no tangled history in between.

Lapin is temporary unavailable on github, website and cloud. I will be back with it as soon as possible. I am rewriting the dependecy of it to the IFClite engine - and port it to my own BubbleBIM C# engine. Due some criticism from the IFClite comunity - I decided to make the project completly independent. I don't have the strenght in me to argue with anyone on this. Sorry for the incovenience. It will be back in a few days!