[wp-hackers] [GSoC] Inline editing idea

Janneke Van Dorpe jannekevandorpe at gmail.com
Wed Feb 26 19:24:45 UTC 2014


TinyMCE is used is because that's what core uses. Using a different editor would mean changing a lot of code, used for both the front- and back-end editor, that assumes TinyMCE. You can't just replace TinyMCE with another editor without breaking things.
The design of your editor is not really a good argument, it gets changed anyway. :)

Janneke

On 26 Feb 2014, at 19:11, Stefan Neculai <stefan.neculai at gmail.com> wrote:

> I do agree and I really like your work on it. I see that you are currently using TinyMCE there and I believe that Froala Editor would fit better for few reasons. First of all it’s lightweight and it offers all basic functionality that TinyMCE comes with too, but in addition it’s the first editor that supports image resize on mobile devices. Also, you can’t ignore the nice flat design from inline mode. 
> 
> Moreover, I will offer all my support to make the editor fit the requirements and do any necessary changes to make it fit the plugin. Can we talk more about it on Skype (my Skype id is in the signature)?
> 
> 
> Stefan Neculai
> Skype: stefanneculai
> 
> On Feb 26, 2014, at 8:49 PM, Janneke Van Dorpe <jannekevandorpe at gmail.com> wrote:
> 
>> Someone doing that as a GSoC project is probably not a good idea since there are already several solutions, one of which, as John pointed out, is a potential feature developed as a plugin that I'm working on.
>> 
>> If anyone is interested in developing a Front-end editor, let's work together on this rather than starting similar projects independently. I'm not saying this plugin is *the* solution. It's always good to look at other approaches. It would just be better to have only one project with good discussions and communication, even if that means creating more than one plugin or branch.
>> 
>> The plugin can be found on wordpress.org (http://wordpress.org/plugins/wp-front-end-editor/) and is developed on GitHub (https://github.com/avryl/wp-front-end-editor).
>> 
>> Janneke
>> 
>> On 26 Feb 2014, at 15:00, Stefan Neculai <stefan.neculai at gmail.com> wrote:
>> 
>>> We are willing to offer a license that allow all Wordpress users to use it for free current and all further improved versions - as far as I know this would be compliant with the GPL license. Would that work?
>>> 
>>> What would be the steps involved in order to get it from a plugin to a core feature?
>>> 
>>> Do you think it would work as a GSoC project?
>>> 
>>> Thanks,
>>> Stefan
>>> 
>>> On Feb 26, 2014, at 4:35 PM, Eric Hendrix <hendronix at gmail.com> wrote:
>>> 
>>>> I should say that successful implementations of the front-end editor are
>>>> new (like Concrete5). Don't mean to jump in the middle of your conversation
>>>> Madalin, but it's an open discussion.
>>>> 
>>>> 
>>>> On Wed, Feb 26, 2014 at 9:33 AM, Madalin Ignisca
>>>> <madalin.ignisca at gmail.com>wrote:
>>>> 
>>>>> I was searching my brain to remember that one John, that is really one I
>>>>> like.
>>>>> 
>>>>> 
>>>>> On Wed, Feb 26, 2014 at 4:30 PM, John Blackbourn
>>>>> <johnbillion+wp at gmail.com>wrote:
>>>>> 
>>>>>> There is currently a Front End Editor plugin in progress, which is
>>>>>> being developed as a feature as a plugin:
>>>>>> http://wptavern.com/wordpress-front-end-editor-plugin-gets-major-updates
>>>>>> . This means the plugin is being developed with an eye on potentially
>>>>>> being included in WordPress core at some point in the future. More
>>>>>> info: http://make.wordpress.org/core/features-as-plugins/
>>>>>> 
>>>>>> Of course, it doesn't mean you shouldn't tackle a new approach yourself!
>>>>>> 
>>>>>> John
>>>>>> 
>>>>>> On 26 February 2014 14:12, Eric Hendrix <hendronix at gmail.com> wrote:
>>>>>>> Front-end editing is a relatively new implementation for WordPress,
>>>>> much
>>>>>> like Concrete5's WYSIWYG solutions.
>>>>>>> 
>>>>>>> 
>>>>>>> I'm interested.
>>>>>>> Eric A. Hendrix
>>>>>>> 308 McFadyen Drive
>>>>>>> Fayetteville, NC
>>>>>>> 28314
>>>>>>> 910.644.8940
>>>>>>> Hendronix at gmail.com
>>>>>>> www.hendronix.com
>>>>>>> 
>>>>>>> On Wed, Feb 26, 2014 at 9:09 AM, Madalin Ignisca
>>>>>>> <madalin.ignisca at gmail.com> wrote:
>>>>>>> 
>>>>>>>> If you'd like to collaborate with somebody to release a plugin for
>>>>> your
>>>>>>>> editor, you need to release a GPL 2/3 compatible version to comply
>>>>> with
>>>>>>>> WordPress and a question would be, what advantages would it offer
>>>>> above
>>>>>>>> other popular solutions already implemented.
>>>>>>>> On Wed, Feb 26, 2014 at 3:04 PM, Stefan Neculai <
>>>>>> stefan.neculai at gmail.com>wrote:
>>>>>>>>> Hello everyone,
>>>>>>>>> 
>>>>>>>>> First of all, I'm not a student. I just want to propose an idea for
>>>>>> this
>>>>>>>>> GSoC: "Inline editing of posts directly on any page.".
>>>>>>>>> 
>>>>>>>>> I'm co-founder of Froala Editor (http://editor.froala.com) and I
>>>>> think
>>>>>>>>> that our inline mode of the editor would work very well with
>>>>>> Wordpress. The
>>>>>>>>> main idea is to allow people to edit their posts directly on the
>>>>>> webpage
>>>>>>>>> without having to go to the admin interface. Don't worry about the
>>>>>> license,
>>>>>>>>> we can update it to allow Wordpress users to use it for free and
>>>>>> overcome
>>>>>>>>> any legal issues related to it.
>>>>>>>>> 
>>>>>>>>> Short bio about me:
>>>>>>>>> http://linkedin.com/in/stefanneculai
>>>>>>>>> https://github.com/stefanneculai
>>>>>>>>> 
>>>>>>>>> I can help mentoring it and I am willing to support any changes
>>>>>> required
>>>>>>>>> to the editor to make it Wordpress compliant. Looking forward to hear
>>>>>> from
>>>>>>>>> you.
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> Stefan
>>>>>>>>> 
>>>>>>>>> _______________________________________________
>>>>>>>>> wp-hackers mailing list
>>>>>>>>> wp-hackers at lists.automattic.com
>>>>>>>>> http://lists.automattic.com/mailman/listinfo/wp-hackers
>>>>>>>>> 
>>>>>>>> --
>>>>>>>> *Madalin Ignisca*
>>>>>>>> *web developer*
>>>>>>>> http://imadalin.ro/
>>>>>>>> _______________________________________________
>>>>>>>> wp-hackers mailing list
>>>>>>>> wp-hackers at lists.automattic.com
>>>>>>>> http://lists.automattic.com/mailman/listinfo/wp-hackers
>>>>>>> _______________________________________________
>>>>>>> wp-hackers mailing list
>>>>>>> wp-hackers at lists.automattic.com
>>>>>>> http://lists.automattic.com/mailman/listinfo/wp-hackers
>>>>>> _______________________________________________
>>>>>> wp-hackers mailing list
>>>>>> wp-hackers at lists.automattic.com
>>>>>> http://lists.automattic.com/mailman/listinfo/wp-hackers
>>>>>> 
>>>>> 
>>>>> 
>>>>> 
>>>>> --
>>>>> *Madalin Ignisca*
>>>>> *web developer*
>>>>> http://imadalin.ro/
>>>>> _______________________________________________
>>>>> wp-hackers mailing list
>>>>> wp-hackers at lists.automattic.com
>>>>> http://lists.automattic.com/mailman/listinfo/wp-hackers
>>>>> 
>>>> 
>>>> 
>>>> 
>>>> -- 
>>>> *Eric A. Hendrix*
>>>> hendronix at gmail.com
>>>> (910) 644-8940
>>>> 
>>>> *"Non Timebo Mala"*
>>>> _______________________________________________
>>>> wp-hackers mailing list
>>>> wp-hackers at lists.automattic.com
>>>> http://lists.automattic.com/mailman/listinfo/wp-hackers
>>> 
>>> _______________________________________________
>>> wp-hackers mailing list
>>> wp-hackers at lists.automattic.com
>>> http://lists.automattic.com/mailman/listinfo/wp-hackers
>> 
>> _______________________________________________
>> wp-hackers mailing list
>> wp-hackers at lists.automattic.com
>> http://lists.automattic.com/mailman/listinfo/wp-hackers
> 
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers



More information about the wp-hackers mailing list