Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. Other Discussions
  3. IT & Infrastructure
  4. Need help from web developers

Need help from web developers

Scheduled Pinned Locked Moved IT & Infrastructure
htmlxmlc++databasesysadmin
1 Posts 1 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • D Offline
    D Offline
    David Chamberlain
    wrote on last edited by
    #1

    In a recent project, I've been able to explore HTML, XML, and XSLT. All pretty cool, to say the least ... at least for obtaining and displaying data. But, for a local machine HTML app, I need some guidance on what kind of strategy is appropriate for updating the data. Sure, I can use forms and some limited scripting, and the MSXML DOM, but what's the strategy for putting it all together? In my work, we get funding with different levels of pay ... managers, programmers, technicians, administrative, etc, where each category gets a certain number of hours to charge against. There are also a set of people who get allocated those hours to use, and every week they post charges against their allocated hours. It's a fairly simple database, easily held in an XML file. I know how to use XSLT to produce HTML and that's fairly straightforward to produce different pages of "reports" (by category, by person, summed by project, etc). But, if I want to add a new person, or a new project, I can create an HTML form and call a script from a button click, but should I use a separate HTML page for each "function" (adding person, adding project, adding allocations, adding a charge)? Or, should it all be wrapped up in one huge HTML file? That's the strategy part. What works well for structuring these kinds of apps for updating data? This is just meant to be a tool for me to use, and not located on a server with cgi capabilities, etc. I've read the articles and scanned the books, but they all talk about the details of forms and transformations, rather than the higher-level strategy for separating the tasks. I don't want to make a C++ program, as that doesn't get me more into the HTML world. Any help or guidance will be appreciated. Thanks, Dave "You can say that again." -- Dept. of Redundancy Dept.

    1 Reply Last reply
    0
    Reply
    • Reply as topic
    Log in to reply
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes


    • Login

    • Don't have an account? Register

    • Login or register to search.
    • First post
      Last post
    0
    • Categories
    • Recent
    • Tags
    • Popular
    • World
    • Users
    • Groups