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. Web Development
  3. Web programming, again.

Web programming, again.

Scheduled Pinned Locked Moved Web Development
databasehelphtmlcsslinux
3 Posts 2 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.
  • F Offline
    F Offline
    FeedScrn
    wrote on last edited by
    #1

    I have a normal HTML/CSS w/some JScript thrown-in webpage, with > 50 individual blog pages that are indexed from the main index.html file. On my wishlist are two things: -would like to add a Search Box. Not one that depends on an external search engine. I want to roll my own, so to speak. I want to have all my pages accessible - so that I can search through the pages and then display the results to a user after a search. I'm thinking that the pages need to be put into a database for this(?) -Would like to add a 'prev' and a 'next' function to the bottom of each sub-webpage. The user should not always have to navigate back to the index to see another page. Would like one function that takes an argument - prev or next. Or two separate functions are ok. What I want to avoid is having to hardcode "num of next page", and "num of prev page" on every subpage. Can be very error-prone. What language(s), DBs would be best for this? I worked as a professional programmer in the past, so complexity of code is not a problem. A language that works good with a DB (if needed), and one where the functions work in Windows and in Linux is important. Also, a great debugger is paramount, as I anticipate using it a lot when first starting out.

    Take Care God Bless... Feedscrn +--------------------------------+ | The screen is hungry, Feed It! | +--------------------------------+

    D 1 Reply Last reply
    0
    • F FeedScrn

      I have a normal HTML/CSS w/some JScript thrown-in webpage, with > 50 individual blog pages that are indexed from the main index.html file. On my wishlist are two things: -would like to add a Search Box. Not one that depends on an external search engine. I want to roll my own, so to speak. I want to have all my pages accessible - so that I can search through the pages and then display the results to a user after a search. I'm thinking that the pages need to be put into a database for this(?) -Would like to add a 'prev' and a 'next' function to the bottom of each sub-webpage. The user should not always have to navigate back to the index to see another page. Would like one function that takes an argument - prev or next. Or two separate functions are ok. What I want to avoid is having to hardcode "num of next page", and "num of prev page" on every subpage. Can be very error-prone. What language(s), DBs would be best for this? I worked as a professional programmer in the past, so complexity of code is not a problem. A language that works good with a DB (if needed), and one where the functions work in Windows and in Linux is important. Also, a great debugger is paramount, as I anticipate using it a lot when first starting out.

      Take Care God Bless... Feedscrn +--------------------------------+ | The screen is hungry, Feed It! | +--------------------------------+

      D Offline
      D Offline
      David Mujica
      wrote on last edited by
      #2

      Consider using a pre-developed blog engine. This is a classic situation of build vs buy. However, there are some nice open-source solutions out there. A quick search pulled up the following: http://www.dotnetblogengine.net/[^]

      F 1 Reply Last reply
      0
      • D David Mujica

        Consider using a pre-developed blog engine. This is a classic situation of build vs buy. However, there are some nice open-source solutions out there. A quick search pulled up the following: http://www.dotnetblogengine.net/[^]

        F Offline
        F Offline
        FeedScrn
        wrote on last edited by
        #3

        Yes, it looks nice. :) Interested in honing my web programming skills at this point. And I have the time. The thing is, most of the blog is already built and working. I just want to add a couple of features to it.

        Take Care God Bless... Feedscrn +--------------------------------+ | The screen is hungry, Feed It! | +--------------------------------+

        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