[mdt.dev] Re: Tip for using the new 'galileo' flag for Eclipse EMF/MDT P

["Christian W. Damus" <cdamus@xxxxxxxxxxxxx>]

Hi, all,

Find, below, David's response to the questions that I directed to  
him.  He sends his regrets for not being subscribed to our Modeling  
mailing lists, and I send my apologies for not replying to y'all sooner.

I actually was without e-mail service all day:  my ISP's mail server  
was down from 8.00 to 17.00, today.  Apparently there were no back-ups  
or contingency plans.  I have instantly developed a huge respect and  
appreciation for the work that Denis and his team do at Eclipse, and  
how smoothly they keep stuff running.

Cheers,

Christian


On 24-Sep-08, at 10:33 PM, David Carver wrote:

> Christian W. Damus wrote:
> > The solution to this was to remove the '[' and ']' characters from  
> > the 'safe' variable, so that finally I had:
> >
> >  <xsl:variable name="safe">%,+,&amp;=?/!'()*-. 
> > 0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZ_abcdefghijklmnopqrstuvwxyz~</ 
> > xsl:variable>
> >
> > and the HTML resulting from my queries is now just what I need.
> >
> > Questions for Dave C.:
> >
> >    * Do you anticipate any problems that these changes to the 'safe'
> >      variable might cause?
> Nope.  I've had to make several modifications to the url-encode.xsl  
> code that came from here originally.
>
> http://skew.org/xml/stylesheets/url-encode/
>
> >    * Is any of this applicable to the plan-rendering script that the
> >      Eclipse website uses?  Or, is it only relevant to your XSL?
> >       Will my queries work with Eclipse's renderer?  (I can't test it
> >      because OCL is not yet recognized as a Project)
> The plan script uses the same XSL stylesheets.  The PHP script  
> actually calls and executes the XSL stylesheet transformation on the  
> server, and then sends the output to the browser.   So with the  
> modified url-encode.xsl applied to the server it will work the same  
> as it does locally.   XSL is used because it is designed to work  
> with XML formatted files, and handles namespaces very easily.   It  
> also reduces the number of times that the php file has to be  
> redeployed and changed.  Changes as you found can be made to the  
> xsl's, tested locally, and then deployed to the server.   This is  
> the way I used XSL Tools to develop the stylesheets that are being  
> run both in web browsers as well as one the servers generating the  
> actual pages.
>
> >    * Would you feel comfortable sharing these changes to the 'safe'
> >      variable with the rest of the Eclipse projects?
> >
> >
> > For a complete example of using the 'galileo' flag in your  
> > plan.xml, see my OCL plan file in CVS:
> >
> > http://dev.eclipse.org/viewcvs/index.cgi/www/modeling/mdt/ocl/project-info/plan.xml?root=Eclipse_Website&view=markup 
> >  <http://dev.eclipse.org/viewcvs/index.cgi/www/modeling/mdt/ocl/project-info/plan.xml?root=Eclipse_Website&view=markup 
> > >
> >
> > Thanks, Dave, for this extremely helpful tooling that you developed!
> That is fine with me, I would suggest opening a bug against the the  
> project plan, and supplying a patch file for the url-encode.xsl to  
> handle this situation.   This way Bjorn can get the patch applied  
> appropriately.
>
> The big problem we are running into is the fact that I'm stuck using  
> XSLT 1.0, and have to do the funky work arounds provided by the url- 
> encode.xsl script.  XSLT 2.0 would help eliminate this problem with  
> it's built in encoding and decoding functions.
>
>
> Dave

--
Christian W. Damus
Senior Software Developer, Zeligsoft Inc.
Component Lead, Eclipse MDT OCL and EMF-QTV
E-mail: cdamus@xxxxxxxxxxxxx