Hi @admin and fellow cooks,

I'm in the middle of quite a large component for J2.5 so I just wanted to check whether or not there is a definitive date by which V2.0 will be stable and production ready?

Also, I've a couple of questions relating to the new config options in the builder, namely, DB Automations & Features.

1. DB Automations - The 2 options in the select are Model & Table. I just wondered whether you could clarify the differences, advantages/drawbacks of each? Also, I was expecting the options to be Model & Controller, as opposed to Model & Table. I'm unsure whether this is relevant but, it's my understanding that in an MVC, as a rule, there should be 'thin' controllers and 'fat' models which would suggest to me that DB automations should almost always go into the model
2. Features - there are 3 options here, of which the first 2 (Reduced & JDom Complete) seem self-explanatory. Presumably, reduced = only necessary JDom classes and complete = all JDom classes, right? If so, I just wondered whether you could explain what Maximum includes?

Any clarification on this would be much appreciated!

Thanks again for this wonderful component!!!

Gez

As for DB Automatims, look at :
www.j-cook.pro/forum/7-design-your-appli.../3482-db-automatisms

Well, since few days, the 'new tickets' has been quiet. I am processing the last issues, then I will annouce publicly the release in newsletter.

V2.0 is becoming stable and I think winthing 15 days, it will be ok.

For production, 2.0 is already safer than 1.5 in terms of security.
About issues, it is almost good.


DB automations is really not relevant. Choose 'Table', I think it is better.
It determines where to write some functionalities. For example the initialization of 'creation date'.

If you put it in table, it will always be called.
If you put in model, you can have a better cusomization if you want to bypass this code for particular reason.

Features :
Your component is reduced to the strict necessary.
When you generate a 'Hello World' component, you do not need the 'classes/upload.php', for example.
If you think an issue about files (your component is missing something), you can try 'Maximum' :
- All the possibles functionalities will be written in the models and controllers.
- All the avalaible classes files and helper will be included

You can also ask only for JDom in complete version. This is good when you want to create a new JDom class and you want to know if the namespace you want to create is available or not.


Comming very soon is another custom :
Form style :
It will determines how to write the form
- JForm foreach loop (Recommendated)
- JForm individual calls
- JDom alone (maybe not) Still using JForms, but not for displaying.

With this option you will be able to choose between a condensed way, or an exploded way to list the fields, so it is much more better to customize.

My advice, you can generate 2 times with 2 different options, and then you can use a method for some pages and other method for other pages.
For example, always use the condensed way, and if you want some exploded fields in some pages (individual templating possible), then only copy the form template file from the second component generated with the exploded option.
Because if you choose 'Exploded', all forms will be exploded, and you will really get bored.
If you use the exploded way, every time you add a field in the xml file, you will have to add it in the template file.

Please do not use the exploded style ONLY to apply a class name or other stupitity that can be handled in native. Have a look in JDom, it is really extensible and customizable.
Then, you only have to write in the XML file.
I will explain further how to add a JDom parameter, callable directly from XML form file.

JDom alone, is not recommended. But it can be usefull to understand how to call a JDom call of any type.
So, you can use this function to debug, or anything else (for example, then you copy the source to use somewhere else)
This option is not for production. Deprecated, and used ONLY for developper.

Thanks for the detailled explanation!

Hi @admin,

I just wondered about some of the forthcoming changes that you are implementing in V2.0.

1. Will publishing wizard account for trashed and archived items too and if so, will it be handling the insertion of a related button in fly, form and grids? Also, will the field change its auto-name to state?
2. Regarding filters, will publishing fields be fixed in combo filters?

Also, and more generally, would you be able to share a list of other features/fixes and so on that will be included in the release?

Many thanks,

Gez

Just a quick follow up to this:

I just wondered, regarding submit all groups option in ajax combo filters;

I've just been testing to see if this feature actually filters results based on each stage of filtering - I mean, in my case, I have specified groupby 1 = Category, groupby2 = section.

It hasn't been working but, also, I didn't actually have the section and category on my grid, so I thought I'd give it a go. So, I added the section/category columns to the grid.

In sandbox the filters refresh the page but the filter is nulled once the page has reloaded. I double checked and this happens for all combos in sandbox. However, this is not the case locally.

In local, the page refreshes after each group as expected except that it does not filter results by the submitted group until you submit the final one.

Just to clarify, this is not a ticket as I know that you (@admin) are working on filters for 2.0 however, I just wondered if there was a patch that hasn't yet been applied to the sandbox that is rendering filters in download builds?

Thanks,

Gez