Helping CodeProject with programming
-
when using specialized HTML editors such as FrontPage the software will put it's own HTML tags. and that is the same for all HTML editors. If the programmer wants total control then use notepad and they can always open the HTML doc on a HTML viewer such as Firefox.
Daniel Engelkes wrote:
FrontPage the software will put it's own HTML tags. and that is the same for all HTML editors
Not in my experience. I'm actually using FrontPage 2003 (Yes - FrontPage classic!) because it's so clean with it's HTML handling. Our HTMLArea based WYSIWYG editor doesn't often add tags. Obviously adding a paragraph or image will result in new tags being added, but they aren't unexpected tags.
cheers Chris Maunder
-
It's been hard not to notice that there are a bunch of you who aren't too shabby when it comes to a bit of keyboard action. There are, in fact, some painfully good (and incredibly generous) programmers hanging out here and I had an idea. Last night I was up till the wee, wee hours of this morning fighting with some alternative WYSIWYG HTML editors for the article editor. Our current HTML WYSIWYG editor is, well, a little long in the tooth and I need to replace it to save my (and your) sanity. CKEditor seems the best so far - except that it refuses to do what I want it to and insists on mangling the HTML it's given. There is no "don't screw with my HTML" option. We discussed, ages ago, the possibility of having you guys take on some interesting bits and pieces of CodeProject development and this seemed a perfect opportunity to give it a try. Is there still any interest? I've opened a new Workspace and setup a Git repo at https://workspaces.codeproject.com/codeproject/codeproject/wysiwyg-editor[^] for anyone who's interested in diving in and helping build some of the CodeProject infrastructure. You'll obviously need to have a basic understanding of JavaScript (and Git!) to get going, but feel free to ping me if you need help getting off the ground. This is just an experiment and if there's interest then I'd love to open more and more up to let you guys start mixing things up a little.
cheers Chris Maunder
This should be fun Lets do this!
-
It's been hard not to notice that there are a bunch of you who aren't too shabby when it comes to a bit of keyboard action. There are, in fact, some painfully good (and incredibly generous) programmers hanging out here and I had an idea. Last night I was up till the wee, wee hours of this morning fighting with some alternative WYSIWYG HTML editors for the article editor. Our current HTML WYSIWYG editor is, well, a little long in the tooth and I need to replace it to save my (and your) sanity. CKEditor seems the best so far - except that it refuses to do what I want it to and insists on mangling the HTML it's given. There is no "don't screw with my HTML" option. We discussed, ages ago, the possibility of having you guys take on some interesting bits and pieces of CodeProject development and this seemed a perfect opportunity to give it a try. Is there still any interest? I've opened a new Workspace and setup a Git repo at https://workspaces.codeproject.com/codeproject/codeproject/wysiwyg-editor[^] for anyone who's interested in diving in and helping build some of the CodeProject infrastructure. You'll obviously need to have a basic understanding of JavaScript (and Git!) to get going, but feel free to ping me if you need help getting off the ground. This is just an experiment and if there's interest then I'd love to open more and more up to let you guys start mixing things up a little.
cheers Chris Maunder
-
Found that page will work with Google Chrome and Internet Explorer 11 Dosn't work with NeoPlanet and other IE clones.
Neoplanet? Wasn't the last stable release 13 years ago?
cheers Chris Maunder
-
Opening up the reporting system via an external API isn't something we're totally keen on at this point. It's a very large, scary can of worms.
cheers Chris Maunder
OK. :-D I understand about the reporting, expecially given what happened to me[^] a few days ago... X| ... so I definitely don't want to create anything that aids such behaviour.
-
It's been hard not to notice that there are a bunch of you who aren't too shabby when it comes to a bit of keyboard action. There are, in fact, some painfully good (and incredibly generous) programmers hanging out here and I had an idea. Last night I was up till the wee, wee hours of this morning fighting with some alternative WYSIWYG HTML editors for the article editor. Our current HTML WYSIWYG editor is, well, a little long in the tooth and I need to replace it to save my (and your) sanity. CKEditor seems the best so far - except that it refuses to do what I want it to and insists on mangling the HTML it's given. There is no "don't screw with my HTML" option. We discussed, ages ago, the possibility of having you guys take on some interesting bits and pieces of CodeProject development and this seemed a perfect opportunity to give it a try. Is there still any interest? I've opened a new Workspace and setup a Git repo at https://workspaces.codeproject.com/codeproject/codeproject/wysiwyg-editor[^] for anyone who's interested in diving in and helping build some of the CodeProject infrastructure. You'll obviously need to have a basic understanding of JavaScript (and Git!) to get going, but feel free to ping me if you need help getting off the ground. This is just an experiment and if there's interest then I'd love to open more and more up to let you guys start mixing things up a little.
cheers Chris Maunder
Hello Chris! I've forked the code and added some event handler for the mode change (not pushed yet). What isn't clear to me is - are you want to use some existing code for content modification on mode change or something new? In both case I need more info... Old case - how to call that code New case - what exactly do you want to change between mode switches? (I saw the
imgproblem, but there is more?) [Modification] I've just playing around and noticed that setting baseHref like thisCKEDITOR.config.baseHref = "http://www.codeproject.com/KB/miscctrl/gridctrl/";
removes the need for playing with image source on editor mode change! It can be always the simple
myimage.jpgform...Consider it... [/Modification]I'm not questioning your powers of observation; I'm merely remarking upon the paradox of asking a masked man who he is. (V)
-
Hello Chris! I've forked the code and added some event handler for the mode change (not pushed yet). What isn't clear to me is - are you want to use some existing code for content modification on mode change or something new? In both case I need more info... Old case - how to call that code New case - what exactly do you want to change between mode switches? (I saw the
imgproblem, but there is more?) [Modification] I've just playing around and noticed that setting baseHref like thisCKEDITOR.config.baseHref = "http://www.codeproject.com/KB/miscctrl/gridctrl/";
removes the need for playing with image source on editor mode change! It can be always the simple
myimage.jpgform...Consider it... [/Modification]I'm not questioning your powers of observation; I'm merely remarking upon the paradox of asking a masked man who he is. (V)
I've merged your suggestions and added a concrete example of what was needed. Issue #1 is considered fixed!
cheers Chris Maunder
-
It's been hard not to notice that there are a bunch of you who aren't too shabby when it comes to a bit of keyboard action. There are, in fact, some painfully good (and incredibly generous) programmers hanging out here and I had an idea. Last night I was up till the wee, wee hours of this morning fighting with some alternative WYSIWYG HTML editors for the article editor. Our current HTML WYSIWYG editor is, well, a little long in the tooth and I need to replace it to save my (and your) sanity. CKEditor seems the best so far - except that it refuses to do what I want it to and insists on mangling the HTML it's given. There is no "don't screw with my HTML" option. We discussed, ages ago, the possibility of having you guys take on some interesting bits and pieces of CodeProject development and this seemed a perfect opportunity to give it a try. Is there still any interest? I've opened a new Workspace and setup a Git repo at https://workspaces.codeproject.com/codeproject/codeproject/wysiwyg-editor[^] for anyone who's interested in diving in and helping build some of the CodeProject infrastructure. You'll obviously need to have a basic understanding of JavaScript (and Git!) to get going, but feel free to ping me if you need help getting off the ground. This is just an experiment and if there's interest then I'd love to open more and more up to let you guys start mixing things up a little.
cheers Chris Maunder
In relation to the fourth item in your updated list (about sensible HTML)... I wrote this article http://www.codeproject.com/Articles/748790/Beginners-Guide-to-HTML-CSS-Part-of[^] using the new editor. At the end I just copied the html code from my local copy to CP. I didn't got any 'insensible' HTML on the way. There is something specific I have to look for (except the line break in copied code, which I see no)?
I'm not questioning your powers of observation; I'm merely remarking upon the paradox of asking a masked man who he is. (V)
-
In relation to the fourth item in your updated list (about sensible HTML)... I wrote this article http://www.codeproject.com/Articles/748790/Beginners-Guide-to-HTML-CSS-Part-of[^] using the new editor. At the end I just copied the html code from my local copy to CP. I didn't got any 'insensible' HTML on the way. There is something specific I have to look for (except the line break in copied code, which I see no)?
I'm not questioning your powers of observation; I'm merely remarking upon the paradox of asking a masked man who he is. (V)
How was the experience with the new editor?
cheers Chris Maunder
-
How was the experience with the new editor?
cheers Chris Maunder
I found it very nice. It never added extra lines between paragraphs (which happening me all the time with the current). I liked the image insertion popup - it nice, clear and easy, also hyperlink creation is very nice... The only thin I found different for the wrong direction is about the <code> block. I added it manually - as it's not on the toolbar (or I missed something) and when positioning the caret at the end of the line it was INSIDE the <code> block. It was a bit disturbing, but I'm sure that we can find a way to handle it... In summary I can say that the new editor much more supportive, than the one we have today...
I'm not questioning your powers of observation; I'm merely remarking upon the paradox of asking a masked man who he is. (V)
