Port API packages from CMS

[mbabker]

There are some API wrappers written over the last couple of years that were contributed to the Platform and CMS (all now reside in the CMS) that aren't present here. Where able, we should reach out to those contributors to see if they're willing to port those packages into the Framework. If they're unable, this could be a good project for someone who is interested in becoming more familiar with namespacing code that previously wasn't.

• Mediawiki (JMediawiki Package for Joomla joomla-platform#1624) - GSoC 2012 project from Prasath Nadarajah
• Microdata (JMicrodata library and tests joomla-cms#1967) - GSoC 2013 project from Pruteanu Alexandru
• OpenStreetMap (JOpenstreetmap Package joomla-platform#1786) - Buddhima Wijeweera
• Cloud Storage APIs (Note - These are still pending review and acceptance by the CMS) (Amazon S3 and Rackspace packages joomla-cms#1925 and Google Cloud Storage package joomla-cms#2017) - GSoC 2013 project from Alex Martin

[eddieajau]

None of those seem particularly well represented on Packagist so it would be good for us to pick them up. Something to would be is there a support package for API where we can suck out the common code.

[piotr-cz]

The JForm package has got some new - cool functionality: GSOC Project 'Improve Form Fields'.

[eddieajau]

I think we should have a "meeting" about what to do with the Form package. I think we need a good plan about how to build it better.

[mbabker]

Agreed. As it stands today, it's really a relic of CMS style development. There's certainly use for a Form package in our Framework, but not in the current shape it's in.

[piotr-cz]

I really like the Form package, but not having an easy option to override Fields HTML output drives me crazy.

[abemedia]

I'd be happy to bring the Form package up to scratch as I already have made various amendments on my local version. Should I include all the new fields introduced in joomla/joomla-cms#1842?
I however prefer the XML attribute for the placeholder to be called placeholder rather than hint.

[piotr-cz]

@abemedia There was a discussion about refactoring the Form package: #303

Personally I like how Symfony2 is using special attributes because you may stick anything inside:

public function buildForm(FormBuilderInterface $builder, array $options)
{
    $builder->add('field', 'type', array(
        'label' => 'fieldLabel',
        'required' => true,
        'attr' => array(
           'placeholder' => 'Field placeholder'
        )
    ));
}

BTW new home for Form is here: https://github.com/joomla-framework/form and I think that and the Framework User group are propitiate places for discussion.

[abemedia]

@piotr-cz Thanks for the pointers. Have posted in the group.

[abemedia]

And yes I definitely like that with the attributes! I was just thinking about how best to go about data-attributes but that approach is perfect.

[spignataro]

This looks to have been not made it in the Joomla! 3.3 package - yet advertised it is. Is there a reason why?

[bweston92]

@piotr-cz and the fact you can't change the form control (i.e jform) after the form instance in created, that drives me crazy.