Relies on #16

Could be similar to this one:

https://material-components.github.io/material-components-web-catalog/#/component/slider

relies on the drag&drop implementation (to move a window by its header or resizing it).

the base class is already in the repo, not functional yet though.

already in progress, not finished yet though.

important, since neo.mjs is now an npm package.

since onHashChange does get triggered initially now, the docs app throws an error when loading.

I am most definitely not a designer, so help on this one would be appreciated.

I can someone comes up with a good idea, we can definitely add a backlink to a company page or linked in profile. Might be one of the easiest ways to show up as a project sponsor.

ideas so far:

( created with https://www.flamingtext.com/Name-Logos/Neo/ )

spinning the auto-generation idea one step further:

we can not only generate the dist dev & prod index files, but could as well generate the non dist ones.

Add a config to listeners like

onlyFireIfMounted: {Boolean}

so that you can limit events to the mounted state. open for different names ;)

Max (elmasse) brought up this topic:

We could set up a separate repository to create a neo.mjs middleware using nodejs & GraphQL.

Take a look at:
https://graphql.org/graphql-js/

https://medium.com/codingthesmartway-com-blog/creating-a-graphql-server-with-node-js-and-express-f6dddc5320e1

This is an epic and probably involves a lot of work.

In short: neo.mjs should have a socket connection to the node server, probably using a custom API.

Schemas defined in the middleware could optionally automatically create models on the client side as well as the other way around. Changes to the data of a middleware schema should automatically update the store data of a bound client-side store as well as the other way around.

Would help for testing buffering of remotely loaded grids & tables.

I could definitely use feedback on this one!

the header links to change when logging in or out

i shortened the tab names to only display the last part of the name (everything behind the last dot),
to keep the width of the tabs shorter.

now it would be nice to add tooltips which show the full name on hover (e.g. when you have multiple tabs with the same name).

new config to enable walking into different months / years using the arrow keys

instead of (or additional to) using the floating mixin, create a Rectangle class which does provide helper methods for aligning components.

e.g. windows, pickers, tooltips

like alignTo(nodeId, 'tl-br');

add zones => t r b l => 0 1 2 3 similar to CSS zones

It would be nice to be able to easily switch between the CSS4 vars themes and the ones not using them.

we are getting one wrong entry at the moment:

Create a local storage provider saving all open tabs to optionally restore the Docs App content when reloading the page.

=> main.mixins.LocalStorage

Both example apps work fine as a standalone app.

Inside the docs app, after showing one example, the other one will not show the content of its store.

Will look into this.

I am thinking about an optional flag for the keyNav. Especially when navigating through the helix items using the arrow keys, it feels like you move 5 / 300 items per second. The reason seems to be that the keydown event does not fire more often in case you keep a key pressed.

My current idea: save the last x onKeyDown events (key & timestamp). In case the same key triggers x times within the time interval y, fire the event handler again with a delay. E.g. the app worker gets the event every 200ms, fire it again with a 100ms delay. If it keeps firing "longer", add 3 delayed handler calls (50, 100, 150ms). OnKeyUp should cancel all timeout calls to stop at the current position.

We could further polish this in case we keep track of the current FPS rate and ensure there is max 1 movement within 1 animation frame (follow up ticket).

Thoughts?

consistency reasons.

Very similar to form.field.triggers.

Needed for menu buttons.

should be easy to implement a custom tag inside our jsdocx parser.

not 100% sure if we even need it anymore. this was a pretty old pre ES6+ modules.

thoughts?

Describe the bug
Example path in getting started guide are wrong

and add content.

they need a border (light gray)

and add content

pass the layout config to the underlying container

Could look like:

Repo is this one: https://github.com/bendavis78/paper-time-picker (examples are broken)

More useful for mobile i guess.

i searched for a couple of hours and it does seem impossible.

added a comment to an already 2 years old bugzilla ticket:

https://bugzilla.mozilla.org/show_bug.cgi?id=1420209

it might help it you add some weight to the mozilla ticket.

exposed as remotes to the app thread

should be pretty straight forward.

we can optionally add a checkbox to the legend to either collapse or disable it.

since the classes are kept in memory anyway, it is not important to delete this reference.

advantage: you can search inside the component tree using the module config.

Relies on #16

The sorting should work similar to tabs inside the chrome browser.

To do this we need to remove the flexbox layout from the tab header toolbar and use style transitions instead.

Since store data objects get changed into "records", i think Nige's idea that a store uses a collection instead of extending it sounds better at this point.

With record i am NOT meaning instances of model, but a more lightweight abstraction of objects.
See: https://github.com/neomjs/neo/blob/dev/src/data/RecordFactory.mjs for details.

Should make the access easier and changing easier.

Using APIs like inside the Real World App, basics on Neo.data.connection.Xhr.

(optional) mode to not select when using the arrow keys. apply a different cls (similar the today cls) and select on enter.

config: selectOnNavigate sounds good to me.

the private repo was using data from my FB friendlist, need to add a new json file pointing to the AI images

the texts should automatically adjust to not match the theme the app was started with.

As a minimum requirement, we should be able to pass the link of an active tab to create it again when reloading the docs app.

Similar to the Real World App.

as a PoC this is implemented inside the docs app, would be nice as a standard feature using a more generic approach.

I found a very nice ES6 based (MIT licensed) example here:

https://shopify.github.io/draggable/

Source example:

https://github.com/Shopify/draggable/blob/master/src/Draggable/Draggable.js

I think neo.mjs should have a similar solution.

It will get a little bit tricky with our workers setup: Main needs to send the relevant events (dragstart, dragenter, dragleave, drop) to App to execute the handler logic, which will then adjust the DOM.

The only bigger issue is the "dragover" event, which fires incredibly often (could get buffered). In case a dragover-handler only uses trivial logic (e.g. no "this"), it could get moved to the main thread.

https://homepage.net/name_generator/

@thorbenziemek pointed me to this one, seems helpful.

we need to generate 1k names and add them to the AI images related json file.

to do so we need to check each image for the gender =/

not exactly a fun task.

the combination breaks right now.

it does not make sense anyway, so there should be check to throw an error if it does get combined at any point.

or setting the position to inline should set hideLabel to false and vice versa.

thoughts?

and show the picker again in case a store.load() happens.

see: jsdoc/jsdoc#1568

we can craft a custom implementation inside our jsdocx parser.
would make a lot of sense to use @Lends instead.

and add content.