Forum: Ruby XML Transformations using REXML

Announcement (2017-05-07): www.ruby-forum.com is now read-only since I unfortunately do not have the time to support and maintain the forum any more. Please see rubyonrails.org/community and ruby-lang.org/en/community for other Rails- und Ruby-related community platforms.
Bc6d88907ce09158581fbb9b469a35a3?d=identicon&s=25 james_b (Guest)
on 2005-12-05 00:29
(Received via mailing list)
Toot toot!

That's the sound of my own horn.

The January 2006 issue of Dr. Dobbs magazine has an article of mine, XML
Transformations using REXML.

I don't know if the article will be available for free reading on the
Dr. Dobbs Web site, so you may have to buy the magazine to read it.

Well worth it, of course. :)

(It's also the 30th Anniversary issue.)

http://www.ddj.com/  (still showing December 2005)


James Britt

--

http://www.ruby-doc.org       - Ruby Help & Documentation
http://www.artima.com/rubycs/ - Ruby Code & Style: Writers wanted
http://www.rubystuff.com      - The Ruby Store for Ruby Stuff
http://www.jamesbritt.com     - Playing with Better Toys
http://www.30secondrule.com   - Building Better Tools
2a29cf86a958617f5be49a18389c8d73?d=identicon&s=25 jcribbs (Guest)
on 2005-12-05 00:46
(Received via mailing list)
James Britt wrote:

> Toot toot!
>
> That's the sound of my own horn.
>
> The January 2006 issue of Dr. Dobbs magazine has an article of mine,
> XML Transformations using REXML.

Congratulations!
280b41a88665fd8c699e83a9a25ef949?d=identicon&s=25 steve (Guest)
on 2005-12-05 01:01
(Received via mailing list)
On Dec 4, 2005, at 3:28 PM, James Britt wrote:

> Toot toot!

Nice job James!

--Steve
2dc2228d8db84b46bdd834b0515a26a1?d=identicon&s=25 lyndon.samson (Guest)
on 2005-12-05 02:21
(Received via mailing list)
Somewhat related to this.

The lack of a pure ruby XSLT engine is on occasions annoying, because
then I
find myself descending to the nether regions of java, PHP and friends
:-)

I was thinking about the viability of an XSLT doc A that matchs
against arbitrary XSLT B and emits ruby code that effectivly performs
the
same transformation as the original XSLT document B.

Eventually the XSLT A would be able to 'self compile' to some ruby code
that
would replace it. Ie read some XSLT and emit functionally equivilent
ruby
code.

Does this sound like a sensible approach to getting 'pure ruby'  XSLT
functionality?
428a020e221d2e442e2e88ca72763fde?d=identicon&s=25 gjblomquist (Guest)
on 2005-12-09 03:04
(Received via mailing list)
The Jan. issue is now on-line.   Haven't read it yet but I intend to :
)

Gary Blomquist
280b41a88665fd8c699e83a9a25ef949?d=identicon&s=25 steve (Guest)
on 2005-12-09 07:52
(Received via mailing list)
On Dec 8, 2005, at 6:02 PM, GJB wrote:

> The Jan. issue is now on-line.   Haven't read it yet but I intend to

And I just received my print issue in the mail today.  I'm heading
off to bed now, eager to read James's fine work.

--Steve
This topic is locked and can not be replied to.