ask for test html editor plugin

[Hiep Lq]

Hi Community.

I just complete a editor for input html text base on ckEditor

I also document about it here http://wiki.idempiere.org/en/Plugin:_CKEditor

by limit from core, it's not seamless install to system without touch database server and run migrate script

if you want to know about limit, please read chat here http://www.globalqss.com/idempiere/irclog/%23idempiere.2017-03-29.log.html

so i deploy a test server here: https://test.hasuvimex.vn/webui/index.zul

and just configuration for field Description of window sale order

welcome you experience to report issue, and contribute idea to improve.

[Hiep Lq]

some update make it more attractive and flexible

http://wiki.idempiere.org/en/Plugin:_CKEditor#Update 

[Carlos Antonio Ruiz Gomez]

Excellent Hiep, thanks for your contribution.

Notes from my test:

1 - Context menu is lost (Value Preference / Change Log)

2 - Would be nice to have a way to view/edit the source?

3 - The toolbar could have more stuff, or make it configurable?
for example in an editor I like to have:
- undo
- redo
- find
- replace
- select all
- blockquote
- justify ...
- insert link
- insert image
- insert special char
- insert table
- maximize

4 - The field is not respecting the definition of the number of lines in AD_Field, it just grows in size according to its content.
I think it would be better to keep the size fixed as defined in field and have a scrollbar.

5 - When showing in grid is too big also - I think in grid it must show just one line, like the actual big text fields

6 - On Find window is showing also the field as an HTML editor - is that OK?  I think because of that you cannot search things with LIKE starting with %

7 - There is no control or warning when the editor content is bigger than the allowed size of the column, it just trim it when saving without a notification to the user

8 - After stabilization this would be very nice to have in core.  We can add also the IsHtml to AD_Field and AD_UserDef_Field


Regards,

Carlos Ruiz



El 05/04/17 a las 05:49, 'Hiep Lq' via iDempiere escribió:

[Hiep Lq]

Thanks for your feedback

On Wed, Apr 5, 2017 at 3:36 PM, Carlos Antonio Ruiz Gomez <car...@gmail.com> wrote:

Excellent Hiep, thanks for your contribution.

Notes from my test:

1 - Context menu is lost (Value Preference / Change Log)

 

it should be add next release  

2 - Would be nice to have a way to view/edit the source?

it's on my mind https://github.com/hieplq/zkckeditor/issues

 

3 - The toolbar could have more stuff, or make it configurable?
for example in an editor I like to have:
- undo
- redo
- find
- replace
- select all
- blockquote
- justify ...
- insert link
- insert image
- insert special char
- insert table
- maximize

it on my mind, do it after IDEMPIERE-3323 i don't want to create new column for each option of each editor. 

4 - The field is not respecting the definition of the number of lines in AD_Field, it just grows in size according to its content.
I think it would be better to keep the size fixed as defined in field and have a scrollbar.

it should be on next version  

5 - When showing in grid is too big also - I think in grid it must show just one line, like the actual big text fields

I forgot this mode, will fix on next version 

6 - On Find window is showing also the field as an HTML editor - is that OK?  I think because of that you cannot search things with LIKE starting with %

value store on database like string, so can be search with LIKE. 

but some time it make user confuse, because when they seach for div, almost record will return

i think better don't allow search with field use long text and html

7 - There is no control or warning when the editor content is bigger than the allowed size of the column, it just trim it when saving without a notification to the user

will get html source to count max character. just allow save after user make it <= max leng.

shouldn't auto trim, because it maybe break html format

 

8 - After stabilization this would be very nice to have in core.  We can add also the IsHtml to AD_Field and AD_UserDef_Field

it's great. 

Regards,

Carlos Ruiz



El 05/04/17 a las 05:49, 'Hiep Lq' via iDempiere escribió:

some update make it more attractive and flexible

http://wiki.idempiere.org/en/Plugin:_CKEditor#Update 

On Sunday, April 2, 2017 at 12:50:07 PM UTC+7, Hiep Lq wrote:

Hi Community.

I just complete a editor for input html text base on ckEditor

I also document about it here http://wiki.idempiere.org/en/Plugin:_CKEditor

by limit from core, it's not seamless install to system without touch database server and run migrate script

if you want to know about limit, please read chat here http://www.globalqss.com/idempiere/irclog/%23idempiere.2017-03-29.log.html

so i deploy a test server here: https://test.hasuvimex.vn/webui/index.zul

and just configuration for field Description of window sale order

welcome you experience to report issue, and contribute idea to improve.

--
You received this message because you are subscribed to the Google Groups "iDempiere" group.
To unsubscribe from this group and stop receiving emails from it, send an email to idempiere+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/idempiere/325caaba-36fc-26ba-de4c-6b18f0c37589%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

--

Lê Quý Hiệp
Email: hie...@hasuvimex.vn
Skype: admin.hasuvimex

Company: Thanh Hoa Fishery Import - Export J.s.c  (Hasuvimex) DL 47

Add: Lot E, Le Mon Industrial Zone, Thanh Hoa, Vietnam

[Carlos Antonio Ruiz Gomez]

Thanks Hiep,

>> 6 - On Find window is showing also the field as an HTML editor - is that OK?  I think because of
>> that you cannot search things with LIKE starting with %

> value store on database like string, so can be search with LIKE. 

> but some time it make user confuse, because when they seach for div, almost record will return

I mean, if you fill the editor in HTML mode with %carlos, expecting to find any record with carlos in that field.
But what I suspect is correct, it will return something like "<p>%carlos</p>" and maybe will return a different thing than user is expecting.

>i think better don't allow search with field use long text and html

If the database supports search on long text I think is OK to allow it, I would think in find window the HTML editor must be simply a textbox.

>> 3 - The toolbar could have more stuff, or make it configurable?

> it on my mind, do it after IDEMPIERE-3323 i don't want to create new column for each option of each editor.

I was thinking something simpler, maybe can be done actually as a fragment of your plugin.

For example, in iDempiere you can customize the toolbar of the string editor in HTML mode adding a fragment changing the file: org.adempiere.ui.zk/js/ckeditor/config.js

Regards,

Carlos Ruiz


El 05/04/17 a las 11:32, 'Hiep Lq' via iDempiere escribió:

[norber...@multimageweb.com]

+1 for nested toolbar not popup in default. in my opinion actual solution s not  enough practical. for me enduser comfort is priority no 1. 

norbert

[Hiep Lq]

for me it's ok, because we can save space. when you focus to editing, popup showing and stable util you leave so comfort to use.
i just to see a issue, log here https://github.com/hieplq/zkckeditor/issues/3

[Hiep Lq]

On Wednesday, April 5, 2017 at 7:16:31 PM UTC+7, Carlos Antonio Ruiz Gómez wrote:

Thanks Hiep,

>> 6 - On Find window is showing also the field as an HTML editor - is that OK?  I think because of
>> that you cannot search things with LIKE starting with %

> value store on database like string, so can be search with LIKE. 

> but some time it make user confuse, because when they seach for div, almost record will return

I mean, if you fill the editor in HTML mode with %carlos, expecting to find any record with carlos in that field.
But what I suspect is correct, it will return something like "<p>%carlos</p>" and maybe will return a different thing than user is expecting.

i find out some idea, i worry it can effect to performance, so need time to test and implement. let it low priority, 

now allow find but acceptable when result include html tag.

example user have record have value "i have a div"

when he input "div", he will get a lot records because <div> exists almost record.

>i think better don't allow search with field use long text and html

If the database supports search on long text I think is OK to allow it, I would think in find window the HTML editor must be simply a textbox.

>> 3 - The toolbar could have more stuff, or make it configurable?

> it on my mind, do it after IDEMPIERE-3323 i don't want to create new column for each option of each editor.

I was thinking something simpler, maybe can be done actually as a fragment of your plugin.

For example, in iDempiere you can customize the toolbar of the string editor in HTML mode adding a fragment changing the file: org.adempiere.ui.zk/js/ckeditor/config.js

for this way every htmlEditor have same toolbar.

but i want let user can configuration per htmlEditor instance

example: help field need more toolbar button than description

so user can define some toolbar configuration on a new table, on ad_column add new column to refer this table.

but better i will do IDEMPIERE-3323, so don't need define new table or new column for each new WEditor plugin

[Ricardo Malla]

Hello All,

I have a related question regarding the built in editor. Is there a way to set it to be default on the field?

I need it in particular on my product description. Currently I edit the descriptons using right click and open the html editor, but when I close it all I see is html code on the field box intead of the parsed content.

Please advise.

Thanks,

Ricardo Malla

[Hiep Lq]

On Tue, Jun 13, 2017 at 7:11 PM, Ricardo Malla <ricard...@venexchange.com> wrote:

Hello All,

I have a related question regarding the built in editor. Is there a way to set it to be default on the field?

 

http://wiki.idempiere.org/en/Developing_Plug-Ins_-_IEditorFactory_and_IDisplayTypeFactory 

I need it in particular on my product description. Currently I edit the descriptons using right click and open the html editor, but when I close it all I see is html code on the field box intead of the parsed content.

that why my plugin is born

 

Please advise.

Thanks,

Ricardo Malla

--
You received this message because you are subscribed to the Google Groups "iDempiere" group.
To unsubscribe from this group and stop receiving emails from it, send an email to idempiere+unsubscribe@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/idempiere/fb08305e-ec64-4ed0-9442-2f0c87b53304%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[Ricardo Malla]

Hey Hiep, 

Thank you very much! I will try to digest the information and try to get the solution

Very happy with the community support! This is what makes products great

Cheers and will be in contact. 

Ricardo Malla

On Tuesday, June 13, 2017 at 10:11:06 AM UTC-4, Hiep Lq wrote:

On Tue, Jun 13, 2017 at 7:11 PM, Ricardo Malla <ricard...@venexchange.com> wrote:

Hello All,

I have a related question regarding the built in editor. Is there a way to set it to be default on the field?

 

http://wiki.idempiere.org/en/Developing_Plug-Ins_-_IEditorFactory_and_IDisplayTypeFactory 

I need it in particular on my product description. Currently I edit the descriptons using right click and open the html editor, but when I close it all I see is html code on the field box intead of the parsed content.

that why my plugin is born

 

Please advise.

Thanks,

Ricardo Malla

--
You received this message because you are subscribed to the Google Groups "iDempiere" group.

To unsubscribe from this group and stop receiving emails from it, send an email to idempiere+...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/idempiere/fb08305e-ec64-4ed0-9442-2f0c87b53304%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[Hiep Lq]

>> if you fill the editor in HTML mode with %carlos, expecting to find any record with carlos in that field.

But what I suspect is correct, it will return something like "<p>%carlos</p>" and maybe will return a different thing than user is expecting.

if we use a editor like wiki (with Markdown syntax), we can resolve it not 100% but a lot.

Markdown is more simple than html, near to blank text.

On Wednesday, April 5, 2017 at 7:16:31 PM UTC+7, Carlos Antonio Ruiz Gómez wrote:

[Carlos Antonio Ruiz Gomez]

Hiep, I think is better if possible not use HTML editor in find mode,
just plain text editor.

So, if you search for "%carlos" - it searchs for exactly that - using
HTML editor there leads to search for <p>%carlos</p> which sounds wrong
in query.

So, I think is just to use normal editor on find window for HTML fields.

Regards,

Carlos Ruiz

[Hiep Lq]

ah, now i clear about what you mention, i can resolve your case.

i concern difference issue.

   example i have below text

             city list List Việt Nam city with name, post code, phone code

  it will save on database like 

             <b> Việt Name city list </b> List Việt Nam city with name, post code, phone code

  so when user find with text

             "city list List Việt"

  he can't find out anything

  or when he find with text "city list </b>"

  he should receive 0 record, but here he will receive 1 record