Actual Transparent Window 歷史版本列表
更新時間：2019-04-22
更新細節：
What's new in this version:
Added:
- option "zebra"
- API
- lexers C/C++: improved rules for float/int/hex numbers
Fixed:
- few bugs with vertical sync-scrolling in Differ plugin
- scrollbars did scroll by 1 pixel on clicking arrows, must scroll faster by char size
- bug with wrong caret pos after pasting multiline block on empty line
更新時間：2019-04-15
更新細節：
What's new in this version:
Added:
- improve behaviour of option "auto_close_brackets":true, now it works with multi-selections too (brackets surround multi-selections)
- on mouse selection, editor draws dotted frame to show mouse rectangle
- option "show_mouse_sel_frame"
- toolbar button "Options Editor" (calls Options Editor plugin dialog)
- toolbar theme icon "opt.png"
- command "selection: remove first caret"
- command "selection: remove last caret"
Changed:
- changed command name "expand selection to word" to more concrete "add next occurrence of selected word"
Fixed:
- crash with plugin Config Menu and changed translation
- bug in lexer engine for Unicode, which caused wrong tokenizing of Unicode names in Clojure lexer
- Linux: must not set dialogs (e.g. Command Palette) border-style to "none", this causes dialog to have "system always on top" style
更新時間：2019-04-07
更新細節：
What's new in this version:
- add: API for EditorConfig plugin
- add: show tooltip over UI tabs with filenames (instead of showing filenames in statusbar)
- add: plugin Sort: added command "Remove duplicate lines, but keep blanks"
- add: option "newdoc_ends" allows value for CR endings
- add: on plugin installation app now skips all hotkeys (from install.inf) which are busy in config
- change: removed command "toggle menu bar"
- fix: CSS auto-completion bugs
- fix: option "saving_force_final_eol" behaviour
- fix: Windows: on rare PCs app hangs with hidden main menu
- fix: on switching tabs, word-wrap state was reset (with lexer-specific cfg)
更新時間：2019-04-01
更新細節：
更新時間：2019-03-27
更新細節：
What's new in this version:
Redesigned element context menu:
We redesigned the element context menu that is accessible by right-clicking on elements on the page view or in the Tree panel:
- Introducing sub-menus allowed us to better organize the menu and to add more commands
- For example, new elements can be added to the page directly from the menu
Insert submenu contains all the elements and components from the Library panel:
The Insert menu also gives us control and preview of the placement of the new element:
- Hint: Hold down the SHIFT key when right-clicking to jump straight into the Insert menu
- Commands that change the HTML structure of the element are tucked under the
Transform submenu:
- Select submenu lets us quickly select parents and children of the current element
- Paste submenu lists the most recent items on the internal clipboard and provides control over placement of the HTML elements
Copy & Paste actions:
- Copy and paste actions from one element to another. Use the Copy submenu to copy all or one of the assigned actions
- Or, click on the Copy icon next to the assigned action in the Action and WordPress panel
- To copy all assigned actions on the element click on the Copy icon next to the element name
- Use Paste to add copied actions to another element
SASS stylesheets compiler:
- Pinegrow now correctly handles projects with complex SASS structures that contain multiple imported files with the same name, for example variables/_buttons, mixins/_buttons…
WordPress Theme Builder:
- Add actions using the context menu
- WordPress actions can now be added to the element using its context menu. Right-click on an element on the page or in the tree and choose an action from the
WordPress submenu:
- And, as mentioned above, WordPress actions can also be copy pasted between elements
- Enhanced display of WordPress actions in the Tree panel
- In the Tree panel view, actions are now displayed before the text snippet in order to make them more visible
- Actions like Customizer Field, Customizer Section and Post Field show their most important arguments right in the Tree display
- Outline all elements with WordPress actions
- Use the new visual helper to outline all elements with WordPress actions
Post & Loop:
- Using the original id on the post element
- The “Post & Loop” Smart action automatically sets the id attribute of the post element to the id value provided by WordPress. This can interfere wi th styling or Javascript code that targets that element by its id
- The action now offers the choice to opt-out of modifying the id attribute, in case the id attribute of the post element is set
- Note that having a fixed element id on the post element only makes sense if only one post item is shown. Otherwise there would be multiple elements with the same id
Displaying a range of elements:
- Sometimes we just want to display a subset of posts contained in the WordPress loop (or custom query). For example, we might want to display the first post in one way and the rest of posts in another way. Or, we might have predefined positions for individual posts and we can’t just display all of them with the same loop
- The new “Range of items to show” lets us specify which of the items returned by the loop query we want to display
- We can either specify a single post, for example 0 for the first one, or a range, for example 1-3 to display second, third and fourth posts
- Note: the post count starts at 0
- Note: this parameter doesn’t affect what posts are retrieved from the WordPress database – it is used to specify which of the posts returned by the WordPress query should be displayed
- The same argument is also available directly on “The Loop” action
Menu – Smart:
- The behavior of the action is changed. It now uses Smart menu walker by default on pages that don’t use Bootstrap (Bootstrap menus are used there). The Smart menu walker replicates the exact HTML layout of menu items, instead of using the default WordPress markup
- The action is also now smarter in figuring out which class is used to denote the active menu item
- As always with smart actions, if you need more control over these actions change them to regular WordPress actions
Reusable Customizer Sections and Fields:
- Customizer Sections (both Smart and regular actions) got the checkbox “Use section id as prefix for enclosed fields”. When checked, the id of the section is used as a prefix for all enclosed customizer fields
- This is very useful in many cases. Let’s take a look at an example
- Imagine that we have four sections for showcasing our past experience on our portfolio website. Each section contains fields for a company name, our job position and duration of the engagement. We want to use the Customizer to control the content of these values
- Normally, we would have to setup four unique fields for company names, four for position and four for the duration – each with unique field id. That makes it impossible to simply copy paste actions from one item to another, or to define these blocks as reusable components.
- Now we can check “Use section id as prefix…” on the first section with id exp1 and assign simple ids – company, job, duration – to enclosed fields. When Pinegrow exports the theme it will append the session id “exp1_” to fields ids, thus creating unique fields ids “exp1_company”, “exp1_job” and “exp1_duration”
- If we copy paste these actions on related elements in other experience sections we’ll get fields experience2_company and so on, provided that “Use section id as prefix…” is checked on their Customizer section actions
- We can go a step further and create a reusable component in the Actions panel with editable attributes that control section id and name
Then we make the other three items instances of this component:
- Then we use the Properties panel to configure section id and name of Work Experience instances
- Using global customizer fields inside a section
- When “Use section id as prefix…” is on the section id will be prepended to all field ids – regardless is fields are registered or just used
- If we want to simply use a value of customizer field from another section – for example, a color value defined in Colors section – we can use Display theme mod action and check its “Don’t use enclosing section id as field prefix” setting
更新時間：2019-02-27
更新細節：
What's new in this version:
- Floating windows with CSS Grid editor, Assign Classes tool, Unsplash Photo browser and Element Code editor.
- Collapse and Expand all nodes in the Tree panel
- Bootstrap Carousel autoplay setting
- Bootstrap 4.3.1
- Bug fixes
更新時間：2019-02-12
更新細節：
更新時間：2019-02-07
更新細節：
What's new in this version:
Color picker:
Picking a color from the screen:
- We had to change how the picking a color from the screen works, so that the feature works with floating windows
- Until now, the screen picker was activated by clicking on the icon and then moving the cursor over the Pinegrow window and then clicking to confirm the selection
- Now, the icon is dragged over the Pinegrow window and releasing the mouse will confirm the selection
Using the system color picker:
- Clicking on the color button next to the Picker icon opens up the system color picker
CSS Grid Editor input validation:
- CSS Grid editor now checks the syntax of grid properties. It caches common error like missing “(“ and “)” characters, wrong units and so on
- Only valid values are stored into CSS rules
Attribute editor:
- The element Attribute editor now supports editing values that contain JSON code, for example … Pinegrow will automatically use the right quote for the attribute in HTML: ‘ if the value contains “ and “ for all other cases
More resilient stylesheet loading:
- A lot of templates and projects out there in the real world contain broken code. Browsers are designed to work around such errors instead of complaining about them
- Pinegrow is more sensitive by design, because the goal is to notice and fix errors during development
- Still, we often get support requests with issues that are caused by such errors. One recent case involved a template with a stylesheet that imported itself. Pinegrow now detects and survives such situations
- On a similar note, we also see a lot commercial templates that are loaded with 10s of Javascript plugins. That can easily lead to performance issues when editing such projects in Pinegrow
- One solution is to disable Javascript while editing in Pinegrow, but then you’re often stuck with poorly implemented loaders that rely on Javascript to be cleared from the screen
- That actually makes Pinegrow a good tool for checking how projects behave in various sub-optimal environments, for example in browsers without Javascript
WordPress Theme Builder:
- Apply Master page command takes the current page, opens its master page and applies any changes to areas outside of the Site content
- A while ago we added the “Apply master page to all open files” that does this for all open pages
- Still, on larger projects with multiple templates and potentially multiple master pages, doing that is cumbersome. The easiest way is to open all template files and then run “Apply master page to all open files”
Now, we added two more options:
- Apply master pages to the whole project will go through all template files in the project and apply their respective master pages to them
- Apply master page to related files will do the same but only for project files that use the current page as their master page
更新時間：2019-01-29
更新細節：
更新時間：2019-01-24
更新細節：
What's new in this version:
Floating Panels and Multiple Screens:
- Supporting multiple screens has been the top feature request for a while now. That’s understandable
- Pinegrow’s UI – with multiple page views, code editor, component libraries, panels for properties, styling, CMS and more – takes up a lot of screen real estate
- Until now the whole UI had to be contained in a single window, so things quickly got crowded
- In Pinegrow 5.1 you can float panels – and groups of panels – in separate windows. Panels can be freely dragged between windows and rearranged within a window
Easily upgrade Bootstrap:
- Bootstrap starter pages, library components and properties have been updated to the latest versions, 4.2.1 and 3.4.0 respectively
- Pinegrow can also easily update your existing Bootstrap projects to the latest Bootstrap version (Bootstrap 3.x to the latest Bootstrap 3 and Bootstrap 4.x to the latest Bootstrap 4)
- Read the complete guide on how to upgrade Bootstrap to the latest version
Fixed Master Pages and WordPress Site actions on plain HTML projects:
- Pinegrow had a bug that prevented using Master Page actions and WordPress Site actions correctly on projects that didn’t use Bootstrap or Foundation
- In those cases both actions didn’t remember their parameters
WordPress Theme builder changes:
Post image – Smart action:
- Until now, the action added the ( is_singular() || in_the_loop() ) when displaying a post image in the background of the element. This created problems with custom queries and non-singular templates
- Now, the action only checks for the presence of the current post ID, if post ID is not specified as a parameter of the action
- Another change is that this action doesn’t automatically add with-image class to the element with the background, as it did before
Action parameters:
- Some WordPress actions had checkbox parameters that were on by default. Unchecking them actually set the non-default, negative. action parameter value
- That made it difficult to spot such checkbox that were set off, and distinguish them from checkboxes that were simply off by default
- That’s why all such checked-by-default checkboxes are changed into select boxes with default value “Yes”. This makes the controls set to “No” very easy to notice
Starter Theme 2 update:
- Starter Theme 2 has been updated to Bootstrap 4.2.1 and optimizations have been applied to some HTML templates. Similarly, some WooCommerce templates have been updated to adapt to the latest versions of the plugin
Save partials:
- Save partial action (in Actions panel) can now correctly save content of script and style elements
Attribute editor in the Properties panel:
- Until now editing attributes that contained HTML tags, stripped the tags from the value
- To prevent this, the Attribute editor now skips such attributes and displays the notice that you can edit them with Element code
Controlling visibility of CSS Grid buttons and resize points:
- CSS Grid buttons can get in a way, especially when elements are small
Network proxy settings:
- It is now possible to let Pinegrow know to use a proxy server for accessing the network by specifying the configuration string in Settings