Help for a newbie dev

[Mircea S.]

Hello,

I’ve installed the gem, and I’m looking through the code. I have two questions:

1. Where can I modify the behavior of cards so that they come open by default? (so I don’t have to click the down arrow on the top left every time I want to see what’s in one)

2. Is it possible to create a wagn site that is empty? When I installed the “manual site” on a vm of mine, I noticed “rake wagn:create” also seeds the database with initial cards. Is it possible to erase this and just have an empty site?

Thank you!

[Gerry Gleason]

On Sunday, June 15, 2014 at 3:50 AM, Mircea S. wrote:
> Hello,
>
> I’ve installed the gem, and I’m looking through the code. I have two questions:
>
> 1. Where can I modify the behavior of cards so that they come open by default? (so I don’t have to click the down arrow on the top left every time I want to see what’s in one)
>

That is in inclusion options, which are after the pipe '|' in the double curly syntax. You'll probably want to read up a bit at wagn.org about the different views, but 'open' and 'closed' are the two you are likely thinking of. The closed cards are probably already under control of an option (not the default).

The other detail to worry about here is whether you are including a single card or a list from a search or pointer card, in that case something line this: {{Some Search Card|item:open}} The new syntax actually lets you give the options in a more general way with multiple pipes: {{Some Search Card|content|open}} which would have 'content' as the main card's view and 'open' for the items cards.

Hope that isn't too confusing.

>
> 2. Is it possible to create a wagn site that is empty? When I installed the “manual site” on a vm of mine, I noticed “rake wagn:create” also seeds the database with initial cards. Is it possible to erase this and just have an empty site?

Not really. Some of the cards could be left out, but many of the cards are needed for Wagn to be able to work. This is because many cards control how other cards work, what we call "rule" cards.

Gerry
> Thank you!
>

____________________________________________________________
FREE 3D MARINE AQUARIUM SCREENSAVER - Watch dolphins, sharks & orcas on your desktop!
Check it out at http://www.inbox.com/marineaquarium

[Ethan McCutchen]

Gerry answered these well, but let me add a little further context.

> 1. Where can I modify the behavior of cards so that they come open by default? (so I don’t have to click the down arrow on the top left every time I want to see what’s in one)

The first term I'd introduce here is "views".  You're seeing the cards in "closed" view but would like to see them in "open" view.  The views doc will provide more information about the various ways you can use views, such as the inclusion context Gerry mentions.  See the "tips" section for other useful contexts.

> 2. Is it possible to create a wagn site that is empty? When I installed the “manual site” on a vm of mine, I noticed “rake wagn:create” also seeds the database with initial cards. Is it possible to erase this and just have an empty site?

Again, Gerry is right.  Without cards you'd have no cardtypes, no roles, no rules, no help text, no stylesheets, no layouts.  So Wagn specifically detects the lack of data and doesn't even fully load.

As Wagn's community continues to develop, however, we'll likely see a lot more support for installing increasingly bare-bones sites.

-ethan

--
You received this message because you are subscribed to the Google Groups "Wagn Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to wagn-dev+u...@googlegroups.com.
To post to this group, send email to wagn...@googlegroups.com.
Visit this group at http://groups.google.com/group/wagn-dev.
For more options, visit https://groups.google.com/d/optout.

--
Ethan McCutchen

One of the Wagneers, Wagn.org

Wagn. How pioneers roll.

s: ethan.mccutchen

t: @intogreater

[Mircea S.]

What about the "+" marker on some cards... what does it do?

[Gerry Gleason]

That's the "joint" character that divides the name into parts. In the name A+B+C, A+B is the "left" or "trunk" and C is the "right" or "tag", then A+B can be broken down similarly. I think of it like a hierarchical name system as in a filesystem where the + is like / (or \ if you like Microsoft).

This naming structure is used in several ways, for example "rule" cards consist of a Set card (*all for all cards or my_tag+*right for all cards with 'my_tag' as the tag part) plus a Setting card (*read for read permissions, *layout for the page layout card). The other big use is for creating something like records with + cards for the field contents.

One important use pattern is to have a template (*structure rule) for a cardtype, so for example: MyType+*type+*structure => "Title: {{+title}} Description: {{+description}}" sets up a template for a record with two fields (title and description). When I create a card of type "MyType", I will see a multi-field form with the two template fields. If the new card's name is "MyCard", saving the template will create MyCard+title and MyCard+description with the data for the two fields. It creates MyCard too, but the contents isn't used (the *structure rule contents is used instead).

Gerry

On Tuesday, June 17, 2014 at 10:12 AM, Mircea S. wrote:

> What about the "+" marker on some cards... what does it do?
>
>
> În 17.06.2014 01:30, Ethan McCutchen a scris:
> > Gerry answered these well, but let me add a little further context.
> >
> > > 1. Where can I modify the behavior of cards so that they come open by default? (so I don’t have to click the down arrow on the top left every time I want to see what’s in one)
> >
> >

> > The first term I'd introduce here is "views". You're seeing the cards in "closed" view but would like to see them in "open" view. The views doc (http://wagn.org/views) will provide more information about the various ways you can use views, such as the inclusion context Gerry mentions. See the "tips" section for other useful contexts.

> >
> >
> > > 2. Is it possible to create a wagn site that is empty? When I installed the “manual site” on a vm of mine, I noticed “rake wagn:create” also seeds the database with initial cards. Is it possible to erase this and just have an empty site?
> >
> >
> > Again, Gerry is right. Without cards you'd have no cardtypes, no roles, no rules, no help text, no stylesheets, no layouts. So Wagn specifically detects the lack of data and doesn't even fully load.
> >
> > As Wagn's community continues to develop, however, we'll likely see a lot more support for installing increasingly bare-bones sites.
> >
> > -ethan
> >
> >
> >
> >
> >
> >
> > On Mon, Jun 16, 2014 at 4:09 PM, Gerry Gleason <ger...@inbox.com (mailto:ger...@inbox.com)> wrote:
> > >
> > > On Sunday, June 15, 2014 at 3:50 AM, Mircea S. wrote:
> > > > Hello,
> > > >
> > > > I’ve installed the gem, and I’m looking through the code. I have two questions:
> > > >
> > > > 1. Where can I modify the behavior of cards so that they come open by default? (so I don’t have to click the down arrow on the top left every time I want to see what’s in one)

> > > > That is in inclusion options, which are after the pipe '|' in the double curly syntax. You'll probably want to read up a bit at wagn.org (http://wagn.org) about the different views, but 'open' and 'closed' are the two you are likely thinking of. The closed cards are probably already under control of an option (not the default).

> > >
> > >
> > > The other detail to worry about here is whether you are including a single card or a list from a search or pointer card, in that case something line this: {{Some Search Card|item:open}} The new syntax actually lets you give the options in a more general way with multiple pipes: {{Some Search Card|content|open}} which would have 'content' as the main card's view and 'open' for the items cards.
> > >
> > > Hope that isn't too confusing.
> > > >
> > > > 2. Is it possible to create a wagn site that is empty? When I installed the “manual site” on a vm of mine, I noticed “rake wagn:create” also seeds the database with initial cards. Is it possible to erase this and just have an empty site?
> > >
> > > Not really. Some of the cards could be left out, but many of the cards are needed for Wagn to be able to work. This is because many cards control how other cards work, what we call "rule" cards.
> > >
> > > Gerry
> > > > Thank you!
> > >
> > >
> > > ____________________________________________________________
> > > FREE 3D MARINE AQUARIUM SCREENSAVER - Watch dolphins, sharks & orcas on your desktop!
> > > Check it out at http://www.inbox.com/marineaquarium
> > >
> > >
> > > --
> > > You received this message because you are subscribed to the Google Groups "Wagn Developers" group.

> > > To unsubscribe from this group and stop receiving emails from it, send an email to wagn-dev+u...@googlegroups.com (mailto:wagn-dev%2Bunsu...@googlegroups.com).
> > > To post to this group, send email to wagn...@googlegroups.com (mailto:wagn...@googlegroups.com).

> > > Visit this group at http://groups.google.com/group/wagn-dev.
> > > For more options, visit https://groups.google.com/d/optout.
> >
> >
> > --
> > Ethan McCutchen

> > One of the Wagneers, Wagn.org (http://Wagn.org)

> >
> > Wagn. How pioneers roll.
> >
> >
> > s: ethan.mccutchen
> > t: @intogreater
> >
> >
> > --
> > You received this message because you are subscribed to the Google Groups "Wagn Developers" group.

> > To unsubscribe from this group and stop receiving emails from it, send an email to wagn-dev+u...@googlegroups.com (mailto:wagn-dev+u...@googlegroups.com).
> > To post to this group, send email to wagn...@googlegroups.com (mailto:wagn...@googlegroups.com).

> > Visit this group at http://groups.google.com/group/wagn-dev.
> > For more options, visit https://groups.google.com/d/optout.
>
>
> --

> You received this message because you are subscribed to the Google Groups "Wagn Developers" group.

> To unsubscribe from this group and stop receiving emails from it, send an email to wagn-dev+u...@googlegroups.com (mailto:wagn-dev+u...@googlegroups.com).
> To post to this group, send email to wagn...@googlegroups.com (mailto:wagn...@googlegroups.com).

> Visit this group at http://groups.google.com/group/wagn-dev.
> For more options, visit https://groups.google.com/d/optout.

____________________________________________________________
GET FREE 5GB EMAIL - Check out spam free email with many cool features!
Visit http://www.inbox.com/email to find out more!

[Mircea S.]

So the "+" sign is somehow parsed by the app, in that it matters and can't be replaced by another character?

[Mircea S.]

What about the *character? What does it do?

Pe 17 iun. 2014, la 19:53, Gerry Gleason <ger...@inbox.com> a scris:

> *right

[Gerry Gleason]

This is really only a convention, it isn't really a special character as far as names go. Although it is exceptional in that most non-alpha-numeric characters get turned into space and squashed out in the key. The keys are important because two names that map to the same key refer to the same card. * stays in the key.

It indicates a "system" card and there are two sets that related to an initial * character:

*star is the Set of all cards beginning with a * (Ethan can elaborate, but I think it includes only "simple" cards, cards without any +)
*rstar is the Set of all cards whose right part (tag) is a *star card.

This makes it possible to create rules that apply only to these "system" cards, and for example make it so most ordinary users can't change or delete these system cards.

Gerry

On Tuesday, June 17, 2014 at 12:24 PM, Mircea S. wrote:

> What about the *character? What does it do?
>
>
>

> Pe 17 iun. 2014, la 19:53, Gerry Gleason <ger...@inbox.com (mailto:ger...@inbox.com)> a scris:
>
> > *right

____________________________________________________________
Protect your computer files with professional cloud backup.
Get PCRx Backup and upload unlimited files automatically.
Learn more at http://backup.pcrx.com/mail

[Ethan McCutchen]

http://wagn.org/plus_cards

http://wagn.org/star_cards

--
You received this message because you are subscribed to the Google Groups "Wagn Developers" group.

To unsubscribe from this group and stop receiving emails from it, send an email to wagn-dev+u...@googlegroups.com.
To post to this group, send email to wagn...@googlegroups.com.

Visit this group at http://groups.google.com/group/wagn-dev.
For more options, visit https://groups.google.com/d/optout.

--
Ethan McCutchen

One of the Wagneers, Wagn.org

Wagn. How pioneers roll.

s: ethan.mccutchen

t: @intogreater

[Mircea S.]

I’ve read up on the documentation.

Please correct the assertions below:

1. The * character has no programatic meaning, that being said, it is only a convention that all “system” cards have a * in front of the name. They could, someday, just have normal names or as in Objective-C Classes a prefix like "NS"String. They could be called SystemCardname and so on, WGCardname (from WAGN) or DKCardname (from Decko)

TRUE or FALSE

2. Compound names are simply card names with a "+" in them. My understanding is that this is kind of a manual way to denote that the Card1+Card2 name is a card that holds Card1 and Card2 part of itself. In the end, it’s just a naming convention and the “+” can be anything like a “space” character or the word “and”.

TRUE or FALSE

Thank you for taking the time to clear up my doubts.

Waiting for a response.

[Ethan McCutchen]

On Tue, Jun 17, 2014 at 1:50 PM, Mircea S. <mir...@unom.ro> wrote:

I’ve read up on the documentation.

Please correct the assertions below:

1. The * character has no programatic meaning, that being said, it is only a convention that all “system” cards have a * in front of the name. They could, someday, just have normal names or as in Objective-C Classes a prefix like "NS"String. They could be called SystemCardname and so on, WGCardname (from WAGN) or DKCardname (from Decko)

TRUE or FALSE

This is almost true.  There are basically two ways that star cards are addressed in the code:

1. name variants.   Whereas "email", "EMAIL", "$$email$$" and "Email?!" are all variants of the same name, "*email" is a different name.  So if you go to a url with any of those other variants, they'll go to one card, and *email will go to another.  We do this so that cards like "*type" and "*children" don't define names (email and children) that sites might want to define for themselves.
2. sets.  If you go to a card like "Mircea+*email" and you go to edit, say, the read permissions for that card, then you will see that you have an option to apply that rule to 'All "+*" cards'.  By default, wagn comes with rules that makes such cards editable only by administrators.

So you can generally change the name of such a card without major breakage, but it may change which rules apply to it.

 

2. Compound names are simply card names with a "+" in them.

This part is correct.

 

My understanding is that this is kind of a manual way to denote that the Card1+Card2 name is a card that holds Card1 and Card2 part of itself. In the end, it’s just a naming convention and the “+” can be anything like a “space” character or the word “and”.

TRUE or FALSE

This is FALSE.  There is a LOT of functionality connected to plusses that you cannot easily replace with other characters, including:

1. short references to card names in links and inclusions
2. querying in WQL (which is used in lots of menu items, like related)
3. contextual names

The sum of all this is that plus cards are how Wagn creates fields.   

[Mircea S.]

Ok. I understand better now.

1. The *cards:

The reason I’m asking is that I’ve had a little test at the office today with the WAGN system on a VM. I have this really nice lady in accounting that is open to anything new I want to try but also has a keen sense of what can be passed around as “normal". I use her as a barometer before a full blown test on the entire 6 person department. She instantly recognized “ * “ as of some compositional importance. A card named *something seemed very unintuitive to her as composition needed another term, also seeing other cards with both some+*thing really got her commenting about it. She said that in writing, under “normal” circumstances, one puts * after a word, like something*.

From what I understand in your answer, this * thing really is like a character that you use as a marker for system cards. This way they show up all neatly in one group when sorted, and are probably easier to select and narrow down that way. Her suggestion to have it at the end of the word really doesn’t help as something*+somethingelse looks just as weird. So when you think about changing this, if you would ever consider that, please think about this e-mail and consider the “System”card as a valid option towards clarity and readability. Or moving to a character that is equally distributed along the vertical axis like > or < or = or ~ or @ so that it better melds with the accompanying word @email or ~email.

While true that people don’t juggle system card every day, that * really doesn’t “say” system it just hints to “important”. I don’t know if any of this is possible as escape characters are an issue.

2. I watch again the video on Inclusion on the "How to” section http://www.youtube.com/watch?v=7-Vvima0Q5M#t=238 and together with your answer I had a lightbulb moment and understood the reasons behind the decision.

So now I have another short question:

Consider the system of + cards as it is designed today. If the “how to fix printer+difficulty” card is embedded in the “how to fix printer” card then all one has to write is {{+difficulty}}. If we set it as {{+difficulty | titled}} is it possible to the + sign to be invisible in the final document? 

Consider: Having + before a title is a little off, especially if partial or total capitalization is used like +Difficulty or +DIFFICULTY.

Be aware that I’m not saying that the + sign be removed from everywhere. A name “How to fix printer+Difficulty” is surely informative “+Difficulty” is also understandable in the code  {{+Difficulty}}. What I’m saying is that the titled Difficulty should be visible without the + sign so end users can read their merry way without wondering that the + is there for. Also having the card open or closed with the + in the title is again a little off.

The case would best be described like this. When the card is referenced to, in it’s shorthand form in code {{+Difficulty}}, the text end result should not include the + if it’s the first character.

Is this even possible, or even probable in the future? (just for the titled version, for everything?) 

Thank you for reading this. Be advised that my familiarity with the code is null so some of this might be more that a little off.

Mir

[Gerry Gleason]

On Tuesday, June 17, 2014 at 4:09 PM, Mircea S. wrote:

> Ok. I understand better now.
>
> 1. The *cards:
> The reason I’m asking is that I’ve had a little test at the office today with the WAGN system on a VM. I have this really nice lady in accounting that is open to anything new I want to try but also has a keen sense of what can be passed around as “normal". I use her as a barometer before a full blown test on the entire 6 person department. She instantly recognized “ * “ as of some compositional importance. A card named *something seemed very unintuitive to her as composition needed another term, also seeing other cards with both some+*thing really got her commenting about it. She said that in writing, under “normal” circumstances, one puts * after a word, like something*.
>
> From what I understand in your answer, this * thing really is like a character that you use as a marker for system cards. This way they show up all neatly in one group when sorted, and are probably easier to select and narrow down that way. Her suggestion to have it at the end of the word really doesn’t help as something*+somethingelse looks just as weird. So when you think about changing this, if you would ever consider that, please think about this e-mail and consider the “System”card as a valid option towards clarity and readability. Or moving to a character that is equally distributed along the vertical axis like > or < or = or ~ or @ so that it better melds with the accompanying word @email or ~email.
> While true that people don’t juggle system card every day, that * really doesn’t “say” system it just hints to “important”. I don’t know if any of this is possible as escape characters are an issue.
>

What you are really asking about here is if we could use a different convention for system cards. The answer is probably yes, but it probably isn't worth it. We do want to support variations and extensions, but this feature really isn't implemented in a way that is easy to override in extension modules. It is probably reasonable to be able to adjust which special characters are left in the name/key and which ones are stripped out as Ethan's examples for Email show. That way you could use different characters in your Wagns. Then having the system card indicator be changable wouldn't be too hard.

The only caution is that there is some value in having these things be the same across wagns to facilitate data interchange, something we want to support a lot more in the future so you can have a network of Wagns that share data back and forth.

>
> 2. I watch again the video on Inclusion on the "How to” section http://www.youtube.com/watch?v=7-Vvima0Q5M#t=238 and together with your answer I had a lightbulb moment and understood the reasons behind the decision.
> So now I have another short question:
> Consider the system of + cards as it is designed today. If the “how to fix printer+difficulty” card is embedded in the “how to fix printer” card then all one has to write is {{+difficulty}}. If we set it as {{+difficulty | titled}} is it possible to the + sign to be invisible in the final document?
>
> Consider: Having + before a title is a little off, especially if partial or total capitalization is used like +Difficulty or +DIFFICULTY.
> Be aware that I’m not saying that the + sign be removed from everywhere. A name “How to fix printer+Difficulty” is surely informative “+Difficulty” is also understandable in the code {{+Difficulty}}. What I’m saying is that the titled Difficulty should be visible without the + sign so end users can read their merry way without wondering that the + is there for. Also having the card open or closed with the + in the title is again a little off.
>
> The case would best be described like this. When the card is referenced to, in it’s shorthand form in code {{+Difficulty}}, the text end result should not include the + if it’s the first character.
> Is this even possible, or even probable in the future? (just for the titled version, for everything?)
>
> Thank you for reading this. Be advised that my familiarity with the code is null so some of this might be more that a little off.
> Mir
>

The + in titled view is a bit of an oddity. If you are pretty good with css, you can fix that with styles. Note that the '+' is in a span with the class 'joint', so you can make the first such span below a title be invisible.

We've talked about changing '+' to '/', which would make it more like file system and URI paths. '/' is actually not allowed in names now, so you don't have to worry about having those in the existing data.

Gerry

>
>
> > Pe 17 iun. 2014, la 23:13, Ethan McCutchen <et...@grasscommons.org (mailto:et...@grasscommons.org)> a scris:

> >
> >
> >
> > On Tue, Jun 17, 2014 at 1:50 PM, Mircea S. <mir...@unom.ro (mailto:mir...@unom.ro)> wrote:
> > > I’ve read up on the documentation.
> > >
> > > Please correct the assertions below:
> > >
> > > 1. The * character has no programatic meaning, that being said, it is only a convention that all “system” cards have a * in front of the name. They could, someday, just have normal names or as in Objective-C Classes a prefix like "NS"String. They could be called SystemCardname and so on, WGCardname (from WAGN) or DKCardname (from Decko)
> > > TRUE or FALSE
> >
> >
> > This is almost true. There are basically two ways that star cards are addressed in the code:
> > name variants. Whereas "email", "EMAIL", "$$email$$" and "Email?!" are all variants of the same name, "*email" is a different name. So if you go to a url with any of those other variants, they'll go to one card, and *email will go to another. We do this so that cards like "*type" and "*children" don't define names (email and children) that sites might want to define for themselves.
> > sets. If you go to a card like "Mircea+*email" and you go to edit, say, the read permissions for that card, then you will see that you have an option to apply that rule to 'All "+*" cards'. By default, wagn comes with rules that makes such cards editable only by administrators.
> >
> > So you can generally change the name of such a card without major breakage, but it may change which rules apply to it.
> >
> >
> > > 2. Compound names are simply card names with a "+" in them.
> >
> >
> > This part is correct.
> >
> > > My understanding is that this is kind of a manual way to denote that the Card1+Card2 name is a card that holds Card1 and Card2 part of itself. In the end, it’s just a naming convention and the “+” can be anything like a “space” character or the word “and”.
> > > TRUE or FALSE
> >
> >
> >
> > This is FALSE. There is a LOT of functionality connected to plusses that you cannot easily replace with other characters, including:

> > short references to card names in links (http://wagn.org/links) and inclusions (http://wagn.org/inclusions)
> > querying in WQL (http://wagn.org/WQL) (which is used in lots of menu items, like related)
> > contextual names (http://wagn.org/contextual_names)
> >
> > The sum of all this is that plus cards (http://wagn.org/plus_cards) are how Wagn creates fields.

> >
> > >
> > > Thank you for taking the time to clear up my doubts.
> > > Waiting for a response.
> > >
> > >
> > > > Pe 17 iun. 2014, la 21:05, Ethan McCutchen <et...@grasscommons.org (mailto:et...@grasscommons.org)> a scris:
> > > >
> > > > http://wagn.org/plus_cards
> > > > http://wagn.org/star_cards
> > > >
> > > >
> > > > On Tue, Jun 17, 2014 at 11:24 AM, Mircea S. <mir...@unom.ro (mailto:mir...@unom.ro)> wrote:
> > > > > What about the *character? What does it do?
> > > > >
> > > > >
> > > > >
> > > > > Pe 17 iun. 2014, la 19:53, Gerry Gleason <ger...@inbox.com (mailto:ger...@inbox.com)> a scris:
> > > > >
> > > > > > *right
> > > > >
> > > > > --
> > > > > You received this message because you are subscribed to the Google Groups "Wagn Developers" group.

> > > > > To unsubscribe from this group and stop receiving emails from it, send an email to wagn-dev+u...@googlegroups.com (mailto:wagn-dev%2Bunsu...@googlegroups.com).
> > > > > To post to this group, send email to wagn...@googlegroups.com (mailto:wagn...@googlegroups.com).

> > > > > Visit this group at http://groups.google.com/group/wagn-dev.
> > > > > For more options, visit https://groups.google.com/d/optout.
> > > >
> > > >
> > > >
> > > >
> > > > --
> > > > Ethan McCutchen

> > > > One of the Wagneers, Wagn.org (http://wagn.org/)

> > > >
> > > > Wagn. How pioneers roll.
> > > >
> > > > s: ethan.mccutchen
> > > > t: @intogreater
> > > >
> > > >
> > > >
> > > > --
> > > > You received this message because you are subscribed to the Google Groups "Wagn Developers" group.

> > > > To unsubscribe from this group and stop receiving emails from it, send an email to wagn-dev+u...@googlegroups.com (mailto:wagn-dev+u...@googlegroups.com).
> > > > To post to this group, send email to wagn...@googlegroups.com (mailto:wagn...@googlegroups.com).

> > > > Visit this group at http://groups.google.com/group/wagn-dev.
> > > > For more options, visit https://groups.google.com/d/optout.
> > >
> > >
> > >
> > > --
> > > You received this message because you are subscribed to the Google Groups "Wagn Developers" group.

> > > To unsubscribe from this group and stop receiving emails from it, send an email to wagn-dev+u...@googlegroups.com (mailto:wagn-dev+u...@googlegroups.com).
> > > To post to this group, send email to wagn...@googlegroups.com (mailto:wagn...@googlegroups.com).

> > > Visit this group at http://groups.google.com/group/wagn-dev.
> > > For more options, visit https://groups.google.com/d/optout.
> >
> >
> >
> >
> > --
> > Ethan McCutchen

> > One of the Wagneers, Wagn.org (http://wagn.org/)

> >
> > Wagn. How pioneers roll.
> >
> > s: ethan.mccutchen
> > t: @intogreater
> >
> >
> >
> > --
> > You received this message because you are subscribed to the Google Groups "Wagn Developers" group.

> > To unsubscribe from this group and stop receiving emails from it, send an email to wagn-dev+u...@googlegroups.com (mailto:wagn-dev+u...@googlegroups.com).
> > To post to this group, send email to wagn...@googlegroups.com (mailto:wagn...@googlegroups.com).

> > Visit this group at http://groups.google.com/group/wagn-dev.
> > For more options, visit https://groups.google.com/d/optout.
>
> --
> You received this message because you are subscribed to the Google Groups "Wagn Developers" group.

> To unsubscribe from this group and stop receiving emails from it, send an email to wagn-dev+u...@googlegroups.com (mailto:wagn-dev+u...@googlegroups.com).
> To post to this group, send email to wagn...@googlegroups.com (mailto:wagn...@googlegroups.com).

> Visit this group at http://groups.google.com/group/wagn-dev.
> For more options, visit https://groups.google.com/d/optout.

____________________________________________________________
FREE ONLINE PHOTOSHARING - Share your photos online with your friends and family!
Visit http://www.inbox.com/photosharing to find out more!

[Mircea S.]

Great! I’ll get right on it.