Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/jerdew5/orbworks.com/forum/includes/bbcode.php on line 112

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/jerdew5/orbworks.com/forum/includes/bbcode.php on line 112

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/jerdew5/orbworks.com/forum/includes/bbcode.php on line 112

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /home/jerdew5/orbworks.com/forum/includes/bbcode.php on line 112
[phpBB Debug] PHP Notice: in file /includes/functions.php on line 3368: Cannot modify header information - headers already sent by (output started at /includes/bbcode.php:112)
[phpBB Debug] PHP Notice: in file /includes/functions.php on line 3370: Cannot modify header information - headers already sent by (output started at /includes/bbcode.php:112)
[phpBB Debug] PHP Notice: in file /includes/functions.php on line 3371: Cannot modify header information - headers already sent by (output started at /includes/bbcode.php:112)
[phpBB Debug] PHP Notice: in file /includes/functions.php on line 3372: Cannot modify header information - headers already sent by (output started at /includes/bbcode.php:112)
OrbWorks Community Forum • View topic - Questions about .ocp vs. .oc samples
Page 1 of 1

PostPosted: Sun Sep 03, 2006 2:53 pm
by steveK
Hi All. I'm a newbie and have been trying to learn by disecting some of the sample projects included with the PocketC Architect download. It seems the .ocp files are Architect files whereas the .oc files are by OrbForms. I've registered Architect and am experimenting with the demo version of OrbForms. Right now I'm mostly just trying to learn what the actual OrbC code looks like and OrbForms doesn't seem to lend itself to that, as much of the code is assembled 'behind-the-scenes.' So anyway, I've been disecting the .ocp files in the sample projects. I'll use TipCalc as an example... The .ocp file *looks* like it contains the code for the entire app, but at the bottom of the file it refers the compiler to the two .oc files (#include "SimpleCalc.oc"
#include "mainform.oc") and the app doesn't seem to work correctly without them ... So the question is; is any of this sample code "stand alone" PocketC Architect code? Second question; given the above learning scheme I've described, are there any resources that you (Dewey or other forum members) would recommend? THanks! -steveK:)

PostPosted: Fri Sep 08, 2006 1:52 am
by dewey
The file extensions are only a convention - the compiler doesn't really care. The convention is:

.ocp - an Architect project file (the main file for you app that usually includes the UI definition). .ocp stands for "OrbC Project".

.oc - an OrbC source file used by either Architect or OrbForms.

.orb - an OrbForms project file. This file is pretty much the OrbForms equivalent of .ocp. This file is generated by the IDE.

PostPosted: Sat Sep 09, 2006 12:23 am
by steveK
Ah yes. Thanks. I actually did read that in the manual, but it didn't 'click.' I see now that I can right-click on either .oc or .ocp and choose to open either with Archie. At this point in the learning process it does seem disconjointed having the handlers separated from the forms. Conventional cause-effect wisdom dictates that there should be
item 1 specs
item 1 handler
item 2 specs
item 2 handler
item 3 specs
item 3 handler
of course I realize that in reality there are technical reasons that this can't be done.

Anyway, thanks again for the reply.

Another question, Is there any chance of an OrbForms discounted price for folks who have JUST registered PocketC Architect???

PostPosted: Wed Sep 13, 2006 3:19 am
by dewey
Contact me (dewey@orbworks) offline