wthit56

Another day, another learn...ing...s.

This covers everything from how to start editing/making a generator, to writing perchance code. (The more web-y stuff are covered in my other tutorial.)

Seems to be related to this: ___htmlToElements(). It takes a string which is the text, ignoring the fact that HTML entities are not normal characters and should not be interpreted as normal HTML. For example, < will be interpreted as < which can open a tag.

Example: https://perchance.org/qzi72h52te#edit

So if an element contains any perchance code, and HTML entities, the HTML entities are essentially lost and become real characters. Which isn't what you want if you're trying to present plain-text code to the user.

Definitely does not work as expected at least.

For example, I'm linking to the Learn tab but that doesn't actually open the Learn tab.

No error message makes it to the display.

In the console there is:

Critical error in __createPerchanceTree: TypeError: Cannot read properties of undefined (reading 'startsWith')

And in the error messages there's just this:

Your generator's script seems to have errors in it. If you haven't recieved any other errors above this one which could indicate what went wrong, then this could be a bug in the Perchance engine. *etc...*

("recieved" should be "received" by the way 😜)

As seen here: https://perchance.org/p5bdhjbfv6#edit

So it still runs somehow? And accesses the grandparent somehow? Likely a bug with how escapes are stripped out--and perhaps recursively processed or something...

https://perchance.org/2p16eseroi#edit

Got a tricky situation here. If I do a .replace() on the html of an element (just some formatting stuff for code blocks), the update() is still referencing old text nodes. So it just doesn't care about the new ones that are there from the replace and they stay there. And it adds new ones that are actually updated.

Not sure what to do about that, honestly. Ideally I'd be able to do this replace before the initial update of code blocks is run. Is there some way of doing that?

The issue seems to only happen for code blocks? Maybe?

Based on the newly added explanation of the public API calls themselves, I've made a little plugin for using those APIs a little easier, along with the usual demos and explanations.

If I have padding on the body, it doesn't do much. Because there's height:100% on the body by default, which is actually incorrect and causes this issue for reasons. As seen here: https://perchance.org/o0demyuvpj#edit Whereas without any default styles the padding would work as expected.

It should be max-height:100% instead, which would not have the problem. Could I request that be changed?

A while back I put together everything I could find about perchance. One such document included all properties on objects on perchance pages (that aren't the built-ins from JS). On discord someone said how they wish there was such a reference. So... now there is!

perchance.org/api/getGeneratorList?max=123 - limit to a maximum of 123 generators

Are they latest-first?

It doesn't seem like this "max" has to do with how many generators are returned. But the number returned does scale with it. So... last-updated age, perhaps? Not sure what unit of time it would be though. Quite confused.

Could be that it's the max, before it removes private generators? Which would kind of make it not be the "maximum" anything really. Not a very useful parameter as it would be if it would actually give X number of generators--for paging, etc.

(Speaking of which is there a way of specifying "start from X generator number and later" for paging to work well?)

I don't know what the default "max" or whatever is for this api. Seems to fluctuate how many are returned, and it's not always a round number.

Does anyone know how to get the image url from the $meta object of another generator? I think there's an /api/ fetch I can do for it, but that stuff isn't documented anywhere, I don't think.

Just finished a web coding primer, for the perchance community. I'm hoping it helps people get started with the non-perchance side of perchance quicker and easier. 👍

(It's not intended as full documentation, just a taster of common features, and a glimpse of more complex concepts so people know they can search for them elsewhere.)