A new navigation gem

Hello, I working on Rails extention gem. The gem named
semantic_navigation and trying to make implementation of navigation
for Rails application as easy as possible.
Link to github: GitHub - fr33z3/semantic_navigation: Simple navigation menus implementation for Rails 3 application with multiple and nesting menus.
There are a lot of possibilities for customization right now and will
be
more in future. I really would be happy to hear something about my gem.
No matter good or bad I really need feed back. You can make it in issues
in github or just write here.
Thank you.

On Thu, Aug 23, 2012 at 1:32 AM, Sergey G. [email protected]
wrote:

really need feed back.

Feedback: provide a link to your new gem and enough explanation
of what it does to make people want to click that link :slight_smile:


Hassan S. ------------------------ [email protected]

twitter: @hassan

Hello guys, thank you for all you answeres and sorry for my faults. I
posted that on the http://www.ruby-forum.com and didn’t know that it will
be forwarded here. So the link to the github you know now (thanks to
Dihital).

About that can the gem do:

  • You can define multilevel menus
  • Override the default renderer’s options (even from the view)
  • Different ways to define urls for navigation items (you can also
    set
    the array of urls)
  • Predefined renderers for twitter bootstrap navigation styles - so
    you
    don’t need to make your own renderers for it (but you can)
  • A lot of logic for rendering (like render only some levels or
    except
    some navigation items)
  • Usefull helpers in definitions like to add a proc to the navigation
    item with code defining when it should be rendered where you can
    catch this
    item.
  • Supports internationalization.

It is not the end all you can read in the Wiki:
Pages · fr33z3/semantic_navigation Wiki · GitHub.
And I would also pleased if you noticed me about grammatically faults.

Thanks to Dihital - I will trying to use cucumber it is a good idea.

Hassan, I think Sergey simply overlooked that part :slight_smile: Here it is with
very
minimal copy/pasting into a search engine:

2012/8/23 Hassan S. [email protected]

Hassan Schroeder | about.me


Pagarbiai,
Gintautas

I haven’t check it yet, but +1 for having what looks to be a decent spec
coverage.

I would advise for you to look into Cucumber and describe your
functionality as features, then it would be a lot easier for people to
give
you feedback (once we know what exactly your gem is supposed to do, and
how
it should behave under various circumstances).

RSpec is great, but is is got too small a scope to grasp the behavior of
the system (the gem in this case). Great resource is
The Cucumber Book: Behaviour-Driven Development for Testers and
Developers

(I have no affiliation with that)

2012/8/23 Gintautas Šimkus [email protected]


Pagarbiai,
Gintautas


Pagarbiai,
Gintautas

Fully understood, but in this case I felt really strongly that it was an
honest overlook :slight_smile:

The lack of key (URL) information simply didn’t turn me off this one.

2012/8/23 Hassan S. [email protected]

A vague reference to “semantic navigation” doesn’t grab me :slight_smile:
To unsubscribe from this group, send email to
[email protected].
For more options, visit https://groups.google.com/groups/opt_out.


Pagarbiai,
Gintautas

On Thu, Aug 23, 2012 at 7:28 AM, Gintautas Šimkus [email protected]
wrote:

Hassan, I think Sergey simply overlooked that part :slight_smile: Here it is with very
minimal copy/pasting into a search engine:

Yes, I’m sure I could have found the URL by searching, but my point
was that a gem announcement should also explain the problem that
the gem addresses: give me a reason to use it.

A vague reference to “semantic navigation” doesn’t grab me :slight_smile:


Hassan S. ------------------------ [email protected]

twitter: @hassan