should we put the yui libraries in svn?

[mingfai]

pro:
1. anyone could checkout the code and run the example immediately
2. we could use / keep track of using different version of YUI.
- recently, i upgraded to YUI 2.6.0 PR1 but the editor won't work
without the 2.5.2 button. it's good to co-exist multiple YUI version
- could expire using YUI3

con:
1. make it harder to distribute zip (?)
2. we can't upgrade YUI without changing the code
- i think it's not a good practice anyway. even minor upgrade may
have a chance to break the code.

for example:
/lib/yui-2.5.2/build/
/lib/yui-2.6.0pr1/build/
(obviously, we keep the build directory only without the other YUI
stuff)

for zip release, we just delete all /lib/*/build.

regards,
mingfai

[unomi]

I think it would make sense to just have branches for each version of
YUI you want to support,
perhaps a bit of checking on YUI version aswell, warning that some
things might not work with this particular branch on this particular
YUI version (recommended YUI version for this branch).
I think many people who use YUI resort to editing some aspects of the
YUI code to get around 'undesirable behaviour'.

[neyric]

good idea !
It is frustrating to checkout the SVN and not being able to run the
examples...

I also agree with unomi that we shouldn't put multiple versions of YUI
in the same branch.
Let's keep the trunk in sync with the latest YUI release (currently
2.5.2, but 2.6.0 should come real soon
http://www.nabble.com/YUI-2.6.0-preview-release-1-td19094498.html),
and create branches for future YUI versions.

[unomi]

*cough* No. :)
But I see that you did, looks like I am about to download the whole
uncompressed source for YUI at less than 5kb per sec. *ALL* of YUI?
how about just the actual dependencies?

Anyway I was itching to see Neyrics kind patch to allow me to set
disabled at start, and now i have to wait :| =)

On Oct 1, 2:31 pm, neyric <eric.abo...@gmail.com> wrote:
> good idea !
> It is frustrating to checkout the SVN and not being able to run the
> examples...
>
> I also agree with unomi that we shouldn't put multiple versions of YUI
> in the same branch.
> Let's keep the trunk in sync with the latest YUI release (currently

> 2.5.2, but 2.6.0 should come real soonhttp://www.nabble.com/YUI-2.6.0-preview-release-1-td19094498.html),

[Mingfai]

i think it's ok to put all to YUI. it's easily if we need additional library. (e.g. for making demo page) and it's much easier to "maintain"

but there is an issue... we need to upgrade to 2.6.0 now. :-)

for my app, there is no compatibility issue. but we need to change some include code from xxx-beta-min.js to xxx-min.js as some components are graduated.

regards,
mingfai

[unomi]

erm, also, why not just link to the online version of YUI?
if people want to download it to try, chances are pretty good they
have internet connections.

On Oct 2, 2:51 pm, Mingfai <mingfai...@gmail.com> wrote:
> i think it's ok to put all to YUI. it's easily if we need additional
> library. (e.g. for making demo page) and it's much easier to "maintain"
>
> but there is an issue... we need to upgrade to 2.6.0 now. :-)
>
> for my app, there is no compatibility issue. but we need to change some
> include code from xxx-beta-min.js to xxx-min.js as some components are
> graduated.
>
> regards,
> mingfai
>