Freelancer Developer
-
-
It’s getting there, it’s getting there ::)
-
Haha thanks a lot OP, but I think you may still like a few features I’m building in. Of course, I’m trying to make them not invasive so you can ignore them if you don’t like them, but some I believe are good all around anyways.
Watch this space, I’m going to try to make a little rush soon to get that out of the door for good
-
btw. I have a little bug report:
Im used to save an IDS infocard and an IDS name under the same ID number, but if I do that with your tool, it throws some errors at me (just try it yourself) and the display overview shows wrong info on the entries. (ingame they are ok)
-
Yeah, I’ve been told about that before but I left it this way because I know this causes problems. I’ve already had bugs happen because a single ID had two different values. Plus, trying to make it work with that would mean rewriting major portions of the code…
-
I’m glad to announce the beta release of the new FLDev 1.1 version.
Please head to FL Forge to download the latest FLDev version.
It includes a host of new features, including a new lightning-quick CRC crawler (similar to CRCTool), configuration settings memorization, Simple Infocards support (allowing to write infocards using pseudo-BBCode), a brand new Output setting, improved CSV sorting, improved DLL editor controls, keyboard shortcuts at multiple places, upgraded color converter, a file/folder existence checker, a vertex helper for manual wireframe creation, autosaves for both the DLL editor and the template in the CSV parser, multithreaded DLL parsing, generally optimized code and a slew of other nifty things I can’t remember!
This release being a beta, I’ve went over a few things. This release does NOT include the following:
-A help file (sorry, it takes a lot of time to make a good one)
-A changelog (I don’t even remember all that changed myself, if that’s any indication!)
-An installerI hope you like the new features and be sure to report any bug you might encounter
-
Awesome tool, same as forsaken, easily recommend this to anyone. ^^
plus im in the credits
XD -
Thanks for the new release ;D I use this tool every day, nice to have a
new one to play with
awesome tool FF still haven’t got the hang of the CSV stuff… i mainly use it to fix my DLL’s
as i use FLIDS as well… (more used to it) for basic template IDS, then add “real” info with FLDev ;D -
perhaps it might be wirth doing a small tut on its usage
would help FF out by him not having one extra thing to do ya kno! 
-
I need feedback people ;D
-
Links to FF WT forums broken
But seems to be indeed a nice tool ^^
-
I know, this is an old thread. I didn’t think making a new one was appropriate, though, so I just bumped it back.
-
;D just used it to repair some IDS… works a charm m8 ;D
I like the new setup makes it easyer to point it to XLR… hehe and keep it there
i’ll be using the other tools latter on tonight…(calculation) they look tasty too…
& nice new GUI (yes i noticed) cleaner and fresher.Great work FF ;D
Oh i do have 1 Q… whats the deal with the CSV files… that make anything easyer…?
U use the tinyfish ini editor for most of the “overhaul” work (balancing fixes)… is this CSV way better…?
that editor can get really confusing and messed up at times (works well though… just my eyes don’t hehe)Chow… back to “work” for me hehe…
-
The CSV Parser is really in its own category. It’s neither an INI editor, nor a full-fledged spreadsheet tool.
In essence, it can dramatically speed up the creation and update of repetitive INI data. The example I always take are guns. With guns, you have a [Gun] entry, a [Munition] entry, plus a [Good] entry and maybe an [Effect] entry. Using the parser and a proper template file, you can simply make a spreadsheet which contains all the needed data and send it in. The parser will take care of “plugging” the values in the proper place, on top of doing a few other nifty things like automatically updating the DLLs if you ask for infocards or names to be added in.
It’s not a replacement to TinyFish or Notepad, it’s more of a complement for specific situations.
-
ST butts the FF dam one more time…
One day I’ll either get his dual-core desktop or he’ll give in and write us a single-core version of his super FL-Dev…
ST keeps on buttin’ that dam!
DAM!
