xslt: making use of edit/delete buttons is that actually work?

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • Andy B

    xslt: making use of edit/delete buttons is that actually work?

    I want to make an xslt file that formats and displays data from an XElement
    object through an xml control. I need to have the xslt file show edit/remove
    buttons next to each element/attribute that is displayed on the page. These
    buttons/links do have to actually work in the sense that you can actually
    edit/remove the particular element/attribute. Is there any way to do
    something like this?


  • Joe Fawcett

    #2
    Re: making use of edit/delete buttons is that actually work?

    "Andy B" <a_borka@sbcglo bal.netwrote in message
    news:uKoP9jvuIH A.4476@TK2MSFTN GP06.phx.gbl...
    >I want to make an xslt file that formats and displays data from an XElement
    >object through an xml control. I need to have the xslt file show
    >edit/remove buttons next to each element/attribute that is displayed on the
    >page. These buttons/links do have to actually work in the sense that you
    >can actually edit/remove the particular element/attribute. Is there any way
    >to do something like this?
    >
    I'm sure there is, XSLT reformats XML. If you know the final output, in this
    case it sounds like (X)HTML and you show the original input we can advise
    further.
    You may have to explain what XElement object is though, is that the LINQ-XML
    XElement?

    --

    Joe Fawcett (MVP - XML)




    Comment

    • Andy B

      #3
      Re: making use of edit/delete buttons is that actually work?

      You may have to explain what XElement object is though, is that the
      LINQ-XML XElement?
      Exactly what it is. As far as showing input, what do you mean by this? I
      haven't designed any of the .net code yet, but what is supposed to happen is
      this: There is a 9 step asp.net wizard that takes a person through creating
      a "blank contract". During each step, the xml being built is shown on the
      page below the wizard so the user can see their progress as they go through
      the wizard. I need to make edit/remove buttons next to the different
      elements/attributes so they can be edited/removed as needed. A good example
      of this would be this: On step 1 of the wizard, the user is asked to enter
      in an editbox the contract type to create. Since it is freehand writing, it
      can be anything they type up to 30 characters long. When they press the add
      button, a new view in the step shows up saying that the new "type" has been
      created. When they press next for step 2, it takes them to the glossary step
      of the wizard. On this step, the user enters word/definition pairs to be
      added to the section. Below the wizard, there is the contract view as it has
      been created so far. In this step, it would have the contract type and
      whatever word/definition pairs they have added so far. These word/definition
      pairs as well as anything added to the contract would have these buttons
      next to them.

      Does this help?



      Comment

      • Joe Fawcett

        #4
        Re: making use of edit/delete buttons is that actually work?

        "Andy B" <a_borka@sbcglo bal.netwrote in message
        news:eUkhtXAvIH A.5472@TK2MSFTN GP06.phx.gbl...
        >You may have to explain what XElement object is though, is that the
        >LINQ-XML XElement?
        Exactly what it is. As far as showing input, what do you mean by this? I
        haven't designed any of the .net code yet, but what is supposed to happen
        is this: There is a 9 step asp.net wizard that takes a person through
        creating a "blank contract". During each step, the xml being built is
        shown on the page below the wizard so the user can see their progress as
        they go through the wizard. I need to make edit/remove buttons next to the
        different elements/attributes so they can be edited/removed as needed. A
        good example of this would be this: On step 1 of the wizard, the user is
        asked to enter in an editbox the contract type to create. Since it is
        freehand writing, it can be anything they type up to 30 characters long.
        When they press the add button, a new view in the step shows up saying
        that the new "type" has been created. When they press next for step 2, it
        takes them to the glossary step of the wizard. On this step, the user
        enters word/definition pairs to be added to the section. Below the wizard,
        there is the contract view as it has been created so far. In this step, it
        would have the contract type and whatever word/definition pairs they have
        added so far. These word/definition pairs as well as anything added to the
        contract would have these buttons next to them.
        >
        Does this help?
        >
        >
        (Sorry for late reply, my newsreader seems plagued by gremlins at the moment
        and messages sometimes don't show for days)
        I think I understand. The XSLT will create HTML that has edit buttons
        against each element/attribute so the user can change their mind etc.
        I'm sure this is doable but seems quite convoluted. Why not just bind the
        XML to a gridview or similar and have the buttons part of the view?

        --

        Joe Fawcett (MVP - XML)




        Comment

        Working...