790:
198:
23:
49:
320:
accomplish what you want. If you're using your regex and you find a false positive or false negative, you can add it to your tests, then modify the regex so that it handles it properly. It will automatically tell you if your regex handles the new situation, but equally important, it will make sure that none of your
781:. I'm definitely a Friedman fan; I really like detailed design histories. Someday I'd like to own 'em all. I'm not a huge Garzke & Dulin fan, but I do eventually want their books on Allied and Axis battleships. They're chock full of detailed specifications and diagrams that'd be really helpful here.
319:
for regular expression tasks. I want to be able to associate sets of "before" and "after" text with my regular expressions. The regex should be run on the "before" text, and then the result should be compared to the "after" text; if it doesn't match, it will warn you that your regex doesn't seem to
813:
cranked them out, but since then I've slowed down. I always had trouble keeping track of where I left off and what was going on, and then there'd be a long gap between episode releases and I'd completely lose my place. These days I try to wait 'til I can grab a complete series and watch it all the
405:
changed every time a new state was admitted, and many ship articles were written simply using the current 50-star flag when an older one would be more appropriate. When I need a light project I can work on for a couple of minutes at a time, I seek out incorrect uses of the U.S. Navy jack or ensign
308:
The ability to put tasks into groups and enable/disable them by group, in addition to enabling/disabling each task individually. For example, I might have some ship-specific tasks defined, but if they were made to other articles they'd look odd. I don't want to scroll through my task list and
300:
So far I've just been calling the thing "Tom's Task Engine". It allows you to create a list of tasks that you want to perform on each article. You can reorder these tasks at will. Sounds a lot like AWB's built-in capability, but the specific improvements I want to accomplish are:
413:. For example, there was no way to express that a ship had been decommissioned for some time and then recommissioned. There was also no way to include service in multiple navies. To try to address this and other issues, I implemented a solution suggested by
297:, and incorporate everything I've learned since I originally wrote them. As I did this, I became unsatisfied with some elements of AWB's built-in find-and-replace capability, and I realized that if I just wrote my own plugin I could take care of all of it.
437:
I have a few pretty beefy texts about ships. I would be happy to confirm facts with these, and provide page numbers so they can be used for citations. Let me know on my talk page, and I'll check them and get back to you as soon as possible.
863:, is way, way easier to find reliable sources on. Also, because I would really love there to be a reliable, organized, detailed, attractive online reference that I can put the name of any ship into and get all the information I could want.
292:
that I used to make certain automatic formatting changes to articles I was working on. A few weeks ago, I realized that it was really time for me to go through all of my regexes and review them to make sure they worked, eliminate
393:
from the discussions we've had over the past year. Things are way better organized than they used to be, so I've slowed down and I try to make real content improvements while I categorize instead of just doing drive-by.
342:. I'd find a bug and fix it, and then realize that I had to apply the same fix to seven other horrifying expressions. Both my forehead and the keyboard were suffering. I realized that I could just write a damn
337:
template to articles, and I found that it's a fairly complex task. I was writing many nasty regexes that were very similar to each other, but I couldn't think of a way to combine them into one without causing a
305:
A compact name and a lengthy description for each task. Regular expressions can get pretty complicated, and I need to be able to write as much as I want about them so I can understand their purpose later.
312:
A simpler interface for creating simple find-and-replace tasks. I feel like more people could perform automated find-and-replace operations if they could be completely separated from regular expressions.
235:, but while I'm at home I can be reached on AOL Instant Messenger if anyone wants to talk "off the record." You can also e-mail me using the "E-mail this user" link on the left, if you've
885:
809:, and I try to watch at least a couple of episodes of something every day. Back in college I used to keep up with a few different series simultaneously, watching each episode as the
713:
478:
814:
way through. As a result, I'm no longer on the cutting edge, but I can usually manage to finish watching something before it gets released in the U.S.
880:
606:
542:
129:
123:
339:
769:
670:
251:
247:
327:
Hard-coded complex regular expression tasks, where you just specify certain inputs. I started to write regexes to automatically apply the
390:
875:
55:
353:
to the method. This single issue is what made me start on the project, and the others were simple "well, as long as I'm doing
263:
309:
figure out which are for ships and which aren't; I want to be able to disable the entire "Ship" group at the same time.
695:
652:
588:
524:
460:
278:
277:
I haven't been doing much editing or participating in WP:SHIPS discussions lately because I'm currently working on a
232:
417:
where each part of the infobox would be a separate template, so you could repeat sections as necessary. Check out
259:
213:
343:
373:. For now, I'm still working out how to store all the data and whatnot, so there's nothing to play with yet.
370:
687:
644:
580:
516:
452:
418:
255:
762:
350:
794:
386:
206:
81:
60:
267:
853:
798:
402:
346:
282:
382:
157:
349:
that would have a single, awful regex at its core, and I could pass in the slight differences as
834:
821:, but again I'm way behind. I usually wait until I can get stuff cheap, often used. I have a
225:
410:
29:
856:
it had terrible traction issues. Then I started breaking motor mounts so I got rid of it.
221:
746:
734:
627:
563:
499:
409:
In cleaning up and updating ship articles, I kept running into the various limitations of
8:
683:
640:
576:
512:
448:
236:
182:
845:
365:
Anyway, once I'm done I'll post it around a few places. Once I get to a stage where it
721:
614:
550:
486:
289:
401:
in order to make it easy to put the proper U.S. Navy ensign into ship infoboxes. The
826:
825:, and I think it's awesome, but I only have a handful of Wii games. I probably play
701:
691:
658:
648:
594:
584:
530:
520:
466:
456:
398:
288:
I've been using AWB for quite some time, and I had built up a pretty good library of
709:
666:
602:
538:
474:
331:
228:. My Knowledge contributions are mostly on history and automotive-related topics.
217:
294:
869:
860:
838:
830:
789:
422:
197:
849:
316:
859:
So why don't I write about any of that stuff? Because my other interest,
414:
837:, but again, I only have a few games for it and use it primarily for my
818:
844:
I like cars, and I drive a 2005 Evo VIII MR. Before this, I drove a
22:
778:
662:
848:, which was a fun car, but with a lightly modded, very torquey
810:
705:
598:
534:
470:
806:
137:
134:
509:
U.S. Submarines
Through 1945: An Illustrated Design History
108:
101:
86:
75:
886:
Wikipedians by alma mater: North
Carolina State University
822:
573:
U.S. Submarines Since 1945: An
Illustrated Design History
376:
829:
games on it more often than anything else. I bought a
48:
777:
My next purchase will probably be
Friedman's book on
369:
but is incomplete, I'll think about offering it for
637:Conway's All The World's Fighting Ships, 1922–1946
680:Battleships: United States Battleships, 1935–1992
867:
445:U.S. Battleships: An Illustrated Design History
421:and its talk page for more details, or look at
272:
881:Wikipedians interested in anime and manga
768:CS1 maint: multiple names: authors list (
788:
784:
634:
570:
506:
442:
239:an e-mail address for your account too.
196:
868:
678:Garzke, William H., Jr. (1976, 1995).
377:My Wiki activities and accomplishments
361:drives me up the wall too" spec creep.
406:and replace them with the template.
242:
212:I am 26 years old and a graduate of
174:
148:
119:
97:
71:
43:
17:
13:
677:
381:I'm currently involved in a large
14:
897:
391:WP:SHIPS categorization guideline
385:project for naval vessels, with
47:
21:
635:Gardiner, Robert (Ed.) (1980).
214:North Carolina State University
876:WikiProject Ships participants
833:while they still offered full
432:
1:
688:United States Naval Institute
645:United States Naval Institute
581:United States Naval Institute
517:United States Naval Institute
453:United States Naval Institute
419:Template:Infobox Ship Example
7:
795:Mitsubishi Lancer Evolution
252:Dates and numbers
10:
902:
389:. I compiled the current
799:Deals Gap, North Carolina
571:Friedman, Norman (1994).
507:Friedman, Norman (1995).
443:Friedman, Norman (1985).
273:Where's Tom been lately?
181:This user page has been
835:backward compatibility
802:
741:Check date values in:
226:Research Triangle Park
209:
792:
785:Hobbies and interests
429:to see it in action.
411:Template:Infobox Ship
200:
30:AOL Instant Messenger
268:WP:SHIPS banner
222:software development
684:Annapolis, Maryland
641:Annapolis, Maryland
577:Annapolis, Maryland
513:Annapolis, Maryland
449:Annapolis, Maryland
290:regular expressions
264:WP:SHIPS flags
231:I work 9-to-5-ish,
216:, with a degree in
156:This user has made
803:
753:Unknown parameter
260:WP:SHIPS talk
210:
207:WikiProject Ships!
399:Template:USN flag
397:I also developed
256:Ship infobox
243:Some links for me
201:Wikipe-tan wants
193:
192:
171:
170:
145:
144:
116:
115:
94:
93:
68:
67:
61:WikiProject Ships
40:
39:
893:
773:
766:
760:
756:
755:|coauthors=
750:
744:
738:
732:
727:
725:
717:
674:
631:
625:
620:
618:
610:
567:
561:
556:
554:
546:
503:
497:
492:
490:
482:
336:
330:
224:at a company in
218:computer science
175:
167:
164:
149:
120:
98:
72:
51:
44:
25:
18:
901:
900:
896:
895:
894:
892:
891:
890:
866:
865:
787:
767:
758:
754:
752:
742:
740:
730:
728:
719:
718:
714:V815.3.G37 1994
698:
655:
623:
621:
612:
611:
591:
559:
557:
548:
547:
527:
495:
493:
484:
483:
479:V815.3.F74 1985
463:
435:
379:
334:
328:
295:false positives
275:
248:Stub types
245:
233:US Eastern time
195:
194:
172:
158:
155:
146:
117:
106:This user is a
95:
69:
54:This user is a
41:
12:
11:
5:
899:
889:
888:
883:
878:
852:engine and no
797:MR edition at
786:
783:
775:
774:
696:
675:
653:
632:
589:
568:
525:
504:
461:
434:
431:
427: (SS-340)
383:categorization
378:
375:
363:
362:
325:
313:
310:
306:
274:
271:
244:
241:
191:
190:
179:
173:
169:
168:
153:
147:
143:
142:
126:
118:
114:
113:
104:
96:
92:
91:
78:
70:
66:
65:
52:
42:
38:
37:
32:screenname is
26:
16:
15:
9:
6:
4:
3:
2:
898:
887:
884:
882:
879:
877:
874:
873:
871:
864:
862:
861:naval history
857:
855:
851:
847:
842:
840:
836:
832:
831:PlayStation 3
828:
824:
820:
815:
812:
808:
800:
796:
791:
782:
780:
771:
764:
759:|author=
748:
736:
723:
715:
711:
707:
703:
699:
697:1-55750-174-2
693:
689:
685:
681:
676:
672:
668:
664:
660:
656:
654:0-85177-146-7
650:
646:
642:
638:
633:
629:
616:
608:
607:V858.F75 1994
604:
600:
596:
592:
590:1-55750-260-9
586:
582:
578:
574:
569:
565:
552:
544:
543:V858.F75 1995
540:
536:
532:
528:
526:1-55750-263-3
522:
518:
514:
510:
505:
501:
488:
480:
476:
472:
468:
464:
462:0-87021-715-1
458:
454:
450:
446:
441:
440:
439:
430:
428:
426:
420:
416:
412:
407:
404:
400:
395:
392:
388:
384:
374:
372:
368:
360:
356:
352:
348:
345:
341:
333:
326:
323:
318:
314:
311:
307:
304:
303:
302:
298:
296:
291:
286:
284:
280:
270:
269:
265:
261:
257:
253:
249:
240:
238:
234:
229:
227:
223:
220:. I work in
219:
215:
208:
204:
199:
188:
184:
180:
177:
176:
166:to Knowledge.
165:
163:contributions
162:
154:
151:
150:
140:
139:
136:
131:
127:
125:
122:
121:
111:
110:
105:
103:
100:
99:
89:
88:
83:
79:
77:
74:
73:
63:
62:
57:
53:
50:
46:
45:
35:
31:
27:
24:
20:
19:
858:
854:limited slip
850:turbocharged
843:
817:I also like
816:
804:
776:
761:suggested) (
679:
636:
572:
508:
444:
436:
424:
408:
396:
380:
371:beta testing
366:
364:
358:
354:
335:}}
329:{{
324:tests break.
321:
317:unit testing
299:
287:
276:
246:
230:
211:
202:
186:
160:
133:
107:
85:
80:This user's
59:
33:
28:This user's
846:VW GTI 1.8T
819:video games
743:|date=
731:|lccn=
624:|lccn=
560:|lccn=
496:|lccn=
433:Books I own
340:Tomsplosion
870:Categories
811:fansubbers
351:parameters
315:Automated
183:vandalized
159:more than
34:TomTheHand
793:Me in my
757:ignored (
722:cite book
615:cite book
551:cite book
487:cite book
425:Entemedor
423:USS
827:GameCube
779:cruisers
671:V765.C66
663:81103282
387:WP:SHIPS
205:to join
84:type is
841:games.
805:I love
733:value (
706:9343601
626:value (
599:9342132
562:value (
535:9429958
498:value (
471:8513769
403:US flag
332:Convert
729:Check
712:
704:
694:
669:
661:
651:
622:Check
605:
597:
587:
558:Check
541:
533:
523:
494:Check
477:
469:
459:
415:wwoods
347:method
279:plugin
237:set up
189:times.
185:
152:9,000+
132:is an
56:member
807:anime
367:works
178:vn-13
161:9,000
138:otaku
135:anime
128:This
770:link
763:help
747:help
735:help
702:LCCN
692:ISBN
659:LCCN
649:ISBN
628:help
595:LCCN
585:ISBN
564:help
531:LCCN
521:ISBN
500:help
467:LCCN
457:ISBN
359:this
355:that
281:for
130:user
109:geek
87:INTP
82:MBTI
76:INTP
839:PS2
823:Wii
710:LCC
667:LCC
603:LCC
539:LCC
475:LCC
322:old
283:AWB
203:you
124:アニメ
58:of
872::
751:;
739:;
726::
724:}}
720:{{
708:.
700:.
690:.
686::
682:.
665:.
657:.
647:.
643::
639:.
619::
617:}}
613:{{
601:.
593:.
583:.
579::
575:.
555::
553:}}
549:{{
537:.
529:.
519:.
515::
511:.
491::
489:}}
485:{{
473:.
465:.
455:.
451::
447:.
357:,
344:C#
285:.
266:|
262:|
258:|
254:|
250:|
187:13
102:gk
801:.
772:)
765:)
749:)
745:(
737:)
716:.
673:.
630:)
609:.
566:)
545:.
502:)
481:.
141:.
112:.
90:.
64:.
36:.
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.
