📄 site.html

📁 its it tracker and used for track
💻 HTML
字号:
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" >
<head>
    <title>ITracker Help</title>
</head>
<body>
    <p style="text-align:center;width:500px;"><span style="font-size:20pt;font-weight:bold;">ITracker Site Help</span><br />
        <a href="default.html">Help Home</a> | <a href="site.html">Site/Page Help</a> | <a href="business.html">Business Help</a> | <a href="database.html">Database Help</a>
    </p>
    <p style="text-align:center;width:500px;">
    The website/UI portion of the application is really quite simplistic. It consists of 5 basic pages (Default, Details, ItemSearch, Vendo and VendorSearch)
    along with 1 master page, images and the Theme. For ease of explanation I'll split these up.
    </p>
    <p style="width:500px;">
    <b>Basic Pages (aspx):</b><br />
    The .aspx files for the application really only server a couple functions. They are there to allow you to see the data
    and to allow you to enter information on the data. I've incorporated some basic functionality in the pages to make my
    development easer (like field validators, etc) but you could easily push these to the business layer if you wanted.
    Anyway, back to the pages. In the following diagram you will see a simple breakdown of all the pages and the functions/methods
    that is associated with each.<br />
    <img onclick="window.open('../images/ITrackerSiteDiagram.jpg');" src="../images/ITrackerSiteDiagram.jpg" alt="Click for full sized diagram" width="495px" style="cursor:hand;" />
    <br />
    <b>Default.aspx</b> is a landing page. I've added a simple gridview to show items that are currently below their specified
    reorder point. This allows the users to quickly see what needs to be done and, with the quicklink on the grid, access that
    particular items details quickly.<br />
    <b>Details.aspx & Vendor.aspx</b> are really almost the same. Both pages are designed to be used to see the specific details
    on a given object. Both pages also do triple duty. They act, as mentioned, as a way to view the details but they also allow
    you to edit the information as well as create a new set of data. It's really just a matter of check for a specified querystring
    value but this could easily be extended to use a Property set on the page or even rolled into a control(ascx) if you wanted more
    reusability.<br />
    <b>ItemSearch.aspx & VendorSearch.aspx</b> again are quite similar. Both of these pages allow you to search for a particular
    set of data/objects based on some criteria. They then both display the results in a simple gridview, again giving you
    a quicklink to the object directly from the grid.
    <br />
    <b>ITracker.Master</b> is, as the name implies, the Master page for the application. With the addition of Master Pages, Microsoft has
    made consistancy a much simplier thing. While I'm not going to go into the details on what Master Pages are or how they
    work (there are plenty of sites out there for that) I will say that I've implemented mine in such a way that the whole
    visual layout is set by the one page and will allow the user to quickly customize their version of the site.<br />
    <b>Themes</b> like Master Pages are something that I really don't need to rehash for you since there are many people out 
    there who are MUCH more qualified but suffice it to say I'm using the Themes to set simple standards/defaults for my controls as well 
    as setting up the StyleSheet which will again centralize the changes that the users will have to make in customizing the site.<br />
    <b>Misc. Notes:</b> While you can see that all the base pages inherit from the Microsoft "Page" class I would recommend that you use your own
    base "Page" class. This will allow you to easily put in shared functionality if the need ever arises.
   <br />
   If you look at the pages, or the diagram, you will notice that there is a consistancy across the pages, namely the 
   naming convension. I highly recommend you put a standard in place. This will help speed up the learning curve if 
   you ever need to share your code with another.<br />
   
    </p> 
    <p style="width:500px;">
       <b>Custom Themes (NEW)</b><br />
       Due to public response I've added the ability to re-theme the site. There are really only 2 key aspects to this.<br />
       The first is the Master Page. By default there is an ITracker.Master page in the root of the site. You are more then
       welcome to create your own. Simply create your new master page (calling it whatever you would like) and place it in
       the site. Then in your web.config file you will find an &lt;appSetting...&gt; key for "MasterPageName", simply put in the path
       to your new Master Page. The only real "requirement" is that you keep the same number (and names) for the ContentPlaceHolder 
       controls. These are key and are pulled into each subsequent page.<br />
       The second aspect of the re-theming is the actual Theme folder. I'd suggest copying the existing theme and giving it a new
       name as your starting point. After you have the new Theme name go into your web.config file and adjust the &lt;pages...&gt; section
       to point to the new Theme. You can now adjust the .skin file and the css files untill you are happy.<br />
       There should really be no need to manually adjust the pages themselves but again, feel free. 
    </p>
    <p style="text-align:center;width:500px;">
        ~
        <br />
        Curt Christianson<br />
        <a href="mailto:darkfalz@darkfalz.com">darkfalz@darkfalz.com</a><br />
        www.Darkfalz.com<br />
        www.DF-Software.com<br />
        
    </p>
</body>
</html>
⌨️ 快捷键说明

复制代码 Ctrl + C
搜索代码 Ctrl + F
全屏模式 F11
切换主题 Ctrl + Shift + D
显示快捷键 ?
增大字号 Ctrl + =
减小字号 Ctrl + -