Nooku tutorials for beginners
I've to write on this weekend for alltogetherasawhole.org two tutorials about Nooku. It will be my first tutorials in english. The tutorials refer to the first component I developed for Joomla! with Nooku. In part 1, I would like to explain, how to setup nooku for developing. Part 2, deals then with developing a simple component for backend and frontend (Screenshots: http://picasaweb.google.de/hent.dev) and with the distribution of nooku as a simple installable plugin for Joomla! 1.5.
I hope that someone will be interested.
I hope that someone will be interested.
Views: 96
Tags: nooku
-
Comment by Amy Stephen on November 6, 2009 at 12:46am
-
Awesome! I am very interested -- thanks for sharing!
-
Comment by ruud van zuidam on November 6, 2009 at 1:01am -
whow super can't wait for the weekend, thanks man
-
Comment by Martin on November 6, 2009 at 1:47am -
es wird sicherlich spannend :-)
-
Comment by Arno Zijlstra on November 6, 2009 at 2:47am -
Just wondering, aren't you guys "worried" about being dependent on to many parties?
There is J to keep updated.
There is your component to keep updated.
There is the Koowa/Nooku lib to keep updated.
Users may have several components depending on different Koowa/Nooku versions at some point.
JX adds it's own lib that needs to be kept in sinc + there extensions.
etc etc etc
Will the user that has to keep it's site up to date be the one that may get in trouble at some point. (I prefer users not doing stuff like that themselves but that's the case in Joomla! land none want's to pay for things)
-
Comment by Oleg Nesterov on November 6, 2009 at 3:38am -
Awesome. I was going to try Nooku in the upcoming project. Would like to get someone's experience.
@Arno: that's true. On the one hand J! core MVC lacks for many things. On the other hand nobody wants to be depended on extra 3rd parties too much. I guess the ideal solution — is to have MVC core enhancements. However as far as I understand this is not a close task.
-
-
@Arno - toss into that mix JS plugins. It's only going to get more complex. We are reaching the point where automated update management tools are absolutely required. It's not a lot different than how Microsoft handles it's operating system updates. Three times this week, my machine rebooted itself to apply fixes from MS. I suspect that is where we'll wind up with Web site updates.
-
Comment by Shayne Bartlett on November 9, 2009 at 12:50am -
Nooku is aiming towards being Joomla! independent and many Nooku developers I know of are limiting their dependence on Joomla!'s framework. This could mean that for Nooku based extensions to run on a newer versions of Joomla! one would only require an upgrade of Nooku. Kinda easy IMO.
Also when you think of it, not being dependent on Joomla! opens up all sorts of doors for 3PD's.
-
Comment by Arno Zijlstra on November 9, 2009 at 5:47am
-
"Also when you think of it, not being dependent on Joomla! opens up all sorts of doors for 3PD's. "
You'd be dependent on Nooku, it's not that simple.
-
Comment by Shayne Bartlett on November 9, 2009 at 9:13am
-
Ditto what Brian said.
@Arno... how is being tied to Nooku any less simple that being tied to Joomla!?
-
-
I think you misunderstood Arno's comment. Shayne - your comment suggested that because of Nooku's independence of the Joomla! Framework (meaning it substitutes it's own framework), upgrades to Joomla! will not impact Nooku users. What you didn't say was that upgrades to Nooku, will. That's what I took Arno's response to mean.
So, instead of only relying only the Joomla! team, developers (and users) end up also relying on the Nooku Team. Good? Bad? Indifferent? That's a personal call. Who do you think will get you there?
I will admit that I have also found myself thinking and coding in these directions about "not being overly dependent on Joomla!'s framework." I don't think that's a good sign for us as a community. It's time to think about why are we thinking in those directions and address those problems that make us want to not depend on one another. That's the truth. By intentionally becoming less dependent, we are duplicating code and trying to beat one another and battle for a development community.
Pretty freaking sobering.
What should happen? Theoretically, the best of these emerging frameworks should make it's way into core and we should all be working to support - enhance - test - etc., this environment. We should be carving out areas for teams/businesses/individuals to take care of - maybe the Nooku team should handle a piece of the framework. Those are the kinds of changes to our project culture that are needed to force us to work together and share ownership in this project.
As long as a small group makes all the calls on what is Joomla! core and in the Joomla! project, this type of thing will happen. People want a piece of the project. So, we have to figure out how to allow broader involvement. And, soon! Or, we'll wind up with extensions that are forking the community by incubating inside of Joomla!, and then splitting off.
This is sooooo far off topic, apologies to Chet, and I look forward to learning more about Nooku.
© 2012 Created by Amy Stephen.
You need to be a member of All Together, As A Whole to add comments!
Join All Together, As A Whole