Giter VIP home page Giter VIP logo

gridfinity-unofficial.github.io's People

Contributors

bigdumb42 avatar bissonex avatar ffux avatar jack-toast avatar jeansidharta avatar maximiliangaedig avatar mrbrain295 avatar mrcbax avatar togos avatar twitchyliquid64 avatar willtree8 avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar

gridfinity-unofficial.github.io's Issues

LICENSE?

I'm thinking of creating a less static site for all the gridfinity pieces, I'd like to use your data.json as a starting point for the database, but I don't want to use it without permission.

Grid Finisty Reference: Define Upper Rim Minimum dimensions

HI All,

While working on a set of light weight designs for the small part boxes, i noted how adhoc the approach to the top rim has been in all models and documentation. This wasn't helped by Zacks original design having a fillet added to it which means the bins are all N*7 + 3.5461906128mm high.

I propose we define the minimum rim that ensures stacking interoperability while reducing the complexity of the design and ensuring the theoretical height is an actual whole mm.

Simplified Rim Change:

The secondary 0.8 mm rim has been removed as was offering limited benefits.
The 0.6 mm fillet on the top surface has been removed. In practical printing this feature is barely discernible however makes definings the
The total height added by the rim is changed from 3.5461906128mm to 4mm.

Dimensions Proposed
image
New profile versus old profile:
image

CAD model with implementation
https://www.printables.com/model/353224-gridfinity-lite-ultra-blocks-template

Suggestion: Wiki/Markdown-based system for less technical people to contribute.

I'm an engineer but more of a backend guy. I'm not great with frontend stuff. This thought came from a chat in VoidStar's #gridfinity chat room.

It started out as an idea to just add a 'beginners guide/things I wish I knew before I started' and evolved into, it would be nice if less technical people could add pages.

The two ways I see this are:

  1. A 3rd party wiki that you can embed.
  2. Do the horrible terrible thing I did for my site below.
  3. Something I'm not thinking of because I'm not a web guy.

The horrible terrible thing I did on my website was a JavaScript system that loaded markdown files and, using a 3rd party library, formats the file appropriately. Example: https://www.zolan.org/dindex.html Loads https://www.zolan.org/index.md and applies the proper html/style. (Note: I also made a extra horrible terrible php implementation because search engines won't index sites that are pure javascript.)

Anyway, I am almost certainly that there is a better way to do this but the end goal.

Again, the whole impetus for this was to have a 'beginners page' but it ballooned into 'how can we make it easier for non-web people to contribute'.

Thank you for your consideration. If you think this is a terrible idea, feel free to decline/murder/destroy this request.

Moving away from Github Pages

Github Pages is a great free resource, but ultimately it's pretty limited in what it can do. I see you've already created a placeholder repo for an eventual migration away from GH Pages so it appears to be on your roadmap anyway!

I'm a fan of the Gridfinity project and appreciate what you've done with this site, so I'd like to give back! I'd like to propose a few things and hear your thoughts:

  • I'd like to fork the Gridfinity placeholder repo and start creating a fully-fledged website. I'd prefer to use Rails just for dev speed, but I have a lot of experience with JS/TS, Elixir, and Rust as well
  • If my fork is accepted, I'd like to pay for some level of hosting for 6-12 months

Please let me know what you think! I'm not much of a design guy, but I have a lot of experience in server-side in general/client-side JS.

Incorrect bottom offsets

image
The bottom offsets need to be half of the current values. So 0.8>0.4 and 2.4>1.2. Otherwise the total width at the top is much larger than the 41.5mm spec.

Standard for Magnet Polarity

Greetings,

I am just getting into gridfinity, and have noticed that there is no published standard on magnet polarity orientation. The thought of people building incompatible thingamabob organizers keeps me up at night. Any possibility to add in some recommendations for that?

Magnet and M3 hole diameter suggestion

I've increased the 6.5mm dimension to 6.8mm in my designs, because that allows me to use either 6mm or 1/4" diameter magnets with better clearance. I've found this helpful when sourcing in the (admittedly peculiar) US when I don't want to wait weeks or months for a shipment from China. Also useful for using steel strike plates to avoid polarity issues, which I've found in 1/4" much easier than 6mm.

Relatedly, I've increased the M3 hole from 3mm to 3.45mm in my design to give better clearance on M3 bolts and screws. It's a pet peeve of mine to have a through hole that gets in the way of the bolt and ultimately needs to be cleared out a bit or forced.

Minor points, and just food for thought. I know this is slightly out of Zach's original proposed spec.

Gridfinity Design Reference

There is not enough information to duplicate the baseplate, based on the Design Reference Drawing. Also I suspect the 0.8mm Diameter is supposed to be 8mm.

height in design reference does not match other user models

The Design Reference here lists 0U=14mm, 1U=21mm, and the lip adds 3mm. This does not match other 3rd-party models, such as https://github.com/kennetek/gridfinity-rebuilt-openscad. There are pros and cons to both approaches. The downside of the gridfinity.xyz approach is that stacking a 0U on top of a 0U is the height of 2U, or 1U+1U=4U. There could also be a use case of a 7mm-high riser, which would be -1U with the xyz spec.

I think it makes more sense to define 2U=14mm, and everything is in increments of 7mm.

Regardless of which spec "wins" - we definitely have an inconsistency with the xyz spec and popular parametric models in use, and that means we could all be printing bins that are incompatible with each other. Sure, the height is not as important, but if you want to stack across bins then NU should always be a consistent height.

I was going to edit the design reference and submit a PR, but I do not see the SVG source in the repo. Is there an editable source available?

Magnet orientation

Would it be possible to define magnet polarization in the specification?

Suggestions

  1. For the catalogue, include a Z.
  2. If you want to be real fancy, the Z is displayed in fractional 6ths, IE, 3/6 for a half height box. 6ths seems to be how Zack has differentiated his own bins.
  3. A column for category, or tags for items. For example, baseplates, vertical baseplates, bins, containers, general tool holders, purpose shaped tool holders (ie fits a specific brand of caliper), mobile storage, novelty (ie hands holding SD card, dungeon tiles), tops (ie lids, between plates, risers)

I'm learning more about web stuff atm, so maybe down the line I can help out. Just my current thoughts.

[Design Reference] Add holes to profile views

I think there is something missing in the design referenze.

You do not know how deep the magnet and screw holes should be.

May be the profile views should be cut sections instead of front views in general?!

image

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.