Page 1 of 2 12 LastLast
Results 1 to 10 of 13

Thread: 'ext-gen' does not work with multi-app workspaces

  1. #1
    Sencha Premium User
    Join Date
    Jun 2015
    Posts
    4

    Exclamation 'ext-gen' does not work with multi-app workspaces

    How can I make the new "Open Tooling" work with multi-app workspaces?

    Assume that I run the following commands to create a new workspace and one application in it:
    Code:
    sencha generate workspace TestWorkspace
    cd TestWorkspace
    sencha -sdk /path/to/ext-6.6.0 generate app SenchaCmdApp SenchaCmdApp
    If I then run "ext-gen upgrade" in the workspace folder, I get the error
    Code:
    no such file or directory, open 'app.json'
    If I instead run "ext-gen upgrade" in the SenchaCmdApp application folder, I get the error
    Code:
    no such file or directory, lstat 'workspace.json'
    From these error codes and from looking at the code for "ext-gen upgrade", it appears that "ext-gen upgrade" is not designed to handle multi-app workspaces.

    I also tried to manually do the steps "ext-gen upgrade" was not able to perform and then run
    Code:
    npm install
    npm start
    Which results in
    Code:
    Error: ENOENT: no such file or directory, scandir './packages'
    Have I missed some documentation for using "Open Tooling" with multi-app workspaces? And when/how can I replace the use of "Sencha Cmd Packages" with npm packages?

  2. #2

    Default

    Same problem here. Did you solve this?

    Best regards
    Maurice

  3. #3
    Sencha Premium User
    Join Date
    Jun 2015
    Posts
    4

    Default

    Quote Originally Posted by Maurice.Rossi View Post
    Same problem here. Did you solve this?

    Best regards
    Maurice
    Hi Maurice,

    Nope, I'm not able to get the "Open Tooling" to work with my setup (Sencha workspace containing ExtJS app folder and package folder). After looking at the ext-gen and ext-build node modules, I don't believe that Sencha expected that to work either. But I did expect Sencha to acknowledge that this is a limitation/bug in the current version (as they did with the other ext-gen issue I reported).

    Even if Sencha has not labeled it as such now, I think you should consider the current "Open Tooling" support as "early access" (as it was originally labeled in this roadmap: https://www.sencha.com/blog/sencha-p...oadmap-update/).

  4. #4
    Sencha Premium User wemerson.januario's Avatar
    Join Date
    Nov 2008
    Location
    Goiânia - GO, Brazil
    Posts
    898
    Answers
    15

    Default

    any update Sencha?
    Wemerson Januario @JanuarioCoder
    Novanti Tecnologia, Sencha MVP/ Ext JS Consultant
    ____________________________________________
    Hire me on UpWork:

    GitHub
    https://github.com/wemersonjanuario

    Treinamento e Consultoria Ext JS. QUALIFIQUE-SE JÁ!

  5. #5
    Sencha - Sales Team
    Join Date
    Feb 2012
    Location
    Fort Myers, Florida
    Posts
    42

    Default

    We did not implement multi-app workspaces in the first version of ext-gen, but we are looking on what is needed to implement it now
    Marc Gusmano
    Sales Engineer
    Sencha Inc.

  6. #6
    Sencha Premium User wemerson.januario's Avatar
    Join Date
    Nov 2008
    Location
    Goiânia - GO, Brazil
    Posts
    898
    Answers
    15

    Default

    Quote Originally Posted by mgusmano View Post
    We did not implement multi-app workspaces in the first version of ext-gen, but we are looking on what is needed to implement it now
    Thank you Marc.
    Wemerson Januario @JanuarioCoder
    Novanti Tecnologia, Sencha MVP/ Ext JS Consultant
    ____________________________________________
    Hire me on UpWork:

    GitHub
    https://github.com/wemersonjanuario

    Treinamento e Consultoria Ext JS. QUALIFIQUE-SE JÁ!

  7. #7
    Sencha - Sales Team
    Join Date
    Feb 2012
    Location
    Fort Myers, Florida
    Posts
    42

    Default

    you are welcome
    Marc Gusmano
    Sales Engineer
    Sencha Inc.

  8. #8
    Sencha Premium User
    Join Date
    Sep 2008
    Posts
    146
    Answers
    4

    Default

    Is there a guideline or some ideas on "how" npm tooling should be used in a multi-app environment?

    Practically, one has a structure like:
    Code:
    - senchaWorkspace
    - app1
    - app2
    - ext
    - packages
      - local
          - package1
          - package2
          - package3
          - theme1
          - theme2
    - theApp


    • How can apps share the same packages with the npm tooling?
    • I assume a package.json will be in the workspace directly, how about the package.json that are in the apps? Those contains code that are application specific
    Management means doing the things right,
    Leadership means doing the right things.
    www.interpid.eu

  9. #9
    Sencha Premium User wemerson.januario's Avatar
    Join Date
    Nov 2008
    Location
    Goiânia - GO, Brazil
    Posts
    898
    Answers
    15

    Default

    I guess you can aproach on multi app scenario using universal application template as a profile and change classpath to , where build.id is your app profile

    Code:
    "classpath": [
    "app/shared/src",
    "app/${build.id}/src"
    ],
    Wemerson Januario @JanuarioCoder
    Novanti Tecnologia, Sencha MVP/ Ext JS Consultant
    ____________________________________________
    Hire me on UpWork:

    GitHub
    https://github.com/wemersonjanuario

    Treinamento e Consultoria Ext JS. QUALIFIQUE-SE JÁ!

  10. #10
    Sencha Premium User
    Join Date
    Sep 2008
    Posts
    146
    Answers
    4

    Default

    I ended up with 2 versions so far:

    1. changing ext-webpack-plugin provided by sencha so that it works with multi-app workspace(nodejs packages are installed in the workspace folder and not in the application folder)
    2. working the "old" way with sencha watch and not webpack-dev-server

    Currently I still tend to use the "old" way, but maybe I'll review the whole setup once I find some time.
    Management means doing the things right,
    Leadership means doing the right things.
    www.interpid.eu

Page 1 of 2 12 LastLast

Similar Threads

  1. [DUP] SA 3.1 does not work with workspaces
    By Roman Tngi in forum Sencha Architect 3.x: Bugs
    Replies: 1
    Last Post: 13 Aug 2014, 2:05 AM
  2. [INFOREQ] Multi Level associations doesn't work.
    By jonathansimmons in forum Sencha Touch 2.x: Bugs
    Replies: 2
    Last Post: 19 May 2012, 12:14 PM
  3. mode:'MULTI' of the List doesn't work?
    By ksdl in forum Sencha Touch 2.x: Q&A
    Replies: 1
    Last Post: 24 Mar 2012, 3:05 PM
  4. CSS3 Multi-Column feature with scrollTo function does not appear to work
    By cavalleydude in forum Sencha Touch 1.x: Discussion
    Replies: 3
    Last Post: 1 Jun 2011, 2:41 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •