[Plugin]bloc *new plugin*
- Iron_Forge
- Posts: 532
- Joined: Sat Sep 20, 2003 9:21 pm
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
Actually, IFP's are the most advanced xml-style plugin available...I'm not sure which types I missed, because I'm pretty sure I got them all...Though, I do label things like vertex's as 3 floats, but as far as the actual values are concerned, they really are just 3 floats...Perhaps in the future some actual schema system could be defined to add lower level types such as a vertex...But when it comes down to it, the editor still has to display it as 3 floats...
I'm not sure how being the most advanced xml-style makes them obsolete...They're one of the newer structures, so I honestly can't see how I missed types the old ones somehow didn't have...Unless you want an entire display schema included in the plugins so you can control how the editor lays them out...But in my opinion, thats something best left to the developer...If people don't like Insolence's IFP display, they could easily create their own (as Insolence does allow for coded-plugins, thats how it handles IFP's)...
But again, separation of display and control is something any modern developer will tell you is a must...It's a standard of design...IFP is also expandable, since it is just a layout...So you could easily add new types if you created your own display control for it...Assuming I did miss some...
I'm not sure how being the most advanced xml-style makes them obsolete...They're one of the newer structures, so I honestly can't see how I missed types the old ones somehow didn't have...Unless you want an entire display schema included in the plugins so you can control how the editor lays them out...But in my opinion, thats something best left to the developer...If people don't like Insolence's IFP display, they could easily create their own (as Insolence does allow for coded-plugins, thats how it handles IFP's)...
But again, separation of display and control is something any modern developer will tell you is a must...It's a standard of design...IFP is also expandable, since it is just a layout...So you could easily add new types if you created your own display control for it...Assuming I did miss some...
Sorry to derail this thread (although it's still pretty much about plugins), but it's silly to see people duplicating work that they don't need to.
Would a simple, ADI-type (Tree View + Editing Space, one map at a time, one tag at a time), Map Editor program, supporting IFPs, allowing Renaming of IFPs from within the program help facilitate people using these plugins?
What kind of an interface would be easiest to use?
Would a simple, ADI-type (Tree View + Editing Space, one map at a time, one tag at a time), Map Editor program, supporting IFPs, allowing Renaming of IFPs from within the program help facilitate people using these plugins?
What kind of an interface would be easiest to use?
Blah blah blah
-
- Posts: 39
- Joined: Sun May 02, 2004 6:37 am
My big question is how you guys go from a MODE tag to a bunch of .obj's, a .mtl file, etc. with DM.
I mean, I understand following tag dependencies when using plugins, but going from hex to obj...how do you guys figure this out? Must take a while
I mean, I understand following tag dependencies when using plugins, but going from hex to obj...how do you guys figure this out? Must take a while
Last edited by aka Monazight on Mon Oct 03, 2005 5:18 pm, edited 1 time in total.

-
- Posts: 169
- Joined: Sat Feb 26, 2005 3:05 pm
- Location: halopatch.com
![]() |
The topic won't get locked, it's discussion, not flaming or arguing, and this thread has more 'real' information in it than probably the 20 threads below it combined.
Anyway, I was just noting that you're doing a lot of work which was already done for you, and everyone, but if that's how you guys like to do things, go for it. I figured maybe some people didn't understand that it was already done for them, so I explained a bit about IFP's differences.
So sorry for being informative, I didn't know that's frowned upon around here.
Anyway, I was just noting that you're doing a lot of work which was already done for you, and everyone, but if that's how you guys like to do things, go for it. I figured maybe some people didn't understand that it was already done for them, so I explained a bit about IFP's differences.
So sorry for being informative, I didn't know that's frowned upon around here.
Blah blah blah
- trepdimeflou
- Posts: 727
- Joined: Sat Dec 25, 2004 12:50 pm
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
only if it supports lightmaps and has a very intuitive camera systemtjc2k4 wrote:Sorry to derail this thread (although it's still pretty much about plugins), but it's silly to see people duplicating work that they don't need to.
Would a simple, ADI-type (Tree View + Editing Space, one map at a time, one tag at a time), Map Editor program, supporting IFPs, allowing Renaming of IFPs from within the program help facilitate people using these plugins?
What kind of an interface would be easiest to use?


Enums are supported.. check [weap] tags, Needler, for an example..xbox7887 wrote:ifps are missing indexes, byte arrays, and enums.
Indexes are something "created" after IFPs and aren't really a data type, more of a linking structure.
And Byte Arrays are another thing noticed after I finished implementing IFPs, therefore not supported in Insolence, but they'll be in all future implementations (not sure whether "indexes" will be added...)
For example
Code: Select all
<struct name="SomeName" bytes="4">
<float/>
</struct>
Blah blah blah
-
- Posts: 169
- Joined: Sat Feb 26, 2005 3:05 pm
- Location: halopatch.com
![]() |
-
- Posts: 169
- Joined: Sat Feb 26, 2005 3:05 pm
- Location: halopatch.com
![]() |