First off, thanks again to everyone that replied. I would have dead in
the water without each of you.
I'm definitely no software engineer much less self-proclaimed rock
star. I'm a kid with a SICP course and a few months of Rails under my
belt. But looking back at the intsallation process, there were a few
messages I wish I had received.
When I generated a resource I first got an error message that said I
didn't have the dm-aggregates package, then when I installed that and
tried the same command I got an error message saying I didn't have the
dm-timestamps package, and then one saying I didn't have dm-types,
then dm-validations.
Generating a resource seems like it'd be a very common command, and
one that every beginner to merb would use.
What about a message that said
"Error when trying to create resource, missing db-aggregates,
Possible reason: To generate a resource with a fresh install of
merb, you must have the following resources
dm-aggregates
dm-timestamps
dm-types
dm-validations"
It would save some time, and aggravation for new users, though I know
the merb is targeted towards more knowledgeable and proficient users
than rails is.
I was a bit confused about this message:
/usr/local/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in
`gem_original_require': no such file to load -- mongrel (LoadError)
from /usr/local/lib/ruby/site_ruby/1.8/rubygems/
custom_require.rb:27:in `require'
I thought I had mongrel (I thought it was installed with merb) and was
missing 'gem_original_require', so I didn't think of installing
mongrel until I was instructed. But all my trouble was due way more to
my ignorance than to ruygem's message.
I got this message when typing in merb to start the server, so when
merb runs across an error like this, can it check with rubygems to see
if mongrel or thin is installed and hand back an error message like:
"No known server has been installed via rubygems"
Once again, like the above proposed message this message is totally
targeted to new users making dumb mistakes, and therefore might not be
worth it to add since anyone would need this message only on their
first day of merb.
I think a very useful error message would be if it displayed a tree of
what I need. I'd like to see the gems that will be installed before
the installation happens.
Like
:Error missing the following gems:
--gem-A (ver 1.0) which requires
----gem-I (ver 1.0)which requires
------gem-a (ver 1.0)
------gem-b (ver 1.0)
----gem-II (ver 1.0)
No I know I'm digressing a bit, but I would
Then when I type in gem install gem-A, I'd like to see the same tree
and have rubygems ask me if this installation tree is acceptable, and
then offers me the chance to download a different version of a
dependency, like install instead gem-I version 0.9 instead, and then
it will repeat the process offer me an updated dependency tree like
--gem-A (ver 1.0) which requires
----gem-I (ver 0.9) which requires
------gem-a (ver 1.0)
------gem-b (ver 0.8)
----gem-II (ver 1.0)
Asks me if this is acceptable, and I can say yes no, or make another
change.
For all I know, gem does offer that. But right now when I install a
gem I don't know what other gems (and what versions of these gems) are
going to be installed until after I give the okay to install.
In all likelihood these ideas aren't implemented because they're
terrible. Like I said in the beginning, I'm an ignorant nobody. But if
I do get an idea of something to add to an error message, I'll be sure
to post it here.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"merb" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/merb?hl=en
-~----------~----~----~----~------~----~------~--~---
