Just to throw my hat in the ring, I agree that a GUI is more desirable in this
day and age. However, I've worked with Bro's mvToolbox for the last 6-7 years
and it's been a godsend, shaving days and weeks from my efforts. I still keep a
copy and recently reached out to Bro to bring it into my place of work.
It does have its learning curve, largely because it is so feature-rich. Let's
not forget the objective of the tookbox is simplifying MV development
cross-platform (Bro told me a few weeks ago he's working on a jbase port). With
its integration into so many telnet clients, mouse clicks and all, I think it
does a very good job meeting it's objective.
Do I wish it supported a true GUI front end? Sure. Does it get the job done
without it? Sure does.
My 30 cents.
Regards,
LeRoy
Sent from my iPhone 4
On Feb 20, 2012, at 6:00 PM, Tony Gravagno 3xk547...@sneakemail.com wrote:
From: Wjhonson
WED is not an inplace full screen editor. It's merely
a hyped up Notepad. Not the same thing. You cannot
use WED to say Oh by the way, go grab the cross
reference files and show me every OTHER program that
also reads the customer file. You could however do
that, with an inplace full screen editor
Keeping this on-topic, that is one of the thousands of features
in mvToolbox. The above functionality is something all of us
wish we had when we're sitting in some editor X and we know the
pain we face to get the information we need to just write that
next line of code. My message here is that there is a solution
to those problems.
We can debate the aesthetics of the character UI (CUI) vs GUI,
the relative productivity gains and losses, and the perceptions
people have when they see one or the other. But when it comes
down to it, we just need to get a job of coding business apps
done. I would rather have the tools to do what I need, and
debate the UI later, than to not have the functionality and
therefore nothing to debate.
(Doug, please don't jump in here, we've seen your ad in every
other posting, this is NOT about YOUR software. Have a little
respect.)
For anyone who does take a look, learning mvToolbox can be a
painful process. I constantly struggle to decide whether I
should take the time to do something myself (like look for file
usage) or whether I should learn how mvToolbox does it. I face
the same problem with all developer tools. But the reward of
learning it once is that development is then streamlined from
that point forward. Bro Cope (author) has opened the software
for free (limited time?) usage to get the software in the hands
of people in order to drum up some demand for improvements. In
the spirit of collaboration for free but not open source
software, I've offered to help with documentation, UI, website,
etc, in an attempt to help minimize some of that pain. (So far
I've just written some docs, nothing else yet. I'll try to help
with the website too. Eugene Perry has been working with Bro for
years, as his own time permits, in the same spirit of making a
contribution for a common cause.) The product is evolving. It
might evolve to add a GUI (thus giving people both options),
eliminating the need for us to discuss the CUI vs GUI arguments,
and allowing us to focus on functionality.
I encourage people to give it a shot, and focus on functionality,
with the understanding that the UI _may_ evolve and that the
overall product experience _will_ evolve as more people use it.
T
___
U2-Users mailing list
U2-Users@listserver.u2ug.org
http://listserver.u2ug.org/mailman/listinfo/u2-users
___
U2-Users mailing list
U2-Users@listserver.u2ug.org
http://listserver.u2ug.org/mailman/listinfo/u2-users
