My wife's first comment as soon as she saw it: "Jon, aren't you going to scare off all your male customers."That's just Jon trying to fill a niche in forumland whilst getting (very) in touch with his feminine side![]()
Plus I imagone the international food shipping costs are pretty intense.I could probably buy @Rob a cake, but probably easier if you buy/make a cake and then send me the bill. I don't think they travel particularly well!
more code can be shared between add-ons, meaning much more efficient add-ons and code that is much easier to understand.
I find it much harder to understand shared code.
Currently just for me, but it will likely be opened up to other developers later.@Jon W, are you create this add-on only as a core for own add-ons or as base core for other developers?
I think useless is a bit strong. When XenForo was first released, there was very little documentation for developers or PHPDoc comments, but it offered something not available elsewhere and was well coded, and that made it attractive to developers. That being said, I'm more than happy to make improvements to code to help other developers. I also have a separate add-on which I haven't yet released which contains a number of tools that makes developing add-ons for Cake incredibly easy (i.e., tools for creating and working with modules, etc.).Because I think such add-on will be useless for developers without documentation of API and without PHPDoc comments (like right now).
These questions have been answered in the first post.What?
What problems resolves add-on?
How?
How exactly it works?
There is no must. It is completely up to developers whether or not they see any value in using it. Given that there is a cost to it for end users, I suspect that a vast majority of developers will not use Cake for their add-ons, but only time will tell.Why?
Why other developers must use it?
Please add this in the first post and in the add-on description.Currently just for me
Documentation - yes. But PHPDoc comments were from start in XenForo. XenForo has well coded sources with PHPDoc comments, so documentation was not needed for me.When XenForo was first released, there was very little documentation for developers or PHPDoc comments,
Right now good add-ons do not load any redundant files and template modifications
- only enable the modules you need, meaning your site doesn't load redundant files, template modifications, etc.;
This is feature for developers or for regular users? Because for developers your add-on is one more level of abstraction without documentation and regular users usually do not look into the code.
- code is much easier to read/understand as you can see which feature each block of code relates to.
Assuming you want all the features of an add-on. Even turning off an option in the control panel isn't going to stop a template modification from being processed if it is part of an add-on. Having it as a separate module that can not even be installed is the best way to manage this other than having to have several different interdependent add-ons.Right now good add-ons do not load any redundant files and template modifications
Again, mainly for me at the moment. If I'm going to translate an add-on to make it work with XenForo 2.0, it needs to be easy for me to read. A side effect of that is that it would also be good for other developers, but as I've mentioned before this is not yet a main priority. Regular users who have some understanding of code may also find this beneficial.This is feature for developers or for regular users? Because for developers your add-on is one more level of abstraction without documentation and regular users usually do not look into the code.
Which "slogan" is not correct?I understand that the advertising slogans one of the main things in sales. But your slogans are not fully correct.
All add-ons already have the cost of XenForo attached to them, but I do agree with you. Personally I would have exactly the same attitude, unless of course I was wanting to extend a paid add-on, like how [AD] Credits extends your paid add-on. But then I am running a company, not doing this as a hobby.Personally I can't ever imagine releasing an add-on which would be dependent on a paid, branded, third party add-on.
I can see how it's worth you having a common core for all of your add-ons but I can't see how it benefits other developers, considering anything they release is going to have an immediate cost associated with it, but not one they will personally benefit from.
Thanks for signing up. Hoping to get back to work on Cake next week.Signed up. I like cake. Presumably one advantage will be that the css and JS for several addons will be combined now.
We use essential cookies to make this site work, and optional cookies to enhance your experience.