paradise beachs at Paradise Philippines Tips and News about paradise beachs

Latest paradise beachs Products

paradise beachs Sources

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

& at ermelo south africa & & at villavicencio vanguardia colombia paradise beachs & paradise island resort maldies

Latest paradise beachs News

Latest paradise lust milton photo


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
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
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
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
Puna man sought for questioning

Big Island police are asking the public's help locating a 22-year-old Puna man wanted for questioning in connection with an October shooting in Puna.

Congrats to Eric Meyer
On the forthcoming CSS book, 2nd edition. Another thing for the reading queue. -m
Unipain
Interestingly, Jon Udell's latest column at InfoWorld has the following title: "InfoWorld: E-mail’s many hats: April 23, 2004: By Jon Udell : APPLICATIONS". (because this will likely get mangled further in the publishing stream, that's a-circumflex, then two of what looks like an A-in-a-box instead of the apostrophe in "E-mail's".

Unicode is hard. Even if your content is fine, chances are good that your content management or publishing system will come in and muck things up. Actually, Unicode isn't what's hard--if the whole world used it exclusively we'd be sailing smooth--what's hard is transitions between encodings. Throw in a few unhelpful substitutions by Microsoft Office's aggravating, so-called "smart quotes" features, and you've got a mess on your hands.

A straight-quotes-are-your-friends production. -m

Update: More related discussion. But not directly related. The web page is still titled oddly, as above. Also, interestingly, RSS readers and Atom readers see the above differently. Which just goes to show...
Seeing XForms Inside Out
At the O'Reilly Open Source Convention in Portland, come see my presentation Seeing XForms Inside Out:: Inside an XForms Validator (Thurs July 29). Whether you're just learning about XForms, or been working with it already, you will find some interesting insights by looking at XForms from the perspective of a validation tool.

If you can make it for the full week, I also have a half-day tutorial on Monday (July 26). Check it out! -m
NeoOffice/J
NeoOffice/J 0.8.2 is highly recommended if you're on OS X. It has tons of scary this-is-beta-and-might-not-even-work warnings, but it does. It seems snappier, looks somehow better (is it the font smoothing?), the command/ctrl keys work like you'd expect (not reversed, as with the X11 version), and it works better for drag-n-drop opening files. -m
Scholarship rummage sale set for April 14

Everyone is invited to hunt for treasure at the AAUW's annual scholarship rummage sale from 7 a.m.-1 p.m. Saturday, April 14, in Hawaiian Paradise Park.

An XM
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

paradise beachs Sponsored Products

by