Hello

Congratulations on this new and improved builder.

I do not know if I am the only one who has j-cook legacy projects still in the pipeline. But I am finding it overly difficult to complete certain features which were well advanced in the old framework.

Although the new builder is almost ready, I am requesting that the j-cook.pro builder be made accessible again for a little while longer to allow the members of the community to migrate their projects and more importantly their thinking to the new framework.

We would not accept the excuse that our job will be late because the worker's saw was broken. By the same token, we could never venture to tell the client that the project changes maybe two -three weeks late because the builder is new and we are still porting all the features they saw last week to the new framework.

If we understand that not all of us use the j-cook platform for mental stimulation, and consider those who use if for incomes which support families, it would become evident that the migration of the framework is but the first step in the move to j-cook dot net. The community and its projects comprise a separate and distinct entity which has its own inertia.

I am not requesting an open ticket with no end in sight, just a slower migration of the community itself to facilitate projects which are near completion in the old framework.

Of course, one can ask which projects? How can we know which ones are near completion? The short answer is we don't know, but we can remove the option to create new projects in the old framework and then monitor the usage of the two sites and decide on some cutoff point [30% to 70%] or whatever is reasonable. It can also be stated that the access comes without support of any kind since Admin has stated that he works alone.

This is becoming lengthy so I will end it here and let the community judge the merits of my submission.

Regards
v