Darksbane0 Posted August 31, 2011 Posted August 31, 2011 IPContent lets you choose between a number of different editors when working with code, I think the skin systme should also.
Marcher Technologies Posted August 31, 2011 Posted August 31, 2011 IPContent lets you choose between a number of different editors when working with code, I think the skin systme should also. ... Dark... EVERY ONE of those Editors BREAKS code.... doesn't recognize template logic... why? isnt the template system and webdav enough? i dont think using a TinyMCE/codeEdit or whatever on skin templates is wise... at all.
Darksbane0 Posted August 31, 2011 Author Posted August 31, 2011 ... Dark... EVERY ONE of those Editors BREAKS code.... doesn't recognize template logic... why? isnt the template system and webdav enough? i dont think using a TinyMCE/codeEdit or whatever on skin templates is wise... at all. No I don't consider the current system and webdav enough, thats why I make the suggestion. And it doesn't have to be tinyMCE/CodeEdit I just want some freckin line numbers and better formatting, trying to edit any skin templates in the current system is extremely frustrating.
qscott86 Posted August 31, 2011 Posted August 31, 2011 ... Dark... EVERY ONE of those Editors BREAKS code.... doesn't recognize template logic... why? isnt the template system and webdav enough? i dont think using a TinyMCE/codeEdit or whatever on skin templates is wise... at all. No they don't break code. You have proven wrong about that before just like with the navigation links.
Ryan H. Posted September 1, 2011 Posted September 1, 2011 No I don't consider the current system and webdav enough, thats why I make the suggestion. And it doesn't have to be tinyMCE/CodeEdit I just want some freckin line numbers and better formatting, trying to edit any skin templates in the current system is extremely frustrating. They tried an enhanced skin editor, I believe in one of the 3.0 betas. Nevermind the bugs it had; those tools proved unable to deal with the massive amount of data involved. No browser could handle the massive processing and memory requirements for it to work. Consider the delay in opening a template as it is, then add thirty seconds of your browser freezing [in the best case]. And some more every time you make a change or save it.
Darksbane0 Posted September 1, 2011 Author Posted September 1, 2011 Well 3.0 beta was what 3 years ago? I've got IPContent pages with far more lines of code than the average skin template and I haven't seen any slowdown. Just to get it to have a slight delay I had to paste about 1k lines of code in it. It seems perfectly capable of handeling the 300-500 lines of code the bigger skin templates have. I'm just not seeing how having the option would be a bad thing.
Ryan H. Posted September 1, 2011 Posted September 1, 2011 The stylesheets can easily be in excess of 50Kb [far more than 1000 lines], and you often will have multiple templates open at the same time.
Darksbane0 Posted September 1, 2011 Author Posted September 1, 2011 So I just pasted a 4000 line style sheet into an editArea box and I'm getting about .5 to 1 second lag, upped that to 10K lines of CSS and I get about 3 seconds lag, and this is with syntax highlighting on. If i turn syntax highlighting off (which still gives me the line numbers, ability to tab, code search, word wrap) I have no lag. I'm not saying it is perfect and there are things which can lag it out but I don't see the harm in giving the choice to use the editor. I'd much rather use editArea and deal with the lag or turn off syntax highlighting than work in the current textbox.
bfarber Posted September 1, 2011 Posted September 1, 2011 So I just pasted a 4000 line style sheet into an editArea box and I'm getting about .5 to 1 second lag, upped that to 10K lines of CSS and I get about 3 seconds lag, and this is with syntax highlighting on. If i turn syntax highlighting off (which still gives me the line numbers, ability to tab, code search, word wrap) I have no lag. I'm not saying it is perfect and there are things which can lag it out but I don't see the harm in giving the choice to use the editor. I'd much rather use editArea and deal with the lag or turn off syntax highlighting than work in the current textbox. And you probably have a semi-decent system. The Windows XP users with 2GB RAM using IE7 would scream bloody murder (in fact...they did!). I wouldn't mind a proper code editor in the ACP, but because so many users would have issues using it, it's not feasible right now.
Darksbane0 Posted September 1, 2011 Author Posted September 1, 2011 Thanks Brandon, hopefully yall can figure out a way eventually, would it require code edits for me to just change my install or is there skin bits to edit the ACP? Incidentally I'm running XP SP3 with 3 gigs ram, Chrome (what I'm editing in) and Firefox open with about 50 tabs loaded, Dreamweaver, Visual Stuido, Photoshop, MS SQL Explorer, Outlook and Virus Scanner running, so perhaps IE was the problem.
Recommended Posts
Archived
This topic is now archived and is closed to further replies.