I've just discovered that having a component slide out on flick is a really interesting UI thing I want to toy with, but Android keeps getting in the way
onFlick={() => { do_thing_flick_should_do(); document.body.style.overscrollBehaviorY = 'auto'; }}
onTouchMove={(ev) => { document.body.style.overscrollBehaviorY = 'contain';}}
requires NODE_OPTIONS=--openssl-legacy-provider right now
it looks like this doesn't effect 16, this is a new change in 17. my production server uses 16 and doesn't set this, though i try to keep my dev machines up to date when i'm active on them. so, not a big deal, but someone will need to be aware that node 17+ will break npm run serve
Thank you, Eric. Sorry for the delay, I’m only seeing msgs at the office. You can just insert React components anywhere in the app, right? One other question, if you will: I’m having the most stupidest thing, where I try to insert an image using the Sandstone Image component, but it doesn’t render. Neither inside a panel, or inside a DIV. Any thoughts?
Hi @martinscola-hwm Yes, you can use react hooks with kind by setting functional: true
Please refer to the https://enactjs.com/docs/modules/core/kind/
Please refer to the https://enactjs.com/docs/modules/core/kind/
quite a time ago, i had asked about creating a PWA with enact.. finally figured out a way to do it.. just built the app manifest and related information, then installed it into the enact dist directory after packing everything with pack-p . . . just totally bypass the problem :-)
i'd just never thought about doing it like that, and i saw someone else doing something similar, and was like... oh.. i can do that. :-D
@seunghoh so setting functional: true does get past the initial "you can't use a hook here" problem, but then it triggers: Line 25:30: React Hook "useSelector" is called in function "render" that is neither a React function component nor a custom React Hook function. React component names must start with an uppercase letter react-hooks/rules-of-hooks
both the variable name and the 'name' field are set to a name that begins with an uppercase letter.
hi @ericblade We've released Enact CLI 4.1.7
It supports absolute path imports. https://github.com/enactjs/cli/releases/tag/4.1.7
It supports absolute path imports. https://github.com/enactjs/cli/releases/tag/4.1.7
i just upgraded to react 18-rc2, and unless there's something really really sticky hiding in there, the entire app appears to work 100% with no changes other than adding react 18 to my peerDeps in one component
I come across Paper Mache - https://www.ryanwatkins.net/software/papermache/press.html
I have huge content to be displayed like Paper Mache or https://lwcast.org/Mobile which uses enjoy framework. Looks the enyo framework is not very active right now or not sure whether i should use enjojs
Could you please kindly suggest the best framework or plugin or anything similar to Paper Mache or Enjo framework implementation like https://lwcast.org/Mobile or should we use enyojs which will satisfy the artcile or paper publishing website with search engine.
I have huge content to be displayed like Paper Mache or https://lwcast.org/Mobile which uses enjoy framework. Looks the enyo framework is not very active right now or not sure whether i should use enjojs
Could you please kindly suggest the best framework or plugin or anything similar to Paper Mache or Enjo framework implementation like https://lwcast.org/Mobile or should we use enyojs which will satisfy the artcile or paper publishing website with search engine.
my development build has no problem with the new typescript
hi @goodev2021 Enyo has switched to Enact in 2018. https://medium.com/enact-js/hello-enact-2d971dc763ab
You can use Enact. https://enactjs.com/
Thanks
You can use Enact. https://enactjs.com/
Thanks
1 reply
@ericblade Can you share the complaining message of new feature?
specifically, type imports
it is very weird. i have doubts that additionalModulePaths is affecting it, it's acting like it's using a specific version of typescript rather than the one installed
and this is what my Dockerfile does up to the point where it builds and fails
FROM node:16 AS build
WORKDIR /usr/src/pos
#ENV NODE_OPTIONS=--openssl-legacy-provider # not allowed in v14, but necessary in v17+ until we get upgraded webpack in enact
RUN npm install -g @enact/cli
#RUN npm install -g ericblade/cli#dev
RUN enact -v
RUN npm install -g typescript
RUN npm install -g workbox-cli
COPY package*.json ./
RUN npm install --production
COPY . .
WORKDIR /usr/src/pos/public
# RUN npm install --production
RUN npm install
RUN npm run pack-p
@goodev2021 Enact has Scroller & VirtualList component which supports huge content with high performance. webOS TV uses these components a lot.
Please refer to our doc https://enactjs.com/docs/developer-guide/virtual-list-scroller/
You can also check our components samples in the storybook at https://enactjs.com/sampler/sandstone/
Please refer to our doc https://enactjs.com/docs/developer-guide/virtual-list-scroller/
You can also check our components samples in the storybook at https://enactjs.com/sampler/sandstone/
1 reply
i checked out for sure that the global installed typescript with the above docker script is in fact 4.6.2.
It is even more strange that switching back to my fork of cli works with the exact same everything else. The only change on my fork are adding the module paths, there are no dependency changes or anything. My fork of cli is 4.1.3 + change. So, I guess this might be something to do with enactjs changes between 4.1.3 and 4.1.7
It is even more strange that switching back to my fork of cli works with the exact same everything else. The only change on my fork are adding the module paths, there are no dependency changes or anything. My fork of cli is 4.1.3 + change. So, I guess this might be something to do with enactjs changes between 4.1.3 and 4.1.7
enact -v reports 4.1.7, tsc -v reports 4.6.2, and then the
npm run pack-p fails on all lines of code that use the new import { type ... } introduced in .. 4.5 https://devblogs.microsoft.com/typescript/announcing-typescript-4-5/#type-on-import-names