I'd like to make the entire cell in a MediaWiki table clickable, and not just the text inside it. I start off with this, for example:
{| style="width:400px;background-color:yellow;"
|-
|[[Article1|Tree]]||style="background-color:green"|[[Article2|Hat]]||[[Article3|Shoe]]
|-
|}
And, as expected, only the text is clickable. Can I rejig something to make it work?
You can make the link fill upp the whole cell using CSS. Unless you turned that functionality off, use MediaWiki:Common.css to add your CSS:
td.clickablecell a {
display:block;
width:100%;
}
and then add the class to your cell:
{|
|-
| [[Article1|Tree]]
| class="clickablecell" | [[Article2|Hat]]
| [[Article3|Shoe]]
|}
Related
I'm trying to implement a table in Markdown for tracking purposes. I know two tildes between texts like ~~this~~ will make it strikethrough text, but I was wondering if there's a possibility to strikethrough the whole table row like the screenshot shown below? Adding two tildes in all the cells of the table doesn't do the work for me as well.
I tried Googling to no avail. I tried putting two tildes outside the whole table row and it wasn't working as well.
The table cells are each parsed individually. The only way to apply markup to all cells in a row is to do so manually:
| col a | col b |
|-------|-------|
| ~~nope~~ | ~~nu-uh~~ |
You could use CSS, e.g. the nth-child construct to do this, but it won't work on sites like GitHub that do not allow custom CSS.
When I create a simple table in Jupyter Notebooks, the table appears in the center of the cell. What do I have to do to align that table to the left instead of center?
Sample Latex Table for Jupyter:
| This | is |
|------|------|
| a | table|
Thank you
When creating a table and assigning it the float: left attribute you end up having to add more CSS to resolve the text that surrounds the table. Place this in a code cell before your markdown cell
%%html
<style>
table {
display: inline-block
}
</style>
However, if you have a lot of CSS, might be best to put it in another file for the overall beauty of the document.
Here are the steps:
Create a Code cell just above your markdown cell where you want to show your table.
Write the following in your Code cell.
%%html
<style>
table {float:left}
</style>
Run your Code cell.
Write Table markdown code in your Markdown cell. Your table should now align to the left.
Align tables only for markdown output:
Jupyter & Jupyter Lab:
%%html
<style>
/* Jupyter */
.rendered_html table,
/* Jupyter Lab*/
div[data-mime-type="text-markdown"] table {
margin-left: 0
}
</style>
Put this code once on the top of notebook in Code cell
Does anyone know how to get a TActionMainMenuBar with TThemedPopupMenu to act like the standard menus, in that if there is too many items to fit on the screen (vertically), two scroll buttons appear (one top, one bottom)?
I have tried:
Setting TActionMainMenuBar.Orientation to boTopToBottom and TActionMainMenuBar.AllowScrolling to true - This makes the bar on the form to have scroll bars and you can't actually see the top items.
It sort of looks like this:
+---------------------+
| ^ |
| v |
+---------------------+
Instead of something like this:
+---------------------+
| File |
+---------------------+
Setting TThemedPopupMenu.Orientation to boTopToBottom and TThemedPopupMenu.AllowScrolling to true. This has the effect of squishing the dropping down menu horizontally, with icons and short cuts drawn on top of each other.
The reason for setting these properties is because TCustomActionDockBar.SetAllowScrolling is only set to true when "AllowScrolling and (Orientation = boTopToBottom))"
The only reference on the Internet I have found about this type of thing is Brian Long's "Actions, Action Lists And Action Managers"
Does anyone know if it is possible to get Action Managers to scroll vertically? or are there any references that might help me out?
I am building an application where i used tinymce-rails gem.It's a nice text editor i am dealing with.But i am not able to set text's font size.Please help me out.
I have the below code in my tinymce.yml file:
default:
plugins:
- image
- link
alternate:
selector: textarea.table-editor
toolbar: styleselect | bold italic | undo redo | table
plugins:
- table
Add this in your tinymce.yml and try,
setup : function(ed)
{
ed.on('init', function()
{
this.getDoc().body.style.fontSize = '50px';
});
}
And change your font size according to your need and it works in tinymca 4.
My app has a form - which is used to design other forms and contains an Object Inspector (bas ascii art follows)
-----------------------
|obj | design forms |
|insp| here |
| | |
-----------------------
so, the app''s main form contains the object form and another form onto which components can be placed (there's also a toolbar at the top to select components, but I haven't shown that).
Now, If I make the main form larger, I would like the contents to expand to fit it ...
-------------------------------
|obj | design forms |
|insp| here |
| | |
| | |
| | |
-------------------------------
so my "form designer" form has Align := alClient;
but, if I place a component on it, so that it overlaps the edge ...
-------------------------------
|obj | design forms |
|insp| here -----------
| | |component|
| | -----------
| | |
-------------------------------
the screen of course shows
-------------------------------
|obj | design forms |
|insp| here -----|
| | |comp|
| | -----|
| | |
-------------------------------
and I would like an auto scroll bar.
But, it seems that Align := alClient; overrides AutoScroll := true;
Any idea how to resolve this conflict?
1) the designer area should shrink and grow, always filling the right part of the main form as the main form is resized
2) if a component is placed which would overhang the edge of the designer form then it should grow scroll bar(s)
OR am I totally missing the point? I have code that handles the placing of the component - should I be checking there if I need to add scrollbars?
I think a relatively easy solution would be to switch the form's Align to alNone and position and size it on the parent form's resize event. Presumably you've got a splitter in there whose size events you would also have to listen to.
So long as you only have the inspector and the design form then that's a pretty simple solution to implement. If you have more tool windows in there then it would get more tricky but the basic idea can be extended.