Man I can't say how much i'm impressed.
This Fork thing would be THE killer feature for me right now.

You will not be able to upload in j-cook.pro.

'Fork Engine' is not a real fork (like a Git system)

Here how it works :
Every available PHP Class has an empty override.
Every single function you have customizated, can be copied in the overload class (fork)
When you reinstall a new generated component, the fork drectory is kept and your component is forked. It works like a charm.
JDom, Css and templates has also overrides (only few things are missing)

Then, when you want to go for production, you can find your changes and replace the original code (for optimization of performances, maybe for a better code, for cleaning and removing this duplicates of files)
I have also created an engine that is merging the forks automatically, but I cannot release it for the moment.

There are some limitations in this system. Because when you call parent::sameFuction(), it create a big problem because you call the original and not the parent of the original. So I sorted out with some tricks for that. I will explain it better in future.

Anyway, the source looks really something new and tricky, but the comfort is amazing. I boosted the dev part once again, and you will too. The only thing is that it is adding more files in your component, but at least all your changes are compilated in one folder. And the forked classes are containing ONLY the functions you have forked.

EDIT :
And also, of course, when you do not need to override a class, you do not need the empty file to be present. In the fork directory, you only have the forked classes files. Cook is generating empty classes for you, but you do not keep them in the component if you do not use them. Every class is checking the presence of an override.

Hope to see this quickly, but rock solid stable is more important.
What about Toulouse ? Going or not ?

Thanks @ admin for the clarification! and K+2 for all of your hard work!!!

Gez

Yes I go in Toulouse, but only for a workshop on sunday.
I am not sponsor this year because everything went too fast and I didn't had time to put energy in.

Joomla day is attracting a lot of 'final users' and much less component developpers, so it is sometime frustrating for users who think Cook is doing the same than a CCK. Cook can generate components without coding, but not really a lot, because a custom is always necessary somewhere and CCK are much better finition for non developers.

Vinz, are you comming ?

EDIT :
Pour celles et ceux qui parlent la langue de Molière :
www.joomladay.fr/programme-du-weekend.html

Baby if you're going, i'm coming but for the two days i believe. Well we're off topic, will send you a mail about it.

Admin said on the 10th of Jan that the J3.0 version would be '15 days I think'. It has now been that 15 and another 15 days and then another 15 days on top of that. I thought you were French, not Spanish. Any news?

It's coming, please be patient!

I was chatting to Jocelyn recently about what's been involved and still I can't really comprehend exactly how much work and love is going into it!

Please just think how much work would be involved to write a J!1.6-3.0 component would be alone, then consider that the framework on which the builder sits has to be able to dynamically suck in all of your configuration options, write out your component practically line by line with lots and lots of evaluation on each before rendering your finished component!

That's a hell of a lot of work!!!

Thanks,

Gez

audibleid wrote: +1 from me

Just try to update your Joomla 2.5 component to 3.0 manually and you will understand...

We could have two scenarios here
1) Admin makes a Joomla 3.x compatible build... - and you have to recreate all of your projects...
2) We continue to wait patiently and our J1.6 - 2.5 components seamlessly upgrade to 3.0 - Just as they did for our 1.5 builds

Just be thankful that Admin is taking the time to make Cook Joomla 3.x ready and backward compatible. (I certainly am)

Exactly it is a hell of work, I realize it doing it. I was either not counsious of that, so I cannot estimate the deadline precise.

I can tell you I am finishing the IU part, so it means we are close to the goal, but I know there are some details more too in the core and MVC to finish as well.

Yes, in fact if you are patient, you will get a component that is compatible 3.0 and compatible since 1.6.

It means that the standard is 3.0 now and the functions and classes missing are included for previous versions.

And when you migrate from 2.5 to 3.0 it is a lot of changes, but to carry a 3.0 component on the 1.6 version, this is another story... For Joomla 1.5 it is absolutly impossible, but 1.6 is enough close to 3.0 to make it possible.

Anyway, the layer managing the cross version is included for you and you will finally understand what comfort is.
The forking feature is as well a feature you will never regret your patience.

My objective is to not ask you 2 migrations in future. This coming migration for your component will be the last.
After that, with the FORK feature, when Cook will evolve, are be able to evolve your component in the same time.
Not absolute science, but for sure, 98% without bugs (the versioning and changelog will be documented to help you better).

A word about JDom :
I keep JDom for meany reasons and one of these reasons is also because when JDom improve, you just download the last version and use it in all your components easily.

Long is the road.

Indeed, the road is long but thankfully you keep tuning up our engine so we're always getting to our destination that much faster!!!

The people paying for subscription for your services are entitled to know when updates are likely to be released, would you not agree? I read your 'News' section and see that the most recent article is about JQuery being added, which I'm sure is about 6 months old.
I'm sorry to say that although I love your application, in terms of updates or even news on when updates will arrive, its not very good.
The N:N functionality which I among many people are crying out for has been promised for a long time, but nothing ever materialises.
Would it be possible to add a roadmap providing us with some idea about when we can expect J3.0 to be supported as well as long-promised features such as N:N support? By just replying to forum posts with 'we're working on it and it'll be ready as soon as possible' your customers are inclined to believe (as I do) that no progress is being made at all towards these goals and that our subscription will expire before there are any updates to the service.

www.j-cook.pro/forum/14-news-a-chillout/...tarting-blocks-#7095

@andypooz,

Please don't be so hard on me.
To my point of view, you pay the correct price for a service wich is not completly finished.

Stay in touch and you can also try the beta tests : www.j-cook.net

N:M will come but not now. The reason is simple : I must rewrite the builder interface for this. And this 2.5 release is not a javascript rewrite. (The builder interface is unchanged)

For the moment Cook is for developpers and curious who want to try. Did you realised Cook never did advertisement until now ? (Even cancelling my presence to the Joomla day events)

Because if I promote more, I will receive more comments like yours.
I must continue my work now.

Admin, you are doing an excellent work, and we all developers/jcook users know you are working hard to provide the best.
unfortunately only developers (who really puts the hands on the code) can understand how hard it is, and how the things could be planned but at the end there is always something more to develop on an endless loop.
thank you.

I agree with Andypooz, it would be nice to have a roadmap and know when a new release should come, but I also know, sometimes that's not easy to schedule and mainly when the development team is very small (I guess the Admin is a "one man band" like many of us).
I'm looking forward to work on the new jcook.