Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • 06:56
    codecov[bot] commented #3043
  • 06:50
    codecov[bot] commented #3043
  • 06:45
    codecov[bot] commented #3043
  • 06:45
    dongsuwon synchronize #3043
  • 06:45

    dongsuwon on WRN-19401

    * Suggested changes. Enact-DCO… (compare)

  • 05:55

    sjro on WRO-3084

    Update react dependency (compare)

  • 05:47
    codecov[bot] commented #3043
  • 05:47
    codecov[bot] commented #3043
  • 05:42
    codecov[bot] commented #3043
  • 05:42
    dongsuwon synchronize #3043
  • 05:42

    dongsuwon on WRN-19401

    * Suggested changes. Enact-DCO… (compare)

  • May 24 15:20

    adrian-cocoara-lgp on WRO-446

    added some mistakes to Button a… (compare)

  • May 24 07:35

    juwonjeong on WRO-3415

    (compare)

  • May 24 07:35

    juwonjeong on develop

    WRO-3415: Provides event payloa… (compare)

  • May 24 07:35
    juwonjeong closed #3060
  • May 24 07:13
    juwonjeong commented #3060
  • May 24 04:58
    jeonghee27 edited #3043
  • May 24 04:58
    jeonghee27 edited #3043
  • May 23 04:34

    0x64 on develop

    WRO-2580: Add optional `contain… (compare)

  • May 23 04:34

    0x64 on WRN-19179

    (compare)

Ahmad Freijeh
@ahmadfreijeh
i have followed steps as in the doc
Seungho Park
@seunghoh
Ahmad Freijeh
@ahmadfreijeh
Hello all
Can i use enact with tizen TVs?
Ahmad Freijeh
@ahmadfreijeh
And if yes what issues could i face?
Ahmad Freijeh
@ahmadfreijeh
and something else I'm trying to launch my app on TV but I got a black screen ?
2 replies
Ahmad Freijeh
@ahmadfreijeh
?
valverde82
@valverde-marcelo
@ahmad-crossplatform your javascript code must be compatible with the browser engine
@ahmad-crossplatform for example, the web engine of webOS TV 3.x is Chrome 38 (see more: https://webostv.developer.lge.com/discover/specifications/web-engine/)
valverde82
@valverde-marcelo
@ahmadfreijeh therefore javascript ES5, ES6(ES2015) will not run...
Ahmad Freijeh
@ahmadfreijeh
Can i use enact with tizen TVs?
Ahmad Freijeh
@ahmadfreijeh
I mean samsung ?
Eric Blade
@ericblade
how's things going enact crew
Eric Blade
@ericblade
wow.. long time here
if anyone's around, after entirely too many years of waiting, i've finally pushed my Enact app to a public server, and I hope to soon be opening it for public beta test, just as soon as i figure out a good way to handle subscriptions
Seungho Park
@seunghoh
Hi Eric, Yes, Enact team is still here :)
Good to hear that your app is almost ready. yay~
Eric Blade
@ericblade
:-) I'm glad to see friends still here
Eric Blade
@ericblade
Merry Christmas Eve!
Roy Sutton
@webOS101
Back at you!
Seungho Park
@seunghoh
Merry Christmas Roy, Eric ;)
최형욱
@brouk2426
Hello World, I liked the font while looking around the site, so can I get it for personal use? "Enact Museo Sans"
Seungho Park
@seunghoh
Hi @brouk2426 Museo Sans license is restrected for use with Enact Application. Please refer to the full license at https://github.com/enactjs/moonstone/blob/master/fonts/MuseoSans/LICENSE.txt
최형욱
@brouk2426
@seunghoh Thanks!!
Eric Blade
@ericblade
anyone found a way to use absolute paths with enact? pretty sick of all the ../../../.. stuff :-D
Drake Witt
@DrakeWitt
@ericblade You can setup resolve aliases with Webpack, that should accomplish what you're looking for: https://webpack.js.org/configuration/resolve/
Eric Blade
@ericblade
@DrakeWitt how does one connect that with enact though
Seungho Park
@seunghoh
Hi @ericblade We fixed the absolute path issue on Enact CLI 4.0.2
Would you please update the Enact CLI and try again?
Eric Blade
@ericblade
@seunghoh :) i'm using 4.1.1 locally, is there something i need to configure ?
just updated to 4.1.6, doesn't seem to work there either
Eric Blade
@ericblade
i do have it apparently setup in my tsconfig correctly, as my editor understands it, but enact serve and pack just tells me that the files aren't findable if i remove the ../../.. strings
Drake Witt
@DrakeWitt
@ericblade Ah you need to run enact eject which will generate the webpack config files and such where you can customize them.
Eric Blade
@ericblade
meh, i will hope for a solution that doesn't require maintaining more configs i don't really care about, and continue using ../.. until then :)
Seungho Park
@seunghoh
Hm.. it should work. Would you explain a bit more detailed so that we can check?
Eric Blade
@ericblade
what information would help? i started this app back around enact first went public, i think before the 1.0 release, and i've slowly upgraded it over time ever since.
Seungho Park
@seunghoh
Enact & Sandstone version, the codes around which you want to use absolute path will help
Eric Blade
@ericblade
enact-cli 4.1.6, deps are "dependencies": { "@enact/core": "^4.1.2", "@enact/i18n": "^4.1.2", "@enact/moonstone": "^4.0.3", "@enact/spotlight": "^4.1.2", "@enact/ui": "^4.1.2",
Eric Blade
@ericblade
and i have a lot of imports that look like import CurrencyInput from '../../components/CurrencyInput/CurrencyInput';
Eric Blade
@ericblade
decided to go dig around and find it.. now checking to see if i can figure out how to add it to the enact options in package.json :)
Eric Blade
@ericblade
ugh also need to fork dev-utils
Eric Blade
@ericblade
ok.. so when i link in my modified dev-tools it deletes all the other modules necessary for cli to run.. :|
Eric Blade
@ericblade
please review enactjs/cli#257 and enactjs/dev-utils#85 to add the feature to package.json
Eric Blade
@ericblade
... and confirming that it works and does what it's supposed to, all the way out to my production server. \o/
i should've called it relative paths, not absolute paths, i thought that sounded weird, but all the articles were like 'absolute paths are amazing'.. but these aren't absolute paths. sorry if that caused any confusion
Eric Blade
@ericblade
image.png
2 hours to clone and figure out how to add the feature to enact, get it added to my production server, and touch every single file in my application to update for it. not too bad.
Mikyung Kim
@MikyungKim
@ericblade ,
Thanks for the PRs. Enact CLI does support "resolve.alias" (https://webpack.js.org/configuration/resolve/#resolvealias) through package.json as "alias" property.
But I guess you wanted to resolve additional paths.
I understand what's the pain point for developers and I think it's reasonable to add the feature.
I found Create React App also supports the feature through js/tsconfig file. (https://create-react-app.dev/docs/importing-a-component/#absolute-imports)
Fortunately, we have plans for adopting Webpack5 near future, we'll take a look at how we could achieve this while updating Webpack.
I think "enact" object in package.json is a good start point. Thanks for the suggestion!
Eric Blade
@ericblade
I don't know enough about webpack configuration to know if that can be used to achieve the same thing or not
hmm. i just looked up those fields, and for the specific purpose, it does look like both can be used to achieve what i wanted, though it does look like there might be good reasons to have both.
If you'd like to accept that change, but need me to make any changes to it, just lmk. I'm not sure my choice of variable names fits well.
Mikyung Kim
@MikyungKim
Sure, we'll let you know! If we need to make another PR for some reason, we'll also comment on your PR to let you know.
Thank you for your support! I really appreciate it.