Beat,
Thanks again for your response. As I've started getting into CB in more detail, and reading several forum posts, I have realized the importance of being specific.
I am using another plug-in that requires J! 1.5 NATIVE mode. Yet, it seems that most of those posting to this CB forum ASSUME that we are running in LEGACY mode and that LEGACY is a mode that is acceptable.
I understand that it can take time to do the development for this upgrade, BUT, I need to have some basic functionality completed by the end of next week, so I don't have time to waste exploring options that will only lead to a dead end in this short term.
Here's my ADDITIONAL questions:
beat wrote:
2) Yes, RC2 is backwards compatible to 1.0 API. There will be a new API doc explaining CB 1.2 stable after we release CB 1.2 stable and plugins that are in the works.
You say it is compatible - is this true only in Legacy mode or also in Native mode?
If it is true only in Legacy mode, any chance I could join your team as a documentator, and provide updates to a document already in progress as I work through? Often times having someone who is new to the environment can make a document really robust in that they will doc stuff that seems obvious to those who have been around for a while.
5) Question: Is there any way for the workflow process to trigger different actions, ie. an administrator approval is required, based on whether a checkbox is checked or not?
Answer: not in CB, but with a plugin yes. The upcoming paid subscriptions plugin does that based on plan chosen (also for free plans).
Again, given my short deadline, any chance I could get a sneak preview of the code, knowing it may contain bugs, so that I can have a base to work on?
This short timeframe development is volunteer work for a local church.
I'm about to abandon CB altogether for now, because of my need for Native 1.5, and the short timeframe.
I'm more than willing to give back to the community. Please help me and I will help the community!!!
Thanks,
WebMuse G