Super Ultra Mega Dynamic Menu Post - all gurus and no gurus invited

[eluser]MEM[/eluser]
[quote author="jedd" date="1257019957"]Of course.
Earlier on you said you were worried about ROUTE changes, because you would have to hard-code things. This meant that if any new things were added - by a user perhaps - you would have to hard-code NEW routes in to handle them.
[/quote]
I was wondering if, for example,the admin user of this site adds a new category to the database I don't want to hard code the possible route changing associated to that new category.
I believe however, that my update II on the previous post, have clear this doubt. By having placeholders that expect not a specific number like 1, 2, or 10, but any number, by using :num. Or any character, by using: :any.



[quote author="jedd" date="1257019957"]
I suggest that you invert this problem. Rather than route a bunch of things that you list, you instead route everything that is NOT in a list.

As I say, this is only helpful if you think that in the future, the kinds of changes that will occur are more likely to be things that you want to automatically route by default. I expect that there will always be times when you need to visit your source and make hard-coded changes to the way things work.
[/quote]

O.o

[quote author="jedd" date="1257019957"]
Does that make more sense?
[/quote]

I will grab some chocolate... Oh... nice birds... do you hear them?
Whistling out...


Ok. No.
Anyway, give me some hours to organize the ideas.



Side note:
The last 20 hours I was playing and reading about Git. It's really nice and fast!
I've installed egit (for enclipse) as an Aptana Plugin.
Also, because I like the command line style, I've added cygwin with git inside as well.

Once on the cygwin, I navigate to my project directory, and I do some commit, and then I create a branch, and then I change from branch to branch. And wow! that's fast.

So, in this case for example, I need to change files on the model, and on the controller, and on the view... instead of always create versions of each of those files, I just create a branch based on my working branch, and I call it: testmenu.
If something goes wrong on my testmenu branch... well... I will return to my working branch.

I realise this is, still, a very limited use of git, but it's a start.

Thanks a lot jedd.

here are other references that I found:
http://book.git-scm.com/

For Aptana (or other eclipse related users), after install the plugin, just follow the steps here:
http://wiki.eclipse.org/EGit/User_Guide



Regards,
Márcio