forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ramón Prades <rpra...@porcelanosa.com>
Subject RE: %20 in breadcrumb trail.
Date Fri, 25 Jul 2003 10:40:48 GMT
Hi

JavaScript function to decode the hexadecimal encoding of a string is
"unescape".

For example:

var s = escape("Hello World!"); // "s" is now "Hello%20World%21"
S = unescape(s);			  // "s" is "Hello World!" again.

Hope this helps!

Regards.

Ramón Prades

-----Mensaje original-----
De: Nicola Ken Barozzi [mailto:nicolaken@apache.org] 
Enviado el: viernes, 25 de julio de 2003 12:21
Para: forrest-dev@xml.apache.org
Asunto: Re: %20 in breadcrumb trail.



Juan Jose Pablos wrote, On 25/07/2003 11.21:

> Nicola,
> 
>> 30 seconds... what did you search for?
> 
> I can not remember, but it was something like "replace %20 URL 
> javascript"

It's too specific. If you are looking for code in Google, you will get 
better results if you simply include the language and some words that 
describe what the function/class/method should do and on what. Then add 
any additional things to refine the search.

In this case:

   Javascript
   replace
   string

If I wanted only regexp, I would add that too.

Start generic, and get more detailed if you are not finding 
specific-enough answers.

>> Well, it's not written. Jeff has outlined it on this list some days
>> back. All the rest are just results of discussions that I remember on 
>> these occasions, so I'm not able to write more down.
>>
>> When I remember, I'll add then to our status doc.
>>
> Thanks,
> 
> I think that making available minor changes it will allow people with
> less knowledge on forrest get something in return & getting more involved.
> 
> What would be nice is to order the todo list on this order:
> 
> High Priority Minor Actions
> High Priority Mayor Actions
> Medium Priority Minor Actions
> Medium Priority Mayor Actions
> Low Priority Minor Actions
> Low Priority Mayor Actions
> 
> To achive that The action element needs an attribute like "change" 
> with
> mayor and minor.
> 
> 
> Should we add something like this:
> 
> RCS file:
> /home/cvs/xml-forrest/src/resources/schema/dtd/common-elems-v10.mod,v
> retrieving revision 1.4
> diff -u -r1.4 common-elems-v10.mod
> --- common-elems-v10.mod    11 Oct 2002 07:22:35 -0000    1.4
> +++ common-elems-v10.mod    25 Jul 2003 09:18:02 -0000
> @@ -42,6 +42,7 @@
> 
>  <!ENTITY % types "add|remove|update|fix">
>  <!ENTITY % contexts "build|docs|code|admin|design">
> +<!ENTITY % change "mayor|minor">
> 
>  <!-- =============================================================== 
> -->
>  <!-- Common elements -->
> @@ -54,6 +55,7 @@
>  <!ATTLIST action %common.att;
>            dev  IDREF  #REQUIRED
>            type (%types;)  #IMPLIED
> +          change (%change;)  #IMPLIED
>            context (%contexts;) #IMPLIED
>            due-to CDATA #IMPLIED
>            due-to-email CDATA #IMPLIED
> 
> 
> 
> What do you think?

I like the idea.

What about this instead (or something like it)


   <!ENTITY % types "add|remove|update|fix">
   <!ENTITY % contexts "build|docs|code|admin|design">
  +<!ENTITY % difficulty "easy|medium|hard|wizard">
  +<!ENTITY % time "little|medium|much|unknown">

   <!-- =============================================================== -->
   <!-- Common elements -->
  @@ -54,6 +55,7 @@
   <!ATTLIST action %common.att;
             dev  IDREF  #REQUIRED
             type (%types;)  #IMPLIED
  +          difficulty (%change;)  #IMPLIED
  +          time (%change;)  #IMPLIED
             context (%contexts;) #IMPLIED
             due-to CDATA #IMPLIED
             due-to-email CDATA #IMPLIED

-- 
Nicola Ken Barozzi                   nicolaken@apache.org
             - verba volant, scripta manent -
    (discussions get forgotten, just code remains)
---------------------------------------------------------------------





Mime
View raw message