lp://staging/rpg+helper

Branch merges

Propose for merging

No branches dependent on this one.

Related source package recipes

No recipes using this branch. (?)

Create packaging recipe

Related snap packages

Related bugs

Related blueprints

14. By japair <japair@Hackworth> on 2008-11-24

 Mergin in my script for fetching monster data from the D&DIC to print out encounters. Basic, but it works.

13. By japair <japair@Hackworth> on 2008-11-20

 I have a silverlight client app. It says hi (static text only).

12. By japair <japair@Hackworth> on 2008-11-20

 Monster model, and nukedb.py creates one in the DB. Also fixed problem with NamedResource that was introduced in a character refactoring. And there's an empty Silverlight UI that isn't working yet.

11. By Kimberly Wallmark <email address hidden> on 2008-11-20

Added more routes for dealing with items and characters. Removed most of the testing-only routes.

10. By japair <japair@Hackworth> on 2008-11-14

 The character view is now a form. It comes as a form to the client, which then transforms the form into a pretty display version. It adds links to re-expose parts of the form, allowing user edit. Thus, the UI looks pretty, and you can expose inline editing for everything. If JS is off, then it'll just look like a form - it won't hide itself.

9. By japair <japair@Hackworth> on 2008-11-14

 I extended the data model out quite a bit. I'm adding the stuff for monsters and encounters. Also, I extracted some common code in model mapping & mapping to resources (shared between Item, Monster, Encounter, and Character). And I added the sqlalchemy relation to item so that we can deal with the item / player relationship as objects, not just as IDs.

8. By Kimberly Wallmark <email address hidden> on 2008-11-13

Items are more interesting now. They go all the way to the database and have owners.

7. By Kimberly Wallmark <kwallmar@Sheila> on 2008-11-10

Basic routing set up.

Added extremely trivial support for items to give a second possible web page, to make routing easier to track.

6. By japair <japair@Hackworth> on 2008-11-08

 Getting closer to editable UI.

5. By japair <japair@Hackworth> on 2008-11-03

 Characters use a custom layout - not just a bunch of widgets. However, it should be reasonably easy to break into widgets - I did repeat common, semmantic, elements.
The character's layout / presentation first whack is done. This includes the header (except for the dynamic XP log) & the card-like layout with rounded corners & a shadow (screen only - haven't even looked at the print version yet). The text in the combat stats is still unstyled, and the other sections aren't even in the mock data.