From mint-bounce@lists.fishpool.fi Tue Jan 12 06:35:27 2010 MIME-Version: 1.0 In-Reply-To: <11a6f2b11001111309q12081f43w85f2fbf0e89f30de@mail.gmail.com> Message-ID: <001636c5a416fd1966047cf5ff39@google.com> Date: Tue, 12 Jan 2010 11:31:50 +0000 Subject: [MiNT] Svar:Re: HRD's & RSC's From: KareAndersen@gmail.com To: mint Content-Type: multipart/alternative; boundary=001636c5a416fd1957047cf5ff36 X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: KareAndersen@gmail.com Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: --001636c5a416fd1957047cf5ff36 Content-Type: text/plain; charset=ISO-8859-1; format=flowed; delsp=yes Den 11. jan. 2010 22.09 skrev Paul Wratt : > Theoretically the resource source format could be defined as xml, or > specifically as html+css style, which would assist in making the > addition of scripting to HighWire a reality, even if the format were a > subset This caught my interest, so I googled a bit. Sounds like the BSDL describes the problem - http://www2002.org/CDROM/alternate/334/ I don't think html+css would really work. You would need custom elements, and the meta tag is just evil. XML + XSL however, could. > That indicates that HighWire might be a good basis for a resource > designer, as it already has the basis for an interpreter, and that > resources in source form could then be previewed in any web browser, > which in itself would allow a lot more people to design for the > platform as a whole This I don't see... However, once a schema has been worked out, there are plenty of tools available to work with XML and XSLT. > This need not be seen as one huge development, as the individual parts > are usable by themselves as well as being needed for a cohesive > development environment It does not sound trivial either, but maybe someone here has more experience with XSLT (transformation of XML to, in this case, .RSC) and can provide some clues? Just thinking out loud... /Kaare --001636c5a416fd1957047cf5ff36 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Den 11. jan. 2010 22.09 skrev Paul Wratt <paul.wratt@gmail.com>:
<snip>
> Theoretically the resource source format could be d= efined as xml, or
> specifically as html+css style, which would ass= ist in making the
> addition of scripting to HighWire a reality, ev= en if the format were a
> subset


This caught my i= nterest, so I googled a bit. Sounds like the BSDL describes the problem - = http://www2002.org/CDROM/alternate/334/
I don't think html+css wo= uld really work. You would need custom elements, and the meta tag is just = evil. XML + XSL however, could.


> That indicates that= HighWire might be a good basis for a resource
> designer, as it al= ready has the basis for an interpreter, and that
> resources in sou= rce form could then be previewed in any web browser,
> which in its= elf would allow a lot more people to design for the
> platform as a= whole

This I don't see... However, once a schema has been w= orked out, there are plenty of tools available to work with XML and XSLT.
> This need not be seen as one huge development, as the indivi= dual parts
> are usable by themselves as well as being needed for a= cohesive
> development environment

It does not sound t= rivial either, but maybe someone here has more experience with XSLT (transf= ormation of XML to, in this case, .RSC) and can provide some clues?
Just thinking out loud...

/Kaare --001636c5a416fd1957047cf5ff36--