>> Drop your fears at the door; love is spoken here. Enjoy the free libre HawsEDC AutoCAD tools too. <<
Download POINTSIN.ZIP
Get help or contribute something
POINTSIN is a civil engineering and survey tool that reads point data (ID, North, East, Elevation, Description) from a file and inserts an attributed Land Desktop(Softdesk/DCA)-style POINT block and a 3d point in AutoCAD for every point in the file. It also has a command to create a single point.
You can change the POINT block if you prefer. The order and graphical arrangement of the attributes doesn't matter. The default POINT block attributes are one unit high. POINTSIN scales the POINT block to the dimension text height (dimscale * dimtxt), so the default POINT block will look as big as the current dimension text height.
You can delete or comment out the lines that insert a 3d point or the POINT block. You can also comment out the lines that create and set layers.
Download POINTSIN.LSP (save it to your computer) by following the link on this page. Also download POINT.DWG (save it to your computer) by following the link on this page or make your own POINT block. If you don't have a points data file to import, you may also want to download the sample POINTS.TXT file.
At minimum, all POINTSIN.LSP needs to work is the POINT block and points data file. Simply drag POINT.DWG from Windows Explorer into your drawing, then load and run POINTSIN.LSP by dragging it into your drawing, typing POINTSIN, and following the prompts to select the data file. That's all there is to it.
It is a very simple matter to change layer behavior. Please open POINTSIN.LSP in NOTEPAD.EXE for guidance.
It is a very simple matter to change whether POINTSIN.LSP inserts 3dpoints, point blocks, or both. Please open POINTSIN.LSP in NOTEPAD.EXE for guidance.
It is a very simple matter to add more file formats. If you need an unsupported file format and you aren't comfortable adding it yourself after reviewing the source code, please contact me.
POINTSIN.LSP neither creates additional files nor writes to the Windows registry.
: A direct link to the 2013 edition in the Awesome-CS-Books-Warehouse repository.
Objects defined by a unique identity that persists over time, rather than by their attributes. A User or an Order is an Entity because its identity remains the same even if its details change.
: Another Vaughn Vernon masterpiece, focusing on the core "strategic" patterns like Bounded Contexts before getting into tactical code. 2. Practical Implementation on GitHub
: The official code repository for the seminal book Implementing Domain-Driven Design by Vaughn Vernon. implementing domain-driven design pdf github
DDD remains critical for managing complexity in finance, healthcare, and logistics.
: The book follows a consistent, large-scale case study—a SaaS system for Scrum-based project management—providing continuity that helps readers see how individual patterns fit into a complete system. Code-First Mentality : While the "
, or domain-driven-design-sample to find implementations in your preferred language (Java, C#, TypeScript). : A direct link to the 2013 edition
Tactical patterns provide the "building blocks" for implementing the domain model within a bounded context: masoud-bahrami/domain-driven-design-roadmap - GitHub
If you are moving beyond "DDD-lite" (using only technical patterns like Repositories and Entities) and want to leverage the full strategic power of DDD to manage complex business logic, this book is arguably the most important technical resource in the field. Implementing Domain-Driven Design
Vaughn Vernon’s official GitHub repository ( vaughnvernon/IDDD_Samples ) contains the complete Java/C# source code from the book. This is the to use while reading the physical or e-book copy. : Another Vaughn Vernon masterpiece, focusing on the
Are you building a or moving toward microservices ?
Implementing DDD is a journey, not a switch. Here is a roadmap to applying it:
Strategic design ensures that technical teams build software that directly matches business goals.
// Order.ts (Aggregate Root) import Price from "./Price"; export class Order { private constructor( public readonly id: string, private items: OrderItem[], private status: "Pending" | "Paid" | "Shipped" ) {} public static create(orderId: string): Order return new Order(orderId, [], "Pending"); // Business Invariant: Cannot add items if already processed public addItem(productId: string, price: Price): void if (this.status !== "Pending") throw new Error("Cannot modify order after payment processing."); this.items.push(new OrderItem(productId, price)); // State mutation protected by business rules public markAsPaid(): void if (this.items.length === 0) throw new Error("Cannot pay for an empty order."); this.status = "Paid"; // Raise a Domain Event here if needed: OrderPaidEvent } Use code with caution. ⚠️ Common Pitfalls to Avoid
Creating explicit boundaries where specific models and language apply, preventing terminology conflicts in large systems.
To submit revisions, send an email with your revised code.
This program is free software under the terms of the GNU (GNU--acronym for Gnu's Not Unix--sounds like canoe) General Public License as published by the Free Software Foundation, version 2 of the License.
You can redistribute this software for any fee or no fee and/or modify it in any way, but it and ANY MODIFICATIONS OR DERIVATIONS continue to be governed by the license, which protects the perpetual availability of the software for free distribution and modification.
You CAN'T put this code into any proprietary package. Read the license.
If you improve this software, please make a revision submittal to the copyright owner at www.hawsedc.com.
This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License on the World Wide Web for more details.