[Interest] Interest Digest, Vol 8, Issue 10
Jeremy
jswigart at gmail.com
Fri May 4 15:41:25 CEST 2012
Can you clarify? Do you mean have an object that exposes the character
properties and such via custom properties? What is the relationship between
the QML character object, the QML character sheet object(the gui
presentor), and this data object(how are they linked for sharing)? What
precludes this data object from itself being a QML object rather than a C++
object?
One of the primary design goals of wanting to drive all this data via QML
is so that this application can support a variety of game systems since all
the real implementation of the game rules, character setup, etc is defined
in QML.
The property binding of QML is a huge asset for this sort of application,
since in RPG games, so many stats/rolls/etc are calculated as an equation
using multiple other stats as variables. I wouldn't want to lose that
capability.
Thanks for your time.
On Fri, May 4, 2012 at 5:00 AM, <interest-request at qt-project.org> wrote:
> Send Interest mailing list submissions to
> interest at qt-project.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.qt-project.org/mailman/listinfo/interest
> or, via email, send a message with subject or body 'help' to
> interest-request at qt-project.org
>
> You can reach the person managing the list at
> interest-owner at qt-project.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Interest digest..."
>
>
> Today's Topics:
>
> 1. QML & QDeclarativeView (Jeremy)
> 2. Re: QML & QDeclarativeView (Bo Thorsen)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Fri, 4 May 2012 00:07:19 -0500
> From: Jeremy <jswigart at gmail.com>
> Subject: [Interest] QML & QDeclarativeView
> To: interest at qt-project.org
> Message-ID:
> <CAKKKtcFeqOWtaZtCPy-r_9AZoc47CNYPV-_T5+qECuyUd44eRg at mail.gmail.com
> >
> Content-Type: text/plain; charset="iso-8859-1"
>
> Suppose you have a custom built UI, with forms and c++ and such. Within
> certain panes/tabs/etc of this custom view, you want to display qml driven
> content. Is it possible for the same QML data to drive the output in
> multiple QDeclarativeView ?
>
> For example:
> I'm writing a combination tile map editor and scenario setup for tabletop
> rpg games, sort of a virtual table sort of application. Here's the
> preliminary thoughts on how I am wanting to set it up.
>
> - Application as a subclassed QDeclarativeView representing the scenario
> map. I subclass so that I may draw the map, grids, etc in a custom
> fashion.
> - All the players/monsters/items/props/etc I would like to be provided
> as QML objects, for customization of behavior and such based on what is
> applicable for the game rules, etc.
> - To narrow in one one example. Suppose QML defines a character for a
> D&D character, complete with stats, skills, etc. This object contains all
> this information.
> - There is a list box, table view, or whatever in another pane of the
> application that shows the list of players, and I would like to be able
> to
> click on them and bring up their character sheet.
> - I want this character sheet also to be created and managed by QML,
> presumably as part of the character QML object, since that's where all
> the
> data is.
>
> How can the QML data/state be shared among different views like this? I
> would prefer not to have to have all the data driven elements instantiated
> inside the main map view if I don't have to. It would be far more flexible
> for example to have each character sheet rendered via different QML views
> on separate tab pages for example, for quick and easy access.
>
> Thoughts?
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> http://lists.qt-project.org/pipermail/interest/attachments/20120504/b51b8f1a/attachment-0001.html
>
> ------------------------------
>
> Message: 2
> Date: Fri, 04 May 2012 09:07:42 +0200
> From: Bo Thorsen <bo at fioniasoftware.dk>
> Subject: Re: [Interest] QML & QDeclarativeView
> To: Jeremy <jswigart at gmail.com>
> Cc: interest at qt-project.org
> Message-ID: <4FA3803E.4030706 at fioniasoftware.dk>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> Hi Jeremy,
>
> Den 04-05-2012 07:07, Jeremy skrev:
> > Suppose you have a custom built UI, with forms and c++ and such. Within
> > certain panes/tabs/etc of this custom view, you want to display qml
> > driven content. Is it possible for the same QML data to drive the output
> > in multiple QDeclarativeView ?
> >
> > For example:
> > I'm writing a combination tile map editor and scenario setup for
> > tabletop rpg games, sort of a virtual table sort of application. Here's
> > the preliminary thoughts on how I am wanting to set it up.
> >
> > * Application as a subclassed QDeclarativeView representing the
> > scenario map. I subclass so that I may draw the map, grids, etc in a
> > custom fashion.
> > * All the players/monsters/items/props/etc I would like to be provided
> > as QML objects, for customization of behavior and such based on what
> > is applicable for the game rules, etc.
> > * To narrow in one one example. Suppose QML defines a character for a
> > D&D character, complete with stats, skills, etc. This object
> > contains all this information.
> > * There is a list box, table view, or whatever in another pane of the
> > application that shows the list of players, and I would like to be
> > able to click on them and bring up their character sheet.
> > * I want this character sheet also to be created and managed by QML,
> > presumably as part of the character QML object, since that's where
> > all the data is.
> >
> > How can the QML data/state be shared among different views like this? I
> > would prefer not to have to have all the data driven elements
> > instantiated inside the main map view if I don't have to. It would be
> > far more flexible for example to have each character sheet rendered via
> > different QML views on separate tab pages for example, for quick and
> > easy access.
>
> The best way to do this is to have the state in C++ objects and export
> those to the QML app.
>
> Short answer to a long question, I know :) If you need help with parts
> of this, just write another email.
>
> Bo Thorsen,
> Fionia Software.
>
> --
>
> Expert Qt and C++ developer for hire
> Contact me if you need expert Qt help
> http://www.fioniasoftware.dk
>
>
> ------------------------------
>
> _______________________________________________
> Interest mailing list
> Interest at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/interest
>
>
> End of Interest Digest, Vol 8, Issue 10
> ***************************************
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/interest/attachments/20120504/2f439fa4/attachment.html>
More information about the Interest
mailing list