This is close to what I mean by separating the tint color from the
material type, the difference is that I don't want to restrict the
combinations to materials that exist, so I would allow a green tire
for example. The material thing is more of POV feature than LeoCAD, I
don't mind having the same shade of black for tires and bricks in
LeoCAD but I want POV to treat them differently.
For this to work you'd need to have the tagging be part of the
LDraw standard or pieces wouldn't get tagged/updated. There's also
the issue of pieces with multiple materials, like a 2x2 slope, so you
need a way to switch materials in the middle of a piece too. I think
something like a 0 MATERIAL RUBBER statement in the middle of a piece
is all I really need.
If we were to get really really fancy we'd have shiny rubber for
town tires, half shiny rubber for tubes, another type for technic
rubber bands, rough rubber for the old big technic tires, etc... but
that's pushing it too far.
On Mar 14, 2007, at 4:19 PM, [EMAIL PROTECTED] wrote:
> My thought was that we/you "tag" rubber pieces (as the best example
> here) such as
> tires/tyres and bands/wedge-belts in memory. Then, when the user is
> setting the color, we switch the palette to show all the colors
> from ldconfig.ldr that
> have the "RUBBER" attribute set (for example, red, blue, grey,
> white, yellow).
>
> The display would show "Red", "Blue", "Grey", "White", "Yellow",
> and the user
> would get those choices with the mouse.
>
> Internally, we set the color to Rubber_Red, Rubber_Blue,
> Rubber_Grey, etc.,
> and use the RGB values from those entries in the list.
>
> The user just picks a color, but the "right" rubberized color gets
> chosen from the
> LDRAW palette. Exporting to POVRay would keep Black and Rubber_Black
> in the right places.
>
> If one got REALLY fancy, then rubber bands would get all the above
> choices,
> whereas most tires would only get Black (Rubber_Black), and certain
> tires might
> get Black (Rubber_Black) and White (Rubber_Dull_White) as choices.
>
> -- joshua
>
> ----- Original Message ----
> From: Leonardo Zide <[EMAIL PROTECTED]>
> To: Joshua Delahunty <[EMAIL PROTECTED]>
> Cc: leocad <[EMAIL PROTECTED]>
> Sent: Wednesday, March 14, 2007 3:58:01 PM
> Subject: Re: Any newer version?
>
>
> That helps the pieces but that doesn't help the users, I don't
> want the users seeing black and rubber black, they should only see
> black. If a piece is made of rubber then it would be drawn using
> rubber black, if it's a brick then it would be plastic black but the
> material type shouldn't be an option to the users, it should be set
> by the pieces.
>
> I think reading color codes from an external file is a good idea,
> I just don't think ldconfig.ldr is a good file because LDraw doesn't
> make a distinction between pieces and models. I don't know how easy
> it would be to propose to the LDraw org a distinction between tint
> values and materials.
>
> Maybe it's possible to scan the file and figure out what the
> material variations are and not show them to the user? Maybe my view
> is just completely wrong. :)
>
>
>
> On Mar 13, 2007, at 6:39 PM, Joshua Delahunty wrote:
>
> >
> > ldconfig.ldr has the following (well, the one that I adjusted to
> > use TLG
> > colorings does):
> >
> > 0 !COLOUR Black CODE 0 VALUE #1b2a34 EDGE 8
> > 0 !COLOUR Rubber_Black CODE 256 VALUE #212121 EDGE #000000
> RUBBER
> >
> > does that help?
> >
> > They've implemented quite a few keywords that should help:
> > ALPHA x
> > PEARLESCENT
> > CHROME
> > METAL
> > LUMINANCE x (for phosphorescent white)
> >
> > I think they've covered a lot of what you're looking for, other
> > than the
> > random-scatter texture of roof-tile sloping faces. That's really a
> > bump
> > map issue over a coloring issue, though, IMHO.
> >
> > ldconfig.ldr is pretty powerful; it gives the user complete control
> > over
> > the color values, without you having to adjust LeoCAD again. The
> > support that LDView has is really nice.
> >
> > Since there are keywords (RUBBER, CHROME, METAL) to mark the
> material
> > type, it would be fairly simple to have the palette reorganize when
> > trying to color a piece of that type (click on a crown, only Cool
> > Silver
> > Lacquered and Warm Gold Drum-Lacquered show up, for instance;
> > click on
> > a metallic ("PEARLESCENT") item, and only the PEARLESCENT colors
> show)
> > -- all optional of course.
> >
> > Once/if I can get the thing building in 6.0; I could drop back from
> > the
> > HEAD and check out things pre-your-latest-changes, if that would
> help.
> >
> > -- joshua
> >
> >> I'm pretty sure the head revision isn't good enough for use
> right
> >> now. I started adding support for submodels and I think I broke the
> >> save/load code.
> >>
> >> I really do want to have better color support but I'd rather
> have
> >> the concept of materials instead. Colors aren't enough to handle
> all
> >> the information that you need, you can have for example black
> colors
> >> for: standard black brick, the rugged side of a 2x2 slope brick,
> >> black tires, black hoses, etc..
> >>
> >> But I don't want to make it too complicated for the users that
> >> just want to add a black brick or black tire, so I want LeoCAD
> to be
> >> smart about that and automatically add the right type so
> probably the
> >> pieces should contain the material information and the user
> picks the
> >> tint for the piece when they add it to the model.
> >>
> >>
> >>
> >>
> >> On Mar 13, 2007, at 4:45 PM, [EMAIL PROTECTED] wrote:
> >>
> >>> If Philo can't test*, or Leo doesn't want it generally released in
> >>> the current state, then I'll make sure to you send you a "private
> >>> build" John.
> >>>
> >>> -- joshua
> >>>
> >>> * I'll do what I can to be sure of the current functionality;
> but I
> >>> think Philo knows the operation of LeoCAD better than anyone,
> and I
> >>> wouldn't want a "bad" release out there for general consumption...
> >>>
> >>> ----- Original Message ----
> >>> From: "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>
> >>> To: leocad <[email protected]>
> >>> Sent: Tuesday, March 13, 2007 4:43:11 PM
> >>> Subject: Re: Any newer version?
> >>>
> >>> It would be great if a downloadable release can be made available.
> >>>
> >>> Thanks,
> >>>
> >>>
> >>> If needed, I can build a
> >>> downloadable release; if that's desired. [Philo, are you willing
> >>> to ascertain
> >>> whether there are any bugs that make it unshippable before I do;
> >>> once I figure
> >>> out the 6.0 issue for you?]
> >>>
> >>>
> >>>
> >>>
> >>>
> >>> --
> >>> John Henry
> >>>
> >>>
> >>>
> >>>
> >>>
> >>>
> >>> _______________________________________________
> >>> Leocad mailing list
> >>> [email protected]
> >>> https://list.gerf.org/listinfo/leocad
> >>>
> >>> _______________________________________________
> >>> Leocad mailing list
> >>> [email protected]
> >>> https://list.gerf.org/listinfo/leocad
> >>
> >>
> >>
> _____________________________________________________________________
> >> _
> >> This email has been scanned by the MessageLabs Email Security
> System.
> >> For more information please visit http://www.messagelabs.com/email
> >>
> _____________________________________________________________________
> >> _
> >>
> >> _______________________________________________
> >> Leocad mailing list
> >> [email protected]
> >> https://list.gerf.org/listinfo/leocad
> >>
> >
> > _______________________________________________
> > Leocad mailing list
> > [email protected]
> > https://list.gerf.org/listinfo/leocad
> >
>
>
> ______________________________________________________________________
> This email has been scanned by the MessageLabs Email Security System.
> For more information please visit http://www.messagelabs.com/email
> ______________________________________________________________________
>
> _______________________________________________
> Leocad mailing list
> [email protected]
> https://list.gerf.org/listinfo/leocad
______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email
______________________________________________________________________
_______________________________________________
Leocad mailing list
[email protected]
https://list.gerf.org/listinfo/leocad
