Hi,
I am taking a close look at COOK with a free account and so far I love what I see.

I have a couple of questions about component development in COOK and custom coding control before I make further decisions about subscription...

1/ When I need to change the automatic generated code from COOK to custom code (i.e. changing model or view files, etc), does COOK control these code modifications or is this something I have to control after I download my component?

2/ If I need to do an update in COOK (after I make modifications to code), what is the recommended system for integrating my custom code changes? SVN control? Or is this integrated in COOK?

Sorry if my questions appear basic, but I am not sure if I am missing out on additional features in COOK without a subscription.

Many thanks.
Dan

1/ No, you have to control it
2/ SVN is cool, but one of the member here has developped an app worth checking out.
www.j-cook.pro/forum/15-reviews-experien...-was-born-last-night

Yes, I know,

A kind of cool versioning system can be appreciated. It is a big job but really necessary.

About versioning, we have talked here few times, there are 2 possible uses.

- DB versioning item for the component itself (like a wiki, or a collaborative component)
- File versioning for the component developer (you), in order to apply the changes to the new generated component.

I never worked with that, even github or such technology, so I am really limited to this, and this one of the reasons why it take time.

I cannot promise anything for the moment.

If you know some nice lessons or tutos to undersand file versioning (and also PHP techniques to code a part in the component for wiki-like creations), ...

I am very interresed to learn.

You know, one very easy way to do versioning (at least being able to revert back) is to use dropbox...
Anyway, i also use Beyond Compare when i re-download the component, and use template overrides for the views