yui in svn

[unomi]

Planning to maintain a custom YUI ? :p
Didn't someone offer to help with setting up YUI Loader for automatic
dependency resolution?
This way we wouldn't have to have YUI in the SVN, *and* most likely we
could define which version of YUI to use depending on branch.
Perhaps even an option to dl the compiled/minimized YUI dependencies.

Even if not people probably won't balk at having to come up with a
path to YUI if they are downloading from SVN? I can understand YUI
being included with the zip though.

or an intermediary step on your site that downloads from svn, bundles
it with /lib/ and sends it off as zip.

Sorry.

[Mingfai]

IMHO, the biggest problem is, after people checkout from svn, they have to manually do some works to get the example work. it's quite undesirable and it discourage people to try.

regards,
mingfai

[unomi]

I see what you are saying, but svn is normally for YMMV source anyway,
I would imagine that for most people that are able to configure and
use a svn client, creating an alias/softlink; search and replace or
copying the yui library to where its expected to be found isn't all
that difficult.
I agree that more people should try it because inputex really is quite
lovely, but then it would be better to have a 'daily build' tarball
that could then have the subset of yui libs it is dependant on
present.

Don't worry I am just bitching because now my inputex svn folder is 68
mb on disk (23.3 in reality) and I honestly don't see why there
wouldnt just be a link to dl yui seperate and where to put it in the
unlikely(?) scenario that people have not used YUI but do want to use
inputex.

Obviously I just need to chill out and get some food, but I am stuck
at work and you are all going to pay. =)

On Oct 2, 2:55 pm, Mingfai <mingfai...@gmail.com> wrote:
> IMHO, the biggest problem is, after people checkout from svn, they have to
> manually do some works to get the example work. it's quite undesirable and
> it discourage people to try.
>
> regards,
> mingfai
>