paradise lost ilton at Paradise Philippines Tips and News about paradise lost ilton

Latest paradise lost ilton Products

paradise lost ilton Sources

Error: http://api.search.yahoo.com/WebSearchService/rss/webSearch.xml?appid=yahoosearchwebrss&query=paradise+lost+ilton&adult_ok=1 not responding with RSS file

& at dublin airport ireland & & at halifax international airport canada paradise lost ilton & paradise bhilippines

Latest paradise lost ilton News

Latest paradise nt photo


Errata the Night Away
All the formerly scattered errata for _XForms Essentials_ are now collected at the official publisher's page. If you spot more report away! -m
Reviewers needed
I'm writing a chapter for an upcoming book, _XML Hacks_. If you're interested in reviewing a whirlwind tour of XForms, mail me.

The objectives here are:
(1) introduce the concepts clearly
(2) demonstrate it in a way the the reader can easily duplicate
(3) reference all resources
(4) do it in roughly 2 to 5 printed pages.

-m
Interesting slide from Mozilla devdays:
here.

Bullet item - Support more standards: SVG, XForms; MNG subset?
- sub bullet -As extensions at first, by default if low overhead

-m
Come learn XForms
So, you've been hanging around on the edges of XForms--why don't you take the plunge and learn it from the inside out?

Come see me at the O'Reilly Open Source conference in Portland, for a half-day tutorial, on the afternoon of Monday, July 26. There's also a shorter 45-minute session on Thursday the 29th. -m
An XM
Why Pick XForms?
This is essentially a snapshot of today's talk at the Gilbane conference.

So why should you pick XForms vs. some non-XForms system?

1) The uninstaller argument
If you had two functionally similar pieces of software, one with a great uninstaller, and one with a tedious/manual uninstall, which would you install first on your own system? I thought so. Ironically, having a great uninstaller gives users peace of mind, making them *less* likely to actually uninstall the program. Open standards, with the associated non-lock-in, have the same effect.

2) Cost of change
Another way to look at the lock-in situation: even a mid-sized organization can have 1000 forms around. If each has a design/production/review cycle of 8hrs, that's an investment of 4 Man-years. Does it make more sense to invest that much in a single-source solution, or something that could be reused/shopped around? If you have a dozen forms, go ahead and try anything. For serious amounts of, use standards.

3) Metadata needs standards too
Forms are metadata. It doesn't seem obvious at first, but it's true. Forms provide a context and interpretation for a core piece of data. Metadata needs to be standardized as much as regular data, maybe more.

4) Choosing your point on the continuum
It's not like you can draw a black and white diagram of "standards-based" and "non-standards-based" software. It's all shades of gray. The flipside of this is that useful standards support isn't a checklist feature. Lots of forms systems have long lists of individual standards supported, but still use a proprietary layer that effectively negates many of the usual benefits of open standards. You have to pick the point on the continuum at which you are comfortable. -m
Is writing like electronics?
TV sets, inside, used to include a full schematic diagram. You'd unfold it, then again, and again, and again. There were huge, tablecloth-sized sheets. Back 'in the day', I used to go through these. You could point to any random symbol representing a component somewhere in the thing, and determine exactly what the purpose of that component was. What would happen if you suddenly yanked it out of a running TV?

That's how writing works. Every word, every sentence, every paragraph has to be active doing something for the piece.

To design a big circuit, you wouldn't start with a blank sheet and just start drawing components hooked together. You'd start with a general block diagram, then reduce that into smaller blocks, then figure out how everything interconnects, THEN start arranging individual components to make each block.

That's how writing works. You don't start with a blank page and write a story A to Z. You start with the big picture, flesh it out more, then finally down the the level of words. -m
Write IE extensions in XForms
The indefatigable Mark Birbeck pointed me to this-- a toolkit to write IE sidebars in pure XForms. Included are Amazon and Google search. This is a sign of changes to come in the development of Internet Apps. -m
mdubinko_afc
That's 'away from country'.

Minimal updates for a while: One week in Southern France, for a W3C meeting. Yes, work can be pretty demanding sometimes. -m
Everything Must Go!
Here's an interesting project that ties in nicely with my recent reading of Text Processing in Python: markdown, a plain-text-ish format for writing.

I just used David Mertz's format in writing a Hack for _XML Hacks_, and I have to admit it was far easier than skipping over the tags, or even the rather good attempt at tagless-WYSIWYG-XML-editing I got from Morphon.

My initial comments:

Paragraphs should be allowed to be uniformly indented a few spaces. Like code, most text is read far more often than written, and every little bit of extra readablility helps.

The inline link syntax -- This is [an example](http://example.com/ "Title") inline link. -- doesn't seem natural. It's not the kind of thing you'd see in use anywhere. (The out-of-line links, however, are very slick) The image syntax is even less so -- 

For the image case, I'd take a hint from TPIP and use keywords (which are only recognized at the start of a line) in these cases
IMAGE: [alt text] "Optional title"

-m
Thanks ^ 4
Of the 7 regular readers around here, four generous souls (none of whom I'd met previously) offered to volunteer to review my Hack that will be in _XML Hacks_.

In no particular order:

Stephen had great comments on the overall flow and structure. Lots of markers where stuff was good too, not just the bad.

Patrick had too had good comments, especially on the ever-important opening lines. Lots of detailed suggestions and great advice.

Eric helped me see my blind spots, where I was skipping over material too fast.

Daniel had lots of detailed comments, almost copyeditor class. Exactly what I needed.

Good job and thanks to all!

-m
What would you do?
..if someone handed you a piece of code that could solve NP-hard problems in a reasonably short time? All ideas welcome. Be creative! email me. -m
Puna man charged in Sunday shooting

Big Island police have charged a 72-year-old Puna man in connection with a shooting Sunday evening at a home in Panaewa.

paradise lost ilton Sponsored Products

by