forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Juan Jose Pablos <che...@che-che.com>
Subject Re: %20 in breadcrumb trail.
Date Fri, 25 Jul 2003 09:21:06 GMT
Nicola,

> 
> 30 seconds... what did you search for?
> 

I can not remember, but it was something like "replace %20 URL javascript"


> 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?

Cheers,
Cheche


Mime
View raw message