kontur / fontsampler-wordpress-plugin Goto Github PK

It would be neat to have an instant preview of the font when selected for upload, so to avoid uploading the wrong font.

In addition, this would check the font file works together with opentype.js

It looks as though an SQL query is being printed out in the FontSampler plugin (this occurred after clicking "Edit" to change the settings of a font sample).

Might seem counter intuitive, but there could be situation where you'd simply like to have some controls, like a nice looking family switcher, and text switcher, but not allow typing in the textarea.

I'm thinking the option to upload woff and woff2 should be ideal. If a user then in the settings enables legacy formats, the upload fields for those formats are offered as well.

Settings should include a list of the common features that users can check to make them defaults for new samplers. There should also be an option to apple defaults to all samplers when they are changed.

Currently only the base frontend and customized css get merged, but customized library css like rangeslider etc. should also be merged to result in one single css file for the plugin.

Allow customising the UI position: Above or below the text input field

This is easily the worst usability issue atm. In order to create a fontsampler the fonts have to already be uploaded, but the intuitive way to go about it would be to upload them while creating the fontsampler.

While it's nice to have different strings or pangrams, or numbers, it might be a nice alternative to instead have preset text strings in the different languages the font supports. This could benefit from integration with the OT locl feature activation.

As Safari will support OpenType Variation soon, it would be useful to fontsampler to be ready. It would require sliders as done by axis-praxis.org but the best way will be a step slider #42

I imagine doing this via custom language files and a lang="" tag on the [fontsampler] shortcode.

There needs to be a better layout for the way the interface gets rendered when some or most options are not picked, so that the different elements collapse into just one row.

Alternatively to this, the admin interface could offer a drag and drop interface for sorting the UI elements.

Like current default settings, but allow to set them on a per instance basis to further customise different fontsamplers on the same site.

When uninstalling the plugin it would be ideal if the remaining [fontsamper id=xx] would either be pointed out to the user or optionally removed.

The default font displayed in a sampler is the first font in the menu. Please add the option to choose other fonts. This could just be a checkbox next to each font that can only be active for a single font.

Fontsampler code is appearing on pages as text. This is what I see when I set up Fontsampler on a clean install of Wordpress with the default theme.

There should be an option to designate a fontsampler as left to right or right to left script and the text field should behave accordingly.

There might be implications for the interface as well, when the UI does not fill complete rows and those would - by default - be left aligned. This might have to be a separate option though, as it should not automatically change the interface: Imagine a page with several fontsamplers of one typeface, of which only one is a LTR script - it would look odd if only the one fontsampler has it's UI aligned differently.

The dropdown selector for multiple fonts does not display all of the fonts in a sampler. It displays the first font set for each menu entry.

As a first level it would be great to be able to change the appearance of the plugin by some simple settings, like:

• changing main colour variables
• changing removing / changing layout borders

It might further be good to implement at least some class or id for each font-sampler so people can manually overwrite styles for specific font samplers as well.

Down the line it would be great if those could be done even via the admin interface as additional styles.

Adding a checkbox to the admin interface to set the input field of the fontsampler to multiline or singleline would be great (i.e. allowing line breaks input). Some of this is already implemented in the jquery-fontsampler

After the initial test for opentype features where are several features still missing, like swashes, stylistic sets, different number styles, etc.

A font sampler with multiple font sets will only work if it is the first sampler created (ID 1). Other samplers with multiple fonts sets display this error, even if they have the same configuration as ID 1.
“The typesampler with ID 4 can not be displayed because some files or the type sampler set are missing!”

Initial size setting is shown in menus, but does not affect the text displayed.

If I put multiple samplers on one page only one set of controls appears. These controls only affect the first sampler, others cannot be changed.

Especially dynamically showing and hiding the available UI ordering options should be synct with the checked options, so only things that are checked can also be included in the ordering.
The page further needs an overall revamp to structure it more clearly.

The Font sets & files page is going to get messy for sites that offer lots of fonts. Two ideas come to my mind:

• Group records into collapsible containers (like dropdown menus) . For example:
  Helvetica
  Helvetica Regular
  Helvetica Bold
• Manage them like pages. Let users assign categories to font records, and add a search bar to the Font sets & files page.

The sliders used for units, in both the front end and back end, are not perfect. For example, I cannot get the “font_size initial px: ” slider to stop at 128px, only 127 or 129. Please allow text to be entered in these fields for setting precise values.

It would help tremendously to see the changes right away in a placeholder fontsampler instance.

Since this is for wordpress, it must be under a GPL-compatible libre license. Please add a license file clarifying which license you choose :)

Following this rough guideline: https://codex.wordpress.org/Creating_Tables_with_Plugins#Adding_an_Upgrade_Function

Essential before initial release.

It would be ideal to sniff available Opentype features from uploaded fonts and automatically offer only available features as an option in the admin interface.

All code should slowly adapt the WP coding standards more stringently: https://github.com/WordPress-Coding-Standards/WordPress-Coding-Standards

Adding any kind of sanity checks is needed - even JS based. Right now both forms fire through even with entirely empty fields.

This will get rid of the mandatory font name, which isn't used except for internal identification anyway.