Mally writes:
> I'm going to complain, mainly because I'm intrigued as to what the
> 7th-century Insular Latin version would be like:
Frightening (classicists need to be monitored closely in case they go
into shock). I recommend Aldhelm's De Virginitate as a starting
point; unfortunately, I c
> > An other idea could be to add a description to every property. So the
> > user can figure out what each of those are good for when browsing the
> > tree. And when we would change our command line options to be property
> > entries we cuold automatically create the --help option which will
Christian Mayer writes:
> > - is readable? (already implemented)
> > - is writable? (already implemented)
> > - is archivable? (already implemented)
> > - data type (already implemented)
> > - list of allowed values
>
> Wouldn't a check for that slow the properties down? Or would it only
David Megginson wrote:
>
> All Properties
> --
>
> - is readable? (already implemented)
> - is writable? (already implemented)
> - is archivable? (already implemented)
> - data type (already implemented)
> - list of allowed values
Wouldn't a check for that slow the properties down?
Jim Wilson writes:
> "Ranges" and "Value lists" would be good. I was thinking of
> enforcing rules defined in xml in the prop_picker, but it sounds
> like your saying that should be in the property manager code.
> Which makes sense. It'd be good to have a error return code(s)
> from the pr
This is what asking about earlier, then we got into the discussion
about xml menus (which I'm still thinking about working on, but have been
spending what little time I have available right now learning Ac3d enough to
build a 3D panel--figuring along the way I'll eventually learn how the panel
cod
Semi-static: click on the . (current directory dot) file entry and it refreshes.
Best,
Jim
"Curtis L. Olson" <[EMAIL PROTECTED]> said:
> David Megginson writes:
> > Jim Wilson's new property picker is great -- I encourage everyone who
> > hasn't done so already to try it out. I'd also be int
Norman Vine <[EMAIL PROTECTED]> said:
>
> One thing we could use are the dimensions and the x and y size
> of the property picker exposed as properties so that one could
> easily position it where desired.
>
That would be easy enough. Almost getting back to the xml gui idea.
For the time bei
Norman Vine writes:
> >I encourage everyone who
> >hasn't done so already to try it out. I'd also be interested in
> >hearing what enhancements to the property manager (such as
> >constraints) would be useful for the property picker's future
> >development.
>
> One thing we could use are
David Megginson writes:
>
>Jim Wilson's new property picker is great --
Indeed !
>I encourage everyone who
>hasn't done so already to try it out. I'd also be interested in
>hearing what enhancements to the property manager (such as
>constraints) would be useful for the property picker's future
David Megginson writes:
> Jim Wilson's new property picker is great -- I encourage everyone who
> hasn't done so already to try it out. I'd also be interested in
> hearing what enhancements to the property manager (such as
> constraints) would be useful for the property picker's future
> developm
Jim Wilson's new property picker is great -- I encourage everyone who
hasn't done so already to try it out. I'd also be interested in
hearing what enhancements to the property manager (such as
constraints) would be useful for the property picker's future
development.
All the best,
David
--
12 matches
Mail list logo
