Hi, I made a component with 2.0 beta and now I've come to CMS. I changed into a form a combo for radiobox and to compile and test in sandbox changes are not, what should be the problem?, Thanks.

If I restart in 2.0 Beta appears again if the radius box.

I will only solve the issues in 2.5, now.

Did you tried there ?
I know it is bit buggy for the moment. The builder interface is lacking.

Since Cook 2.5, (in order to optimize performances), you must click on 'Preview' on the top of the form to see the control choice.

All this will be re arranged, to have a 'easy-to-build' interface.
Now Cook is making a real distinction between the data and the control (still confusing in Joomla).
And this is why JDom is used. To abstract control from data source.

Also, you can also define the control to use in the properties box.

Anyway, in case of problem, just make the change in your XML file :
replace :
type="ckcombo"

to:
type="ckradio"

If you deal direct to JDom :
replace JDom::_('html.form.input.combo', ...)

to:
replace JDom::_('html.form.input.radio', ...)

When I say the builder interface is lacking, it is because I extended the features but my MooTools builder (your favorite tool), is going to its limits.
I will rewrite it when I can.
For N-M feature, it is the same : I am only limited by the JS interface (adding new drag/drop structure, ...)

In the builder :
- The previews of your form fields are not loading assets correctly or CSS is buggy, (jQuery/MooTools together)
- Changing combo to radio sometimes do not keep changes because you have to switch 2 times to make him remembering your changes (Strange behaviors..)
- Not all controls are available (not curated job, I recognize)

Ok, understood thanks.

The new version of j-cook.net this operation to work?.

How I can make the migration from the current to the new?.

I can lose my projects?.

I have to start a new project, if you start at j-cook.pro be available in j-cook.net?, Thanks.

I tried to test in chrome and obtendo this error:

Your browser is not supported. Please use Chrome (recommended) or Firefox

You must create your projects in j-cook.pro

Then I will clone the beta for you.
Lately I didn't cloned it, so it is normal if you do not see your projects.

You will lost your changes if you create under beta 2.5

I may clone tonight.

This is what I have on both platforms, tell me if I will continue to keep all or is there something to be deleted during the migration and where I work from today, thanks.

2.5 beta is CLONED from www.j-cook.pro

So you will obtain a copy of your projects from .PRO
If you change anything in beta (to try), then those changes will be overriden by the next clone.

I do not clone everyday in facts.

You have asked a lot of questions lately, can I ask you gently to reduce the quantity of your posts, even if they are very usefull fo me too. I do not ask you to stop contributing and reviewing. Really thank you.
There is nothing against you, only that I would like to treat older posts.
I treat the last arrived first (LIFO) and then go back in time. Almost 3 months of posts are stacked I have to read them all and fix.
My priority are also the posts concerning 2.5 beta, posted after the 27th of May... Anyway...

Hope you understand.
Take it easy, if there was something bad I would not have answered so fast.

Kind regards
J.

I understand completely, but due to the possibility of a project being deleted because I've been nervous. Also, I'm new and I paid good components with you and so I have many doubts.

Since then, I congratulate him on his j-cook, is wonderful (although there are still things to debug).

Nevertheless, I understand quite well that will happen or has happened.

One last question very directly, I work in j-cook.net from now?.
I have the j-cook.pro projects and have made ​​many changes, you can go to j-cook.net?.

In short, if I have to work on j-cook.net, then clone the project and forget about j-cook.pro.

Thank you.

Until the 15th of June, it is still possible to download in the old version. This is why the idea is to still keep it alive, so the .PRO is still the main user database.

I have cloned .NET, for you this morning.
It mean that you can now see your last changes done in .PRO, visible in .NET (copy)
Now, you can download in .NET and see the source.

If you change something in .NET (for example you add a filter, or a field in form, change properties....) All this you can do freely, but at the next clone, you will lost them. So if you want to modify important stuff, do it in .PRO

I know it is a bit strange but with my limited knowledge, it is the best I could do for the moment for this important migration.

For example, if you want to try the new State filter, you can but you can only try it from .NEt because it does not exists under 2.0 (.PRO)

It means, you cannot really instance State filter in .PRO and everytime you want to download in .NEt, you must recreate it if the clone has occured.

.NET beta is only for you to check the new code, and for you to start forking your projects.
I don't know if you already started to custom your component under 2.0 (I guess not if you are new here)

Forking means that now you must separate your custom in the way it is explained. A kind of Cook standard for developping fast and efficiently.

I invite you to read this doc :
www.j-cook.net/index.php/f/forks


Last but not least :
The support forum is free for all. I voluntary do not see from the forum if you have paid or not. It is my philosophy. When you tell me that you can download, it always means that you have paid something.

Ok, all understood.

Again I congratulate the tool created and see that it still continues to outperform, thanks.

By the way, I paid a year and six months I think.