some changes for work with params

most of changes have effect in view translate layout edit

in view translate layout edit:
	we can now work with JForm, used for Parameters and at this moment for field 'category' (in contentelemtnt content)

in view translate layout default:
	add org language filter
	for native translation i have change the function createContentSQL() and countContentSQL() in ContentElement.php
			
		to get all items also for different languages
			not only selected language and * 
			
			an example:
			
			we have two user
			1. User : write in en-GB
			2. User : write in de-DE
			
			both Users create an article 1.User over monkeys in en-GB
			 the 2.User over flowers in de-DE and also create an article over buildings in *
			and after create 
			what we want to see in the overview
			
			1. User want to translate the flowers. See the user it whitout the changes belowabove?
			
			extend the #__jf_translationmap with field org_reference_id ?
			or extend the #__jf_translationmap with field time-stamp?
			example:
			we have an 3. User: write in it-IT
			what article will display here in overview? 
			both english and german?
			only german?
			only english?
			
			and which is the base article to translate?
			
			what is if the users have create and translate the articles without joomfish
			make an extra view for manuel set translationmap? (see under)

	also add an new view translationmap (startpoint is in view translate layout default only have is an field 'language') to set translationmap manual 
	if we have existing j1.6/2.5 translation not make with joomfish

contentelement categories:
	add field extension and filter extension and also in xml '<filter>c.id > 1 </filter>' to hide the root


Fix for editTranslation if new and apply


other way for 3rd party where want use contentelements and TranslationObject:
	for this i have add in classes/JoomfishManager.class.php
	includePaths can set over JoomfishManager or request
	
	have add functions to load contentelements over request.
	and can load other path over the xml (contentelement )
		<treatment>	
			is not needed if use in ContentElement.php getTranslationObjectClass
			<translationObject>TranslationObjectContent</translationObject>
			is not needed if use in ContentElement.php getTranslateFormsClass
			<translateForms>TranslateFormsContent</translateForms>
			
			see also comment in ContentElement.php
			
			for other paths we can add in the treatment
			
			<includePath>relative to JPATH_ROOT</includePath>
			or 
			<includePath extension="1" site="0">jf</includePath>
			<extension>com_content</extension>
		<treatment>
	ContentElement,TranslationFilter,TranslateForms,TranslateModel,TranslationObject and TranslateParams
	can load over the treatment->includePath
	(see in JoomfishManager function _loadContentElements(), ContentElement function getTranslationObjectClass(), TranslationFilter function getTranslationFilters() )
	
	so developer of other components there use joomfish must not copy all the needed files
	or can create some on the fly if needed.
	



others:

folder contentelements moved to models/jf/xmls

all Filters (also TranslationFilter.php) is moved from contentelements and models to models/jf/filters
all Filters in seperate files

all TranslateParams is moved from models to models/jf/params
all TranslateParams in seperate files

created models/jf/forms
and created TranslateForms all in seperate files

created models/jf/models
and created TranslateModel all in seperate files

created models/jf/models
and created TranslateModel all in seperate files

all Objects is moved from models to models/jf/objects
all TranslationObject in seperate files

moved ContentElement.php, ContentElementTable.php and ContentElementTableField.php to models/jf/element

all above is do for easy find the classes and files
for work with 'params' 
and also other special fields like 'category' (use JForm for output like params)


make category field work (over new TranslateForms)

The params and field category work and save
but only Content, Menus and Modules at this moment work with the new classes (TranslateParams, TranslateForms) 
for the other components the work must done.


Fix for editTranslation if new and apply

add org language filter and fix countContentSQL and createContentSQL (only for native)

add an manual translationmap view to set translationmap manual if we have existing j1.6/2.5 translation not make with joomfish

also change some double space with tab