10 More Discussions You Might Find Interesting
1. Web Development
I changed the CSS and Javascript in the "Advanced Editor" to clean it up. This is also the editor seen in "New Thread" and "New Reply". Basically I got rid of the mouseover style changes which were messed up due to vB legacy JS code from a decade ago.
While doing this change, I then completed... (8 Replies)
Discussion started by: Neo
8 Replies
2. Web Development
Added some Bootstrap to our lists (first draft subject to change) with PHP changes to the functions_bbcode.php:
if ($listtype)
{
$outstuff = '<ol class="list-group" style="list-style-type: ' . $listtype . '">' . $output . '</ol>';
... (0 Replies)
Discussion started by: Neo
0 Replies
3. War Stories
YAY!
Finally, seems like forever, I added this CSS to the posts (postbit) for table columns and scrollbars work still do not work for code tags and text inside posts.
<style>
td {
max-width:200px;
overflow: auto;
white-space: nowrap;
}
</style>
YAY...
Now scollbars... (3 Replies)
Discussion started by: Neo
3 Replies
4. What is on Your Mind?
See attached screen movie that demos the revised tooltips which includes thread previews, or double click on the YT video below to go to YT and view in full screen mode, etc:
HkObCAYg6LI (0 Replies)
Discussion started by: Neo
0 Replies
5. What is on Your Mind?
Hi,
Well, I changed the descriptions for threads to use Bootstrap's UI and here is the results (make sure you set your YT setting for 1080 HD):
New Tooltip for UNIX.COM Using Bootstrap - YouTube
Here is the simple CSS I'm using for the fonts and colors:
.tooltip-inner {
... (0 Replies)
Discussion started by: Neo
0 Replies
6. UNIX for Advanced & Expert Users
hi!
my computer is...
system: Digital Personal Workstation 433a
Processor: Digital Alpha 21164, 433 MHz
Memory: 64 MB
Operating System: Digital Unix Console(SRM), Digital Unix V4.0D
That computer is used for radar display. Application run on Unix. I have a problem now. I can't boot dkc0... (2 Replies)
Discussion started by: akz
2 Replies
7. Solaris
Exactly how can I redirect bootstrap data generated by Networker to a file? The company's policy is to have this electronically saved remotely. The idea is to have the bootstrap info saved to a file and then use rsync to move that file to a remote server. So instead of sending it to a printer... (0 Replies)
Discussion started by: Jshwon
0 Replies
8. Shell Programming and Scripting
I am trying to transpose tables listed in the format into format. Any help would be greatly appreciated.
Input:
test_data_1
1 2 90%
4 3 91%
5 4 90%
6 5 90%
9 6 90%
test_data_2
3 5 92%
5 4 92%
7 3 93%
9 2 92%
1 1 92%
...
Output:... (7 Replies)
Discussion started by: justthisguy
7 Replies
9. Shell Programming and Scripting
Hi !
Anyone can tell me how to controll two listboxes with only one scrollbar in TCL? I have tried the following but it didn't work:
listbox .listw.list -width 25 -height 25 -yscrollcommand {.listw.scroll set}
listbox .listw.list2 -width 25 -height 25 -yscrollcommand {.listw.scroll set}... (0 Replies)
Discussion started by: cordobapab
0 Replies
10. AIX
I'm trying to build gcc-3.4.4 on AIX 5.3, and I get the following error in phase 2. I suspect that the problem is related to AIX's "as" assembler somehow, but from what I understand, the binutils assembler is not useable on AIX 5.1 or later. Any ideas?
checking for powl declaration... yes... (2 Replies)
Discussion started by: Duggerdee
2 Replies
Jifty::Plugin(3pm) User Contributed Perl Documentation Jifty::Plugin(3pm)
NAME
Jifty::Plugin - Describes a plugin to the Jifty framework
DESCRIPTION
Plugins are like mini-apps. They come in packages with share directories which provide static and template files; they provide actions;
they have dispatcher rules. To create the skeleton of a new plugin, you can use the command:
jifty plugin --name SomePlugin
To use a plugin in your Jifty application, find the "Plugins:" line in the "config.yml" file:
Plugins:
- SpiffyThing: {}
- SomePlugin:
arguments: to
the: constructor
The dispatcher for a plugin should live in "Jifty::Plugin::name::Dispatcher"; it is written like any other Jifty::Dispatcher. Plugin
dispatcher rules are checked before the application's rules; however, see "Plugins and rule ordering" in Jifty::Dispatcher for how to
manually specify exceptions to this.
Actions and models under a plugin's namespace are automatically discovered and made available to applications.
new
Sets up a new instance of this plugin. This is called by Jifty after reading the configuration file, and is supplied whatever plugin-
specific settings were in the config file. Note that because plugins affect Mason's component roots, adding plugins during runtime is not
supported.
init [ARGS]
Called by "new", this does any custom configuration that the plugin might need. It is passed the same parameters as "new", gleaned from
the configuration file.
new_request
Called right before every request. By default, does nothing.
template_root
Returns the root of the "HTML::Mason" template directory for this plugin
po_root
Returns the plugin's message catalog directory. Returns undef if it doesn't exist.
template_class
Returns the Template::Declare view package for this plugin
static_root
Returns the root of the static directory for this plugin
dispatcher
Returns the classname of the dispatcher class for this plugin
prereq_plugins
Returns an array of plugin module names that this plugin depends on.
version
Returns the database version of the plugin. Needs to be bumped any time the database schema needs to be updated. Plugins that do not
directly define any models don't need to worry about this.
bootstrapper
Returns the name of the class that can be used to bootstrap the database models. This normally returns the plugin's class name with
"::Bootstrap" added to the end. Plugin bootstrappers can be built in exactly the same way as application bootstraps.
See Jifty::Bootstrap.
upgrade_class
Returns the name of the class that can be used to upgrade the database models and schema (such as adding new data, fixing default values,
and renaming columns). This normally returns the plugin's class name with "::Upgrade" added to the end. Plugin upgrade classes can be built
in exactly the same was as application upgrade classes.
See Jifty::Upgrade.
table_prefix
Returns a prefix that will be placed in the front of all table names for plugin models. Be default, the plugin name is converted to an
identifier based upon the class name.
wrap
Takes a PSGI-$app closure and returns the wrapped one if your plugin wants to do something to the request handling process. See also
Plack::Middleware.
psgi_app_static
Returns a PSGI-$app that serves the static content of the plugin if any. The default is a <Plack::App::File> app with root set to plugin's
"static_root"
perl v5.14.2 2010-12-08 Jifty::Plugin(3pm)