New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Split NetteExtension to each component into separate bridges in backwards compatible way #4

Closed
fprochazka opened this Issue May 23, 2014 · 10 comments

Comments

Projects
None yet
4 participants
@fprochazka
Contributor

fprochazka commented May 23, 2014

@fprochazka fprochazka changed the title from Split NetteExtension to each component in separate bridges to Split NetteExtension to each component in separate bridges in backwards compatible way May 23, 2014

@fprochazka fprochazka changed the title from Split NetteExtension to each component in separate bridges in backwards compatible way to Split NetteExtension to each component into separate bridges in backwards compatible way May 23, 2014

@xificurk

This comment has been minimized.

Show comment
Hide comment
@xificurk

xificurk Aug 7, 2014

Contributor

@fprochazka Any progress on this? Imho this is pretty critical issue blocking the truly component-based usage of Nette. I planned to look into this myself, but as you've taken up the responsibility for this, I put it aside.

Some of the dependencies seem pretty easy to split up and I think even partial resolution of this issue is better than nothing. Shall I look into it or are you already working on it?

Contributor

xificurk commented Aug 7, 2014

@fprochazka Any progress on this? Imho this is pretty critical issue blocking the truly component-based usage of Nette. I planned to look into this myself, but as you've taken up the responsibility for this, I put it aside.

Some of the dependencies seem pretty easy to split up and I think even partial resolution of this issue is better than nothing. Shall I look into it or are you already working on it?

@fprochazka

This comment has been minimized.

Show comment
Hide comment
@fprochazka

fprochazka Aug 7, 2014

Contributor

I still haven't had time to start working on this. If you want, you can do it. I planned it on this weekend, but I'm not promising.

Contributor

fprochazka commented Aug 7, 2014

I still haven't had time to start working on this. If you want, you can do it. I planned it on this weekend, but I'm not promising.

@fprochazka

This comment has been minimized.

Show comment
Hide comment
@fprochazka

fprochazka Aug 9, 2014

Contributor

@xificurk great work so far, are you going to do all of them? I may happen to have some time soon, so I could do few of them. It would be great if you write here every time you start working on one, so we won't be doing it both.

Contributor

fprochazka commented Aug 9, 2014

@xificurk great work so far, are you going to do all of them? I may happen to have some time soon, so I could do few of them. It would be great if you write here every time you start working on one, so we won't be doing it both.

@xificurk

This comment has been minimized.

Show comment
Hide comment
@xificurk

xificurk Aug 10, 2014

Contributor

I think I'll have time to do http and latte - they seem pretty straightforward to do. The debugger (Tracy) and its interactions with the rest of NetteExtension will be a bit harder, so if you've got time to spare, I'd suggest you look into that.

Contributor

xificurk commented Aug 10, 2014

I think I'll have time to do http and latte - they seem pretty straightforward to do. The debugger (Tracy) and its interactions with the rest of NetteExtension will be a bit harder, so if you've got time to spare, I'd suggest you look into that.

@xificurk

This comment has been minimized.

Show comment
Hide comment
@xificurk

xificurk Aug 10, 2014

Contributor

After this is done, we should add test that checks if all the default extensions from Configurator were really loaded.

Contributor

xificurk commented Aug 10, 2014

After this is done, we should add test that checks if all the default extensions from Configurator were really loaded.

@xificurk

This comment has been minimized.

Show comment
Hide comment
@xificurk

xificurk Aug 17, 2014

Contributor

I realized that for http I need tracy first, so I'm just letting you know that I'll try to separate tracy as well.

Contributor

xificurk commented Aug 17, 2014

I realized that for http I need tracy first, so I'm just letting you know that I'll try to separate tracy as well.

@castamir

This comment has been minimized.

Show comment
Hide comment
@castamir

castamir Nov 20, 2014

Contributor

@fprochazka remove duplicated mailer and debugger/tracy from list please.

It seems like there is everything almost ready to separate from NetteExtension. Just take content of each single setup* method and put it to separate extension. Am I right?

Contributor

castamir commented Nov 20, 2014

@fprochazka remove duplicated mailer and debugger/tracy from list please.

It seems like there is everything almost ready to separate from NetteExtension. Just take content of each single setup* method and put it to separate extension. Am I right?

@xificurk

This comment has been minimized.

Show comment
Hide comment
@xificurk

xificurk Nov 20, 2014

Contributor

Well, Tracy is more or less ready in nette/tracy#58, but @dg would like it to be part of nette/bootstrap and I (for a change) don't want to install nette/bootstrap just to enable Tracy in Nette :-)

Contributor

xificurk commented Nov 20, 2014

Well, Tracy is more or less ready in nette/tracy#58, but @dg would like it to be part of nette/bootstrap and I (for a change) don't want to install nette/bootstrap just to enable Tracy in Nette :-)

@hrach

This comment has been minimized.

Show comment
Hide comment
@hrach

hrach Nov 21, 2014

Contributor

+1 for separating from nette/bootstrap.

Contributor

hrach commented Nov 21, 2014

+1 for separating from nette/bootstrap.

@xificurk

This comment has been minimized.

Show comment
Hide comment
@xificurk

xificurk Jan 10, 2015

Contributor

This should be imho resolved before releasing v2.3...
ping @dg

Contributor

xificurk commented Jan 10, 2015

This should be imho resolved before releasing v2.3...
ping @dg

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment