• Please note: In an effort to ensure that all of our users feel welcome on our forums, we’ve updated our forum rules. You can review the updated rules here: http://forums.wolflair.com/showthread.php?t=5528.

    If a fellow Community member is not following the forum rules, please report the post by clicking the Report button (the red yield sign on the left) located on every post. This will notify the moderators directly. If you have any questions about these new rules, please contact support@wolflair.com.

    - The Lone Wolf Development Team

Colorization

  • Thread starter Thread starter scspieker at yahoo.com
  • Start date Start date
S

scspieker at yahoo.com

Guest
Probably a bad idea, but one that came to mind while using Word 97...

Would it be feasable to have a roster which is updated be colorized with
changes from the previous roster.


For example, I play Mordheim, and find that the changes in my roster are
somewhat hard to follow unless I keep all of the previous printed rosters
with notes attached. So when we get to playing agian, we can share our
rosters to see what changes had been applied since the last game.

I play a player who has several different bands, and each time we play,
I cannot remember what changes had gone into his band, and we like to share
our rosters so that we can guage how well we did against each other and know
a little more in advance of something a little sneaky that may come up.

If I were to be so bold as to offer a suggestion on how this can be
accomplished, I would think a copy of the roster object or an array of the
roster contents (possibly the saved file itself) being the 'original'
document, then each option that was changed to be compared to the original
and then colored in red or something to signify the 'update'.

When the roster is printed is where it is most important, and so
updating the colors on the screen would have a low priority for me.

Thanks,
Scott
 
How about this idea:

Original Roster for your warband name = Warband052901 (signifying that it
was Warband [name] saved on 05/29/01).

Then, after you have a battle and your warband improves, then you can open
up Warband052901 and make the changes, then instead of just saving the file,
use the 'save as' option instead, and save it as Warband053001 (signifying
that it was Warband [name] saved on 05/30/01).

Doing it this way, you can keep a running record of rosters and when they
were last updated. So, if you ever want to look at a history of your
improvements, then you can just print out each version of your warband.

I actually do this for a 40K campaign that I play in, and it is easier in
practice than it is to type it out =]

Well, good Hunting,
TP

-----Original Message-----
From: Scott Spieker [mailto:scspieker@yahoo.com]
Sent: Tuesday, May 29, 2001 10:37 AM
To: ab@support.wolflair.com
Subject: [AB] Colorization

Probably a bad idea, but one that came to mind while using Word 97...

Would it be feasable to have a roster which is updated be colorized with
changes from the previous roster.


For example, I play Mordheim, and find that the changes in my roster are
somewhat hard to follow unless I keep all of the previous printed rosters
with notes attached. So when we get to playing agian, we can share our
rosters to see what changes had been applied since the last game.

I play a player who has several different bands, and each time we play,
I cannot remember what changes had gone into his band, and we like to share
our rosters so that we can guage how well we did against each other and know
a little more in advance of something a little sneaky that may come up.

If I were to be so bold as to offer a suggestion on how this can be
accomplished, I would think a copy of the roster object or an array of the
roster contents (possibly the saved file itself) being the 'original'
document, then each option that was changed to be compared to the original
and then colored in red or something to signify the 'update'.

When the roster is printed is where it is most important, and so
updating the colors on the screen would have a low priority for me.

Thanks,
Scott


To unsubscribe from this group, email

armybuilder-unsubscribe@egroups.com

Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
 
Another idea would be to output the roster in HTML and then add color
manually before printing.

It would also be possible to write a program to do this using either the
HTML output or the XML output.

Brad

-----Original Message-----
From: The Prophet [mailto:TheProphet@voyager.net]
Sent: Tuesday, May 29, 2001 11:11 AM
To: armybuilder@yahoogroups.com
Subject: RE: [AB] Colorization


How about this idea:

Original Roster for your warband name = Warband052901 (signifying that it
was Warband [name] saved on 05/29/01).

Then, after you have a battle and your warband improves, then you can open
up Warband052901 and make the changes, then instead of just saving the
file,
use the 'save as' option instead, and save it as Warband053001 (signifying
that it was Warband [name] saved on 05/30/01).

Doing it this way, you can keep a running record of rosters and when they
were last updated. So, if you ever want to look at a history of your
improvements, then you can just print out each version of your warband.

I actually do this for a 40K campaign that I play in, and it is easier in
practice than it is to type it out =]

Well, good Hunting,
TP

-----Original Message-----
From: Scott Spieker [mailto:scspieker@yahoo.com]
Sent: Tuesday, May 29, 2001 10:37 AM
To: armybuilder@yahoogroups.com
Subject: [AB] Colorization

Probably a bad idea, but one that came to mind while using Word 97...

Would it be feasable to have a roster which is updated be colorized with
changes from the previous roster.


For example, I play Mordheim, and find that the changes in my roster are
somewhat hard to follow unless I keep all of the previous printed rosters
with notes attached. So when we get to playing agian, we can share our
rosters to see what changes had been applied since the last game.

I play a player who has several different bands, and each time we
play,
I cannot remember what changes had gone into his band, and we like to
share
our rosters so that we can guage how well we did against each other and
know
a little more in advance of something a little sneaky that may come up.

If I were to be so bold as to offer a suggestion on how this can be
accomplished, I would think a copy of the roster object or an array of the
roster contents (possibly the saved file itself) being the 'original'
document, then each option that was changed to be compared to the original
and then colored in red or something to signify the 'update'.

When the roster is printed is where it is most important, and so
updating the colors on the screen would have a low priority for me.

Thanks,
Scott


To unsubscribe from this group, email

armybuilder-unsubscribe@egroups.com

Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/




Yahoo! Groups Sponsor

Yahoo! Website Services- Click Here!


To unsubscribe from this group, email

armybuilder-unsubscribe@egroups.com

Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.



[Non-text portions of this message have been removed]
 
> How about this idea:
>
> Original Roster for your warband name = Warband052901 (signifying that it
> was Warband [name] saved on 05/29/01).
>
> Then, after you have a battle and your warband improves, then you can open
> up Warband052901 and make the changes, then instead of just saving the
file,
> use the 'save as' option instead, and save it as Warband053001 (signifying
> that it was Warband [name] saved on 05/30/01).
>
> Doing it this way, you can keep a running record of rosters and when they
> were last updated. So, if you ever want to look at a history of your
> improvements, then you can just print out each version of your warband.
>
> I actually do this for a 40K campaign that I play in, and it is easier in
> practice than it is to type it out =]
>
> Well, good Hunting,
> TP

This is OK to do, I have no problem tracking the changes between games with
my own forces, but what about my normal gaming pals. They wouldn't
necessarily know unless they remember getting beat up by one particular
model or something. Unless I have the previous roster sheets with me, there
is nothing to compare the new values against.

Now I know this CAN be done - I do it already with the programs I write
at work, and they are not even fully Object Oriented. So if AB is written
in C++ or something like it, making a copy of an object should be rather
easy to do, then compare the two object's properties to view which has
changed and which has not. Seems rather simple to me since I have done this
for years.

I like the idea of using HTML to colorize, but that is more work than
what I was looking for. It's easier to print the roster (since it has to be
printed anyway), then just use a highlighter to indicate what had changed.
Less aggravation and accomplishes the same function as colorizing the roster
from the printer.

It was just an idea, thought I would get some others interested enough
to add it in. Obviously it does not seem very popular.

Scott
 
It's definitely doable, but it's actually a fair bit of work within AB. The
main reason is that options are not a flat list for each unit internally.
They LOOK that way to the user, but internally they are a bunch of chains
that ultimately get flattened for display. This is necessary to enable the
engine to swap groups of options in and out dynamically based on other
factors in the unit (e.g. the unit is given option X so a whole group of
other options becomes inaccessible, or a whole group of options now becomes
available). Tracking the changes would entail sorting through all this.
It's not hard or complicated - just a lot of stuff to process in order to
do a complete comparision. It would also require caching the original
roster contents so that the delta can be determined, which is something AB
currently doesn't do.

Given that the amount of work is moderate and only a small subset of users
would seriously utilize this feature, it's not something that will be added
immediately. However, I'm putting it on the todo list and it will hopefully
be added at some point in the future.

Thanks, Rob


At 07:37 AM 5/30/2001 -0400, you wrote:
> Now I know this CAN be done - I do it already with the programs I write
>at work, and they are not even fully Object Oriented. So if AB is written
>in C++ or something like it, making a copy of an object should be rather
>easy to do, then compare the two object's properties to view which has
>changed and which has not. Seems rather simple to me since I have done this
>for years.


---------------------------------------------------------------------------
Rob Bowes (rob@wolflair.com) (650) 726-9689
Lone Wolf Development www.wolflair.com
 
--- In armybuilder@y..., Rob Bowes <rob@w...> wrote:
> It would also require caching the original
> roster contents so that the delta can be determined

One hacky workaround for this would be to make this a menu pick that
diffs the disk file with what's currently in RAM. Of course, this
only works if the user doesn't save their changes.

Or to make things a little more certain, copy roster to a temp file
and then run your diffs vs. that.

--
Mark Sironi
 
You must log in or register to reply here.
Back
Top