I get the same result when I use make build and make source. The 'custom'
file only contains script includes for each file, not the file itself. I
guess this is why I thought I was missing something. I expected that make
source would give me the desired result but it didn't. Could this be a side
effect from the fact that I didn't start from ground zero, I broke apart a
large file. My 'application' file does not have any includes in it, are they
needed? I have not worked with a make system before (I come from the Windows
GUI world where I just press a button and an EXE pops out). I might be
missing some commands in the main application file letting the make system
know what's going on. Perhaps I should Google the make system to learn it's
idiosyncrasies.
Any more help would be appreciated.
Thanks,
Jim
On 2/26/07, [EMAIL PROTECTED] <
[EMAIL PROTECTED]> wrote:
"Jim Hunter" <[EMAIL PROTECTED]> writes:
> I have been using .6.2 for some time now and with all the new
functionality
> being put into the new versions I thought that I would take a look at
them
> to see what things I will have to change. The first thing I noticed is
that
> I had to break my single JS file into individual class files. At first I
> didn't like this but I think in the long run it will be better for me so
I
> moved on. Then I tried to use the new skeleton method of creating my
builds.
> I was able to get everything to build with no errors so I thought I was
on
> my way to success. But then I noticed that no matter how I tried to
build I
> always got a custom.js file that was full of script includes and my
files
> were never brought together into a single file. I have read everything I
can
> find and I don't see any mention of how to build my application into a
> single (or two+ if you include the qooxdoo files that are created) file?
> Leaving my files as individual files is not an acceptable result. What
am I
> missing? What do I need to do to create a single file out of my
individual
> class files?
The distinction is between "make source" and "make build" (assuming you're
using the Makefile system). The former generates a custom.js (or whatever
name you choose to give it) that just brings in all of the individual
files by
adding a copious number of <script src="..."> tags. The latter creates a
custom.js file that itself includes all of the necessary classes, avoiding
the
need to add any <script> tags to bring in additional files.
If you're not using the Makefile system, then you'll want to look here:
http://qooxdoo.org/documentation/user_manual/custom_builds
Unless that page has been updated, I believe there are some differences
between what was documented and what exists in svn at the current
time. You
may need to ask some questions of Sebastian and Fabian, but at least that
should explain what you need to know.
Whether documented or now, there is an option (as used by the Makefile) to
include only those classes from the framework and your skeleton-derived
source
that are actually used.
Cheers,
Derrell
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share
your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
