Minor “fat-finger” issue. Could the trash bin be moved an em or two left?
TT
Right. I really see the value of a second page. Not least as you work on different layouts of the same sources … e.g. …
I’ve moved the trash can to the left of the “select a field” prompt text.  That moves it as far as possible from the “open drop list” arrow to avoid even the fattest of fat fingers 
-e
Note that when using PasteUpEmbed, you can provide a page:N parameter to embed a specific page from a layout, allowing a single PasteUp tiddler to contain several alternative layouts to be displayed in different places or contexts.
-e
You simply don’t know my fingers, man!  
This seriously is starting to look like a page layout app or Desktop publishing such as;
Aldus PageMaker (later Adobe PageMaker) belonged to the class of desktop publishing (DTP) software.
And like those it has so many features crammed in, it may take time to learn. It would be nice to have a concise but comprehensive tutorial, so just putting the call out there.
Updates to TidldyTools/PasteUp and TiddlyTools/PasteUp/View:
<< and >> buttons to decrement/increment the width, height, layer and page values, you can now directly edit those values:
$edit-text widget instead of just a static text displayenjoy,
-e
Actually it is quite easy to learn—once you grasp the Tripartite inter-relation (Data, Layout, Style [DLS]). In that sense it is fully canonical, elegant, with the emerged fundamentals on web (and before) regarding “content” v. “structure” v. “presentation.”
I personally find the simple, explicit, DLS easy & powerful.
TT
Updates to TiddlyTools/PasteUp/View:
Inputs controls for “contents” and “styles” have been added to the toolbox. When you put the focus into one of these inputs, it automatically expands to a textarea for easy editing of its value; when the focus leaves the input, it automatically collapses back to a small control. Changes made in these input controls are immediately reflected in the rendered field on the layout grid.
You can now drag a field from the layout grid and drop it onto the toolbox panel to select that dropped field in the toolbox droplist.
enjoy,
-e
Really good! Intuitive.
I need use all a few days before I comment more, I think, on them.
I have more techie questions I’ll ask first.
TECHNICAL QUERY #1
Given I’m a bear of small brain I’m kinda at my limits on this Q.
A pasteup looks like this …
When I open the editor for it I see the preview Output as …
When I preview it as RAW Html I see
My Question: Is it possible (or desirable) to see / capture the raw code for the visual render I see too?
I hope this makes sense!
TT
As you can see, a PasteUp tiddler’s text field contains JSON index values for the current layout and fieldtable settings (cols, rows, background, showadvanced, etc), but the actual grid output for the PasteUp tiddler is rendered by the TiddlyTools/PasteUp/View template, which is tagged with $:/tags/ViewTemplate.
When the wikitext contained in the TiddlyTools/PasteUp/View template is processed, it automatically applies CSS to hide the tiddler’s .tc-tiddler-body and then invokes the layout_grid() macro (defined in TiddlyTools/PasteUp) to display the grid output.
However, when you are using the standard TWCore editor preview, it does not apply this custom ViewTemplate, and thus it can only show you the default rendering of the PasteUp tiddler’s text field (i.e., the JSON settings).
I’ve done some experimenting with creating a custom cascade definition to provide an alternative to the $:/tags/ViewTemplate strategy described above (see $:/config/ViewTemplateBodyFilters/PasteUp which is tagged with $:/tags/ViewTemplateBodyFilter).
This cascade DOES succeed in previewing (and printing) the PasteUp grid output when using TiddlyTools/PrintTiddler to open a PasteUp tiddler in a separate window.
Unfortunately, this cascade definition simply won’t work when viewing the tiddler editor’s preview pane because it is actually rendering the contents of “Draft of 'YourPasteUpTiddler'”, but it can’t access the field layout and styles definitions, since there are no corresponding “Draft of 'YourPasteUpTiddler'/layout” and “Draft of 'YourPasteUpTiddler'/styles” tiddlers available to complete the PasteUp rendering process.
-e
Ah! Is there anyway I could redirect the output of PrintTiddler to a tiddler?
Why? I’m just interested if the render alone is useable (for some use cases).
Not wanting to cause a headache!
Just wondering.
TT
I previously made a snapshot tool that captures the html output that is rendered, and saves this. It means the output is stored in a static form (in a sub Tiddler) and displays a non interactive result. Arguably one could do this on any tiddler. Perhaps is supports a few features;
The reason I steped in to share this is perhaps it can help avoid complexity in PasteUP but using a seperate solution that can be used in other cases.
This snapshot tool will need to be expanded if it is to capture other content generated in the tiddler but outside the rendering of the text field.
Some significant updates to TiddlyTools/PasteUp and TiddlyTools/PasteUp/View:
There’s four nice new buttons that appear at the bottom of the “toolbox” panel:
Please note that the toolbox macro definitions have been moved from the TiddlyTools/PasteUp/View template into the main TiddlyTools/PasteUp code tiddler so it is a now “first-class citizen”.  This makes it much easier for me to maintain and also reduced the size of the code since it can now share some of the existing macros that are used in other parts of the TiddlyTools/PasteUp code.
I’ve also fixed a whole bunch of nasty bugs (!!) in the “field table” input handling. Some of the problems that I’ve fixed include:
$edit-text inputs to change the top, left, bottom,right, layer, or page layout values.The solutions involved implementing a “constrain()” filter and a “normalize()” macro.
The constrain() filter ensures that if you enter negative numbers, zeros or blanks they are automatically adjusted to be within the minimum and maximum allowable values:
tm-modal “mask”)If values are entered in the wrong order, they are now stored “as-is” in that order, but when they are actually drawn on the layout grid the normalize() macro automatically adjusts the displayed field rectangle so it’s dimensions are handled as if “top,left” and “bottom,right” corners were entered.
When you resize a field by dragging a corner icon, its coordinates are automatically re-saved in their “normalized” order. In particular, this is done if you drag a field’s corner so far that it “turns the field inside-out”. For example, suppose you drag the top-left corner of a field below and to the right of it’s bottom-left corner, the field’s corners will be automatically “swapped” so that the result has properly normalized “top-left” and “bottom-right” coordinates.
I recommend getting the updates as soon as possible so that you don’t run into any of these (now extinct) bugs.
enjoy,
-e
All good here.
Thank you!
TT
Yet another update:
TiddlyTools/PasteUp/Edit tiddler. The “core” TiddlyTools/PasteUp tiddler is now just 13K (as compared to the previous 54K).TiddlyTools/PasteUp (13K) and TiddlyTools/PasteUp/Embed (860 bytes), and skip all the other stuff.Get updates for all PasteUp parts here: TiddlyTools/PasteUp/Info.
Just drag-and-drop the “There are 8 program tiddlers” text to your TiddlyWiki to import all the changes.
enjoy,
-e
FYI I started on EMBED simply. It looks easy & was
Everything above the “info” (bottom right) is the embed.