Raymond,
Yeah, I would love to try to come up with a reliable way to add the
semi-colons in. I'm sure I missed some in the DynAPI code. I made a
bunch of changes, but I'm sure I didn't catch them all.
I'll update the revisions.html file with my changes, and I'll also
add to the tipst
Really nice! Now we can use compressed DynAPI code.
Thanks a lot Jesse.
You can docoument you changes inside the
docs/docs/revisions.html file
I think we should also work together on a function
that will add missing semi-colons to the compressed
files. From time to time we might miss out on a
se
Finally! I finally got some free time and CVS cooperated with me, and I
got to check in the java.compressor stuff in bin. I also checked in the
added semi-colon changes I made.
This is my first time checking stuff in, so please let me know if I
screwed things up.
Besides the java.compressor
Hi,
Any word on the java.compressor as yet? Even the
command line version would be ok.
Sorry, but it's just that I'm so excited about this
compress and merge utility. Can't wait see it in
action.
--
Raymond Irving
--- Jesse Vitrone <[EMAIL PROTECTED]> wrote:
> OK, I've got 2 things to add, I'v
I'd love to add something like that, but does anyone know all the rules
for when to add? If we could come up with a good algorithm for that,
I'd be up for adding it to the code.
Jesse
Raymond Irving wrote:
One other question... Does the compressor checks for
missing semi-colons (;)? It w
One other question... Does the compressor checks for
missing semi-colons (;)? It would be very good if it
does and had the ability to insert the missing
semi-colon.
--
Raymond Irving
--- Jesse Vitrone <[EMAIL PROTECTED]> wrote:
> OK, I merged with CVS the other day with no
> problems, I'll mak
OK, I merged with CVS the other day with no problems, I'll make sure I
do it again before committal.
My source forge user name is jessev.
Jesse
Raymond Irving wrote:
CVS is the better of the two options. Please make sure
that you first have the lastest version in CVS before
merging your change
CVS is the better of the two options. Please make sure
that you first have the lastest version in CVS before
merging your changes. As for documentation on change
please use the docs/docs/revision.html file
--
Raymond Irving
--- Jesse Vitrone <[EMAIL PROTECTED]> wrote:
I don't mind just committing the code with CVS, it's easier than doing
the whole patch deal. As long as you don't mind me checking in the
stuff before someone looks it over. Do you prefer me using the patch
method or just commiting it with CVS?
I can always make a list of the changes I made.
Well you could:
1) zip up the files and use the patch on sourceforge
to upload your change. Then on of the devs with write
access can then upload your changes to CVS. To submit
a patch go to the followinf URL:
http://sourceforge.net/tracker/?group_id=5757&atid=305757
2) Sign-up with SourceForg
OK, I've got 2 things to add, I've got the java.compressor code, and
some updated js files, with semi-colons added and stuff.
The js files should be added as a patch?
Do I need to do anything more than have a regular source forge account?
Should I be a member of the project?
It looks like I ca
11 matches
Mail list logo
