User talk:Cacycle/wikEd/Archive 002

Kudos !

I started editing Wikipedia about six weeks ago. As I made more edits and worked on larger articles, I found myself getting frustrated with the vanilla editor and thinking "if only there were an editor like CodeWright (for example) that could color-code the Wiki syntax, and maybe color my changes so I could see where I've been so far, and maybe a few other things I haven't thought of yet..." I'm a timid editor; I like to test for appearance every few changes, so doing a cut-and-paste into the vanilla editor from CodeWright or such to see how the latest few changes look is not very practical. I spent some time earlier today scouting around for alternatives and came across wikEd. People don't always appreciate all that's involved in writing something like an editor, but let me just say good job. wikEd is perfect for the kind of editing I've found myself doing. I'm sure it will have a lot of happy users. Thank you! --CliffC 01:08, 25 October 2006 (UTC)

Red &nbsp:'s on one side of a diff

Maybe this is similar to what was reported in "A couple bugs?" above, but it looks like the " & n b s p ; " 's have gotten lost from that report. I recently reverted the vandalism Having withdrawn his army from Boston,he had sex with 12 women and 14 men from American Revolutionary War. If you look at the diff here [1] of the revert I did (automated, using Popups) while wikEd was my editor, you'll see that the "& n b s p ;" 's appear differently on the two sides. No big deal, but it would be confusing to a third party trying to figure out what exactly I changed. The diff seems to look the same when read with the vanilla editor.

Finally, is this the right venue to report problems like this, and is there a list posted somewhere so users don't pester you with the same problem over and over? I plan to continue to use wikEd, and will be glad (in a perverse, software-tester kind of way) to report anything else odd I might see. --CliffC 13:58, 28 October 2006 (UTC)

(Later) A small wikiEd edit to Francis E. Dorn broke a table. It looks like the two spaces leading certain table elements were replaced by one space and an "& n b s p ;" ; and to Wikipedia table formatting that makes a difference; had to revert to the vanilla editor to fix it. --CliffC 03:07, 29 October 2006 (UTC)

I'm sorry for those bugs. Most of them have been fixed during the last days (and nights) and we are approaching beta status... Press Shift-Reload! to update. Feel free to submit your bug reports to my user talk page. Cacycle 10:38, 5 November 2006 (UTC)

First look at the latest version - diff diffs - spaces?

The new editor looks great, and I see it now has the full complement of buttons. Nice new color for HTML comments.

I made a copy of the Francis E. Dorn article in my own userspace at User:CliffC/Luis Fernandez de la Reguera to check the table formatting/ & n b s p problem mentioned above. I removed the double brackets from the phrase "under God", same as with the original article, and saved. The revised article now formats fine. The diff HERE shows differences in paragraphs that were not changed, so something subtle seems to be going on  - maybe with double spaces?

I don't see any differences in the diff beside that link. So what do you mean with " something subtle seems to be going on  - maybe with double spaces?". Cacycle 07:34, 6 November 2006 (UTC)

The diff shows (at least for me it does, maybe our setups are different somehow, I am using the vanilla editor for the time being) 5 paragraphs above the one with the actual change. 3 of them have a '+' sign indicating some sort of change. I thought '+' meant some sort of spacing change, but I didn't touch anything in those paragraphs. --CliffC 18:20, 6 November 2006 (UTC)

It is actually caused by trimmed spaces at the end of lines. Cacycle 04:09, 19 November 2006 (UTC)

I notice clicking the standard Insert: characters and Sign your name: below the edit window don't seem to work; not sure if this is a new problem or something that's just not finished yet. Sorry for all these PTRs... --CliffC 15:10, 5 November 2006 (UTC) Cacycle 07:34, 6 November 2006 (UTC)[[Category:]]

These do not work (yet?) because they change the 'classic' input field. But you can click the "use wikEd" button (with the logo) to switch to the classic field, press your insert-links, and return to wikEd (or submit). Cacycle 07:34, 6 November 2006 (UTC)

They now work :-) Shift-Reload to update. Cacycle 03:46, 7 November 2006 (UTC)

Mac Os X Firefox 2

There is one major bug in FF2 Mac OS X, that is that a scrollbar appears under the edit field. (Refer to the screenshot for view). O.k. so not a major bug, but an annoying one nontheless :) .

Resolution: 1024x768 Sfacets 22:01, 8 November 2006 (UTC)

File:Ss22.jpg

I too report this bug Spiff 23:37, 8 November 2006 (UTC)

I think I know what causes this. Before I try to fix this, please tell me if you see still see scrollbars when you turn wikEd off by pressing the button. Thanks, Cacycle 00:03, 9 November 2006 (UTC)

Hi. I seem to have this problem with Firefox 1.5.0.6 & OS X 10.4.2 (old Powerbook G4 gigabit ethernet from 2001), but right now it only occurs if I disable wikEd with the button. Re-enabling it moved the "phantom scrollbar" down. It seems this has to do with what I will call the edit window "content logic." I'm deliberately typing a lot of text here to force the edit box to fill up. As I started this line the "real" scroll bar appeared, but the "phantom" has stayed put. I've noticed another cosmetic bug: the pointer becomes an insertion point only where characters are entered, which is a confusing user-interface behavior. There is, I think, an issue as to whether there is enough text to require a scrollbar. Does this have also to do with the syntax-highlighting feature? oops, here's another little bug: I just tried to "find-ahead" the word "confusing" a few sentences back. As I type the word into the Find box, the matching letters in the word alternately highlight and unhighlight! Therefore the interface behavior is different depending on whether the word (I'm sorry, the search target) has an even or odd number of letters! There also seems to be ann odd insertion point behavior when entering fresh text, as I am doing now as a test. I think I can tell you how to reproduce it: Type a space after a completed sss word or period. Then type another space. Type a left arrow to move the insertion point between the two spaces. Now continue typing. Notice what happens the next time you type a space: the insertion point doesn't advance because of the extra space preceding the insertion point. This only seems to occur with a single space following the insertion point. Please excuse the wordiness of this entry, but it certainly helps uncover these endearing cosmetic anomalies! I hope they can be confirmed elsewhere. P.S. The button icons are great once one learns their function.  Schweiwikist   (talk)  02:47, 9 November 2006 (UTC)

Actually it has to do with how I hide the standard edit box or the wikEd frame when they are not in use (actually I just make them invisible by hiding them behind anything else). Obviously this and a few other things that work fine under Windows do not work under Mac OS X (actually I cannot reproduce the "confusing" bug and the "spaces bug". I am pretty sure that I can fix some of these issues soon. It would help me a loot if you could continue posting such anomalies :-) Cacycle 03:43, 9 November 2006 (UTC)

I think I have fixed the Mac OS X issue. Please update by pressing SHIFT-Reload and report if you still experience those strange effects. Thanks, Cacycle 04:55, 9 November 2006 (UTC)

Hi again. Nope, the phantom scollbar still appears. I just switched to Ffox 2 btw and the anomaly continues after I use "Clear Private Data" to purge the cache.. You should know that the scrollbar issue vanishes under fullscreen mode, however. Another test I did was seeing how long it takes to load up the entire text of the George W. Bush article. Quite a challenge to a PowerBook G4 667MHz! Scrolling the page once it loads is fast however, and even with tiny text view, which is most impressive. Here's another bug I've uncovered, though: A user ought to disable fullscreen view before any disabling of wikEd. There also seems to be an issue with selecting/highlighting syntax-highlighted text, and toggling syntax-highlighting while text is selected. The click of the toggle button (outside the edit box) deselects the text selection, which qualifies as "unexpected response". One more comment: I of course appreciate the tooltips, but I wonder if the text of the tooltip ought to change respective to the current status, e.g.: Enable wikEd--Disable wikEd. Also the text: Fullscreen mode has no verb, might as well call it "Toggle Fullscreen mode". That's all for now, I'm supposed to be in bed ;)  Schweiwikist   (talk)  05:52, 9 November 2006 (UTC) after an edit conflict!

UPDATE: Hi. Reverted back to editor.js for a day or two, keep me posted. It loads so much faster. One small additional report: I did some testing on my desktop G4(500MHz) last night. The "hidden" scrollbar also peek thru but not in the same location. It also operates (but its associated edit box is of course invisible). Fullscreen mode gats rid of the issue too. So the glitches are not machine-specific. ttfn.  Schweiwikist   (talk)  14:52, 9 November 2006 (UTC)

The phantom scrollbar is gone! Nope, sorry, it has just been moved to the top of the page... damnit! :)

Also another small bug (small yet annoying) is the fact that upon first editing content (still under OS X FF) one is unable to delete content without first entering content. Hmmm

Good work though, this is a great tool!

Sfacets 05:28, 9 November 2006 (UTC)

The scrollbar artifact is still there. Also, all my other scripts that interacyt withe the textarea are not working. I have scripts that insert user warnings, AfD closing tags, etc. that no longer work when I have wikiEd enabled. The worked OK on the editor.js. ≈ jossi ≈ t • @ 16:08, 9 November 2006 (UTC)

The phantom scrollbar appears overlayed on top-left on text area. When I disabl;e and re-enable WikEd, the phantom scrollbar shows up at the top left of page. ≈ jossi ≈ t • @ 20:00, 9 November 2006 (UTC)

It is obvious that this is a Mozilla OS X bug and I can't do anything about it because the only other solution is not possible because of another Mozilla bug. It is pretty frustrating, I have been spending many days in finding work-arounds for far too many Mozilla bugs! From that perspective Mozilla clearly sucks. Sorry, that had to be said. Cacycle 01:10, 10 November 2006 (UTC)

ref tags

Wow, the new version looks great! One possible bug: I tried the double check button (fixes basic, HTML, etc.) on Christian views of alcohol, and it tried to strip the references' names (e.g., "SoAndSo" in code like <ref name=SoAndSo>...</ref> ... <ref name=SoAndSo />). Is that a known bug? --Flex (talk|contribs) 22:14, 8 November 2006 (UTC)

Thanks for your bug report. The reason for that is that <ref name="Eastons" /> is not correct. It is missing the quotation marks in order to be valid XHTML, the correct version would be <ref name="Eastons" /> (But because the ref tag has not to be valid XHTML I might fix this :-). The fixing buttons are inherently dangerous, never use them without checking the diff! Cacycle 00:12, 9 November 2006 (UTC)

Loading note

It is suggested that you display a message while the code is loading. On my system, it takes a while. The bottleneck for me is probably dial-up. Will (Talk - contribs) 05:31, 9 November 2006 (UTC)

Yes, the program is about 200 kB in size, but it is loaded only once. There is a small indicator: When wikEd is loaded it will disolay its logo at the very top of the page. If there is a program loading error it will leave a logo with a thick red x. Cacycle 16:29, 9 November 2006 (UTC)

I finally located your X. That icon doesn't appear at all until the app loads. What I was thinking of was a large image that gets replaced once the app is ready. Will (Talk - contribs) 23:57, 9 November 2006 (UTC)

Using the + tab with wikEd

If you look at the + tab, you will find the Edit Summary box becomes the Subject box and moves up top. The wikEd tools follow it. This appears to confuse your code. For starters, once init is complete, it scrolls the tools out of view. Next, the preview window is still below the tab. Will (Talk - contribs) 05:33, 9 November 2006 (UTC)

What the hell is '+ tab'. :-) Cacycle

Look at the top of this page. Next to the edit tab, you will see a Plus sign. Click it. Will (Talk - contribs) 20:20, 9 November 2006 (UTC)

Yes, that looks funny. I will try to fix that. Cacycle 01:03, 10 November 2006 (UTC)

I noticed that too, on my first real use of this editor. It was different from what I was used to seeing with the + tab, that's all. —Długosz 20:39, 14 December 2006 (UTC)

Actually, when I use the plus tab, I like to enter the title of the new section first. Think about it. In a normal forum system, your e-mail editor, or just an essay in Word; the title is the first thing you enter. Besides, now that wikEd always has the subject/heading box under the main edit box, by the time I get down there, I sometime forget that I am creating a heading with that box and put in the missing /**/ stuff. Will (Talk - contribs) 02:25, 15 December 2006 (UTC)

Please add a button to strip the link(s) from selected text

I copied text to the edit window that had a link in it. I wanted the link text (a user name), but not the link URL (which probably would not get translated to the Wiki page name anyway). As is turned out, the check button fixed it. However, buttons like other editors have to remove formatting would be more intuitive. Will (Talk - contribs) 05:36, 9 November 2006 (UTC)

I acknowledge that it is not intuitive :-) You can either ignore the formatting as only the visible plain text is finally submitted. Or you can press the [T] button to remove any formatting, see also the button descriptions on the User:Cacycle/wikEd Help page. Cacycle 16:21, 9 November 2006 (UTC)

Ok. I missed the [T] button. However, if the RTF control is used only for syntax highlighting, could you run the [T] button code on the pasted text automatically? If I paste formatted text into the control, I expect the formatted text to be submitted still formatted. Will (Talk - contribs) 20:23, 9 November 2006 (UTC)

That would need lot's of trickery, it is not as easy as as it sounds. I might think about it later.

Re: "I expect the formatted text to be submitted still formatted.": Actually I have tried it and it is a bad idea. Sometimes formatting is invisible and you don't want to submit strange code fragments without knowing it. Cacycle 01:00, 10 November 2006 (UTC)

Then I would suggest the code that handles the paste detected them, warned the user, and offered to remove them. Will (Talk - contribs) 02:04, 10 November 2006 (UTC)

Preview button does not work as expected

Is there a way for the wikEd preview to expand templates? Also, can I help it with signatures by telling it what my sig is? Will (Talk - contribs) 05:37, 9 November 2006 (UTC)

wikEd uses another program for this, check User:Pilaf/Live_Preview. As far as I know there is no way to expand templates, but there is a way to set your signature if I remember correctly. Cacycle 16:15, 9 November 2006 (UTC)

What are the details on that? Do I need to adjust some of your code for that? Will (Talk - contribs) 23:58, 9 November 2006 (UTC)

Live Preview is completely independent and has to be loaded independently. It is merely called from within wikEd. Cacycle 00:53, 10 November 2006 (UTC)

I still don't know what to do. Will (Talk - contribs) 02:05, 10 November 2006 (UTC)

Workaround or method for "expanding templates"

First, visit and read the help page on Substitution. Once you've absorbed that, experiment by copying or typing the following two items on an empty new page (live links would be a problem on this page) and see if wikEd's preview helps you out: {{FebruaryCalendar2007}}, which is a calendar template that will transclude onto the page, and {{subst:FebruaryCalendar2007}}, which previews the same way successfully, but copies the template code (however it stands at that instant) into the new page itself once it's saved. If your desire is for the template code to expand into the edit window itself during the preview, that's a tall order, considering the <noinclude> and <includeonly> factor! I would simply "edit" the template and copy and paste the code from it.
 Schweiwikist   (talk)  18:06, 11 November 2006 (UTC)

I did happen to be testing with user warning templates, which do get subst'ed in. However, I do not see how that is relevant considering both types should preview the same way. Will (Talk - contribs) 05:24, 12 November 2006 (UTC)

Changes button doesn't work

All it does it cause the cursor to become a hourglass when the mouse is over that button. Will (Talk - contribs) 05:38, 9 November 2006 (UTC)

Are you sure wikEd has loaded completely (as indicated by the disappearance of the red X over the logo at the very top of the page). Cacycle 16:06, 9 November 2006 (UTC)

What X? Also, which logo? The Wikipedia logo?

No, it is somewhere close to your logout and watchlist links. Cacycle 00:48, 10 November 2006 (UTC)

BTW: In this page, all occurances of the word "red" appear with a red background. Is that by design? Will (Talk - contribs) 20:33, 9 November 2006 (UTC)

Yes. That's a feature. Don't you like it? :-) Cacycle 00:48, 10 November 2006 (UTC)

Black worried me. But the tests I just did showed you switched to white text for the black background. At least you thought about that. Has no effect on hexadecimal colors. Should it? Will (Talk - contribs) 02:09, 10 November 2006 (UTC)

I found a situation where the syntax coloring is unreadable. View Template:User MLB-Cardinals in the editor. Colors like #00004d are unreadable. Will (Talk - contribs) 05:43, 23 November 2006 (UTC)

Wikia.com support?

When I pasted your code into Wikia:Starwars:User:Will Pittenger/monobook.js, it had no effect. I did refresh with CTRL-F5 on both the edit page and the article page. Will (Talk - contribs) 05:41, 9 November 2006 (UTC)

It only works under Firefox or other Mozilla browsers. Try Shift-Reload. Good luck, Cacycle 15:56, 9 November 2006 (UTC)

Oh, I see. In order to get the correct paste text you have to open the edit page and copy the text from the conventional textarea (wikEd has to be disabled by clicking the wikEd logo button or by disabling JavaScript). Sorry, this problem is caused by a workaround for a Mozilla browser bug ;-S Cacycle 16:10, 9 November 2006 (UTC)

It's now visible, but still doesn't work. No button reacts to me pushing it.

BTW: When I view the source on your pages, the edit attempts to enable itself -- even with read only controls. It should even bother loading. Also, the button to disable wikEd does the same thing the Changes buttons do: show an hourglass when I click them. It also reads "Enable" rather than "Disable" from the start. —Preceding unsigned comment added by Will Pittenger (talk • contribs)

Still not working. A while back, I switched from copying the actual code to importing. That help with Wikipedia, but made to worse in Wikia. Just in case, I updated the code. No luck. Could you check for problems? I put it at Wikia:StarWars:User:Will Pittenger/Monobook.js. Also, note that I have code at Wikia:StarWars:User:Will Pittenger/Monobook.css that turns the sidebar into a menu bar along the top with drop menus. The user menu replaced the row of links that you added your icon into. This might be part of the problem. However, I tried disabling that code with no effect. -Will Pittenger 23:03, 9 December 2006 (UTC)

Should work now in 0.9.12b. Cacycle 00:41, 10 December 2006 (UTC)

With 0.9.12b, it does display the status icon. (I found it in the drop menu with the stuff like Watchlist.) However, the editor itself is missing. Ditto for Live Preview and all other related items. -Will Pittenger 04:23, 14 December 2006 (UTC)

My mistake. It is complete working there. Thanks. Will (Talk - contribs) 03:04, 15 December 2006 (UTC)

I was using Firefox 1.5.0.8 on Windows XP for all above tests

Figured you might ask. Will (Talk - contribs) 05:43, 9 November 2006 (UTC)

WikiEd suggestions

I used WikiEd for a day or two; here's some suggestions:

1. Itwould be quite awesome if the syntax highlighting could be stripped outand made available as a separate package. I don't particularly want allof WikiEd, but the syntax highlighting, like FF 2's inlinespellchecker, is something that just Makes Life Better.

• 1. On a related note, could you make the default color for internal links to be something other than that bright red? It is totally overpowering, and overpowers FF 2's spellchecking default color.

1. I don't know what it is doing to the edit box, but I reallyhate how tab is stolen; hitting tab to go to the edit summary box andsave is so second nature that I ran into this every time I edited, eventhough I knew better.

That's all for now. More speedmight be better - it's disconcerting to see WikiEd catch up half asecond or whatever after the edit box has loaded, but I realize thatthat is a nebulous and hard to implement suggestion. --Gwern (contribs) 16:29, 9 November 2006 (UTC)

1 Syntax highlighting is deeply dependent on the whole thing, there is no probably no easy way to extract it.

2 wikEd id fully customizable, check the start of the program User:Cacycle/wikEd.js for your options. In case of the link color simply add the following statement to your monobook.js for a nice neon green:

var wikEdFrameCSS = [];
wikEdFrameCSS['.wikEdLinkName'] = 'color: #00f000; font-weight: bold;';

BTW, on my LCD with TrueType enabled the red looks quite good, when I disable TrueType it looks way too bold.

3 Oh, that seems to be the tab issue from above. I'll check it out.

Cacycle 16:45, 9 November 2006 (UTC)

If you find a nice alternative link style please tell me, I might change wikEd if it looks bad for more users. Cacycle 00:51, 10 November 2006 (UTC)

The tab is no longer be stolen, the issue has been fixed for the next version. Cacycle 05:51, 20 November 2006 (UTC)

Detailed Install Steps

Cacycle I apply to you for adding more details about installing wikEd. I suggest creating numbered step install procedures (1,2,3). I also advise you to supply more information regarding to backwards compatibility like: works with Firefox (1.5, 2.0), MediaWiki 1.8.2, Etc. I’m sure you know this stuff. I am currently installing it and I read your instructions over and over and I couldn’t put it for work, yet. Well I edited my PHP mediawiki files and added an include line to your JS…

I am using the most recent Seamonkey and Firefox under Windows and Wikipedia. I guess that any Mozilla version form the last about one and a half year should work. The code is adapted to the latest current MediaWiki version that Wikipedia is running. Since wikEd is highly dependent on the arrangement and names of certain html code elements on thepage it might not work correctly with older versions.Cacycle 00:45, 10 November 2006 (UTC)

I'm experincing problems with wikEd

Found that JS and CSS variables must be added and enabled under the LocalSettings.php file for this to begin to work. Once done, all of the buttons to appear on the screen, but none work. Error given;

 wikEdFrameDocument.getElementsByTagName is not a function

Not sure what's broke, but I'd like to get it fixed soon. Any ideas?

Please provide more details. Even the least one might help resolving your problem. Under which URL are you running it. Can I get a user account there in order to test it. Thanks, Cacycle 00:40, 10 November 2006 (UTC)

BTW, please sign your comments with ~~~~. Cacycle 01:13, 10 November 2006 (UTC)

12.151.80.14 14:59, 10 November 2006 (UTC) Hi Cacycle. The Wiki in question is an "internal" Wiki that I've started at our company and is not on the Internet at large. I'm using FF 2.0, MediaWiki 1.8.2, have added the variables $wgAllowUserJs = true; and $wgAllowUserCss = true; to my LocalSettings.php file. I went ahead and tried to do the '''{{subst:wikEd}}''' in my User:Nicklutz/monobook.js and it didn't work. I then used the "simple" code setup and the buttons appear at the bottom of the editor window, but they don't work and give me the errors noted above in my FF logs. I really like the screen prints and know wikEd is on kick butt addon, but man, I just can't get it to sing. Also, since your database is locked, I've been unable to create an account on your Wiki. Thanks for the help!

Sysanalyst 18:51, 10 November 2006 (UTC)I was able to finally set up and account and find that wikEd is neat to use on your site. Man, I really want to get it working for our Wiki. All/any help would be great. I'm sure it is just something stupid I've done on my server end. Perhaps a missing add-in/extension/variable. Nice work on wikEd!

Sysanalyst 03:46, 11 November 2006 (UTC) Another person in our company has tried to install and configure wikEd and ran into the exact same error. This other person is using an older version of MediaWiki (1.5) and php (4). I'm trying to get FCKeditor to work as I need something to make it easier for my users to input marked up pages. Thanks.

I am sorry. Maybe you should ask on one of the MediaWiki developers mailing lists. Cacycle 06:05, 14 November 2006 (UTC)

Syntax highlighting updates

I noticed that the syntax highlighting doesn't update as you type. I have to preview my changes with the old preview button to see the new syntax. Will (Talk - contribs) 02:11, 10 November 2006 (UTC)

That is a known problem, but it is quite difficult to solve. Updating the syntax a few moments after the last change might be a solution. Cacycle 03:47, 10 November 2006 (UTC)

The only real problem with that is how long. If you must wait several minutes, it's probably not worth it to most users. Will (Talk - contribs) 04:26, 10 November 2006 (UTC)

Mac OS X & Firefox 2—STOP PRESS: Scrollbar bug fixed!

UPDATE to this post: reflects changes in version 0.9.5
I can report success with version 0.9.4 of wikEd: The phantom scrollbar is now eliminated!

Here are one or two behaviors that still are going on, now that I can edit normally:

1. Using fullscreen mode while editing a comment on a User_talk page is not recommended. Refresh the page to get your editor back. Fixed.

2. When a fresh page editor is invoked, the page is apparently deliberately scrolled down such that the blueWP toolbar buttons are at the top edge of the browser page display area. This is especially convenient when starting a new page, since the"Wikipedia does not have a (whatever) page with this exact name . . ."box does not need to be read by an experienced editor. However, this is a problem when invoking the editing of a talk page comment, since the wE controls, the Subject/headline text edit strip (an edit strip is hereby defined as a single-line text edit box), and all the wE controls are above this toolbar. It seems to me better to "home" the page if possible in all cases for now, and/or make this is a user option that can be turned on and off. Unless this behavior is a bug!NOT Fixed, but see workaround below.

3. Oops, a phantom scrollbar just re-appeared when I first "hot" previewed this comment with the wikEd preview button---incidentally, the wikEd help page doesn't yet have a table describing the button bar with the preview/changes/close preview/scrollToEditButtons/scrollToEditWindow buttons---but it's gone now.Seems to be gone in v0.9.5.

4. At certain moments in a session, clicking a wE control button scrolls the page to the top instead of doing the desired action. Scrolling to reveal the button again and clicking again executes the desired task.Status of this is subject to further testing. Hard to replicate.

Need to get some sleep. Long night before this bug-reporting session. Great job so far, and ttfn.
 Schweiwikist   (talk)  08:51, 10 November 2006 (UTC)
P.S. Would like to post screen shots of these anomalies if it wasn't necessary to upload them to WP with all the "red tape" first!! (odd, the loading error alert has appeared!)

brief followup: can't test this morning, but will be back online asap. thanx!  Schweiwikist   (talk)  14:52, 10 November 2006 (UTC)

Had not seen this when I wrote to your user page, sorry. Thank you so much for your effort, it is appreciated.

1 and 2 are bugs, it happens if you use the [+] tab to add a paragraph.

Do the other problems still happen with 0.9.5. Cacycle 15:59, 10 November 2006 (UTC)

Apparently not. Great job. I'll be working further for a short while. Schweiwikist   (talk)  02:41, 11 November 2006 (UTC)

New comment section for further wikEd bug tests

Add comment (+ tab) bug still manifest in version 0.9.5

There's a decent workaround for this bug until our valiant Java coder can squash it:

1. Scroll down to last comment on page;
2. Invoke a section edit on the comment;
3. Manually type a new comment header with ==Two equal signs arond it== at the end of the old comment to set up a new editable section, and . . .
4. . . .save the page.
5. Now, scroll to the bottom of the updated page;
6. Invoke a section edit on the new editable section you manually created. This is probably doable with a macro.

It's fixed in the upcoming version! Meanwhile just don't use that damn + tab :-)

Cacycle 01:17, 14 November 2006 (UTC)

Fixed in the current version 0.9.6 Cacycle 06:14, 14 November 2006 (UTC)

Compatibility check with "preinstalled" edit buttons (the blue ones on top)

1. testing bold-italic: LOGIC FAULT: select some plain text, then use the preinstalled buttons to make the text bold, then italic, for a bold and italic style. Undo twice to remove the text styling. Now test the preinstalled button behavior in reverse order: italic, then bold: note that the logic works well: the number of quotes is correct. Now try this same experiment with the wikEd buttons: note a discrepancy: clicking bold applies '''three quotes''' to the target. So far so good. Now click the italic wikEd button: it 'subtracts' rather than adds quotes! Test again, but apply italic first, then bold: the behavior is as expected. Can't assume the user's behavior! Programming is like baseball: if it was easy, we'd all play. ;)

Fixed in the current version 0.9.6 Cacycle 06:14, 14 November 2006 (UTC)

1. testing underline, ^super and _sub: very cool syntax highlighting effect, do you call it WYSIKOWILL _{(what you see is kind of what it'll look like)}? in combination with the wiki markup (except for the above problem), this seems fine since here HTML is invoked. I presume there's no issue as to whether HTML markup should surround wiki markup or vice-versa.

Oops, almost forgot:  Schweiwikist   (talk)  04:16, 11 November 2006 (UTC)

Further testing

Coudn't get a wikiproper capitalization above with the "Fix caps inn headers and lists" button. But using it on the list below works! Try it by clicking here.

1. able
2. baker
3. charlie
4. daniel
5. edward
6. frank

 Schweiwikist   (talk)  04:38, 11 November 2006 (UTC)

That's because usually Wikipedia article headings start on level two (==...==). Cacycle 01:27, 14 November 2006 (UTC)

Fixed in the current version 0.9.6 Cacycle 06:14, 14 November 2006 (UTC)

Control arrangment problems

Currently when I edit Wikipedia pages, the tool buttons are laid out improperly (on top of each other) and none are currently working. Futhermore, when I edit a preexisting section, the Minor Edit and Watch This Page check boxes are missing. Will (Talk - contribs) 05:27, 12 November 2006 (UTC)

Does the small wikEd logo on top of the page have the red cross. If so, what is the JavaScript Console error message (Firefox: Tools::JavaScript Console). Cacycle 01:31, 14 November 2006 (UTC)

Editing section broke section header

I clicked on Edit for User talk:AntiVandalBot#Tarot - External Link Deleted. This resulted in version 87484000. I then noticed that the section header for the section I had just changed was broken. So I edited the page and fixed it in version 87484342.

I have every reason to believe that wikEd caused the broken header. Will (Talk - contribs) 05:33, 13 November 2006 (UTC)

You have probably accidentally hit one of those regular Wikipedia character insert links below the edit window. It is the eighth char in the bottom row (ʡ). Cacycle 01:24, 14 November 2006 (UTC)

I don't remember doing so, but it is possible. However, I think I have edited pages, including this one, with wikEd enabled -- only to discover later my changes weren't saved. There was not a version entry for my change. Will (Talk - contribs) 08:33, 14 November 2006 (UTC)

Please read the following section: Known general issues. Do not use the back button to return to an edit page. Cacycle 20:26, 14 November 2006 (UTC)

I can rule that out. I never use the back button. In many cases, the page (typically an anon vandal's IP user page) was blank -- before and after my edit. When I notice that happens, I do use the back button and click save again. That successfully saves the page. Will (Talk - contribs) 20:56, 14 November 2006 (UTC)

Please could you try to figure out what to do to replicate this behaviour and post it here. I have never experienced it, even when I tried to edit an non-existing page. You might be experiencing a squid cache updating delay, i.e. your page has already been saved, but the cached page view still shows the previous version. To figure this out check the page history or reload the page (but do not resubmit, click-enter into the address bar). Cacycle 21:38, 14 November 2006 (UTC)

There definitely is no history entry for the missing edit. Will (Talk - contribs) 06:58, 23 November 2006 (UTC)

Space before typing and other problems

Using FireFox 2.0 on Mac OS 10

1. I need to enter a space before I can type in the textarea
2. if I have some text selected and I type, it adds the text at the end of the selected text, rather than overwrite the selection

≈ jossi ≈ t • @ 07:00, 14 November 2006 (UTC)

Firefox for Mac OS is a litle bugger :-) I'll try to figure out a workaround for these Firefox bugs, but it may take a while because I don't have A Mac for testing. Cacycle 20:32, 14 November 2006 (UTC)

Jossi or Schweiwikist: do you experience the same efects when using this Midas demo. Thanks, Cacycle 20:38, 14 November 2006 (UTC)

the Midas demo seems to work just fine on my PBG4. The "space before" problem seems to only be a problem when editing a large block of text. As I add this comment, wikEd seems to be working just fine in "show highlighting" mode. The only thing that's a little odd is that the keystrokes for copy and paste work, but the copy menu item is not selectable, just paste.  Schweiwikist   (talk)  05:33, 20 November 2006 (UTC)

Paste buttons

The [W] and [T] buttons have a problem. The tool tip for those buttons implies they paste the text from the clipboard. In fact, they appear to modify selected text. A button that combined the two would be welcome.

What would be your suggestion. The [W] is already a combined button. Cacycle 21:29, 14 November 2006 (UTC)

[W] doesn't paste the clipboard contents. Will (Talk - contribs) 22:09, 14 November 2006 (UTC)

They are not supposed to. What exactly makes you think they should paste anything? Their tooltips are "Wikify pasted content" and "Convert pasted content to plain text". Also check User:Cacycle/wikEd_Help. Cacycle 22:18, 14 November 2006 (UTC)

Because the word "pasted" is included in the text. What you want is "selected". What the buttons do has nothing to do with pasting. However, I commonly would like a paste button that does the rest. So you need both. Will (Talk - contribs) 01:50, 15 November 2006 (UTC)

Also, with the update syntax highlighting and fixup buttons, it would be appreciated if you did not change the cursor position or selection. Will (Talk - contribs) 20:42, 14 November 2006 (UTC)

Thanks for this suggestion. Cacycle 21:29, 14 November 2006 (UTC)

My long term wikEd wishlist

I may add to this later. I will note new items below any comments added by others, but those new items will be listed with the initial items.

• WYSIWYG editor^†
• Spell checker^†
• Support for image upload pages

^† marks items that users should be able to disable by adding statements to their monobook.js. If disabled, the code would not load, making the loading time faster for those users.

Will (Talk - contribs) 20:47, 14 November 2006 (UTC)

wikEd will never become a WYSIWIG editor, it is intentionally designed to be a pseudo-WYSIWIG editor. Firefox 2 comes with a spellchecker, wikEd will never have its own spellchecker. Cacycle 21:25, 14 November 2006 (UTC)

Would this help? User talk:Gerbrant/gui/htmlEdit.js. It is supposed to be a WYSIWIG editor. Will (Talk - contribs) 08:05, 14 December 2006 (UTC)

Added item for support of image upload pages. -Will Pittenger 06:36, 18 November 2006 (UTC)

I seem to have broken wikEd completely for me

I tried to readd wikEd to my monobook.js. While looking, I found other stuff I wanted and attempted to add them as well. Now the only item that is working is some adds a edit link to the top part (above the TOC) of each page. And that is providing double links.

It looks like something in more or more of the code sections below is causing part of the problems. The good news is when wikEd is working, it no longer has the problems that it had before with the disable buttons and review changes buttons not working.

I have it working again, but without any of the following. Do you happen to see any conflicts with these?

Code items not working:

User Tabs

//Please leave the following line
 //[[user:Where/usertabs]]

 addOnloadHook(function() {
   if (document.title.search("/") != -1 || document.title.search("- History -") != -1) { //no subpages or history
      return;
   }
   if (document.title.indexOf("User:") == 0 || document.title.indexOf("User talk:") == 0) {
      username_a = document.URL.match(/:.*:(.*)/);
      username=username_a[1];
      addTab("http://en.wikipedia.org/wiki/Special:Contributions/" + username, "contrib", "ca-contrib", "contribs", "");
addTab("http://en.wikipedia.org/w/index.php?title=Special%3ALog&type=move&user="+ username, "page moves", "ca-pagemoves", "page moves", "");
addTab("http://en.wikipedia.org/w/index.php?title=Special%3ALog&type=block&user="+ username, "block log", "ca-blog", "blog", "");
addTab("http://tools.wikimedia.de/~interiot/cgi-bin/count_edits?dbname=enwiki_p&user="+ username, "edit count", "ca-kate", "kate", "");
   }
 });

Purge

// addPurge
addOnloadHook( function (){
    var x = document.getElementById('ca-history');
    if(!x) return;
    if(x.children) x = x.children[0].href;
    else x = x.childNodes[0].href;
    addLink("p-cactions", x.replace(/=history/, "=purge"), 'purge', 'ca-purge', 'Purge the internal cache for this page', 0);
});

AutoArchive

//AUTO ARCHIVE

//The header to put on top of all archives (if the archive is in 'w' mode (modes explained below))
var archiveheader = '';
//Your talk page header for to use when archiving. Remember to keep the <noinclude> tags or else your archive will have your talk page header along with it.
var talkheader = '<noinclude>{{User:Mypage/header}}</noinclude>';
//Your talk page archive page. Insert "NUMBER" where the number of archive you are on goes
var archiveurl = "User_talk:GeorgeMoney/ArchiveNUMBER";
//The mode to archive your talk page. Making this value 'a' will make the script add your archive to the bottom of the current archive. Making it 'w' will totally erase the contents of the current archive (usually you should set the current archive value to a new archive to avoid erasing old archives, where as in append mode (a), you should set it to your current archive to append the contents)
var archivemode = 'w';
//
if(readCookie('archive1') == 'yes' && window.location.href.indexOf('archivestep') == -1) { (window.location.href) = wikiurl+mytalk+'?action=edit&archivestep=2'; }
function changearccontents() {
document.title = "Archival Script Manager";
document.getElementById('bodyContent').innerHTML =
'<div class="dontshow" style="display: none !important;"></div>\n' +
'

<h1 class="firstHeading" style="display:block;">Archive Script Manager</h1>\n' +
'Current archive number (the one that you haven\'t done yet (like if I want to archive to archive 2 then that is the next one not done)): <br> <input type="text" id="archnuminput" value="' + readCookie('archivenum') + '"  size="1" maxlength="4" /> <input type="button" value="save number" onclick="createCookie(\'archivenum\', document.getElementById(\'archnuminput\').value); document.getElementById(\'arclink\').href = wikiurl+archiveurl.replace(\'NUMBER\',readCookie(\'archivenum\'))+\'?action=edit&archivestep=1\';" /><br><br>\n'+
'<a href="'+wikiurl+archiveurl.replace('NUMBER',readCookie('archivenum'))+'?action=edit&archivestep=1" id="arclink" style="font-size: 2em; font-weight: bold;">Click here to begin the archive</a><br>\n' +
'';
document.write('<style type="text/css">.firstHeading, .editsection {display:none;} .dontshow { display: none !important; } #content {background: honeydew !important; border: 3px solid green;} #p-cactions {display: none;}</style>');
}

if(window.location.href.indexOf('archivemanage') != -1||window.location.href.indexOf('Archivemanage') != -1) {
addOnloadHook(function(){ changearccontents(); });
}
if (window.location.href.indexOf('archivestep=1') != -1 && window.location.href.indexOf('action=edit') != -1) {
addOnloadHook(function (){
  if(!readCookie('archivenum') != 'yes') { (window.location.href) = wikiurl+'User:GeorgeMoney/archivemanage' }
  if(archivemode == 'a') {
  document.getElementById('wpTextbox1').value += "\n{{sub"+"st:"+mytalk+"}}";
  } else {
  document.getElementById('wpTextbox1').value = archiveheader+"\n{{sub"+"st:"+mytalk+"}}";
  }
  document.getElementById('wpSummary').value = "JS: Copying talkpage to archive";
  createCookie('archive1', 'yes');
  document.getElementById('editform').submit();
});
}
if (window.location.href.indexOf('archivestep=2') != -1 && window.location.href.indexOf('action=edit') != -1) {
addOnloadHook(function (){
  if(readCookie('archive1') != 'yes') { alert("You shouldn't be at \"&archivestep=2\" because you haven't completed &archivestep=1. Please read the instructions on this archiving script. Redirecting to archive manager. "); (window.location.href) = wikiurl+'User:GeorgeMoney/archivemanage'; return; }
  createCookie('archive1', 'no');
  document.getElementById('wpTextbox1').value = talkheader;
  document.getElementById('wpSummary').value = "JS: Archiving talk page";
  document.getElementById('editform').submit();
});
}

sigContract

addOnloadHook(function() {
   if (document.title.indexOf("Editing ") != 0) {return;}
   var textArea = document.getElementById("wpTextbox1");
   var text = textArea.value;
   var re = /<!--\[\[User:Where\/sigContract\]\];(.*)-->.*<!--ESC:(.*)-->/g;
   var lastIndex = 0;
/*   while (1) {
      var textSubstr = text.substr(lastIndex);
      alert(lastIndex);
      alert(textSubstr); //TODO: remove
      var newIndex = textSubstr.search(re);
      alert("newindex:" + newIndex);
      if (newIndex == -1) {
     break;
      }
      lastIndex += newIndex+1;*/
      text = text.replace(re,
     function(str, p1, p2, offset, s) {
//        alert("In replacement function");
        if (p1 == p2) {
           var newString = "-[[User:" + p1 + "|" + p1 + "]]";
           scKeys[scIndex] = newString;
           scValues[scIndex] = str;
           ++scIndex;
           return newString;
        }
        else {
           return str;
        }
     });
   //}
   textArea.value = text;
});

Signature time localized

//Localized time/date script

function numToMonth(num) {
   if (num==0) {return "Janurary";}
   else if (num==1) {return "February";}
   else if (num==2) {return "March";}
   else if (num==3) {return "April";}
   else if (num==4) {return "May";}
   else if (num==5) {return "June";}
   else if (num==6) {return "July";}
   else if (num==7) {return "August";}
   else if (num==8) {return "September";}
   else if (num==9) {return "October";}
   else if (num==10) {return "November";}
   else if (num==11) {return "December";}
}
 
function monthToNum(month) {
   var tmp = new Date(month + " 1, 2006");
   return tmp.getMonth();
}
 
function adjustTime(str, hour, minute, day, month, year,  offset, s) {
   var time = new Date();
   time.setUTCHours(hour);
   time.setUTCMinutes(minute);
   time.setUTCDate(day);
   time.setUTCMonth(monthToNum(month));
   time.setUTCFullYear(year);

   var timeStr = "";
   if (time.getHours()<10) {timeStr += "0";}
   timeStr += parseInt(time.getHours()) + ":";
   if (time.getMinutes()<10) {timeStr += "0";}
   timeStr += parseInt(time.getMinutes());
   timeStr += ", ";
   timeStr += time.getDate();
   timeStr += " ";
   timeStr += numToMonth(time.getMonth());
   timeStr += " ";
   timeStr += time.getFullYear();
   timeStr += " (UTC";
   var offset = -1*time.getTimezoneOffset()/60;
   if (offset >= 0) {timeStr += "+";}
   timeStr += offset + ")";
   return timeStr;
}

function adjustTime2(str, hour, minute, month, day, year,  offset, s) {
   return adjustTime(str, hour, minute, day, month, year, offset, s);
}

addOnloadHook(function() {
      if (document.title.indexOf("Editing ") == 0) {
       return;
      }
      if (document.location.href.indexOf("action=history") != -1) {
       return;
      }
   if (document.title.indexOf("Talk:") == 0 || document.title.indexOf("talk:") != -1 || document.title.indexOf("Wikipedia:") == 0) {
      var newDoc = document.getElementById("column-content").innerHTML.replace(/(\d\d):(\d\d), (\d{1,2}) ([A-Z][a-z]+) (\d{4}) \(UTC\)/g, adjustTime);
      document.getElementById("column-content").innerHTML = newDoc;
   }
/*   if (document.location.href.indexOf("&action=history") != -1) {
      var newDoc = document.getElementById("bodyContent").innerHTML.replace(/(\d\d):(\d\d), ([A-Z][a-z]+) (\d{1,2}), (\d{4})/g, adjustTime2);
      document.getElementById("bodyContent").innerHTML = newDoc;
   }*/
});
[[User:Where/commentLocalize]]

-Will Pittenger 01:45, 15 November 2006 (UTC)

Please try to figure it out youself by commenting out different parts of your monobook.js (use the multi-line JavaScript comment tag /* ... */) and/or check your JavaScript console for the error message and line number. Don't forget to update with Shift-Reload. Cacycle 01:05, 16 November 2006 (UTC)

That is how I narrowed it down to the listed sections of code. BTW: Your suggestion about /*...*/ would not help. Too often that commenting system was used by the code segments. I ended up copying the code elsewhere. -Will Pittenger 06:08, 16 November 2006 (UTC)

I completely rebuilt the page again. Now only auto archiving is causing problems. I have that disabled until the author can tell me what I am doing wrong. Thanks anyway. Sorry to bother you on this. Will (Talk - contribs) 05:42, 17 November 2006 (UTC)