DeleD Community Edition

jwatte · DeleD PRO user Joined: 26 Apr 2006 Posts: 513

For the NuXporter, I would like getting the scene name and the scene file path through the XML API.

jwatte · DeleD PRO user Joined: 26 Apr 2006 Posts: 513

... wind ... tumbleweeds ...

Jeroen · Posted: Sun May 13, 2007 6:27 am Post subject:

Gee, another post I missed... Confused

Will work on this one a.s.a.p!

Do you mean the scene filename or the name as found in the scene properties? I assume the latter when also assuming the scene file path contains the filename already.

jwatte · DeleD PRO user Joined: 26 Apr 2006 Posts: 513

I want to get both :-)

Paul-Jan · Posted: Wed May 16, 2007 10:14 am Post subject:

The scene name is already in the xml, in scene.settings.name (I think Jeroen might have meant to say this in his post above, but I'm not sure). We could add the filename to those settings as well (although I kinda liked the plugins not knowing/caring whether there was a physical source file).

jwatte · DeleD PRO user Joined: 26 Apr 2006 Posts: 513

Paul-Jan · Posted: Wed May 23, 2007 12:30 pm Post subject:

As far as we know not too many users are trying to integrate DeleD into their production process to that extend (most just want to use it as a lightweight one-click alternative modeling package), I think 99/100 are modelers that just want to spend their time modeling, can't be bothered to download separate plugins unless they truely absolutely need them, let alone develop new ones to extend the functionality... but I think what our other users want is our "problem", not yours. You want/need the application to be more extendible, so do make sure to keep hammering your requests for a more complete plugin system into our heads. If an extended plugin system attracts more quality plugin builders, that'd be great.

jwatte · DeleD PRO user Joined: 26 Apr 2006 Posts: 513

Well, you can't get a quality plug-in built if there's no API to build it on!

Again, what I keep saying is that, if you structure DeleD so that your own commands are plug-ins, the API will come of itself. Maybe try to make each new command/feature as a plug-in, and only re-factor/move the bits you need to change to enable that one command, as a start? The incremental effort there should be minimal.

Perhaps I'm saying that you guys are aiming too low :-)

Jeroen · Posted: Thu May 24, 2007 6:37 am Post subject:

jwatte · DeleD PRO user Joined: 26 Apr 2006 Posts: 513

What I'm saying is, if you think of yourself as plug-in developers, you wouldn't spend any "extra" time developing such an API. And I think you can start developing new commands (say, the "double" command for triangles) as plug-ins without necessarily spend a whole lot of time making an API first. In my opinion, it's mostly about a mind-set.

Mr.Fletcher · Posted: Sun Jun 03, 2007 12:09 pm Post subject:

Uhm okay, I just read into the whole plugin thing and tried it out and it would be really great if you had
a) access to the selection of sub-items like polygons, edges, vertices
b) access to deled commands.
with a+b combined, there would be a lot more possible than today Very Happy

_________________
Behold! The DeleD Wiki! Please help us expanding it Smile

DeleD on IRC

jwatte · DeleD PRO user Joined: 26 Apr 2006 Posts: 513

Fletcher, you're repeating a whole thread of communication I've had with them over the last year or so. I'm glad I'm getting some support on this :-)