Textpattern CMS support forum
You are not logged in. Register | Login | Help
- Topics: Active | Unanswered
Re: Feedback to: Textpattern 4.5.0 Beta released
zero wrote:
Bloke wrote:
Updated. Any more advances on this?
That’s really good, Stef, I can’t improve on that.
How about this (excuse english) making the focus is what a Form is in txp:
In Textpattern, a Form represents snippet or chunk of text, HTML, and Textpattern tags that can be reused to display content throughout your website. (This definition of Form differs from the usual meaning of a series of fields to be completed, such as in a Contact Form or Search Form.)
Offline
Re: Feedback to: Textpattern 4.5.0 Beta released
I prefer tye’s text, as it puts the positive definition before the negative distinction.
I always thought of Textpattern’s “forms” in terms of Platonic Forms: the archetypal patterns that shape content into specific phenomena. Although I agree the jargon can be confusing to newbies, and I wouldn’t complain if it were changed to something like “partial”, I think the Platonic vision of Forms fits Textpattern’s model very well.
Offline
Re: Feedback to: Textpattern 4.5.0 Beta released
There is a file in the temp directory called .nodelete. As it starts with a dot, it is not visible to osX.x. Shouldn’t it be a readme file?
Yiannis
——————————
NeMe | hblack.art | EMAP | A Sea change | Toolkit of Care
I do my best editing after I click on the submit button.
Offline
Re: Feedback to: Textpattern 4.5.0 Beta released
johnstephens wrote:
After selecting one or more checkboxes from the table, I picked “Change privilege” from the “With selected…” dropdown. Usually, another select input appears with the privilege levels, but in Remora, it remains hidden.
Cannot reproduce here. I think your browser still uses cached a stale copy of .../textpattern/textpattern.js. Safari for instance is notorious for keeping old caches. Please try again with a clean cache or a different browser and report back.
Offline
Re: Feedback to: Textpattern 4.5.0 Beta released
wornout wrote:
Problem with GLZ_CF.
Due to the changes in the “Write” tab this is to be expected. Please raise an issue in the plugin’s queue.
Offline
Re: Feedback to: Textpattern 4.5.0 Beta released
colak wrote:
There is a file in the temp directory called .nodelete.
This is for technical reasons: Git does not work for empty directories so users who want to fork Textpattern’s blessed repository mirror on Github would miss this directory if it didn’t contain at least one file.
Offline
Re: Feedback to: Textpattern 4.5.0 Beta released
I just updated my local site and I’m really liking the admin theme improvements—and everything else I’ve yet to fully appreciate. I’m now a lot less fired up to design a new admin theme because they all look so nice. :)
I do agree with Gocom, though. I think the system messages are not visible enough. I understand the space-saving decision to put them at bottom, but I actually rely on the “Article saved” cue all the time, so it was immediately apparent when it didn’t stand out to me. I can imagine what Gocom is saying might work well… making the colors more bold so that even in peripheral vision the green, orange, and red are more discernable. That would probably work and they could stay at bottom fine.
But, here’s another thing. I notice that the ‘Article saved’ message, for example, doesn’t go away with any scrolling or after a short period of time. I come and go from my computer A LOT when editing, and I don’t always save every time, especially if I’m intervening with the kids, or in the writing groove and don’t want to lose my place of focus… I’m first getting the words out, etc. But it can be confusing when the Article saved message is perpetually displayed, when in fact I haven’t saved it since the last time. You see what I’m saying? The persistant message is no longer in context to what the actual situation is, which is unsaved changes exist. Article saved messages need to disappear after a few moments, or after some mouse action or hand swipe on the screen, thus leaving no message until the next click of the save button. For other messages, I don’t know. If they’re critical errors, maybe they should remain, which means different messages need different handling on the behaviors.
Just putting it out there.
Offline
Re: Feedback to: Textpattern 4.5.0 Beta released
after some mouse action or hand swipe on the screen.
Press Esc.
Offline
Re: Feedback to: Textpattern 4.5.0 Beta released
re: the alerts. It was always going to be a tough nut to crack – the new AJAX save method means the page doesn’t reload and jump back to the page top (which is good) so the previous methods of displaying the alert message near the top of the page would simply not work anymore. Similarly, fixing the message to page top would not be viable as it would interfere with the navigation elements.
So the only logical position is to fix the message to screen bottom, with a pulse effect that hopefully draws the eye. There are 2 methods to dismiss this message: either by pressing the esc key or by clicking on the close icon to the right of the message alert.
Anyway, I will look into maybe making the colouring stronger, or animating the alert to slide in instead of pulse fade, and see if that helps make them more noticeable.
Last edited by philwareham (2012-08-01 16:27:53)
Offline
Re: Feedback to: Textpattern 4.5.0 Beta released
philwareham wrote:
Anyway, I will look into maybe making the colouring stronger, or animating the alert to slide in instead of pulse fade, and see if that helps make them more noticeable.
+1
Yiannis
——————————
NeMe | hblack.art | EMAP | A Sea change | Toolkit of Care
I do my best editing after I click on the submit button.
Offline
Re: Feedback to: Textpattern 4.5.0 Beta released
OK, r4039 makes the Classic/Remora alerts more noticeable. I’ll deal with Hive as a separate entity.
This will be in tonights build, not the beta (which is a snapshot at r4033). Of course you can always grab the latest SVN version straight away if that’s your thing.
Last edited by philwareham (2012-08-01 16:26:36)
Offline
Re: Feedback to: Textpattern 4.5.0 Beta released
I agree it would be nice if the alert disappeared after the keyboard is used or something. Currently if you do not dismiss the alert then click Save again you can’t really tell if it was saved.
Piwik Dashboard, Google Analytics Dashboard, Minibar, Article Image Colorpicker, Admin Datepicker, Admin Google Map, Admin Colorpicker
Offline
Re: Feedback to: Textpattern 4.5.0 Beta released
If you do change the animation, please could you use accelerated CSS3 animations instead of JavaScript? The performance isn’t exceptional on a lower-tier hardware. Please remember that drawing CSS3 decorations can take close to a second (i.e. shadows). In which case the user just sees epileptic shadows, and even in general the animations are low FPS.
The notification’s JavaScript has some slight issues too — or unneeded stuff. For instance the the ESC key is bind run again on each time a message is shown, and to all .close elements, not just to the notification. This causes bubbling.
In other words, the JavaScript used for the notification should be moved out of the theme’s PHP file to textpattern.js. The keyboard closing code could be made universal by attaching it to .close-on-esc class for instance.
I can make a patch for the JavaScript keyboard bind if you want.
Offline
Offline
Re: Feedback to: Textpattern 4.5.0 Beta released
The animation on Hive theme is CSS3, I left the JavaScript on Classic/Remora alone as I felt that theme would generally be better suited to lower-end hardware (which might not handle CSS3 at all).
That being said, I’ll review your patch and probably roll it in, so thanks for that.
Just as a side note, I’ll be moving the alert messages out of the theme files as part of v4.6.
Offline