oqapi/webgui
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

upgrading to YUI 2.6

Browse source 
data tables are going to need some work yet, but the other stuff seems to be working 100%
This commit is contained in:
JT Smith 2008-10-22 23:53:29 +00:00
parent a041e93da8
commit 20f8df1291
2106 changed files with 993560 additions and 237 deletions
Download patch file Download diff file Expand all files Collapse all files

93
www/extras/yui/examples/container/module_clean.html Normal file
View file

@ -0,0 +1,93 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
<title>The Module Control</title>
<style type="text/css">
/*margin and padding on body element
can introduce errors in determining
element position and are not recommended;
we turn them off as a foundation for YUI
CSS treatments. */
body {
margin:0;
padding:0;
}
</style>
<link rel="stylesheet" type="text/css" href="../../build/fonts/fonts-min.css" />
<link rel="stylesheet" type="text/css" href="../../build/container/assets/skins/sam/container.css" />
<script type="text/javascript" src="../../build/yahoo-dom-event/yahoo-dom-event.js"></script>
<script type="text/javascript" src="../../build/container/container-min.js"></script>
<!--there is no custom header content for this example-->
</head>
<body class=" yui-skin-sam">
<h1>The Module Control</h1>
<div class="exampleIntro">
<p>This example looks at the "standard module format" used by many components in YUI to represent modular content on the page. The Module Control is a JavaScript representation of a standard module, one that provides some basic plumbing for interacting with the head, body and foot sections of a standard module. Convenience methods for showing, hinding and rendering the module are also included in the Module Control.</p>
<p>You're most likely to use the Module Control when building a custom widget; its importance in the YUI Library is as a foundation rather than as a UI control in its own right.</p>
</div>
<!--BEGIN SOURCE CODE FOR EXAMPLE =============================== -->
<style type="text/css">
.yui-module { border:1px dotted black;padding:5px;margin:10px; display:none; }
.yui-module .hd { border:1px solid red;padding:5px; }
.yui-module .bd { border:1px solid green;padding:5px; }
.yui-module .ft { border:1px solid blue;padding:5px; }
</style>
<script type="text/javascript">
YAHOO.namespace("example.container");
YAHOO.util.Event.onDOMReady(function () {
YAHOO.example.container.module1 = new YAHOO.widget.Module("module1", { visible: false });
YAHOO.example.container.module1.render();
YAHOO.example.container.module2 = new YAHOO.widget.Module("module2", { visible: false });
YAHOO.example.container.module2.setHeader("Module #2 from Script");
YAHOO.example.container.module2.setBody("This is a dynamically generated Module.");
YAHOO.example.container.module2.setFooter("End of Module #2");
YAHOO.example.container.module2.render();
YAHOO.util.Event.addListener("show1", "click", YAHOO.example.container.module1.show, YAHOO.example.container.module1, true);
YAHOO.util.Event.addListener("hide1", "click", YAHOO.example.container.module1.hide, YAHOO.example.container.module1, true);
YAHOO.util.Event.addListener("show2", "click", YAHOO.example.container.module2.show, YAHOO.example.container.module2, true);
YAHOO.util.Event.addListener("hide2", "click", YAHOO.example.container.module2.hide, YAHOO.example.container.module2, true);
});
</script>
<div>
<button id="show1">Show module1</button>
<button id="hide1">Hide module1</button>
</div>
<div id="module1">
<div class="hd">Module #1 from Markup</div>
<div class="bd">This is a Module that was marked up in the document.</div>
<div class="ft">End of Module #1</div>
</div>
<div id="module2"></div>
<div>
<button id="show2">Show module2</button>
<button id="hide2">Hide module2</button>
</div>
<!--END SOURCE CODE FOR EXAMPLE =============================== -->
</body>
</html>