Hi,
why can't we have, for example, a folder structure that mirrors the
qooxdoo directory in each contributed folder? Then each author would only
have to include files there which add to or replace existing files in the
main source, and the process of adding them to the final build can be
automate
I don't know what's so wrong with the solution. I'm really sure you
don't want the same layout in the contributed folder as in the qooxdoo
directories itself. For example you normally don't need each
contribution for your application. Also some contributions are more
stable than others. Some of
Marco LOMBARDO schrieb:
Kent,
a small README, or sh/bat script that moves files around when
contribution is not checkout&play will cost 1 minute to you and save 1
hour to newbies... like me.
A README is included in the most examples for some weeks now. Especially
Kent's stuff. I would really l
Christian!
Thanks for the attention! It could help people saving time. It also
would increase the interest to keep the contributed up-to-date if you do
not need to do some extra work to put it there.
> Wouldn't it make more sense if the qooxdoo developers prescribed a
> directory layout for the
Mar,
Ok! I will do that during the weekend.
Kent
On Thu, 2006-04-13 at 11:31 +0200, Marco LOMBARDO wrote:
> Kent,
> a small README, or sh/bat script that moves files around when
> contribution is not checkout&play will cost 1 minute to you and save 1
> hour to newbies... like me.
>
> Bye.
> Mar
Wouldn't it make more sense if the qooxdoo developers prescribed a
directory layout for the contributed folder which mirrored the qooxdoo
directory, and if there would be a build_with_contributed.sh script
which then makes a build version with all contributed widgets? Then
everybody who works o
Kent,
a small README, or sh/bat script that moves files around when
contribution is not checkout&play will cost 1 minute to you and save 1
hour to newbies... like me.
Bye.
Mar
On 4/13/06, Simon Bull <[EMAIL PROTECTED]> wrote:
> Marco LOMBARDO gmail.com> writes:
>
> > however you need also to cop
Marco LOMBARDO gmail.com> writes:
> however you need also to copy gif in
> source/themes/widgets/windows/arrows/. Now is working.
> A newbie like me think: why should I put images in
> widgets/windows/arrows/ if source code contains widgets/arrows/ ?
Thanks for the pointer Marco :)
I now have t
Hej Mar!
I agree completely on what you say. I have discussed the problem of
access, but there is so far no interest from Sebastian et al to change
it. Today it is too much work for us here to have three different
versions. Therefore we have chosen to have our own version. Sorry about
the inconven
Hi Kent,
you are very productive as contributor. However many of your example
do not work directly after checkout. I patched the QxExtend.diff
however you need also to copy gif in
source/themes/widgets/windows/arrows/. Now is working.
A newbie like me think: why should I put images in
widgets/windo
1. use QxExtent.diff
2. do tools/make.sh
before use
Kent
On Wed, 2006-04-05 at 07:31 +, Simon Bull wrote:
> > I upload the whole directory of my machine.
> > Try it out!
> >
> > Kent
>
>
> Thanks Kent,
>
> I'll checkout and try it tonight :)
>
> Simon
>
>
>
>
>
> --
> I upload the whole directory of my machine.
> Try it out!
>
> Kent
Thanks Kent,
I'll checkout and try it tonight :)
Simon
---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into we
12 matches
Mail list logo
