Move Tracy under namespace Nette\Tracy

[janmarek]

I don't think Tracy should be ashamed of to be part of Nette Framework (or being developed by Nette Foundation). If you will create more repositories with parts of Nette (e.q. Nette\Image) in future, it will be impossible to find cool names for all of them.

In fact, I don't think it is necessary to rename Nette\Diagnostics at all :)

[JanJakes]

+1 and same for Tester: Tester -> Nette\Tester.

[dg]

Tester is common name, Tracy is trademark. Nette Tracy are two trademarks combined. Always is better to use one name.

[hrach]

:+1: for @janmarek But I would definitely rename it to Nette\Tracy\Debugger.

[JanJakes]

@dg: I understand your point but what to do with all the packages when Nette is separated? You want to find some trademarks for all the important packages? And you don't want to use the "vendor" prefix? It should be there anyway I think...

[fprochazka]

I like Tracy\Debugger.

[JanJakes]

Now I get it: https://github.com/nette/tracy/commit/8fb7b546107e7d4bb4fdfcedf6c990cacc885a30#L0R2

You want to use names evoking really separated projects (and trademarks) so we will have packages like "tracy/tracy", "latte/latte", etc.? Sounds good - this way each package may have higher chance to become a famous component for example as a bundle for Symfony.

[Majkl578]

:+1 for Nette\Tracy

[Majkl578]

Sounds good - this way each package may have higher chance to become a famous component for example as a bundle for Symfony.

Wth? Do you think if Symfony\Console was Console\Console, it would be more widely used?

[JanJakes]

No, in fact I don't know - I've written "may", but you are right it doesn't sound so good. I was just trying to understand @dg's reasons for this.

To be honest personally I prefer Nette\Tracy style because Tracy\Tracy is just duplicating things. Nette Foundation is the real vendor of this package so it actually makes more sense. Also the homepage of the package is tracy.nette.org. So for me (as I said originally) I would put everything into the Nette vendor namespace and nette\* package.

[rostenkowski]

I understand both.

Symfony\Console is like Nette\Tester Tracy\Tracy is like Twig/Twig

It is hard to say which variant is better and for what...

I agree with David that Nette\Tracy combines trademarks... and with this argument I am probably inclined to believe that tracy/tracy is better.

On the other side the Nette trademark probably will be weakened by such component name fragmentation, and yes, the vendor is Nette Foundation so from this point of view the nette/tracy name is better.

[hrach]

It's really logical to have trademark duplicity "tracy/tracy" :D

[Majkl578]

So following the same logic, lets have Nette\Nette then. I'm just imagining how strange Nette\Nette\Application\Application would be.

@rosret: Where did you see Twig/Twig? It's fabpot/Twig and classes are named Twig_*. @hrach: +1

[rostenkowski]

I think that the nette/tracy is better in summary - because it supports the main Nette trademark.

[rostenkowski]

@Majkl578 it's the package name...

[Majkl578]

But we are speaking about namespace here…

[vojtech-dobes]

A: "I use Tracy for debugging." B: "Great." A: "I use Nette Tracy for debugging." B: "What's Nette?"

There is no need for duplication in namespace and I don't believe someone like @dg plans that. But it makes sense to create really independent trademarks. This way was hinted with Neon, which is also branded from the beginning as standalone component.

It also makes sense to have Github organizations like tracy or latte if these packages will have their own build tools, own versioned documentation or whatever may be needed.

[rostenkowski]

@vojtech-dobes :+1:

[dg]

@vojtech-dobes :+1:

[Majkl578]

So are we going to have separate names for Nette\Forms (Formies), Nette\Templating (Templikes), Nette\Database (CrapDB), , Nette\Mail (Mailie) etc.?

[rostenkowski]

CrapDB :lollipop:

That's the risk - and I think it's known ;)