readably | Static blogs : YAML Slim HTML5

I'm working with appBuilder/procedure editor for Progress release 11.6 (I'm not working with Progress Studio). When I launch the compiler, the compiler result window which comes up is unreadably small, as you can see in following screenshot:

How can I make this readable? (Larger font size)

Thanks in advance

...

So I got this JSON string which looks like this:

...

I have a simple method where I just concatenate a bunch of strings and format it somewhat readably.

...

There's a function which takes optional arguments.

...

I want to use perl to build a document graph as readably as possible. For re-use of nodes, I want to refer to nodes using variables (or constants, if that is easier). The following code works and illustrates the idea with node types represented by literals or factory function calls to a and b. (For simple demo purposes, the functions do not create nodes but just return a string.)

...

Consider a Pandas Dataframe like:

...

I'm working on a single-page web app, that will most typically be used on mobile devices. One of its features is a map mode, which temporarily takes over the entire browser window; a distance scale and some controls are attached to the four corners of the map. Here's a little screenshot of the map so you can tell what I'm talking about:

The map is implemented as a

with position: fixed and all four coordinates zero; I also temporarily set the to overflow: hidden while the map is visible to handle the case of the underlying app display being scrolled away from the origin. That's sufficient to make the map work exactly how I want on desktop browsers. Mobile browsers also required that I give a meta viewport tag with something like "width=device-width,user-scalable=no" in order to make the visible area of the window exactly correspond with the viewport.

This all worked beautifully a few years back when I originally wrote this app, but somewhere along the line iOS Safari stopped honoring any of the meta viewport options involving scaling - apparently too many sites were misapplying the tag, resulting in text that was unreadably small, yet unzoomable. Currently, if you enable the map on this browser, you're likely to get a slightly zoomed-in view, that cuts off those buttons on the right and bottom - and you can't do anything about it, because all touches are interpreted as zoom/pan gestures for the map, rather than browser scrolling. The map isn't terribly useful without the features accessed through those buttons - and without the top-right button, you can't even close the map. The only way out is to reload the page, which may result in loss of unsaved data.

I'm definitely going to be adding the use of history.pushState/onpopstate so that the map overlay behaves like a separate page. You'd be able to get out of the map mode using the browser's Back button - but that doesn't address the rest of the loss of the functionality due to missing buttons.

I've considered using .requestFullscreen() to implement the map overlay, but it's not supported everywhere that the app would otherwise be usable. In particular, it apparently doesn't work at all on iPhones, and on iPads you get a status bar and a huge 'X' button overlaying your content - my distance scale would likely not be readable any more. It's not semantically what I really want, anyway - I need the full window, not the full screen.

How do I get a full-window display working on modern browsers? All the information I can find on the subject talks about using the meta viewport tag, but as I mentioned that no longer works.

...

I'm going to ask a series of questions of increasing complexity to see how far we can get using regexes (and regexes only!) to analyze poker hands. Perhaps I'll put the successive answers into something like a blog post to demonstrate the power of regexes when used creatively.

Is regex the right tool for this job? Absolutely not! Any programmatic string processing could do this task a million times better and more readably. Having said that, I'm hoping that the answers to these questions will show someone how powerful regexes can be with a little bit of creativity and also, perhaps where even with some creativity it cannot be done without some programming logic.

Goal: the goal in these posts is to construct a single regex expression to determine the rank of someone's five-card poker hand. For example, "AKAKA" would be a full house.

Cards: for this question, we'll use 52 cards displayed as follows:

...

While running a batch file, I get the below error: nuget is not a recognized as an internal or external command It's not working from command prompt. Have a look at the below screenshot.

...