New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Future of richtext editing in DNNFuture of richtext editing in DNN
Previous
 
Next
New Post
10/12/2014 11:12 AM
 

to underline the statement from Ingo, I created a table of all issues in dnnCkEditor project on Codeplex:

  Bugs Task Feature other
proposed 1 1 0 3
active 0 0 0 0
resolved 167 14 5 10
closed 18 0 2 55

 

(I interpreted one of the "others" as task, the remaining 3 are waiting for response or are caused by DNN).

If we want a better integration into DNN, we need to create more advanced interfaces inside the framework first.

And I'd like to thank Ingo for his fast response on all issues and  providing fixes within days (sometimes hours), although I know, that he is working hard nearly all day and night!


Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
10/12/2014 1:10 PM
 

"Sorry but that is simply not true, i build the editor provider long before i used the forum module. And when did i ever said that i dont want the provider to be used with Evoq? If you would have read my comments on why i cannot support Evoq, because dnn no longer provides a trial version so iam unable to test my provider against evoq."

The html agility dll is the best html writing component in the Microsoft platform , so the DNN text editor control will not prevent adding html components to the page because you implemented IPOSTBACKDATAHANDLER interface the base required for most custom control, I have also seen skin developers use skin objects to do inline editing.  What I see now is DNN blocking the contenteditable attribute of html5.  And Philip is talking about asset integration that is the Asp.net Maxlengthproperty adjustment; it can be ajdusted in system32 in the applicationhost file the core of IIS7 and up when IIS metabase was deprecated.

One more thing you just deleted more than twenty issues so clean review of the issues is not possible, please check the link below for a previous implementation of Philip’s proposal using config files.  I should also add that DNNUI added sliders, carousel and other features to Ventrain Article by just adding literal control to an aspx page in the module back in 2010.

 

http://www.uchithar.net/2010/03/some-...

 
New Post
10/14/2014 5:14 AM
 
Here's my 2cents

I believe that the current WYSIWYG-problem is actually a conceptual mistake. To put it simply: DNN is lousy at managing content. Really managing it. It simply doesn't *manage* the content at all.

Now we all kept claiming that it does, and said the HTML-module is the solution. We said "Yes, it does manage content - look here". Because of this wrong approach, the HTML-Module had to be powerful enough for every thinkable solution - incl. video, flash, etc. That sucked, so we also wanted pre-fabricated html-templates. Then DIVs came, and that sucked as well...

So IMHO to tackle the WYSIWYG problem, I believe that you must first clearly define what the WYSIWYG should do - and what it should not do. Without this, you'll just get a new "Eierlegende-Wollmilchsau" (sorry, no English word for that :) which does everything not really well.

BTW: I also believe that it's better to incorporate an existing solution. Everything that "we" develop must also be maintained (like the current mini-fiasco with the razor menus which have large bugs and performance issues that "never" get fixed). Whenever we use (and contribute) to an existing solution like tinyMCE, things will probably stay better...

Love from Switzerland
 
New Post
10/14/2014 8:54 AM
 
Google Translate gives "Egg-laying wool milk sow". In English we'd probably say "All singing, all dancing" or "trying to be too clever".

I love Egg-laying wool milk sow. I think I may start using it in English!

Best wishes,
- Richard
Agile Development Consultant, Practitioner, and Trainer
www.dynamisys.co.uk
 
New Post
10/14/2014 2:39 PM
 
"I believe that the current WYSIWYG-problem is actually a conceptual mistake. To put it simply: DNN is lousy at managing content. Really managing it. It simply doesn't *manage* the content at all.

Now we all kept claiming that it does, and said the HTML-module is the solution. We said "Yes, it does manage content - look here". Because of this wrong approach, the HTML-Module had to be powerful enough for every thinkable solution - incl. video, flash, etc. That sucked, so we also wanted pre-fabricated html-templates. Then DIVs came, and that sucked as well..."


The above was inherited by DNN from Microsoft and their lazy greedy custom control vendors but Microsoft joined the html5 users like Google, Adobe et al; so back in 2011 Asp.net made dramatic changes, DNN panicked and imported the bloated Razor engine with Web matrix to appease Microsoft and it worked.  But it also allows DNN to write and run really substandard http code and obsolete and sometimes invalid database code.
Now Asp.net uses three to four dll to create any page like WordPress with or without relevant CSS files using the dlls in packages.

"(like the current mini-fiasco with the razor menus which have large bugs and performance issues that "never" get fixed)."

This is actually a different and very complicated issue that is DNN specific, not related to Asp.net because navigate url in Asp.net 4.5 is optional even in old code just import packages and makes changes in the site.master aspx file.   Asp.net 4.5 Webform is similar to WordPress out of the box with just packages and Awesome fonts, so I am going to add that to DNN Platform without using twelve to twenty two dlls per page.  The DNN Platform is running really bad code that is not doing anything for all simple and content users, the core messaging comes with 65 stored procedures, a content user does not need it.
 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Future of richtext editing in DNNFuture of richtext editing in DNN


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.