Check out Janggi (Korean Chess), our featured variant for December, 2024.


[ Help | Earliest Comments | Latest Comments ]
[ List All Subjects of Discussion | Create New Subject of Discussion ]
[ List Earliest Comments Only For Pages | Games | Rated Pages | Rated Games | Subjects of Discussion ]

Comments/Ratings for a Single Item

EarliestEarlier Reverse Order LaterLatest
Bob Greenwade's SVG Library. The SVG files used in Bob's library of pieces.[All Comments] [Add Comment or Rating]
🕸Fergus Duniho wrote on Mon, Jan 8 04:31 PM UTC in reply to Bob Greenwade from 02:50 AM:

I merely copied the practice from one of the other SVG pages (the main Alfaerie one, I think).

I have now looked at that page. It didn't have the mistakes in HTML I noticed on this page. Although you copied the inner part of the table, you didn't copy the <table> tags. Additionally, the Alfaerie SVG page didn't use <figure> tags at all. Your page is better for using them, because they let you place the name of each piece underneath its image. But you also used <figure> as a container for other <figure> tags, and that wasn't a correct use of this tag.


💡📝Bob Greenwade wrote on Mon, Jan 8 04:58 PM UTC in reply to Fergus Duniho from 04:31 PM:

Now, that is something I didn't know about. Short term, I'll look up those tags to get the thought process in my brain.

If nothing else, I'll try to remember about it, and take a good look before editing, the next time I have an update to this. (That's liable to be a good while, unless I come across something really unexpected once I can start building variants again.)


💡📝Bob Greenwade wrote on Sun, Jan 14 05:27 PM UTC:

Minor edit to this page: The Flying Stag at the bottom is now wstag-welementair (instead of wstag-wwings).

No rush to change this on the actual page, Fergus, but please do when you have a minute.


💡📝Bob Greenwade wrote on Mon, Jan 15 05:36 PM UTC:

Argh. I just found that I'd neglected to include the Malkia on the page. The icon's there; it just didn't have a space on the list.

That's fixed here; make the transfer when you can, Fergus.


💡📝Bob Greenwade wrote on Fri, Jan 19 06:44 PM UTC:

@Fergus: And now I did the same thing with the Angel.

I won't be sending a new upload until I get some open slots, so please transfer the HTML when you have a couple of minutes.


💡📝Bob Greenwade wrote on Tue, Jan 23 03:08 AM UTC:

@Fergus: Once more, and probably the penultimate for a good while.

A new ZIP file, and updated content.

If I don't get any new discoveries, requests, etc. (such as someone pointing out icons to represent colors), I'll have one more update to the HTML with the ZIP file of everything.

(I don't know whether it'd be better to put the encompassing ZIP file with this page, or have you transfer it to the official page.)


💡📝Bob Greenwade wrote on Tue, Jan 23 05:01 PM UTC in reply to Bob Greenwade from 03:08 AM:

@Fergus: I spoke too soon; I figured out how to do color Modifiers. So, I'll upload those and make a new edit later today; you can then unzip both files at once, and only have to change the HTML one time.


💡📝Bob Greenwade wrote on Tue, Jan 23 08:29 PM UTC:

@ Fergus: Okay, I uploaded the Color Modifiers, and created a new section for them in the HTML. Please unzip that ZIP and this one, and transfer the HTML for what I hope is the second-to-last time for a good while.


🕸Fergus Duniho wrote on Wed, Jan 24 02:31 AM UTC in reply to Bob Greenwade from Tue Jan 23 08:29 PM:

Okay, I have unzipped your files and copied your page. I made one change, turning a second <P> tag into a closing </P> tag.


💡📝Bob Greenwade wrote on Wed, Jan 24 03:22 AM UTC in reply to Fergus Duniho from 02:31 AM:

Thank you, for both the copying and the correction. (A special thank-you for being that much on the ball!)


💡📝Bob Greenwade wrote on Sat, Jan 27 12:35 AM UTC:

@Fergus: I've set this page to Private, but as I did so it made all the icon windows appear in my browser in a single column. I'm not sure whether that's just an idiosyncrasy, or I did something to screw things up.

I'm coming across a few icons that I failed to catalogue the last time around, but I'll add them as I go and they can be added after I upload the master ZIP.

Addendum: Also, the link to this page is no longer showing up anywhere on my profile or Unpublished sections, so I don't have a way (short of bookmarking in my browser) of marking where it is.


🕸Fergus Duniho wrote on Sat, Jan 27 02:37 AM UTC in reply to Bob Greenwade from 12:35 AM:

I've set this page to Private, but as I did so it made all the icon windows appear in my browser in a single column. I'm not sure whether that's just an idiosyncrasy, or I did something to screw things up.

I temporarily switched it back to Members-Only, and it made no difference. Looking at your HTML, I see that you radically changed it, and the code that enabled the images to neatly line up in rows is no longer there. I would recommend going back to the last revision using FIGURE tags. If you didn't intentionally change your HTML, you might have used WYSIWYG mode. Do not use this mode on carefully written HTML, as it can mess it up.

Also, the link to this page is no longer showing up anywhere on my profile or Unpublished sections, so I don't have a way (short of bookmarking in my browser) of marking where it is.

There is a new menu item in the menu for seeing your works-in-progress.


Kevin Pacey wrote on Sat, Jan 27 04:20 AM UTC in reply to Fergus Duniho from 02:37 AM:

@ Fergus

In clicking on the works-in-progress menu item, I saw a paragraph that was followed by '(not working yet)'. Assuming that still holds, if fresh submissions are submitted during the transition process (I cannot guess if it will be short), do they currently still go onto the 'Your Unpublished Submissions' page list?


💡📝Bob Greenwade wrote on Sat, Jan 27 04:25 AM UTC in reply to Fergus Duniho from 02:37 AM:

OK, I reinstated the previous version. I actually hadn't done anything in the way of editing at all, other than changing that one thing, so I'm not sure what happened.

There is a new menu item in the menu for seeing your works-in-progress.

Yes, there is now. Thanks for adding that. (It wasn't there when I wrote the remark about not seeing a link; I did look for it exactly where it is now.)


🕸Fergus Duniho wrote on Sat, Jan 27 01:20 PM UTC in reply to Kevin Pacey from 04:20 AM:

In clicking on the works-in-progress menu item, I saw a paragraph that was followed by '(not working yet)'.

I deleted that, because it is working now.

Assuming that still holds, if fresh submissions are submitted during the transition process (I cannot guess if it will be short), do they currently still go onto the 'Your Unpublished Submissions' page list?

No, it just meant that until it was working, someone who went to the page's URL could still see its contents.


🕸Fergus Duniho wrote on Sat, Jan 27 01:26 PM UTC in reply to Bob Greenwade from 04:25 AM:

OK, I reinstated the previous version. I actually hadn't done anything in the way of editing at all, other than changing that one thing, so I'm not sure what happened.

I did an experiment where I went into WYSIWYG mode and back to HTML mode without editing anything, and the result was what you got. Instead of FIGURE tags connecting images and captions, each image and each caption was in its own P tag, and the FIGURE tags were just gone. So, I should put up a confirm box with a warning when someone tries to switch to WYSIWYG mode when there is content that might be damaged by it.


💡📝Bob Greenwade wrote on Sat, Jan 27 03:16 PM UTC in reply to Fergus Duniho from 01:26 PM:

I did an experiment where I went into WYSIWYG mode and back to HTML mode without editing anything, and the result was what you got. Instead of FIGURE tags connecting images and captions, each image and each caption was in its own P tag, and the FIGURE tags were just gone. So, I should put up a confirm box with a warning when someone tries to switch to WYSIWYG mode when there is content that might be damaged by it.

That'll do, at least until the sections with such content can automatically activate the Source button (and manually deactivating it generates that warning).

Reminder: This happens to Interactive Diagrams as well.


H. G. Muller wrote on Sat, Jan 27 06:13 PM UTC in reply to Fergus Duniho from 01:26 PM:

WYSIWYG mode pretty much destroys all HTML tags, except for a very small subset that it could have generated itself through the editor buttons. And even then it will destroy almost any property of such tags (such as id, style or class).


🕸Fergus Duniho wrote on Sat, Jan 27 07:07 PM UTC in reply to H. G. Muller from 06:13 PM:

WYSIWYG mode pretty much destroys all HTML tags, except for a very small subset that it could have generated itself through the editor buttons. And even then it will destroy almost any property of such tags (such as id, style or class).

I have removed the Source button from CkEditor, which makes the Format button the only way to switch it between HTML and WYSIWYG mode, and I have put a confirm box on the Format button to warn anyone who uses it to select WYSIWYG mode. Besides that, I have edited the text about each format to make it clear that WYSIWYG is not recommended, as it can alter your HTML.


H. G. Muller wrote on Sat, Jan 27 07:22 PM UTC in reply to Fergus Duniho from 07:07 PM:

I am not sure this is a good idea; I often need the Source button in texts I composed entirely in WYSIWYG mode, to fix a typo in a URL of an embedded image or link.


💡📝Bob Greenwade wrote on Sat, Jan 27 07:34 PM UTC in reply to H. G. Muller from 07:22 PM:

I am not sure this is a good idea; I often need the Source button in texts I composed entirely in WYSIWYG mode, to fix a typo in a URL of an embedded image or link.

I agree. There are times when I want to edit the ID in one section and the text of another in one go, switching back and forth, such as when I'm changing a few pieces' icons and/or XBetza.

In fact, if the Source button can be made "sticky," so that leaving with it on means that it's on when I come back, that would be ideal.


🕸Fergus Duniho wrote on Sat, Jan 27 07:58 PM UTC in reply to H. G. Muller from 07:22 PM:

I often need the Source button in texts I composed entirely in WYSIWYG mode, to fix a typo in a URL of an embedded image or link.

You do not need the Source button for that. The Format SELECT item will let you do that without using the Source button.


🕸Fergus Duniho wrote on Sat, Jan 27 08:04 PM UTC in reply to Bob Greenwade from 07:34 PM:

There are times when I want to edit the ID in one section and the text of another in one go, switching back and forth, such as when I'm changing a few pieces' icons and/or XBetza.

Just change the format with the Format drop down box. Nothing is stopping you from switching modes in CkEditor. You just can't do it with the Source button, because that makes it too easy to mess up your code without warning.

In fact, if the Source button can be made "sticky," so that leaving with it on means that it's on when I come back, that would be ideal.

The Format drop down box is sticky. When you load a page to edit it, it will be on the format used for your page when it was last saved.


💡📝Bob Greenwade wrote on Sat, Jan 27 08:12 PM UTC in reply to Fergus Duniho from 08:04 PM:

Just change the format with the Format drop down box. Nothing is stopping you from switching modes in CkEditor.

The problem with this is that when I have an ID in one section and text to edit in the other, switching to WYSIWYG for the whole thing screws up the ID, and I have to start over. There's no ability to go back and forth.

You just can't do it with the Source button, because that makes it too easy to mess up your code without warning.

I've never messed up my code using the Source button. When it's happened, it's always been with the Format drop-down. When the Source button's been involved, it's because I had the page in WYSIWYG with the Source button on in the section in question, and of course the Source button isn't sticky so it switched directly to WYSIWYG. It's for this reason that I'm careful to never edit a page with an ID without opening the source code first.


🕸Fergus Duniho wrote on Sat, Jan 27 08:30 PM UTC in reply to Bob Greenwade from 08:12 PM:

The problem with this is that when I have an ID in one section and text to edit in the other, switching to WYSIWYG for the whole thing screws up the ID, and I have to start over. There's no ability to go back and forth.

The lesson here is don't use WYSIWYG at all. While its destruction may be greater for an Interactive Diagram, it can mess up other HTML too.

I've never messed up my code using the Source button.

Whether or not you have is not as important as whether you could. As a test, I briefly restored the Source button, opened your page to edit it, clicked on the Source button twice for the pieces section, and it destroyed all your <FIGURE> tags, placing each image and caption in its own <P> tags.


25 comments displayed

EarliestEarlier Reverse Order LaterLatest

Permalink to the exact comments currently displayed.