可伸缩布局方案

OS-Lib is a simple, flexible, high-performance Scala interface to common OS filesystem and subprocess APIs

A flexible UI lib for PixiJS engine.

# big-o-performance A simple html app to demonstrate performance costs of data structures. - Clone the project - Navigate to the root of the project in a termina or command prompt - Run 'npm install' - Run 'npm start' - Go to the URL specified in the terminal or command prompt to try out the app. # This app was created from the Create React App NPM. Below are instructions from that project. Below you will find some information on how to perform common tasks. You can find the most recent version of this guide [here](https://github.com/facebookincubator/create-react-app/blob/master/template/README.md). ## Table of Contents - [Updating to New Releases](#updating-to-new-releases) - [Sending Feedback](#sending-feedback) - [Folder Structure](#folder-structure) - [Available Scripts](#available-scripts) - [npm start](#npm-start) - [npm run build](#npm-run-build) - [npm run eject](#npm-run-eject) - [Displaying Lint Output in the Editor](#displaying-lint-output-in-the-editor) - [Installing a Dependency](#installing-a-dependency) - [Importing a Component](#importing-a-component) - [Adding a Stylesheet](#adding-a-stylesheet) - [Post-Processing CSS](#post-processing-css) - [Adding Images and Fonts](#adding-images-and-fonts) - [Adding Bootstrap](#adding-bootstrap) - [Adding Flow](#adding-flow) - [Adding Custom Environment Variables](#adding-custom-environment-variables) - [Integrating with a Node Backend](#integrating-with-a-node-backend) - [Proxying API Requests in Development](#proxying-api-requests-in-development) - [Deployment](#deployment) - [Now](#now) - [Heroku](#heroku) - [Surge](#surge) - [GitHub Pages](#github-pages) - [Something Missing?](#something-missing) ## Updating to New Releases Create React App is divided into two packages: * `create-react-app` is a global command-line utility that you use to create new projects. * `react-scripts` is a development dependency in the generated projects (including this one). You almost never need to update `create-react-app` itself: it’s delegates all the setup to `react-scripts`. When you run `create-react-app`, it always creates the project with the latest version of `react-scripts` so you’ll get all the new features and improvements in newly created apps automatically. To update an existing project to a new version of `react-scripts`, [open the changelog](https://github.com/facebookincubator/create-react-app/blob/master/CHANGELOG.md), find the version you’re currently on (check `package.json` in this folder if you’re not sure), and apply the migration instructions for the newer versions. In most cases bumping the `react-scripts` version in `package.json` and running `npm install` in this folder should be enough, but it’s good to consult the [changelog](https://github.com/facebookincubator/create-react-app/blob/master/CHANGELOG.md) for potential breaking changes. We commit to keeping the breaking changes minimal so you can upgrade `react-scripts` painlessly. ## Sending Feedback We are always open to [your feedback](https://github.com/facebookincubator/create-react-app/issues). ## Folder Structure After creation, your project should look like this: ``` my-app/ README.md index.html favicon.ico node_modules/ package.json src/ App.css App.js index.css index.js logo.svg ``` For the project to build, **these files must exist with exact filenames**: * `index.html` is the page template; * `favicon.ico` is the icon you see in the browser tab; * `src/index.js` is the JavaScript entry point. You can delete or rename the other files. You may create subdirectories inside `src`. For faster rebuilds, only files inside `src` are processed by Webpack. You need to **put any JS and CSS files inside `src`**, or Webpack won’t see them. You can, however, create more top-level directories. They will not be included in the production build so you can use them for things like documentation. ## Available Scripts In the project directory, you can run: ### `npm start` Runs the app in the development mode.<br> Open [http://localhost:3000](http://localhost:3000) to view it in the browser. The page will reload if you make edits.<br> You will also see any lint errors in the console. ### `npm run build` Builds the app for production to the `build` folder.<br> It correctly bundles React in production mode and optimizes the build for the best performance. The build is minified and the filenames include the hashes.<br> Your app is ready to be deployed! ### `npm run eject` **Note: this is a one-way operation. Once you `eject`, you can’t go back!** If you aren’t satisfied with the build tool and configuration choices, you can `eject` at any time. This command will remove the single build dependency from your project. Instead, it will copy all the configuration files and the transitive dependencies (Webpack, Babel, ESLint, etc) right into your project so you have full control over them. All of the commands except `eject` will still work, but they will point to the copied scripts so you can tweak them. At this point you’re on your own. You don’t have to ever use `eject`. The curated feature set is suitable for small and middle deployments, and you shouldn’t feel obligated to use this feature. However we understand that this tool wouldn’t be useful if you couldn’t customize it when you are ready for it. ## Displaying Lint Output in the Editor >Note: this feature is available with `react-scripts@0.2.0` and higher. Some editors, including Sublime Text, Atom, and Visual Studio Code, provide plugins for ESLint. They are not required for linting. You should see the linter output right in your terminal as well as the browser console. However, if you prefer the lint results to appear right in your editor, there are some extra steps you can do. You would need to install an ESLint plugin for your editor first. >**A note for Atom `linter-eslint` users** >If you are using the Atom `linter-eslint` plugin, make sure that **Use global ESLint installation** option is checked: ><img src="http://i.imgur.com/yVNNHJM.png" width="300"> Then make sure `package.json` of your project ends with this block: ```js { // ... "eslintConfig": { "extends": "./node_modules/react-scripts/config/eslint.js" } } ``` Projects generated with `react-scripts@0.2.0` and higher should already have it. If you don’t need ESLint integration with your editor, you can safely delete those three lines from your `package.json`. Finally, you will need to install some packages *globally*: ```sh npm install -g eslint babel-eslint eslint-plugin-react eslint-plugin-import eslint-plugin-jsx-a11y eslint-plugin-flowtype ``` We recognize that this is suboptimal, but it is currently required due to the way we hide the ESLint dependency. The ESLint team is already [working on a solution to this](https://github.com/eslint/eslint/issues/3458) so this may become unnecessary in a couple of months. ## Installing a Dependency The generated project includes React and ReactDOM as dependencies. It also includes a set of scripts used by Create React App as a development dependency. You may install other dependencies (for example, React Router) with `npm`: ``` npm install --save <library-name> ``` ## Importing a Component This project setup supports ES6 modules thanks to Babel. While you can still use `require()` and `module.exports`, we encourage you to use [`import` and `export`](http://exploringjs.com/es6/ch_modules.html) instead. For example: ### `Button.js` ```js import React, { Component } from 'react'; class Button extends Component { render() { // ... } } export default Button; // Don’t forget to use export default! ``` ### `DangerButton.js` ```js import React, { Component } from 'react'; import Button from './Button'; // Import a component from another file class DangerButton extends Component { render() { return <Button color="red" />; } } export default DangerButton; ``` Be aware of the [difference between default and named exports](http://stackoverflow.com/questions/36795819/react-native-es-6-when-should-i-use-curly-braces-for-import/36796281#36796281). It is a common source of mistakes. We suggest that you stick to using default imports and exports when a module only exports a single thing (for example, a component). That’s what you get when you use `export default Button` and `import Button from './Button'`. Named exports are useful for utility modules that export several functions. A module may have at most one default export and as many named exports as you like. Learn more about ES6 modules: * [When to use the curly braces?](http://stackoverflow.com/questions/36795819/react-native-es-6-when-should-i-use-curly-braces-for-import/36796281#36796281) * [Exploring ES6: Modules](http://exploringjs.com/es6/ch_modules.html) * [Understanding ES6: Modules](https://leanpub.com/understandinges6/read#leanpub-auto-encapsulating-code-with-modules) ## Adding a Stylesheet This project setup uses [Webpack](https://webpack.github.io/) for handling all assets. Webpack offers a custom way of “extending” the concept of `import` beyond JavaScript. To express that a JavaScript file depends on a CSS file, you need to **import the CSS from the JavaScript file**: ### `Button.css` ```css .Button { padding: 20px; } ``` ### `Button.js` ```js import React, { Component } from 'react'; import './Button.css'; // Tell Webpack that Button.js uses these styles class Button extends Component { render() { // You can use them as regular CSS styles return <div className="Button" />; } } ``` **This is not required for React** but many people find this feature convenient. You can read about the benefits of this approach [here](https://medium.com/seek-ui-engineering/block-element-modifying-your-javascript-components-d7f99fcab52b). However you should be aware that this makes your code less portable to other build tools and environments than Webpack. In development, expressing dependencies this way allows your styles to be reloaded on the fly as you edit them. In production, all CSS files will be concatenated into a single minified `.css` file in the build output. If you are concerned about using Webpack-specific semantics, you can put all your CSS right into `src/index.css`. It would still be imported from `src/index.js`, but you could always remove that import if you later migrate to a different build tool. ## Post-Processing CSS This project setup minifies your CSS and adds vendor prefixes to it automatically through [Autoprefixer](https://github.com/postcss/autoprefixer) so you don’t need to worry about it. For example, this: ```css .App { display: flex; flex-direction: row; align-items: center; } ``` becomes this: ```css .App { display: -webkit-box; display: -ms-flexbox; display: flex; -webkit-box-orient: horizontal; -webkit-box-direction: normal; -ms-flex-direction: row; flex-direction: row; -webkit-box-align: center; -ms-flex-align: center; align-items: center; } ``` There is currently no support for preprocessors such as Less, or for sharing variables across CSS files. ## Adding Images and Fonts With Webpack, using static assets like images and fonts works similarly to CSS. You can **`import` an image right in a JavaScript module**. This tells Webpack to include that image in the bundle. Unlike CSS imports, importing an image or a font gives you a string value. This value is the final image path you can reference in your code. Here is an example: ```js import React from 'react'; import logo from './logo.png'; // Tell Webpack this JS file uses this image console.log(logo); // /logo.84287d09.png function Header() { // Import result is the URL of your image return <img src={logo} alt="Logo" />; } export default function Header; ``` This works in CSS too: ```css .Logo { background-image: url(./logo.png); } ``` Webpack finds all relative module references in CSS (they start with `./`) and replaces them with the final paths from the compiled bundle. If you make a typo or accidentally delete an important file, you will see a compilation error, just like when you import a non-existent JavaScript module. The final filenames in the compiled bundle are generated by Webpack from content hashes. If the file content changes in the future, Webpack will give it a different name in production so you don’t need to worry about long-term caching of assets. Please be advised that this is also a custom feature of Webpack. **It is not required for React** but many people enjoy it (and React Native uses a similar mechanism for images). However it may not be portable to some other environments, such as Node.js and Browserify. If you prefer to reference static assets in a more traditional way outside the module system, please let us know [in this issue](https://github.com/facebookincubator/create-react-app/issues/28), and we will consider support for this. ## Adding Bootstrap You don’t have to use [React Bootstrap](https://react-bootstrap.github.io) together with React but it is a popular library for integrating Bootstrap with React apps. If you need it, you can integrate it with Create React App by following these steps: Install React Bootstrap and Bootstrap from NPM. React Bootstrap does not include Bootstrap CSS so this needs to be installed as well: ``` npm install react-bootstrap --save npm install bootstrap@3 --save ``` Import Bootstrap CSS and optionally Bootstrap theme CSS in the ```src/index.js``` file: ```js import 'bootstrap/dist/css/bootstrap.css'; import 'bootstrap/dist/css/bootstrap-theme.css'; ``` Import required React Bootstrap components within ```src/App.js``` file or your custom component files: ```js import { Navbar, Jumbotron, Button } from 'react-bootstrap'; ``` Now you are ready to use the imported React Bootstrap components within your component hierarchy defined in the render method. Here is an example [`App.js`](https://gist.githubusercontent.com/gaearon/85d8c067f6af1e56277c82d19fd4da7b/raw/6158dd991b67284e9fc8d70b9d973efe87659d72/App.js) redone using React Bootstrap. ## Adding Flow Flow typing is currently [not supported out of the box](https://github.com/facebookincubator/create-react-app/issues/72) with the default `.flowconfig` generated by Flow. If you run it, you might get errors like this: ```js node_modules/fbjs/lib/Deferred.js.flow:60 60: Promise.prototype.done.apply(this._promise, arguments); ^^^^ property `done`. Property not found in 495: declare class Promise<+R> { ^ Promise. See lib: /private/tmp/flow/flowlib_34952d31/core.js:495 node_modules/fbjs/lib/shallowEqual.js.flow:29 29: return x !== 0 || 1 / (x: $FlowIssue) === 1 / (y: $FlowIssue); ^^^^^^^^^^ identifier `$FlowIssue`. Could not resolve name src/App.js:3 3: import logo from './logo.svg'; ^^^^^^^^^^^^ ./logo.svg. Required module not found src/App.js:4 4: import './App.css'; ^^^^^^^^^^^ ./App.css. Required module not found src/index.js:5 5: import './index.css'; ^^^^^^^^^^^^^ ./index.css. Required module not found ``` To fix this, change your `.flowconfig` to look like this: ```ini [libs] ./node_modules/fbjs/flow/lib [options] esproposal.class_static_fields=enable esproposal.class_instance_fields=enable module.name_mapper='^\(.*\)\.css$' -> 'react-scripts/config/flow/css' module.name_mapper='^\(.*\)\.\(jpg\|png\|gif\|eot\|otf\|webp\|svg\|ttf\|woff\|woff2\|mp4\|webm\)$' -> 'react-scripts/config/flow/file' suppress_type=$FlowIssue suppress_type=$FlowFixMe ``` Re-run flow, and you shouldn’t get any extra issues. If you later `eject`, you’ll need to replace `react-scripts` references with the `<PROJECT_ROOT>` placeholder, for example: ```ini module.name_mapper='^\(.*\)\.css$' -> '<PROJECT_ROOT>/config/flow/css' module.name_mapper='^\(.*\)\.\(jpg\|png\|gif\|eot\|otf\|webp\|svg\|ttf\|woff\|woff2\|mp4\|webm\)$' -> '<PROJECT_ROOT>/config/flow/file' ``` We will consider integrating more tightly with Flow in the future so that you don’t have to do this. ## Adding Custom Environment Variables >Note: this feature is available with `react-scripts@0.2.3` and higher. Your project can consume variables declared in your environment as if they were declared locally in your JS files. By default you will have `NODE_ENV` defined for you, and any other environment variables starting with `REACT_APP_`. These environment variables will be defined for you on `process.env`. For example, having an environment variable named `REACT_APP_SECRET_CODE` will be exposed in your JS as `process.env.REACT_APP_SECRET_CODE`, in addition to `process.env.NODE_ENV`. These environment variables can be useful for displaying information conditionally based on where the project is deployed or consuming sensitive data that lives outside of version control. First, you need to have environment variables defined, which can vary between OSes. For example, let's say you wanted to consume a secret defined in the environment inside a `<form>`: ```jsx render() { return ( <div> <small>You are running this application in <b>{process.env.NODE_ENV}</b> mode.</small> <form> <input type="hidden" defaultValue={process.env.REACT_APP_SECRET_CODE} /> </form> </div> ); } ``` The above form is looking for a variable called `REACT_APP_SECRET_CODE` from the environment. In order to consume this value, we need to have it defined in the environment: ### Windows (cmd.exe) ```cmd set REACT_APP_SECRET_CODE=abcdef&&npm start ``` (Note: the lack of whitespace is intentional.) ### Linux, OS X (Bash) ```bash REACT_APP_SECRET_CODE=abcdef npm start ``` > Note: Defining environment variables in this manner is temporary for the life of the shell session. Setting permanent environment variables is outside the scope of these docs. With our environment variable defined, we start the app and consume the values. Remember that the `NODE_ENV` variable will be set for you automatically. When you load the app in the browser and inspect the `<input>`, you will see its value set to `abcdef`, and the bold text will show the environment provided when using `npm start`: ```html <div> <small>You are running this application in <b>development</b> mode.</small> <form> <input type="hidden" value="abcdef" /> </form> </div> ``` Having access to the `NODE_ENV` is also useful for performing actions conditionally: ```js if (process.env.NODE_ENV !== 'production') { analytics.disable(); } ``` ## Integrating with a Node Backend Check out [this tutorial](https://www.fullstackreact.com/articles/using-create-react-app-with-a-server/) for instructions on integrating an app with a Node backend running on another port, and using `fetch()` to access it. You can find the companion GitHub repository [here](https://github.com/fullstackreact/food-lookup-demo). ## Proxying API Requests in Development >Note: this feature is available with `react-scripts@0.2.3` and higher. People often serve the front-end React app from the same host and port as their backend implementation. For example, a production setup might look like this after the app is deployed: ``` / - static server returns index.html with React app /todos - static server returns index.html with React app /api/todos - server handles any /api/* requests using the backend implementation ``` Such setup is **not** required. However, if you **do** have a setup like this, it is convenient to write requests like `fetch('/api/todos')` without worrying about redirecting them to another host or port during development. To tell the development server to proxy any unknown requests to your API server in development, add a `proxy` field to your `package.json`, for example: ```js "proxy": "http://localhost:4000", ``` This way, when you `fetch('/api/todos')` in development, the development server will recognize that it’s not a static asset, and will proxy your request to `http://localhost:4000/api/todos` as a fallback. Conveniently, this avoids [CORS issues](http://stackoverflow.com/questions/21854516/understanding-ajax-cors-and-security-considerations) and error messages like this in development: ``` Fetch API cannot load http://localhost:4000/api/todos. No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://localhost:3000' is therefore not allowed access. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled. ``` Keep in mind that `proxy` only has effect in development (with `npm start`), and it is up to you to ensure that URLs like `/api/todos` point to the right thing in production. You don’t have to use the `/api` prefix. Any unrecognized request will be redirected to the specified `proxy`. Currently the `proxy` option only handles HTTP requests, and it won’t proxy WebSocket connections. If the `proxy` option is **not** flexible enough for you, alternatively you can: * Enable CORS on your server ([here’s how to do it for Express](http://enable-cors.org/server_expressjs.html)). * Use [environment variables](#adding-custom-environment-variables) to inject the right server host and port into your app. ## Deployment By default, Create React App produces a build assuming your app is hosted at the server root. To override this, specify the `homepage` in your `package.json`, for example: ```js "homepage": "http://mywebsite.com/relativepath", ``` This will let Create React App correctly infer the root path to use in the generated HTML file. ### Now See [this example](https://github.com/xkawi/create-react-app-now) for a zero-configuration single-command deployment with [now](https://zeit.co/now). ### Heroku Use the [Heroku Buildpack for Create React App](https://github.com/mars/create-react-app-buildpack). You can find instructions in [Deploying React with Zero Configuration](https://blog.heroku.com/deploying-react-with-zero-configuration). ### Surge Install the Surge CLI if you haven't already by running `npm install -g surge`. Run the `surge` command and log in you or create a new account. You just need to specify the *build* folder and your custom domain, and you are done. ```sh email: email@domain.com password: ******** project path: /path/to/project/build size: 7 files, 1.8 MB domain: create-react-app.surge.sh upload: [====================] 100%, eta: 0.0s propagate on CDN: [====================] 100% plan: Free users: email@domain.com IP Address: X.X.X.X Success! Project is published and running at create-react-app.surge.sh ``` Note that in order to support routers that use html5 `pushState` API, you may want to rename the `index.html` in your build folder to `200.html` before deploying to Surge. This [ensures that every URL falls back to that file](https://surge.sh/help/adding-a-200-page-for-client-side-routing). ### GitHub Pages >Note: this feature is available with `react-scripts@0.2.0` and higher. Open your `package.json` and add a `homepage` field: ```js "homepage": "http://myusername.github.io/my-app", ``` **The above step is important!** Create React App uses the `homepage` field to determine the root URL in the built HTML file. Now, whenever you run `npm run build`, you will see a cheat sheet with a sequence of commands to deploy to GitHub pages: ```sh git commit -am "Save local changes" git checkout -B gh-pages git add -f build git commit -am "Rebuild website" git filter-branch -f --prune-empty --subdirectory-filter build git push -f origin gh-pages git checkout - ``` You may copy and paste them, or put them into a custom shell script. You may also customize them for another hosting provider. Note that GitHub Pages doesn't support routers that use the HTML5 `pushState` history API under the hood (for example, React Router using `browserHistory`). This is because when there is a fresh page load for a url like `http://user.github.io/todomvc/todos/42`, where `/todos/42` is a frontend route, the GitHub Pages server returns 404 because it knows nothing of `/todos/42`. If you want to add a router to a project hosted on GitHub Pages, here are a couple of solutions: * You could switch from using HTML5 history API to routing with hashes. If you use React Router, you can switch to `hashHistory` for this effect, but the URL will be longer and more verbose (for example, `http://user.github.io/todomvc/#/todos/42?_k=yknaj`). [Read more](https://github.com/reactjs/react-router/blob/master/docs/guides/Histories.md#histories) about different history implementations in React Router. * Alternatively, you can use a trick to teach GitHub Pages to handle 404 by redirecting to your `index.html` page with a special redirect parameter. You would need to add a `404.html` file with the redirection code to the `build` folder before deploying your project, and you’ll need to add code handling the redirect parameter to `index.html`. You can find a detailed explanation of this technique [in this guide](https://github.com/rafrex/spa-github-pages). ## Something Missing? If you have ideas for more “How To” recipes that should be on this page, [let us know](https://github.com/facebookincubator/create-react-app/issues) or [contribute some!](https://github.com/facebookincubator/create-react-app/edit/master/template/README.md)

Flexible client helper for making and validating calls to OpenAPI backends. For Node and the browser. Runtime lib - no need for code generation!

A flexible solution for fullscreen dashboard on big screen

这是一个集成vux和淘宝移动端自适应屏幕解决方案

HTTP request lib for Emacs built on curl with flexible callback dispatch

Lib for advanced LLM-interaction focusing on flexibility and a strong OOP design

AkenoAI-Lib is a high-performance library for making raw HTTP requests, powered by aiohttp. It provides a simple yet powerful syntax for handling API requests efficiently, ensuring speed and flexibility.

amfe/lib-flexible usage test

Flexible UI buttons in PixiJS v5. Quick, simple and common solution for PixiJS UI without ReactJS, VueJS and similar heavy libs.

No description available

No description available

API documentation of FCL

A TypeScript-based library designed for streamlined development workflows and enhanced scalability. With customizable CSS styling and minimal JavaScript, Uni-Lib delivers performance, flexibility, and maintainability for modern web applications.

<!DOCTYPE html> <html> <head> <meta charset="utf-8"> <meta name="bigo-author" content="chenyongzhao"> <meta name="applicable-device" content="mobile"> <meta name="apple-touch-fullscreen" content="yes"> <meta name="apple-mobile-web-app-capable" content="yes"> <meta name="apple-mobile-web-app-status-bar-style" content="black"> <meta name="format-detection" content="telephone=no"> <meta name="format-detection" content="address=no"> <meta http-equiv="Content-Security-Policy" content="upgrade-insecure-requests"> <meta property="og:image" itemprop="image" th:content="https://static-web.likeevideo.com/as/indigo-static/act-45685/share/meta-image.png"> <meta http-equiv="Cache-Control" content="no-cache, no-store, must-revalidate"> <meta name="viewport" content="width=device-width,initial-scale=1,maximum-scale=1,minimum-scale=1,user-scalable=no"> <meta http-equiv="Pragma" content="no-cache"> <meta http-equiv="Expires" content="0"> <title>imo 2021 Ceremony</title> <script> window.$_PERF_OPTIONS = { sampleRate: 1, costTimeLimit: 20000, api: "https://front-perf.like-video.com/api/call", reportWaitMilliseconds: 2000 } </script> <script src="//static.f2ecdn.com/comm/libs/assets-load-monitor/2.5.6/assets-load-monitor-init.min.js"></script> <script> ; /eruda=true/.test(window.location) || true && (document.write('<script src="//cdn.jsdelivr.net/npm/eruda"><\/script>'), document.write("<script>eruda.init();<\/script>")); </script> <link href="//static-imo.sdonlyn.net/as/indigo/act-45685/css/chunk-vendors.2babbbd5.css" rel="stylesheet"> <link href="//static-imo.sdonlyn.net/as/indigo/act-45685/css/chunk-common.2333e189.css" rel="stylesheet"> <link href="//static-imo.sdonlyn.net/as/indigo/act-45685/css/index.c65a98b4.css" rel="stylesheet"> </head> <body> <div id="app"></div> <script src="//static-act.like-video.com/live/comm/libs/flexible/1.0.0/flexible.min.js"></script> <script src="//static.f2ecdn.com/comm/libs/common-vendor/1.1.0/common_vendor.min.js"></script> <script src="//static-imo.sdonlyn.net/as/indigo/act-45685/js/chunk-vendors.191c72f2.js"></script> <script src="//static-imo.sdonlyn.net/as/indigo/act-45685/js/chunk-common.49ec2cbc.js"></script> <script src="//static-imo.sdonlyn.net/as/indigo/act-45685/js/index.7f46c77c.js"></script> </body> </html>

portable server/clock with enhanced functionality. what can this thing do? it can have a Wi-Fi connection, reception/transmission of the IR spectrum (remotes for the TV, air conditioner), reception/transmission of 433 MHz (smart gate, lamps). It is planned to add games and a few more tricks ;)

移动端页面开发(lib-flexible)这样用~~~~~~

vux 和lib_flexible.js同时使用问题

使用vue-cli + lib-flexible + px2rem-loader技术配置移动端解决方案

Open-source game engine(now in the start of its way) written on C++ and made with boost libs for [cross?] to fix usability of most known engines and get more flexible engine. Now is only for Windows, but you can help to make it cross-platform)

The Configurable Calendar Lib is a versatile library for creating and managing customizable calendars. With a hierarchical tree structure, it enables intuitive navigation from yearly overviews to specific time slots. Whether setting up daily, weekly, or recurring schedules, this library offers flexibility and precision. Ideal for developers focused

Welcome to Cloud Shell! Type "help" to get started. Your Cloud Platform project in this session is set to qwiklabs-gcp-00-caaddc51ae14. Use “gcloud config set project [PROJECT_ID]” to change to a different project. student_00_bea2289b69fb@cloudshell:~ (qwiklabs-gcp-00-caaddc51ae14)$ gcloud auth list Credentialed Accounts ACTIVE: * ACCOUNT: student-00-bea2289b69fb@qwiklabs.net To set the active account, run: $ gcloud config set account `ACCOUNT` student_00_bea2289b69fb@cloudshell:~ (qwiklabs-gcp-00-caaddc51ae14)$ gcloud config list project [core] project = qwiklabs-gcp-00-caaddc51ae14 Your active configuration is: [cloudshell-633] student_00_bea2289b69fb@cloudshell:~ (qwiklabs-gcp-00-caaddc51ae14)$ gcloud config set accessibility/screen_reader true Updated property [accessibility/screen_reader]. student_00_bea2289b69fb@cloudshell:~ (qwiklabs-gcp-00-caaddc51ae14)$ gcloud config set project <project-id> -bash: syntax error near unexpected token `newline' student_00_bea2289b69fb@cloudshell:~ (qwiklabs-gcp-00-caaddc51ae14)$ gcloud config set project <project-id> -bash: syntax error near unexpected token `newline' student_00_bea2289b69fb@cloudshell:~ (qwiklabs-gcp-00-caaddc51ae14)$ ls README-cloudshell.txt student_00_bea2289b69fb@cloudshell:~ (qwiklabs-gcp-00-caaddc51ae14)$ bq show bigquery-public-data:samples.shakespeare Table bigquery-public-data:samples.shakespeare Last modified Schema Total Rows Total Bytes Expiration Time Partitioning Clustered Fields Labels ----------------- ------------------------------------ ------------ ------------- ------------ ------------------- ------------------ -------- 14 Mar 17:16:45 |- word: string (required) 164656 6432064 |- word_count: integer (required) |- corpus: string (required) |- corpus_date: integer (required) student_00_bea2289b69fb@cloudshell:~ (qwiklabs-gcp-00-caaddc51ae14)$ bq help query Python script for interacting with BigQuery. USAGE: bq.py [--global_flags] <command> [--command_flags] [args] query Execute a query. Query should be specified on command line, or passed on stdin. Examples: bq query 'select count(*) from publicdata:samples.shakespeare' echo 'select count(*) from publicdata:samples.shakespeare' | bq query Usage: query [<sql_query>] Flags for query: /usr/lib/google-cloud-sdk/platform/bq/bq.py: --[no]allow_large_results: Enables larger destination table sizes for legacy SQL queries. --[no]append_table: When a destination table is specified, whether or not to append. (default: 'false') --[no]batch: Whether to run the query in batch mode. Ignored if --priority flag is specified. --clustering_fields: Comma-separated list of field names that specifies the columns on which a table is clustered. To remove the clustering, set an empty value. --connection_property: Connection properties; repeat this option to specify a list of values --[no]create_session: Whether to create a new session and run the query in the sesson. --destination_kms_key: Cloud KMS key for encryption of the destination table data. --destination_schema: Schema for the destination table. Either a filename or a comma-separated list of fields in the form name[:type]. (default: '') --destination_table: Name of destination table for query results. (default: '') --display_name: Display name for the created scheduled query configuration. (default: '') --[no]dry_run: Whether the query should be validated without executing. --external_table_definition: Specifies a table name and either an inline table definition or a path to a file containing a JSON table definition to use in the query. The format is "table_name::path_to_file_with_json_def" or "table_name::schema@format=uri@connection". Note using connection is an experimental feature and is still under development.For example, "--external_table_definition=Example::/tmp/example_table_def.txt" will define a table named "Example" using the URIs and schema encoded in example_table_def.txt.; repeat this option to specify a list of values --[no]flatten_results: Whether to flatten nested and repeated fields in the result schema for legacy SQL queries. If not set, the default behavior is to flatten. --job_timeout_ms: Maximum time to run the entire script. --label: A label to set on a query job. The format is "key:value"; repeat this option to specify a list of values --max_child_jobs: Maximum number of child jobs to fetch results from after executing a script. If the number of child jobs exceeds this limit, only the final result will be displayed. (default: '1000') (an integer) -n,--max_rows: How many rows to return in the result. (default: '100') (an integer) --max_statement_results: Maximum number of script statements to display the results for. (default: '100') (an integer) --maximum_billing_tier: The upper limit of billing tier for the query. (an integer) --maximum_bytes_billed: The upper limit of bytes billed for the query. (an integer) --min_completion_ratio: [Experimental] The minimum fraction of data that must be scanned before a query returns. If not set, the default server value (1.0) will be used. (a number in the range [0, 1.0]) --parameter: Either a file containing a JSON list of query parameters, or a query parameter in the form "name:type:value". An empty name produces a positional parameter. The type may be omitted to assume STRING: name::value or ::value. The value "NULL" produces a null value.; repeat this option to specify a list of values --priority: <HIGH|INTERACTIVE|BATCH>: Query priority. If not specified, priority is determined using the --batch flag. Options include: HIGH (only available for whitelisted reservations) INTERACTIVE BATCH --range_partitioning: Enables range partitioning on the table. The format should be "field,start,end,interval". The table will be partitioned based on the value of the field. Field must be a top-level, non-repeated INT64 field. Start, end, and interval are INT64 values defining the ranges. --[no]replace: If true, erase existing contents before loading new data. (default: 'false') --request_id: The request_id to use for the jobs.query request. Only valid when used in combination with --rpc. --[no]require_cache: Whether to only run the query if it is already cached. --[no]require_partition_filter: Whether to require partition filter for queries over this table. Only apply to partitioned table. --[no]rpc: If true, use rpc-style query API instead of jobs.insert(). (default: 'false') --schedule: Scheduled query schedule. If non-empty, this query requests could create a scheduled query understand the customer project. See https://cloud.google.com/appengine/docs/flexible/python/scheduling-jobs-with-cron-yaml#the_schedule_format for the schedule format --schema_update_option: Can be specified when append to a table, or replace a table partition. When specified, the schema of the destination table will be updated with the schema of the new data. One or more of the following options can be specified: ALLOW_FIELD_ADDITION: allow new fields to be added ALLOW_FIELD_RELAXATION: allow relaxing required fields to nullable; repeat this option to specify a list of values --script_statement_byte_budget: Maximum bytes that can be billed for any statement in a script. --script_statement_timeout_ms: Maximum time to complete each statement in a script. --session_id: An existing session id where the query will be run. -s,--start_row: First row to return in the result. (default: '0') (an integer) --target_dataset: Target dataset used to create scheduled query. --time_partitioning_expiration: Enables time based partitioning on the table and sets the number of seconds for which to keep the storage for the partitions in the table. The storage in a partition will have an expiration time of its partition time plus this value. (an integer) --time_partitioning_field: Enables time based partitioning on the table and the table will be partitioned based on the value of this field. If time based partitioning is enabled without this value, the table will be partitioned based on the loading time. --time_partitioning_type: Enables time based partitioning on the table and set the type. The default value is DAY, which will generate one partition per day. Other supported values are HOUR, MONTH, and YEAR. --udf_resource: The URI or local filesystem path of a code file to load and evaluate immediately as a User-Defined Function resource.; repeat this option to specify a list of values --[no]use_cache: Whether to use the query cache to avoid rerunning cached queries. --[no]use_legacy_sql: Whether to use Legacy SQL for the query. If not set, the default value is true. absl.flags: --flagfile: Insert flag definitions from the given file into the command line. (default: '') --undefok: comma-separated list of flag names that it is okay to specify on the command line even if the program does not define a flag with that name. IMPORTANT: flags in this list that have arguments MUST use the --flag=value format. (default: '') Run 'bq.py --help' to get help for global flags. Run 'bq.py help' to see the list of available commands. student_00_bea2289b69fb@cloudshell:~ (qwiklabs-gcp-00-caaddc51ae14)$ bq query --use_legacy_sql=false \ 'SELECT word, SUM(word_count) AS count FROM `bigquery-public-data`.samples.shakespeare WHERE word LIKE "%raisin%" GROUP BY word' +---------------+-------+ | word | count | +---------------+-------+ | praising | 8 | | Praising | 4 | | raising | 5 | | dispraising | 2 | | dispraisingly | 1 | | raisins | 1 | +---------------+-------+ student_00_bea2289b69fb@cloudshell:~ (qwiklabs-gcp-00-caaddc51ae14)$ bq query --use_legacy_sql=false \ 'SELECT word FROM `bigquery-public-data`.samples.shakespeare WHERE word = "huzzah"' student_00_bea2289b69fb@cloudshell:~ (qwiklabs-gcp-00-caaddc51ae14)$ bq ls student_00_bea2289b69fb@cloudshell:~ (qwiklabs-gcp-00-caaddc51ae14)$ 200~bq ls bigquery-public-data:~ -bash: 200~bq: command not found student_00_bea2289b69fb@cloudshell:~ (qwiklabs-gcp-00-caaddc51ae14)$ bq ls student_00_bea2289b69fb@cloudshell:~ (qwiklabs-gcp-00-caaddc51ae14)$ bq ls bigquery-public-data: datasetId ------------------------------------- austin_311 austin_bikeshare austin_crime austin_incidents austin_waste baseball bitcoin_blockchain blackhole_database bls bls_qcew breathe broadstreet_adi catalonian_mobile_coverage catalonian_mobile_coverage_eu census_bureau_acs census_bureau_construction census_bureau_international census_bureau_usa census_utility cfpb_complaints chicago_crime chicago_taxi_trips cloud_storage_geo_index cms_codes cms_medicare cms_synthetic_patient_data_omop covid19_aha covid19_ecdc covid19_ecdc_eu covid19_geotab_mobility_impact covid19_geotab_mobility_impact_eu covid19_google_mobility covid19_google_mobility_eu covid19_govt_response covid19_italy covid19_italy_eu covid19_jhu_csse covid19_jhu_csse_eu covid19_nyt covid19_open_data covid19_open_data_eu covid19_public_forecasts covid19_public_forecasts_asia_ne1 covid19_rxrx19 covid19_symptom_search covid19_tracking covid19_usafacts covid19_vaccination_access covid19_vaccination_search_insights covid19_weathersource_com student_00_bea2289b69fb@cloudshell:~ (qwiklabs-gcp-00-caaddc51ae14)$ bq mk babynames Dataset 'qwiklabs-gcp-00-caaddc51ae14:babynames' successfully created. student_00_bea2289b69fb@cloudshell:~ (qwiklabs-gcp-00-caaddc51ae14)$ bq ls datasetId ----------- babynames student_00_bea2289b69fb@cloudshell:~ (qwiklabs-gcp-00-caaddc51ae14)$ curl -LO http://www.ssa.gov/OACT/babynames/names.zip % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 100 7231k 100 7231k 0 0 270k 0 0:00:26 0:00:26 --:--:-- 294k student_00_bea2289b69fb@cloudshell:~ (qwiklabs-gcp-00-caaddc51ae14)$ ls names.zip README-cloudshell.txt student_00_bea2289b69fb@cloudshell:~ (qwiklabs-gcp-00-caaddc51ae14)$ unzip names.zip Archive: names.zip inflating: yob1880.txt inflating: yob1881.txt inflating: yob1882.txt inflating: yob1883.txt inflating: yob1884.txt inflating: yob1885.txt inflating: yob1886.txt inflating: yob1887.txt inflating: yob1888.txt inflating: yob1889.txt inflating: yob1890.txt inflating: yob1891.txt inflating: yob1892.txt inflating: yob1893.txt inflating: yob1894.txt inflating: yob1895.txt inflating: yob1896.txt inflating: yob1897.txt inflating: yob1898.txt inflating: yob1899.txt inflating: yob1900.txt inflating: yob1901.txt inflating: yob1902.txt inflating: yob1903.txt inflating: yob1904.txt inflating: yob1905.txt inflating: yob1906.txt inflating: yob1907.txt inflating: yob1908.txt inflating: yob1909.txt inflating: yob1910.txt inflating: yob1911.txt inflating: yob1912.txt inflating: yob1913.txt inflating: yob1914.txt inflating: yob1915.txt inflating: yob1916.txt inflating: yob1917.txt inflating: yob1918.txt inflating: yob1919.txt inflating: yob1920.txt inflating: yob1921.txt inflating: yob1922.txt inflating: yob1923.txt inflating: yob1924.txt inflating: yob1925.txt inflating: yob1926.txt inflating: yob1927.txt inflating: yob1928.txt inflating: yob1929.txt inflating: yob1930.txt inflating: yob1931.txt inflating: yob1932.txt inflating: yob1933.txt inflating: yob1934.txt inflating: yob1935.txt inflating: yob1936.txt inflating: yob1937.txt inflating: yob1938.txt inflating: yob1939.txt inflating: yob1940.txt inflating: yob1941.txt inflating: yob1942.txt inflating: yob1943.txt inflating: yob1944.txt inflating: yob1945.txt inflating: yob1946.txt inflating: yob1947.txt inflating: yob1948.txt inflating: yob1949.txt inflating: yob1950.txt inflating: yob1951.txt inflating: yob1952.txt inflating: yob1953.txt inflating: yob1954.txt inflating: yob1955.txt inflating: yob1956.txt inflating: yob1957.txt inflating: yob1958.txt inflating: yob1959.txt inflating: yob1960.txt inflating: yob1961.txt inflating: yob1962.txt inflating: yob1963.txt inflating: yob1964.txt inflating: yob1965.txt inflating: yob1966.txt inflating: yob1967.txt inflating: yob1968.txt inflating: yob1969.txt inflating: yob1970.txt inflating: yob1971.txt inflating: yob1972.txt inflating: yob1973.txt inflating: yob1974.txt inflating: yob1975.txt inflating: yob1976.txt inflating: yob1977.txt inflating: yob1978.txt inflating: yob1979.txt inflating: yob1980.txt inflating: yob1981.txt inflating: yob1982.txt inflating: yob1983.txt inflating: yob1984.txt inflating: yob1985.txt inflating: yob1986.txt inflating: yob1987.txt inflating: yob1988.txt inflating: yob1989.txt inflating: yob1990.txt inflating: yob1991.txt inflating: yob1992.txt inflating: yob1993.txt inflating: yob1994.txt inflating: yob1995.txt inflating: yob1996.txt inflating: yob1997.txt inflating: yob1998.txt inflating: yob1999.txt inflating: yob2000.txt inflating: yob2001.txt inflating: yob2002.txt inflating: yob2003.txt inflating: yob2004.txt inflating: yob2005.txt inflating: yob2006.txt inflating: yob2007.txt inflating: yob2008.txt inflating: yob2009.txt inflating: yob2010.txt inflating: yob2011.txt inflating: yob2012.txt inflating: yob2013.txt inflating: yob2014.txt inflating: yob2015.txt inflating: yob2016.txt inflating: yob2017.txt inflating: yob2018.txt inflating: yob2019.txt inflating: yob2020.txt inflating: yob2021.txt inflating: NationalReadMe.pdf student_00_bea2289b69fb@cloudshell:~ (qwiklabs-gcp-00-caaddc51ae14)$ ls names.zip yob1888.txt yob1899.txt yob1910.txt yob1921.txt yob1932.txt yob1943.txt yob1954.txt yob1965.txt yob1976.txt yob1987.txt yob1998.txt yob2009.txt yob2020.txt NationalReadMe.pdf yob1889.txt yob1900.txt yob1911.txt yob1922.txt yob1933.txt yob1944.txt yob1955.txt yob1966.txt yob1977.txt yob1988.txt yob1999.txt yob2010.txt yob2021.txt README-cloudshell.txt yob1890.txt yob1901.txt yob1912.txt yob1923.txt yob1934.txt yob1945.txt yob1956.txt yob1967.txt yob1978.txt yob1989.txt yob2000.txt yob2011.txt yob1880.txt yob1891.txt yob1902.txt yob1913.txt yob1924.txt yob1935.txt yob1946.txt yob1957.txt yob1968.txt yob1979.txt yob1990.txt yob2001.txt yob2012.txt yob1881.txt yob1892.txt yob1903.txt yob1914.txt yob1925.txt yob1936.txt yob1947.txt yob1958.txt yob1969.txt yob1980.txt yob1991.txt yob2002.txt yob2013.txt yob1882.txt yob1893.txt yob1904.txt yob1915.txt yob1926.txt yob1937.txt yob1948.txt yob1959.txt yob1970.txt yob1981.txt yob1992.txt yob2003.txt yob2014.txt yob1883.txt yob1894.txt yob1905.txt yob1916.txt yob1927.txt yob1938.txt yob1949.txt yob1960.txt yob1971.txt yob1982.txt yob1993.txt yob2004.txt yob2015.txt yob1884.txt yob1895.txt yob1906.txt yob1917.txt yob1928.txt yob1939.txt yob1950.txt yob1961.txt yob1972.txt yob1983.txt yob1994.txt yob2005.txt yob2016.txt yob1885.txt yob1896.txt yob1907.txt yob1918.txt yob1929.txt yob1940.txt yob1951.txt yob1962.txt yob1973.txt yob1984.txt yob1995.txt yob2006.txt yob2017.txt yob1886.txt yob1897.txt yob1908.txt yob1919.txt yob1930.txt yob1941.txt yob1952.txt yob1963.txt yob1974.txt yob1985.txt yob1996.txt yob2007.txt yob2018.txt yob1887.txt yob1898.txt yob1909.txt yob1920.txt yob1931.txt yob1942.txt yob1953.txt yob1964.txt yob1975.txt yob1986.txt yob1997.txt yob2008.txt yob2019.txt student_00_bea2289b69fb@cloudshell:~ (qwiklabs-gcp-00-caaddc51ae14)$ bq load babynames.names2010 yob2010.txt name:string,gender:string,count:integer Upload complete. Waiting on bqjob_r51f4afab0a557e40_00000181441c98fc_1 ... (1s) Current status: DONE student_00_bea2289b69fb@cloudshell:~ (qwiklabs-gcp-00-caaddc51ae14)$ bq ls babynames tableId Type Labels Time Partitioning Clustered Fields ----------- ------- -------- ------------------- ------------------ names2010 TABLE student_00_bea2289b69fb@cloudshell:~ (qwiklabs-gcp-00-caaddc51ae14)$ bq show babynames.names2010 Table qwiklabs-gcp-00-caaddc51ae14:babynames.names2010 Last modified Schema Total Rows Total Bytes Expiration Time Partitioning Clustered Fields Labels ----------------- ------------------- ------------ ------------- ----------------- ------------------- ------------------ -------- 08 Jun 16:18:57 |- name: string 34089 654791 07 Aug 16:18:57 |- gender: string |- count: integer student_00_bea2289b69fb@cloudshell:~ (qwiklabs-gcp-00-caaddc51ae14)$ bq query "SELECT name,count FROM babynames.names2010 WHERE gender = 'F' ORDER BY count DESC LIMIT 5" Waiting on bqjob_r3d9cdc571f84e7b1_00000181441d69b0_1 ... (0s) Current status: DONE +----------+-------+ | name | count | +----------+-------+ | Isabella | 22925 | | Sophia | 20648 | | Emma | 17354 | | Olivia | 17030 | | Ava | 15436 | +----------+-------+ student_00_bea2289b69fb@cloudshell:~ (qwiklabs-gcp-00-caaddc51ae14)$ bq query "SELECT name,count FROM babynames.names2010 WHERE gender = 'M' ORDER BY count ASC LIMIT 5" Waiting on bqjob_r7c3e7c9d164aeee6_00000181441d9d21_1 ... (0s) Current status: DONE +----------+-------+ | name | count | +----------+-------+ | Aaqib | 5 | | Aaidan | 5 | | Aadhavan | 5 | | Aarian | 5 | | Aamarion | 5 | +----------+-------+ student_00_bea2289b69fb@cloudshell:~ (qwiklabs-gcp-00-caaddc51ae14)$ bq rm -r babynames rm: remove dataset 'qwiklabs-gcp-00-caaddc51ae14:babynames'? (y/N) y student_00_bea2289b69fb@cloudshell:~ (qwiklabs-gcp-00-caaddc51ae14)$ ls names.zip yob1888.txt yob1899.txt yob1910.txt yob1921.txt yob1932.txt yob1943.txt yob1954.txt yob1965.txt yob1976.txt yob1987.txt yob1998.txt yob2009.txt yob2020.txt NationalReadMe.pdf yob1889.txt yob1900.txt yob1911.txt yob1922.txt yob1933.txt yob1944.txt yob1955.txt yob1966.txt yob1977.txt yob1988.txt yob1999.txt yob2010.txt yob2021.txt README-cloudshell.txt yob1890.txt yob1901.txt yob1912.txt yob1923.txt yob1934.txt yob1945.txt yob1956.txt yob1967.txt yob1978.txt yob1989.txt yob2000.txt yob2011.txt yob1880.txt yob1891.txt yob1902.txt yob1913.txt yob1924.txt yob1935.txt yob1946.txt yob1957.txt yob1968.txt yob1979.txt yob1990.txt yob2001.txt yob2012.txt yob1881.txt yob1892.txt yob1903.txt yob1914.txt yob1925.txt yob1936.txt yob1947.txt yob1958.txt yob1969.txt yob1980.txt yob1991.txt yob2002.txt yob2013.txt yob1882.txt yob1893.txt yob1904.txt yob1915.txt yob1926.txt yob1937.txt yob1948.txt yob1959.txt yob1970.txt yob1981.txt yob1992.txt yob2003.txt yob2014.txt yob1883.txt yob1894.txt yob1905.txt yob1916.txt yob1927.txt yob1938.txt yob1949.txt yob1960.txt yob1971.txt yob1982.txt yob1993.txt yob2004.txt yob2015.txt yob1884.txt yob1895.txt yob1906.txt yob1917.txt yob1928.txt yob1939.txt yob1950.txt yob1961.txt yob1972.txt yob1983.txt yob1994.txt yob2005.txt yob2016.txt yob1885.txt yob1896.txt yob1907.txt yob1918.txt yob1929.txt yob1940.txt yob1951.txt yob1962.txt yob1973.txt yob1984.txt yob1995.txt yob2006.txt yob2017.txt yob1886.txt yob1897.txt yob1908.txt yob1919.txt yob1930.txt yob1941.txt yob1952.txt yob1963.txt yob1974.txt yob1985.txt yob1996.txt yob2007.txt yob2018.txt yob1887.txt yob1898.txt yob1909.txt yob1920.txt yob1931.txt yob1942.txt yob1953.txt yob1964.txt yob1975.txt yob1986.txt yob1997.txt yob2008.txt yob2019.txt student_00_bea2289b69fb@cloudshell:~ (qwiklabs-gcp-00-caaddc51ae14)$ bq rm -r babynames BigQuery error in rm operation: Not found: Dataset qwiklabs-gcp-00-caaddc51ae14:babynames.

No description available

lib-flexible

读lib-flexible源码

Library to implement flexible leraning proposals

anyproxy本地代理预发在线小栗子 添加firefly(火萤)调试工具

vue中使用手淘的 lib-flexible