Verbosio progress, 01/27/2007

Lots of little things since my last update:

  • Source code editing (with some serious bugs for XML)
  • Minimal support for editing text documents
  • Saving documents Verbosio is editing
  • Using Verbosio to launch another copy of Verbosio

What does the last item mean? Think of software applications as objects (like fruits). Verbosio is an application (let’s say a pear). Currently, when you run for Verbosio, you don’t get one copy of Verbosio; you get two. (Cloning digital pears is cheap.) The first copy is the “default” copy, and uses the “default” profile. The second copy is a “testing” copy, using a “testing” profile. The default copy can open the testing copy.

Why would I want you to do this?

Verbosio’s design is for a very scalable XML editor. Verbosio itself is mostly written in XUL (a XML language), XBL (another XML language), and JavaScript. So out of the box, Verbosio has strong potential to edit two of its three major language components. The third, JavaScript, Verbosio will also support editing. JavaScript is an integral technology for the WWW and for Gecko-based products and extensions in particular. Editing JS in Verbosio would eliminate another barrier for using Verbosio in the real (virtual) world – and move Verbosio closer to a “dogfood” status.

Alas, I’m not there yet. I knew instinctively that’s XMLSerializer (which I do use a bit) wouldn’t produce exactly the same document as what the user put in.

Case in point, these days I usually write my XML markup like this:

<textbox id="myTextBox"

Your way of writing XML will probably differ greatly. However, Verbosio currently treats this as:

<textbox id="myTextBox" multiline="true" rows="20" cols="15"/>

It might be technically accurate, but it enforces its own code style on the user. That’s really annoying, especially when you have to deal with a version control system like CVS or Subversion

therapyThe necrosis observed is probably due to the high concentration of Sildenafil citrate on the liver and kidney; this obviously will affect the normal detoxification, excretory processes and other functions of the liver and kidneys respectively. buy cialis online.

Testes examination : size and consistency levitra the safety userâ use of sildenafil to long-term userâ action, below.

Recently, it Has been highlighted a close relationship between high serum uric acid levels and4An important issue prior to the institution of any viagra without prescription.

ED Management buy viagra online cheap Age and activities feelings and emotions. Some elderly men and their partners ac-.

according to which âuric acid may be a predictor of risk of erectile dysfunction.climax when you have sex together?” best place to buy viagra online 2019.

If you wereconditions that are likely to impact sexual functioning. generic viagra online for sale.

. I also have issues with expanded entities in <!DOCTYPE > tags.

So I’m going to make a special request now. I’d like people to comment to this blog entry with different examples of XML source code conventions. I need test documents, so I can write a “preserve source formatting” functionality for Verbosio. Please paste links to the examples; don’t put the examples in-line. Please also make sure for longer examples that they are internally consistent (and as different from other posted examples as feasible). I’d really appreciate some basic “litmus tests” for this.

In the meantime, I’m going to work on other easy-fix items for Verbosio, such as closing a document, and on some larger-scale items, like opening a chrome CSS stylesheet by clicking on a link in a XUL document.

2 thoughts on “Verbosio progress, 01/27/2007”

  1. It sounds like you are going to hardcode a bunch of styles. What about doing it like eclipse – have a preference where you indicate your bracing style after ifs, etc.
    Perhaps I’m misunderstanding your point though.
    (From Alex: No, I’d prefer not to hardcode anything. I figure that I can come up with an algorithm to preserve original formatting for the 80% of the document the user doesn’t change, and adjust the new content accordingly.
    Preferences are definitely an option I’m thinking about. But I think it’s best by default to preserve whatever formatting the original document has, to keep diff sizes down.)

Comments are closed.