Copy resources from source to build

View: New views
6 Messages — Rating Filter:   Alert me  

Copy resources from source to build

by panyasan :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message


Hello,

I have a file in the script folder that I need to be copied into the built
package. I have tried this in my config.json

...

  "copy-files" :
  {
    "files"     : [ "script/rpcconsole.testData.js" ]
  },  

...

However, the file is not copied into build/script. What am I doing wrong?

Thanks,

C.
--
View this message in context: http://n2.nabble.com/Copy-resources-from-source-to-build-tp3902667p3902667.html
Sent from the qooxdoo mailing list archive at Nabble.com.

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@...
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

Re: Copy resources from source to build

by thron7-2 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message



panyasan wrote:

> Hello,
>
> I have a file in the script folder that I need to be copied into the built
> package. I have tried this in my config.json
>
> ...
>
>   "copy-files" :
>   {
>     "files"     : [ "script/rpcconsole.testData.js" ]
>   },  
>
> ...
>
> However, the file is not copied into build/script. What am I doing wrong?
>  

This is not enough context you are providing. It all depends on the job
that contains the "copy-files" trigger. You should put this trigger into
the "build-files" job. There it will be picked up correctly.

T.

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@...
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

Re: Copy resources from source to build

by panyasan :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message


Ok, this worked, thanks. As usual, there is tons of useful information on the
website, but it is sometimes hard to figure out something basic as this
because the generator configuration is a very complex matter that would
deserve a whole series of tutorials. As I said, the Book of Qooxdoo still
has to be written ;-)

C.


thron7-2 wrote:

>
>
>
> panyasan wrote:
>> Hello,
>>
>> I have a file in the script folder that I need to be copied into the
>> built
>> package. I have tried this in my config.json
>>
>> ...
>>
>>   "copy-files" :
>>   {
>>     "files"     : [ "script/rpcconsole.testData.js" ]
>>   },  
>>
>> ...
>>
>> However, the file is not copied into build/script. What am I doing wrong?
>>  
>
> This is not enough context you are providing. It all depends on the job
> that contains the "copy-files" trigger. You should put this trigger into
> the "build-files" job. There it will be picked up correctly.
>
> T.
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> http://p.sf.net/sfu/devconference
> _______________________________________________
> qooxdoo-devel mailing list
> qooxdoo-devel@...
> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>
>

--
View this message in context: http://n2.nabble.com/Copy-resources-from-source-to-build-tp3902667p3908758.html
Sent from the qooxdoo mailing list archive at Nabble.com.

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@...
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

Re: Copy resources from source to build

by thron7-2 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message



panyasan wrote:
Ok, this worked, thanks. As usual, there is tons of useful information on the
website, but it is sometimes hard to figure out something basic as this
  
Ok, in that particular case, where did you get lost? The generator configuration overview clearly lines out that config keys have to be in the context of a job [1]. It says

   "The job names job1, ..., jobN are freely chooseable but must form a valid key."

and later

   "The value of each job is a map where the keys are not freely chooseable, but are predefined."

and then continues to present an overview of the valid keys. Then there is an entire section dedicated to job shadowing, which I agree may take some browsing to find (but as there are only 4 pages dealing with generator configuration that shouldn't be so hard)[2]. But every skeleton config comes with a minimal example of overriding an existing job [3]:

    "build-script" :
        {
          "compile-dist" :
          {
            "code" :
            {
              "format" : false
            }
          }
        }


So, along that way, where did you miss additional aid to get you further?

T.

[1] http://qooxdoo.org/documentation/0.8/generator_config
[2] http://qooxdoo.org/documentation/0.8/generator_config_articles#job_shadowing_and_partial_overriding
[3] http://qooxdoo.svn.sourceforge.net/viewvc/qooxdoo/trunk/qooxdoo/component/skeleton/gui/config.tmpl.json?revision=20525&view=markup

because the generator configuration is a very complex matter that would
deserve a whole series of tutorials. As I said, the Book of Qooxdoo still
has to be written ;-)

C. 


thron7-2 wrote:
  

panyasan wrote:
    
Hello,

I have a file in the script folder that I need to be copied into the
built
package. I have tried this in my config.json

...

  "copy-files" :
  {
    "files"     : [ "script/rpcconsole.testData.js" ]
  },  

...

However, the file is not copied into build/script. What am I doing wrong?
  
      
This is not enough context you are providing. It all depends on the job 
that contains the "copy-files" trigger. You should put this trigger into 
the "build-files" job. There it will be picked up correctly.

T.

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@...
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel


    

  

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@...
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

Re: Copy resources from source to build

by panyasan :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message


Hi Thomas,

as you show, the information is all there and very detailed. I am not saying
that you don't provide excellent documentation! We talked about that before
- I tried the "search, don't sort" approach and came across the config key,
which then I used without a job context because this would have required
reading the whole manual on the generator. Which I should have of course.
The way a typical user thinks, I suppose, is outcome-oriented: "I want to
copy the files from source to build", without knowing what job this requires
and what keys to use - and without the patience to read up on the whole
generator documentation. So maybe there should be a collection of "How-to's"
which only cover the most common cases - some sort of FAQ for the generator.

Cheers,

Christian


thron7-2 wrote:

>
>
>
> panyasan wrote:
>> Ok, this worked, thanks. As usual, there is tons of useful information on
>> the
>> website, but it is sometimes hard to figure out something basic as this
>>  
> Ok, in that particular case, where did you get lost? The generator
> configuration overview clearly lines out that config keys have to be in
> the context of a job [1]. It says
>
>    "The job names job1, ..., jobN are freely chooseable but must form a
> valid key."
>
> and later
>
>    "The value of each job is a map where the keys are not freely
> chooseable, but are predefined."
>
> and then continues to present an overview of the valid keys. Then there
> is an entire section dedicated to job shadowing, which I agree may take
> some browsing to find (but as there are only 4 pages dealing with
> generator configuration that shouldn't be so hard)[2]. But every
> skeleton config comes with a minimal example of overriding an existing
> job [3]:
>
>     "build-script" :
>         {
>           "compile-dist" :
>           {
>             "code" :
>             {
>               "format" : false
>             }
>           }
>         }
>
>
> So, along that way, where did you miss additional aid to get you further?
>
> T.
>
> [1] http://qooxdoo.org/documentation/0.8/generator_config
> [2]
> http://qooxdoo.org/documentation/0.8/generator_config_articles#job_shadowing_and_partial_overriding
> [3]
> http://qooxdoo.svn.sourceforge.net/viewvc/qooxdoo/trunk/qooxdoo/component/skeleton/gui/config.tmpl.json?revision=20525&view=markup
>
>> because the generator configuration is a very complex matter that would
>> deserve a whole series of tutorials. As I said, the Book of Qooxdoo still
>> has to be written ;-)
>>
>> C.
>>
>>
>> thron7-2 wrote:
>>  
>>>
>>> panyasan wrote:
>>>    
>>>> Hello,
>>>>
>>>> I have a file in the script folder that I need to be copied into the
>>>> built
>>>> package. I have tried this in my config.json
>>>>
>>>> ...
>>>>
>>>>   "copy-files" :
>>>>   {
>>>>     "files"     : [ "script/rpcconsole.testData.js" ]
>>>>   },  
>>>>
>>>> ...
>>>>
>>>> However, the file is not copied into build/script. What am I doing
>>>> wrong?
>>>>  
>>>>      
>>> This is not enough context you are providing. It all depends on the job
>>> that contains the "copy-files" trigger. You should put this trigger into
>>> the "build-files" job. There it will be picked up correctly.
>>>
>>> T.
>>>
>>> ------------------------------------------------------------------------------
>>> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
>>> is the only developer event you need to attend this year. Jumpstart your
>>> developing skills, take BlackBerry mobile applications to market and
>>> stay
>>> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
>>> http://p.sf.net/sfu/devconference
>>> _______________________________________________
>>> qooxdoo-devel mailing list
>>> qooxdoo-devel@...
>>> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>>>
>>>
>>>    
>>
>>  
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay
> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> http://p.sf.net/sfu/devconference
> _______________________________________________
> qooxdoo-devel mailing list
> qooxdoo-devel@...
> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>
>

--
View this message in context: http://n2.nabble.com/Copy-resources-from-source-to-build-tp3902667p3910763.html
Sent from the qooxdoo mailing list archive at Nabble.com.

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@...
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

Re: Copy resources from source to build

by Gene Amtower :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Team,

Another thought that came to my mind is wishing I could see a graphical representation of the config sections (in both the application and framework) that a typical "source" or "build" job ends up examining and evaluating.  It all struck me as pretty confusing when I read through that portion of the manual in the beginning, and I haven't gone back there since to avoid the frustration and confusion. 

FWIW, the minimal example in the skeleton job didn't help clarify these linkages very well for me. 

Without seeing it all at a high level, I struggled to see exactly how the tool traverses the config files.  Pictures can say very quickly what 4 pages of documentation might take, and do a better job of explaining it to a novice.  Fortunately, my simple use of Qooxdoo to-date hasn't required me to really mess with the config files, but I'm betting I'm going to have the opportunity (or misery) of dealing with it soon.

Thanks,

  Gene

On Thu, 2009-10-29 at 02:32 -0700, panyasan wrote:
Hi Thomas,

as you show, the information is all there and very detailed. I am not saying
that you don't provide excellent documentation! We talked about that before
- I tried the "search, don't sort" approach and came across the config key,
which then I used without a job context because this would have required
reading the whole manual on the generator. Which I should have of course.
The way a typical user thinks, I suppose, is outcome-oriented: "I want to
copy the files from source to build", without knowing what job this requires
and what keys to use - and without the patience to read up on the whole
generator documentation. So maybe there should be a collection of "How-to's"
which only cover the most common cases - some sort of FAQ for the generator. 

Cheers,

Christian 


thron7-2 wrote:
> 
> 
> 
> panyasan wrote:
>> Ok, this worked, thanks. As usual, there is tons of useful information on
>> the
>> website, but it is sometimes hard to figure out something basic as this
>>   
> Ok, in that particular case, where did you get lost? The generator 
> configuration overview clearly lines out that config keys have to be in 
> the context of a job [1]. It says
> 
>    "The job names job1, ..., jobN are freely chooseable but must form a 
> valid key."
> 
> and later
> 
>    "The value of each job is a map where the keys are not freely 
> chooseable, but are predefined."
> 
> and then continues to present an overview of the valid keys. Then there 
> is an entire section dedicated to job shadowing, which I agree may take 
> some browsing to find (but as there are only 4 pages dealing with 
> generator configuration that shouldn't be so hard)[2]. But every 
> skeleton config comes with a minimal example of overriding an existing 
> job [3]:
> 
>     "build-script" :
>         {
>           "compile-dist" :
>           {
>             "code" :
>             {
>               "format" : false
>             }
>           }
>         }
> 
> 
> So, along that way, where did you miss additional aid to get you further?
> 
> T.
> 
> [1] http://qooxdoo.org/documentation/0.8/generator_config
> [2] 
> http://qooxdoo.org/documentation/0.8/generator_config_articles#job_shadowing_and_partial_overriding
> [3] 
> http://qooxdoo.svn.sourceforge.net/viewvc/qooxdoo/trunk/qooxdoo/component/skeleton/gui/config.tmpl.json?revision=20525&view=markup
> 
>> because the generator configuration is a very complex matter that would
>> deserve a whole series of tutorials. As I said, the Book of Qooxdoo still
>> has to be written ;-)
>>
>> C. 
>>
>>
>> thron7-2 wrote:
>>   
>>>
>>> panyasan wrote:
>>>     
>>>> Hello,
>>>>
>>>> I have a file in the script folder that I need to be copied into the
>>>> built
>>>> package. I have tried this in my config.json
>>>>
>>>> ...
>>>>
>>>>   "copy-files" :
>>>>   {
>>>>     "files"     : [ "script/rpcconsole.testData.js" ]
>>>>   },  
>>>>
>>>> ...
>>>>
>>>> However, the file is not copied into build/script. What am I doing
>>>> wrong?
>>>>   
>>>>       
>>> This is not enough context you are providing. It all depends on the job 
>>> that contains the "copy-files" trigger. You should put this trigger into 
>>> the "build-files" job. There it will be picked up correctly.
>>>
>>> T.
>>>
>>> ------------------------------------------------------------------------------
>>> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
>>> is the only developer event you need to attend this year. Jumpstart your
>>> developing skills, take BlackBerry mobile applications to market and
>>> stay 
>>> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
>>> http://p.sf.net/sfu/devconference
>>> _______________________________________________
>>> qooxdoo-devel mailing list
>>> qooxdoo-devel@...
>>> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>>>
>>>
>>>     
>>
>>   
> 
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry(R) Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay 
> ahead of the curve. Join us from November 9 - 12, 2009. Register now!
> http://p.sf.net/sfu/devconference
> _______________________________________________
> qooxdoo-devel mailing list
> qooxdoo-devel@...
> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
> 
> 


------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@...
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel