Copy a card
Moderators: FourthWorld, heatherlaine, Klaus, kevinmiller
-
- Posts: 3
- Joined: Mon Mar 04, 2013 10:26 pm
Copy a card
I am building my first App, and have created a new card that will have the same layout as 90% of the main stack, can I use that as template, copy it, rename it, make the small changes (image,description, price etc)
Re: Copy a card
Hi.
Check out the "clone" command in the dictionary. And you must learn a little about groups and their ability to have a "backGround" behavior. This may or may not be relevant to your current needs, as I am not sure how your copies are to be made, or what is to be done with the objects derived from the parent card. But the good news is that you can do whatever you need to. LC has all the tools and flexibility you could ask for.
Write back if you get stuck.
Craig Newman
Check out the "clone" command in the dictionary. And you must learn a little about groups and their ability to have a "backGround" behavior. This may or may not be relevant to your current needs, as I am not sure how your copies are to be made, or what is to be done with the objects derived from the parent card. But the good news is that you can do whatever you need to. LC has all the tools and flexibility you could ask for.
Write back if you get stuck.
Craig Newman
-
- Posts: 3
- Joined: Mon Mar 04, 2013 10:26 pm
Re: Copy a card
Thank you, once I copy a card, all I need to do is change image, price, model, then its just the hyperlinks to the next card, or back, I will have a look at the clone command, its a very simple app, but lots of cards
Re: Copy a card
Hmmm.
You are aware that a field (or several) that is grouped, and has its "backgroundBehavior" set to true, will automatically appear on any new cards that you make. Correct? And that the information in those fields is, normally, unique to that card. So that you don't have to worry about lots of cards, as they all have the same "background" with respect to that particular group, but each has its own data, unique to its card.
The names of the cards can change, but the name of the group will be the same. The cards "share" the group. This is one of the most important features of groups.
Likewise with your navigation arrows, or whatever. Group and set the background behavior. They will then appear on each new card, and if a script says:
"go next card"
you will have that feature everywhere.
Do you have experience with this? For the app you are making, this seems like an essential tool to master. As usual, write back...
Craig Newman
You are aware that a field (or several) that is grouped, and has its "backgroundBehavior" set to true, will automatically appear on any new cards that you make. Correct? And that the information in those fields is, normally, unique to that card. So that you don't have to worry about lots of cards, as they all have the same "background" with respect to that particular group, but each has its own data, unique to its card.
The names of the cards can change, but the name of the group will be the same. The cards "share" the group. This is one of the most important features of groups.
Likewise with your navigation arrows, or whatever. Group and set the background behavior. They will then appear on each new card, and if a script says:
"go next card"
you will have that feature everywhere.
Do you have experience with this? For the app you are making, this seems like an essential tool to master. As usual, write back...
Craig Newman