[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
| RE: [tigerstripe-dev] Spread the misery | 
Title: Re: [tigerstripe-dev] Spread the misery
Attached two files :
 
bad.links is a list of links that don't go anywhere 
valid (IMHO). The format is FILE <tab> Link.
 
unused.files is a list of files that are in the plugin 
but not referenced anywhere - this is a simple list.
 
Not too bad. I can rerun my script whenever necessary. 
I will tart it up and put it somewhere safe! 
 
I also went through and removed the image header form 
all files - I don't think I have messed anything up - but its always 
possible!
 
Let me know if this is useful!
 
RC
 
 
 
ditto
I am all for a bit of awk scripting :-)... As long as I 
don’t have to write the awk script :-)
Eric
On 10/21/08 8:44 
AM, "John Worrell (jworrell)" <jworrell@xxxxxxxxx> 
wrote:
What I was driving at is that I think the rest (apart from the URL 
  tweaking) can be done automatically. A bit of 'awk' 
  scripting?
Cheers,
JohnW
  
  From: tigerstripe-dev-bounces@xxxxxxxxxxx 
  [mailto:tigerstripe-dev-bounces@xxxxxxxxxxx] 
  On Behalf Of Steve Jerman (stjerman)
Sent: 21 October 2008 
  16:32
To: Tigerstripe developers list
Subject: RE: 
  [tigerstripe-dev] Spread the misery
 
  
  From: tigerstripe-dev-bounces@xxxxxxxxxxx 
  [mailto:tigerstripe-dev-bounces@xxxxxxxxxxx] 
  On Behalf Of John Worrell (jworrell)
Sent: Tuesday, October 
  21, 2008 8:20 AM
To: Tigerstripe developers list
Subject: 
  RE: [tigerstripe-dev] Spread the misery
Hi Steve,
My higher priority tasks at the moment are to deliver the IRD stuff 
  and to write help for the IRD stuff.
But, for when I do get to this task can I check a couple of 
  things:
1) we are taking the title from the existing file and putting it 
  into title in the new file 
--> Sure
2) we are fixing the URL to CSS 
-->  Not sure what you mean. The USL of the css file 
  will need fixing to be correct relative to the position of the body.css file 
  in the root of the HTML docs (which the includes the formal 
  body.css)
3) we take the stuff between <!-- InstanceBeginEditable 
  name="Body" --> and <!-- InstanceEndEditable name="Body" --> and copy 
  it into <body></body> 
--> Yup
4) Q - do we need to keep the magic comments, that is, <!-- 
  Instance..--> etc.?? 
- Nope there are just Dreamweaver 
  cruft
5) Q - shouldn't we put a standard copyright into the 
  template?
-> Probably. I think that can be added autmatically though... 
  once we do the other stuff.
So, how's that?
Cheers,
JohnW
  
  From: tigerstripe-dev-bounces@xxxxxxxxxxx 
  [mailto:tigerstripe-dev-bounces@xxxxxxxxxxx] 
  On Behalf Of Steve Jerman (stjerman)
Sent: 21 October 2008 
  15:13
To: Tigerstripe developers list
Subject: 
  [tigerstripe-dev] Spread the misery
Hi 
  Folks,
as Eric 
  suggested on Monday, I have created a Wiki page outlining the steps needed to 
  reskin the documentation. I also split up the pages between 
  them.
http://wikicentral.cisco.com/confluence/display/GROUP/helpEdit
Let me know if you have any questions. This work is covere  by 
  https://bugs.eclipse.org/bugs/show_bug.cgi?id=251417
Steve
  
  _______________________________________________
tigerstripe-dev 
  mailing list
tigerstripe-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/tigerstripe-dev
Attachment:
bad.links
Description: bad.links
Attachment:
unused.files
Description: unused.files