fde101

No need for algorithms for a simple 1D barcode.  Just use a font.

Just make sure we keep the v2 requests for this in one thread.  Things get more confusing when they wind up scrambled all over the forum.

Serif had actually suggested that we should for requests which are still relevant.  That was way back when v2 had just been released.
Thankfully they don't make us "shell" out any additional money for posting our requests...

I think what is being suggested is that the popup box where the URI is entered have a few tabs to build some of the common schemes for the user so that the user doesn't need to work out the encoding for all of them.
For example, iQR (on the App Store for the Mac), in addition to the URL option (which they label "WWW"), has tabs for Phone (enter a phone number), SMS (phone number and message), eMail (to address, subject and body), Map (enter an address and it looks it up using Google Maps or some other map service), Contact (first/last name, phone number(s), email address, web page, street address), Calendar (event name, when, where, etc.), PayPal/Bitcoin/SEPA payments (account, description, price, etc.), WiFi (network name/SSID, password, encryption type, hidden?), and Text.
 

 
It also provides an interesting range of formatting options to spice up the appearance of the generated codes:

 
Granted that this range of formatting options is probably a bit out of scope for a program that is not specialized in producing QR codes, but still thought I would point it out.  The more important thing to consider is to throw in the forms for a few of the common URI schemes.

I think what is being suggested is that the popup box where the URI is entered have a few tabs to build some of the common schemes for the user so that the user doesn't need to work out the encoding for all of them.
For example, iQR (on the App Store for the Mac), in addition to the URL option (which they label "WWW"), has tabs for Phone (enter a phone number), SMS (phone number and message), eMail (to address, subject and body), Map (enter an address and it looks it up using Google Maps or some other map service), Contact (first/last name, phone number(s), email address, web page, street address), Calendar (event name, when, where, etc.), PayPal/Bitcoin/SEPA payments (account, description, price, etc.), WiFi (network name/SSID, password, encryption type, hidden?), and Text.
 

 
It also provides an interesting range of formatting options to spice up the appearance of the generated codes:

 
Granted that this range of formatting options is probably a bit out of scope for a program that is not specialized in producing QR codes, but still thought I would point it out.  The more important thing to consider is to throw in the forms for a few of the common URI schemes.

Serif had actually suggested that we should for requests which are still relevant.  That was way back when v2 had just been released.
Thankfully they don't make us "shell" out any additional money for posting our requests...

This strikes me as a great example of something that would hopefully be simple to provide with a plugin if an API/SDK is ever released...

@GarryP that is not what @A_B_C is asking for - I understood the request quite clearly, and it is an obvious thing to have in place, which I definitely believe should have been there from the beginning.
The request is not to open or close the entire panel, but the individual sections within the panel, all at once.
In other words, clicking the triangle to collapse or expand "Ligatures", "Figure Position", "Capitals", etc. - but instead of just one of them, when a modifier is held down, collapse or expand all of them at the same time.
The idea is that if they are all expanded, you could collapse all of them at once, then expand individually the one you are interested in, without having to go hunt through the expanded sections that might have the one you are looking for scrolled out of view.

No, those are not global colors in the sense that is being requested here.  If you edit a global color on a swatch palette, every object in the document which uses that global color is updated immediately to use the new color which was set.
Global colors are only supported in Document-level swatch palettes, and for good reasons, which have been discussed previously here on the forum.
What is being requested here is basically, if the document has global colors A, B and C, then allow me to save schemes X, Y and Z, each of which may have different colors for each of A, B and C, so that when I switch to scheme Y, every object in the document which uses one of those global colors is immediately updated to match the selected scheme.

They are not simplifying it artificially.  They are ignoring nodes that are already flagged to be ignored by the file they are reading the shape from.
To simplify an arbitrary existing shape they would need an algorithm to identify which nodes to remove and/or adjust, which is not part of what they are doing here.

@GarryP that is not what @A_B_C is asking for - I understood the request quite clearly, and it is an obvious thing to have in place, which I definitely believe should have been there from the beginning.
The request is not to open or close the entire panel, but the individual sections within the panel, all at once.
In other words, clicking the triangle to collapse or expand "Ligatures", "Figure Position", "Capitals", etc. - but instead of just one of them, when a modifier is held down, collapse or expand all of them at the same time.
The idea is that if they are all expanded, you could collapse all of them at once, then expand individually the one you are interested in, without having to go hunt through the expanded sections that might have the one you are looking for scrolled out of view.

@GarryP that is not what @A_B_C is asking for - I understood the request quite clearly, and it is an obvious thing to have in place, which I definitely believe should have been there from the beginning.
The request is not to open or close the entire panel, but the individual sections within the panel, all at once.
In other words, clicking the triangle to collapse or expand "Ligatures", "Figure Position", "Capitals", etc. - but instead of just one of them, when a modifier is held down, collapse or expand all of them at the same time.
The idea is that if they are all expanded, you could collapse all of them at once, then expand individually the one you are interested in, without having to go hunt through the expanded sections that might have the one you are looking for scrolled out of view.

A modest suggestion that would improve UX in the present framework: please add Collapse-all and Expand-all by Alt-clicking the section headers inside a panel.
This would at least provide a workaround for many orientation problems in crowded panels and reduce search time.

That change just missed this build, thanks 

I think what is being suggested is that the popup box where the URI is entered have a few tabs to build some of the common schemes for the user so that the user doesn't need to work out the encoding for all of them.
For example, iQR (on the App Store for the Mac), in addition to the URL option (which they label "WWW"), has tabs for Phone (enter a phone number), SMS (phone number and message), eMail (to address, subject and body), Map (enter an address and it looks it up using Google Maps or some other map service), Contact (first/last name, phone number(s), email address, web page, street address), Calendar (event name, when, where, etc.), PayPal/Bitcoin/SEPA payments (account, description, price, etc.), WiFi (network name/SSID, password, encryption type, hidden?), and Text.
 

 
It also provides an interesting range of formatting options to spice up the appearance of the generated codes:

 
Granted that this range of formatting options is probably a bit out of scope for a program that is not specialized in producing QR codes, but still thought I would point it out.  The more important thing to consider is to throw in the forms for a few of the common URI schemes.

This is almost as bad as RED getting a patent on lossy-compressed RAW encodings that happen to be above a certain resolution.  Making it specific to high resolutions suddenly gets past prior art of doing exactly the same thing at lower resolutions, which had been around since before RED existed?  Patenting a specific algorithm for doing that - maybe, but stretching it.  Patenting it as a concept?  Inexcusable.
There is plenty of software which moved (or duplicated) sliders and numeric fields onto the canvas in the form of handles, so creating on-canvas handles for yet another set of sliders is suddenly inventive enough to be patentable?  The patent offices may be stupid enough to let something like that slide, but they certainly shouldn't be.
Direct manipulation of just about anything should be an obvious end goal by now, hardly inventive enough to be considered for a patent, even if no one else has tried it yet.

No need for algorithms for a simple 1D barcode.  Just use a font.

What would be really interesting would be to also find a way to represent at least some of the common ones as handles on the letters (when zoomed in far enough!!!) the way that handles are used for rounding rectangles and shaping gears and the like...
The Typography panel would be a logical place for these otherwise, in my way of thinking.

I think what is being suggested is that the popup box where the URI is entered have a few tabs to build some of the common schemes for the user so that the user doesn't need to work out the encoding for all of them.
For example, iQR (on the App Store for the Mac), in addition to the URL option (which they label "WWW"), has tabs for Phone (enter a phone number), SMS (phone number and message), eMail (to address, subject and body), Map (enter an address and it looks it up using Google Maps or some other map service), Contact (first/last name, phone number(s), email address, web page, street address), Calendar (event name, when, where, etc.), PayPal/Bitcoin/SEPA payments (account, description, price, etc.), WiFi (network name/SSID, password, encryption type, hidden?), and Text.
 

 
It also provides an interesting range of formatting options to spice up the appearance of the generated codes:

 
Granted that this range of formatting options is probably a bit out of scope for a program that is not specialized in producing QR codes, but still thought I would point it out.  The more important thing to consider is to throw in the forms for a few of the common URI schemes.

What would be really interesting would be to also find a way to represent at least some of the common ones as handles on the letters (when zoomed in far enough!!!) the way that handles are used for rounding rectangles and shaping gears and the like...
The Typography panel would be a logical place for these otherwise, in my way of thinking.

I would have thought a dialog box is rather too transient for something like this. I hope the controls will be added via a panel.

I think what is being suggested is that the popup box where the URI is entered have a few tabs to build some of the common schemes for the user so that the user doesn't need to work out the encoding for all of them.
For example, iQR (on the App Store for the Mac), in addition to the URL option (which they label "WWW"), has tabs for Phone (enter a phone number), SMS (phone number and message), eMail (to address, subject and body), Map (enter an address and it looks it up using Google Maps or some other map service), Contact (first/last name, phone number(s), email address, web page, street address), Calendar (event name, when, where, etc.), PayPal/Bitcoin/SEPA payments (account, description, price, etc.), WiFi (network name/SSID, password, encryption type, hidden?), and Text.
 

 
It also provides an interesting range of formatting options to spice up the appearance of the generated codes:

 
Granted that this range of formatting options is probably a bit out of scope for a program that is not specialized in producing QR codes, but still thought I would point it out.  The more important thing to consider is to throw in the forms for a few of the common URI schemes.

An important step, but don't discount that color font support is also important.
If not in parallel to variable fonts, please make sure these are not neglected either!

I think what is being suggested is that the popup box where the URI is entered have a few tabs to build some of the common schemes for the user so that the user doesn't need to work out the encoding for all of them.
For example, iQR (on the App Store for the Mac), in addition to the URL option (which they label "WWW"), has tabs for Phone (enter a phone number), SMS (phone number and message), eMail (to address, subject and body), Map (enter an address and it looks it up using Google Maps or some other map service), Contact (first/last name, phone number(s), email address, web page, street address), Calendar (event name, when, where, etc.), PayPal/Bitcoin/SEPA payments (account, description, price, etc.), WiFi (network name/SSID, password, encryption type, hidden?), and Text.
 

 
It also provides an interesting range of formatting options to spice up the appearance of the generated codes:

 
Granted that this range of formatting options is probably a bit out of scope for a program that is not specialized in producing QR codes, but still thought I would point it out.  The more important thing to consider is to throw in the forms for a few of the common URI schemes.

Accordingly, shouldn't that be in the Feedback forum as it is not for this beta?
In any case, since these fonts are constructed by center-line strokes, when this is done, please consider leveraging that fact by allowing brushes to be applied to them (for those not doing CNC work, anyway...).