vic20
Fool
eTools is great software!
I have been writing software for 19 years, have programmed professionally in six languages, and have analyzed/designed/built dozens of technologies in diverse customer domains. I don't reference my experience in a vain attempt to elevate myself or my opinion. Its just that there are patterns of a sort hidden in the chaos of software development that I don't think would be apparent to somebody who hasn't been inside the storm.
When I read a comment like the above, I am reminded of the difficulty of managing one's expectations in proportion to the clarity of one's "vision". 30+ years is a long time to roll a fantasy technology around in your head. Try communicating these needs into a software requirements specification sometime, and (if you are doing the task correctly), you will immediately begin to find holes in your fantasy.
I don't know what was behind the shift from MasterTools to eTools, but I'm sure its all been written in the boards here and elsewhere. Reading posts to the board of late, I had imagined that the "drek" that has been "pushed on us" was going to be a poorly-thought-out mish mash of ugly interface elements that often results from shifting project requirements. Imagine my surprise to discover this morning that eTools is actually great software!
I don't understand the complaints about it being unusable. I have designed and programmed interfaces for the Mac, for Newton, for Windows, for Java, for Palm, for HTML, for the Vic20, and the Com64. I have used software on all of these platforms, and I have been assaulted by my fair share of bad interfaces.
The GUI for eTools is fine. Sure, it's not going to cause a revolution in the way that humans interact with computers, and it certainly isn't going to be the fantasy "Silver Bullet" software that will make paper obsolete. It is a tool for generating monsters and characters for 3ed D&D.
In short, I am pleased with the efforts of the good people that have shed blood and sweat on my behalf. I like the fact that the product ships in a simple cardboard sleeve. I like the data storage mechanism. I like the export capabilities. I like the extensibility potential. I like supporting software artists that build tools that make me smile.
Its a Durn (good evening, Grandmother Noah) shame that a vocal few seem to feel that the developers at fluid have insulted them personally.
I'd really be interested to read more about this MSAccess license violation that you allude to. That's a pretty heavy implication. Maybe I'm misunderstanding something.
HexGunna said:In 30+ years of tabletop gaming history, I have yet to see a Good Commercial RPG Character Generator. Master Tools was to be that tool.
I have been writing software for 19 years, have programmed professionally in six languages, and have analyzed/designed/built dozens of technologies in diverse customer domains. I don't reference my experience in a vain attempt to elevate myself or my opinion. Its just that there are patterns of a sort hidden in the chaos of software development that I don't think would be apparent to somebody who hasn't been inside the storm.
When I read a comment like the above, I am reminded of the difficulty of managing one's expectations in proportion to the clarity of one's "vision". 30+ years is a long time to roll a fantasy technology around in your head. Try communicating these needs into a software requirements specification sometime, and (if you are doing the task correctly), you will immediately begin to find holes in your fantasy.
I don't know what was behind the shift from MasterTools to eTools, but I'm sure its all been written in the boards here and elsewhere. Reading posts to the board of late, I had imagined that the "drek" that has been "pushed on us" was going to be a poorly-thought-out mish mash of ugly interface elements that often results from shifting project requirements. Imagine my surprise to discover this morning that eTools is actually great software!
I don't understand the complaints about it being unusable. I have designed and programmed interfaces for the Mac, for Newton, for Windows, for Java, for Palm, for HTML, for the Vic20, and the Com64. I have used software on all of these platforms, and I have been assaulted by my fair share of bad interfaces.
The GUI for eTools is fine. Sure, it's not going to cause a revolution in the way that humans interact with computers, and it certainly isn't going to be the fantasy "Silver Bullet" software that will make paper obsolete. It is a tool for generating monsters and characters for 3ed D&D.
In short, I am pleased with the efforts of the good people that have shed blood and sweat on my behalf. I like the fact that the product ships in a simple cardboard sleeve. I like the data storage mechanism. I like the export capabilities. I like the extensibility potential. I like supporting software artists that build tools that make me smile.
HexGunna said:And thats Why you oughta get your cash back, IF you're unhappy with the product, don't settle man, don't wait, no hoping.
It's why we ain't got a good one now, somebody at Fluid/WotC thought it was okay to push this drek out on us...
on me.
Its a Durn (good evening, Grandmother Noah) shame that a vocal few seem to feel that the developers at fluid have insulted them personally.
HexGunna said:Somebody there thought we'd be okay with it, we'll buy and settle, and if enough of us settle then maybe we'll get an expansion for it.
I didn't settle.
And neither should you. Any of you.
Now if you liked ETools - please disregard my sober rant, It's nearly quittin time and I'll be intoxicated shortly![]()
For the record - There is nothing buggy about Etools, it didn't crash on me, it made most of the CRB characters.
But there ain't a DAMN thing right about it either.
no amount of 3rd party fixing - not tweaking, customising, or modifing, fixin' is gonna make it right.
'sides then you talking about a MSAccess license...or Breakin' the law[/B]
I'd really be interested to read more about this MSAccess license violation that you allude to. That's a pretty heavy implication. Maybe I'm misunderstanding something.