Thanks for the response. I know this suggestion came out of left field since the focus so far has been on speed and meeting the spec. Unfortunately, after much serious thought, we have concluded that using it in our embedded app is too problematic given our timeframe for this project along with the memory and processor constraints we are working under. So we decided to move the xsl engine over to the server side for now. I still think long term embedded xsl may be the way to go as our processors get faster and memory is more available. At least for now though, our plans to try to shrink the size of the engine for our embedded app are on hold.
Thanks,
Dan
-----Original Message-----
From: Petr Cimprich [mailto:[EMAIL PROTECTED]]
Sent: Friday, October 06, 2000 8:57 AM
To: Sablotron Mailing List
Subject: Re: [Sab] minXSL?
Hi,
Sablotron and embedded environment is a very interesting topic for us.
One of reasons why we started the development of new processor almost
one year ago was the possibility of porting to small devices. Though we
have tried to keep this in mind and keep the code as compact as possible
from the beginning, we can't avoid its current size. We haven't tried to
optimized the code size yet and we see making Sablotron compliant as a
higher priority now. However, if you want and can look at the code from
this point of view, you are mostly welcome and we will help you as much
as possible.
It may be useful for you to know, that there is another guy thinking of
porting Sablot on PalmOS and stripping the size down. I enclose his
message from the pilot.programmer forum:
-----
I am looking for an XSLT engine for PalmOS. I know there are Java
based parsers out there but for
efficiency reasons I need C/C++ based parser.
I have checked out Sablotron XSLT engine. It works fine on my PC but
it will have to be ported to the
PalmOS. Sablotron uses Expat XML parser which is C based but the XSLT
part is C++. I am not exactly
sure what is involved in porting both of the parts but I am anticipating
more problems with C++ part.
Any guidelines/pointers regarding porting will be highly
appreciated. BTW I understand that palms are not meant for this kind
of heavy computing but I am willing to strip down the XML/XSL features
to improve performance.
Thanks
Kamran
Em: [EMAIL PROTECTED]
-----
"Hammond, Daniel" wrote:
>
>
> There are numerous features of XSL that are not used in many
> applications. Has anyone ever proposed a minimum subset of XSL that
> could be a lightweight substitute for full-blown XSL implementations?
> The reason I am asking is because I am trying to see if I can use XSL
> in an embedded environment.
>
> Sablotron is already pretty small, but I have been asked to see if it
> is possible to get the code even smaller. Preferably about half of
> its current size. So I am asking if this seems like a reasonable
> goal. There are numerous functions and xsl tags in the spec that we
> are not using for our stylesheets. Would it be possible to cut down
> the size very much by removing functionality? I know there have many
> speed optimizations made in Sablotron, but has anyone explicitly tried
> to optimize for code size also? Where does most of the code size come
> from? I know that templates can result in code bloat but there are
> good type-safe work around for this problem (from Scott Meyer's
> _Effective_C++_ Item 42).
>
> Sablotron is a great product, and I would like to use it in my
> architecture if possible, however, the prospect of cutting the code
> size down seems daunting. How likely do these goals seem?
>
> Thanks,
> Dan
--
Petr Cimprich
Ginger Alliance Ltd.
www.gingerall.com
- - - - - - - Appended by Scientific-Atlanta, Inc. - - - - - - -
This e-mail and any attachments may contain information which is confidential, proprietary, privileged or otherwise protected by law. The information is solely intended for the named addressee (or a person responsible for delivering it to the addressee). If you are not the intended recipient of this message, you are not authorized to read, print, retain, copy or disseminate this message or any part of it. If you have received this e-mail in error, please notify the sender immediately by return e-mail and delete it from your computer.
