Dantas I like the look of yours as well, but I think it looks good now because you have a small amount of objects where you may not need a tree anyway. If you have an scene with 80 different components it is then the same size as what I had. I do like that it looks simple and in keeping with tht UI overall but when it pops up it will be in the middle of the workspace I think instead of off to the side so it may obstruct viewing.

Hi Danny...

I like you idea that keep moi in simple ui. But for the position of this new stuff I prefer the idea by Grendel, so put on the right, not bottom. Just my opinion. Lets wait also for Michael idea and wish he can post some image someday.

Edit : As I know, Michael also want to put "object editing" inside the object organization. So when pick a circle, we can resize by type new value for the radius or diameter. Michael, please tell us if my explanation not correct.


-Cheers

Dany's idea to have a System Object (orange button bottom)can be cool
Only visible objects in the view will be display

But why not make the same for all views? So put here the tree icon ;)

But manage all that is not a task of programming? (only visible objects)

I did'nt know if he was intending on placing object history in the tree or leaving it under the little clock icon.

Hi Anis, you wrote:

> Edit : As I know, Michael also want to put "object editing" inside
> the object organization. So when pick a circle, we can resize by
> type new value for the radius or diameter.


And Grendel wrote:
> I did'nt know if he was intending on placing object history in the
> tree or leaving it under the little clock icon.

Actually, I would like to remove that little clock icon from the Edit palette and instead have history options for an object be part of the object properties panel.

The object properties panel would be something that would show up in this area:



It would be active when you are in selection mode - I mean in the mode before you have starting to run any command.

The idea is that the properties for the currently selected object or objects would be displayed there, probably by default it will show only a small amount of info like the type of object, its name, and color, and then have some way to expand it into different sections, like shape properties (endpoints of a line, center and radius of a circle), bounding box size (see and/or edit an object's size by its bounding box dimensions), and probably a bunch of "advanced" properties...

This panel would be something that was always available even when the browser tree thing was closed, it would show up in that currently empty area.

- Michael

I like that Michael, it would keep the tree functions to a minimum and that space is empty during selection anyway so two birds with one stone.

Hi Grendel,

> that space is empty during selection anyway so two birds with one stone.

Yeah, it will be good way to reuse that space I think. The main problem is that there is not a whole lot of room there, so it has to be kind of sparse by default but have ways to optionally expand to get at more stuff...

- Michael

Definitely a lot of great ideas in here, keep on posting stuff!

Just a note - I think that probably the initial focus for this will need to be for handling a larger quantity of items.

I'd definitely like to have an optional way for it to be used in a smaller panel, there are many options for this like a pop-up or entry on the bottom toolbar as shown above, also another idea is to have it as an item on a tab on the side pane similar to "Construct", "Transform", etc...

But I think that lightweight option will have to come later, once a more comprehensive mechanism is available first.

- Michael

My 2 cents would be to utilize the most minimal layer/object manager within MoI's CommandProc, and have it read and write a "seperate" xml data file linked to objects. This could have a "Customizeable" tag/hierarchy system managed by the user. I could keep it simple or make it as robust as I want. I suppose the downfall would be that it's not compatable with "Other" higher end packages and these Moi Tags would be proprietary to MoI (At first, Down the road third party can easily manipulate the xml data)



Kind of a "Seperate" script with access to the objects and linking capabilities through the layer manager implemented in MoI.

Hi Burr - interesting idea... If you wanted to send a file to another person, would that mean that you would have to send both an .xml and a .3dm file to them in order for them to get layer data?

Data transfer to other machines tends to be the problem area with this kind of scheme...

- Michael

>>interesting idea... If you wanted to send a file to another person, would that mean that you would have to send both an .xml and a .3dm file to them in order for them to get layer data?


I suppose. It does get bloated when you bring all the stuff in. The MoI "Assembly Exporter" could automatically "zipp" the required stuff if needing to share all the "added features" with others. The zip file could have a proprietary extension that then needs never be unzipped, MoI's "Assembly Importer" unzips the 2 files uses them, anytime an assembly is closed, it's just zipped up again. Something only utilized by those that require it. A "Moi.assm" file if you will.

It could get bloated when considering all the possibilities. I would think this could also be a third party tool if later MoI could expose the "Objects" through some kind of SDK. This could open the door (down the road) to incorporate database feature based modeling and have MoI be "third partied" into a full featured high end assembly package.

Seems for the common man, and probably your main target, alot of this kind of stuff is not considered or desired, but you have such a great product, your attracting Solidworks/nx users who want/can utilize the heavy stuff.

It could just be understood that if this is used in the process, there are some steps that have to be adhered to. (the whole reason opposite of your vision of MoI! :) but satisfying your high end clients.)

Again, it's just 2 cents from the peanut gallery!

Burr

Could even be an option in the installer! "Clean light version" "Add Organizational tools".

But if your like me, when you buy a new package and it says "will you need to be using this in space", I always say "yes" and install it because I want ALL" the functionality, even if I will never be in space.

Hi Michael,

> Actually, I would like to remove that little clock icon from the Edit palette
> and instead have history options for an object be part of the object properties panel.

Ahuh! I get it now.
That would! be nice.

> The main problem is that there is not a whole lot of room there, so it has to be kind
> of sparse by default but have ways to optionally expand to get at more stuff...

Couldn't you have that info window scroll or maybe tabbed to access the different areas of info ?

.

Hi Burr, in the future I definitely do want to put some focus on opening up MoI for 3rd party developers, but in the early stages I've got to sort of keep more focused just on "regular" non-developer users first to make sure the basic UI is working well...

So I think that more of that kind of thing will happen later on, but for now just getting the basics is more of the target.

- Michael

> Couldn't you have that info window scroll or maybe tabbed
> to access the different areas of info ?

Yeah - I try to avoid scrolling if possible, I had been thinking of tabs. But still there is not a lot of space even for a whole bunch of tabs so it won't necessarily be easy.

- Michael

>>So I think that more of that kind of thing will happen later on, but for now just getting the basics is more of the target.

Here here!

But you have to admit, the assembly file is a great idea! Ha! (Looking forward to MoI's future)

Burr

Repost this Video by Steph ;)
http://moi3d.com/forum/messages.php?webtag=MOI&msg=944.1
and this one: sliding line
http://traveaux.steph3d.net/FichiersForum/4D_Onglets.swf

A "miniature preview" on the right side panel when you select something on the tree list before to put in the screen view?

Hi Pilou, interesting idea, but space is going to be very tight over there on the right side panel, I don't think that there will be adequate space available to have a preview like that but we'll see.

Also, usually the plan for showing object is to show them in the 3D viewports.

- Michael

About the Helpers and "constructions lines"
part of the tree? a special layer ? colors? ...