Welcome, Guest |
You have to register before you can post on our site.
|
Online Users |
There are currently 241 online users. » 0 Member(s) | 238 Guest(s) Bing, Google, Yandex
|
Latest Threads |
Parts request
Forum: Part Requests
Last Post: Peter Grass
1 hour ago
» Replies: 1
» Views: 116
|
Batman Cowls
Forum: Part Requests
Last Post: Peter Grass
9 hours ago
» Replies: 1
» Views: 173
|
A fresh list of "most com...
Forum: Part Requests
Last Post: tom alphin
10 hours ago
» Replies: 7
» Views: 642
|
Transparent sticker colou...
Forum: General LDraw.org Discussion
Last Post: N. W. Perry
Yesterday, 19:12
» Replies: 1
» Views: 277
|
Fix for slightly incorrec...
Forum: Part Requests
Last Post: Huib Versteeg
Yesterday, 9:50
» Replies: 4
» Views: 829
|
Lego Town Racer 1996 - 63...
Forum: Official Models
Last Post: Chris Böhnke
2025-09-13, 23:39
» Replies: 14
» Views: 2,046
|
Eyesight on Linux
Forum: Rendering Techniques
Last Post: Orion Pobursky
2025-09-13, 18:56
» Replies: 12
» Views: 8,712
|
Another common varient: 1...
Forum: Part Requests
Last Post: Rene Rechthaler
2025-09-12, 14:51
» Replies: 8
» Views: 5,584
|
1Lx1Lx2L brick with studs...
Forum: Parts Authoring
Last Post: SNIPE
2025-09-12, 10:14
» Replies: 0
» Views: 754
|
LDraw Colors for OpenScad
Forum: LDraw Editors and Viewers
Last Post: Hageta
2025-09-12, 10:03
» Replies: 0
» Views: 682
|
|
|
Slope textures |
Posted by: Orion Pobursky - 2011-11-21, 12:59 - Forum: Parts Authoring
- Replies (13)
|
 |
Whilst building the Super Star Destroyer, a thought occurred to me: we have no way of specifying what faces of a brick (if any) required the slope texture. I see 2 solutions: - Use the existing !COLOUR specification to set a new main color for linetypes that need a slope texture. The disadvantage to this being that it would break MLCad. Yet another reason why Micheal should open source the program.
- Make a new meta, something like !SLOPE_TEXTURE, that would go before the linetypes that need slope texture.
|
|
|
Question to the Linux users |
Posted by: Roland Melkert - 2011-11-19, 19:50 - Forum: LDraw Editors and Viewers
- Replies (9)
|
 |
Anyone here a seasoned Linux desktop user (with some programming experience)?
With LDCad 1.0 beta out, I'm playing around with getting a Linux version going. But having only experience with Linux server systems I'm a bit lost with all the desktop options out there.
I'm currently downloading Ubuntu wubi (I use Ubuntu server for work so this is at least some what familiar) to get a look, but maybe people think I should use something other for the base development environment.
The goal is to get a (set of) pre compiled binaries to add to the LDCad download site covering most used desktop stuff. I'm figuring when it compiles in Ubuntu 11, it would also go in most other recent distro's.
I'm just hoping to avoid pitfalls by using any info people can give me.
ps: this might be more of a 'dev' thing, but there is no section for that (yet).
|
|
|
Any interest in Java API? |
Posted by: Greg Teft - 2011-11-19, 1:22 - Forum: All Other Programs.
- Replies (4)
|
 |
Hello all after a long absence. I started a new job last summer, and it has taken up a lot of my time.
I am revisiting a pet project of mine - a Java API to parse and represent LDraw files.
This was started a few years ago when I wanted to create .dat files from AutoCAD .dxf files.
I had a working prototype that got lost in between computers, and am starting to recreate it.
Well, I'm starting over, and was wondering if any one is interested in the effort. If there are any programmers out there that want to see the preliminaries, I can start a project out on SourceForge. The source itself will be initially be in my name, and I need to make sure that anything I put out there conforms to the licensing agreements for the Java3D and the Apache commons APIs. I do plan for the effort to be able to be used for creating Java applications in accordance with the Creative Commons Attribution Licence.
The intent is to:
- Fully represent the part file specification including the standard meta comments.
- Support the Java3D and the commons-math APIs for representing vector and matrix data.
- Actually give me some time doing development work in an area that also interests me.
Once I'm at a point that this is complete, tested, and documented. I'll be going back to that DXF parser and DXF-DAT app I started.
Why Java? I like and respect what Java has become. I know bytecode can be slower than optimized compiled code, but it's not that bad, and my experience is that sloppy programming is what makes a Java (or any) application perform badly.
Why bother? Why not. I'm a programmer and I enjoy programming and even if it never gets accepted or used, I'm enjoying the journey.
|
|
|
Connection Standard |
Posted by: Orion Pobursky - 2011-11-18, 15:06 - Forum: Parts Authoring
- Replies (3)
|
 |
I'd like to request that the LSC take up the topic of a connection standard. Also, since Sergio was first to the develop something like this, I think his way to doing things should probably be what is standardized.
|
|
|
LPub 4 for Mac |
Posted by: Chris Eyerly - 2011-11-17, 23:10 - Forum: LDraw File Processing and Conversion
- Replies (7)
|
 |
I have a couple questions.
1. Where is the best place to notify Lpub developers of bugs? Should we just email Kevin directly?
2. The Edit -> Add Text menu option is always greyed out for me (On an "inserted coverpage" where I have already added a picture it does not allow me to add text). What is LPUB command to add it manually?
I think that is for now
Thanks!
Chris Eyerly
|
|
|
Spaces in filenames |
Posted by: Travis Cobbs - 2011-11-15, 17:29 - Forum: Standards Board
- Replies (17)
|
 |
Michael Heidemann pointed out that the newly created OMR spec requires that filenames contain spaces, while the pre-existing LDraw 1.0.0 spec strongly discourages spaces or tabs in filenames. He (quite rightly, in my opinion) felt that this was inconsistent.
So, the way I see it, we have three choices:
- Ignore the problem.
- Remove the discouragement text from the LDraw standard.
- Change the OMR standard so that the filenames don't include spaces.
My vote is to do go with option 2, at least for spaces. I think tabs should still be discouraged, since they just seem like a bad idea in filenames (assuming they're even valid on all OSes). Please note that the official parts restriction document already disallows spaces in the filenames of files in the library, so this won't affect the parts library. (More specifically, it lists the only allowed characters, and spaces, tab, etc. are not listed.)
|
|
|
|