Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Footkerchief]

I'm not the biggest Eclipse fan, but this is really hot.

[Kaelem Gaen]

anyone good with that type of stuff, I wouldn't mind something like this for Notepad ++ ... or can it use eclipse plug ins -ponders-

[zwei]

Fixed item raws for new version and started progress on material templates.

anyone good with that type of stuff, I wouldn't mind something like this for Notepad ++ ... or can it use eclipse plug ins -ponders-

I guess it certainly possible to do something similar for Notepad++ (and that someone propably did this already), but i am sure it can not use eclipse plugins.

Remember, i am using different approach than notepad++, what i do is that i am making formal language description of raw format and let editor figure out how do to folding, highlighting or autocompletition/code suggest.

[Kaelem Gaen]

Ah okay.

[Stargrasper]

I'll have to keep an eye on this.  Particularly for when you get around to entities and reactions.  Think you can give an error on entities for permitting jobs/buildings/reactions that don't exist?  And a warning on said things if no entity uses them?

[zwei]

Got color-definitions crosslinked with matrial template colors.

I'll have to keep an eye on this.  Particularly for when you get around to entities and reactions.  Think you can give an error on entities for permitting jobs/buildings/reactions that don't exist?  And a warning on said things if no entity uses them?

Warnings similar of this whole point of this project

[Eagle0600]

Yeah, reference to other objects (and stopping us from typing the wrong token) would be awesome.

[zwei]

Made project on google code: https://code.google.com/p/dwarffotressraweditor

Material template is finalized and inorganic templates are done, plants are half done.

[zwei]

Plants are done.

Reactions are halfways done. I am now using cutting edge nightly builds because they fix some of my issues. Apparenty, Raw format is huuuuuge (parser for it passed 64k of bytecode) and engine was choking on it.

[Zared]

Oh, you can make a grammar recognize comments as everything outside of brackets.  You might not be able to do it in the scanner and ignore them completely, but you can easily identify them while keeping it LL(2).  (Or LL(1) if you have your open bracket be part of the tag token set.)

You just need an optional "Comment" non-terminal after every "]" terminal symbol you use.  For example, if you have the production rule

Code: [Select]

"[" "OBJECT" ":" "REACTION" "]" { ReactionDef }
It would become

Code: [Select]

"[" "OBJECT" ":" "REACTION" "]" [ Comment ] { ReactionDef }
Then your Comment production would just be a chain of anything, minus "[". In effect, if you remember to always follow a "]" terminal symbol with an optional Comment non-terminal, you're telling your grammar that "Everything between a "]" and either EOF or "[" is a comment"...oh yeah, I guess you'd need an optional Comment non-terminal after the file name declaration, too, not just after every "]" terminal.

Then you just have it color any Comment symbols in the same way it colors "real" comments

[zwei]

Oh, you can make a grammar recognize comments as everything outside of brackets.  You might not be able to do it in the scanner and ignore them completely, but you can easily identify them while keeping it LL(2).  (Or LL(1) if you have your open bracket be part of the tag token set.)

You just need an optional "Comment" non-terminal after every "]" terminal symbol you use.  For example, if you have the production rule

Code: [Select]

"[" "OBJECT" ":" "REACTION" "]" { ReactionDef }
It would become

Code: [Select]

"[" "OBJECT" ":" "REACTION" "]" [ Comment ] { ReactionDef }
Then your Comment production would just be a chain of anything, minus "[". In effect, if you remember to always follow a "]" terminal symbol with an optional Comment non-terminal, you're telling your grammar that "Everything between a "]" and either EOF or "[" is a comment"...oh yeah, I guess you'd need an optional Comment non-terminal after the file name declaration, too, not just after every "]" terminal.

Then you just have it color any Comment symbols in the same way it colors "real" comments

Thanks for ideas, i'll try to get soemthing working from it. This seems like a lot of work thou (300 tags and counting, could be messy), but i guess that i can redefine all closing brackets neatly globally.

So far thou, it is quite comfortable to just ctrl+shift+c any offending lines thou, so i will give it low priority.

I am currently more concerned about raw format itself because it is quite a messy one. Documentation is quite lacking.

[zwei]

Done with reactions, entities are nearly done and creature raws are about 1/2 done

[Kazang]

Nice work, eclipse is a great tool.

[Vester]

This is nifty.

[anallyst]

nice stuff. i actually wonder if we could take the part of the code that parses the config file to a tree out and use it for a mod distribution tool like Uristmod, by using a not-so-exotic language as haskell. i'm pretty sure the java code could be translated to C++ relatively easy. that would become libdwarfconfig, which in turn would be used by the mod tool.