webui-client issueshttps://gitlab.fit.cvut.cz/algorithms-library-toolkit/webui-client/-/issues2022-12-04T12:36:44+01:00https://gitlab.fit.cvut.cz/algorithms-library-toolkit/webui-client/-/issues/92Grammars can't have digits as terminals2022-12-04T12:36:44+01:00Filip GregorGrammars can't have digits as terminalsSee the image
![image](/uploads/10f155a65a3774ec6e520d0e5d35b555/image.png)See the image
![image](/uploads/10f155a65a3774ec6e520d0e5d35b555/image.png)Tomáš PeckaTomáš Pecka2022-12-01https://gitlab.fit.cvut.cz/algorithms-library-toolkit/webui-client/-/issues/91Internal error after Determinize -> Total2022-10-19T21:56:59+02:00Tomáš PeckaInternal error after Determinize -> Totalhttps://alt.fit.cvut.cz/webui/?s=6ABabzH7jr3jIWuDLPlkkjhttps://alt.fit.cvut.cz/webui/?s=6ABabzH7jr3jIWuDLPlkkjTomáš PeckaTomáš Pecka2022-10-19https://gitlab.fit.cvut.cz/algorithms-library-toolkit/webui-client/-/issues/81Check keys in dialog components2022-10-18T09:31:48+02:00Hana LitavskáCheck keys in dialog componentsCheck prop key in
* input dialog
* input grammar
* output dialog
* output grammar
input automaton table and output automaton table should be ok now.Check prop key in
* input dialog
* input grammar
* output dialog
* output grammar
input automaton table and output automaton table should be ok now.Hana LitavskáHana Litavskáhttps://gitlab.fit.cvut.cz/algorithms-library-toolkit/webui-client/-/issues/90Automaton/grammar input box: table and string should show the same input when...2022-10-16T14:56:43+02:00Tomáš PeckaAutomaton/grammar input box: table and string should show the same input when switchingIf you write input in the table then it is not persisted in the text area. Let's implement shared state and only fill the data.If you write input in the table then it is not persisted in the text area. Let's implement shared state and only fill the data.Tomáš PeckaTomáš Peckahttps://gitlab.fit.cvut.cz/algorithms-library-toolkit/webui-client/-/issues/87Automaton input - Tab jumps to wrong field2022-10-04T13:19:12+02:00Filip GregorAutomaton input - Tab jumps to wrong fieldWhen using the Input node with type Automaton, Table format, the cursor sometimes dissapears when creating new row.
How to reproduce:
- Create input node, Automaton, Table.
- Write into first row some states and press enter.
- This crea...When using the Input node with type Automaton, Table format, the cursor sometimes dissapears when creating new row.
How to reproduce:
- Create input node, Automaton, Table.
- Write into first row some states and press enter.
- This creates new row, try to write single letter, the cursor should dissapear after that.
- It also happens when you try to write under the delta, when writing one symbol the cursor immediately dissapers. This does not seem to happen when writing under the other columns.
It is particularly annoying when trying to tab to next field.
Tested on Firefox and Chromium.Tomáš PeckaTomáš Peckahttps://gitlab.fit.cvut.cz/algorithms-library-toolkit/webui-client/-/issues/88Input Automaton Table doesn't accept digits as symbols2022-10-04T09:55:31+02:00Filip GregorInput Automaton Table doesn't accept digits as symbols![image](/uploads/86cc4dcbeba99af1c2cf8a70e40ca918/image.png)![image](/uploads/86cc4dcbeba99af1c2cf8a70e40ca918/image.png)Tomáš PeckaTomáš Peckahttps://gitlab.fit.cvut.cz/algorithms-library-toolkit/webui-client/-/issues/36Latex Converter2022-05-15T22:59:17+02:00Tomáš PeckaLatex ConverterThe latex converter should probably be a priority now. When composing a text table output for automata with states labelled like `{A,B,C}` or `(a, 1)`, the output gets quite messy because the columns are unaligned.The latex converter should probably be a priority now. When composing a text table output for automata with states labelled like `{A,B,C}` or `(a, 1)`, the output gets quite messy because the columns are unaligned.Tomáš PeckaTomáš Peckahttps://gitlab.fit.cvut.cz/algorithms-library-toolkit/webui-client/-/issues/76Adapt to changes in Determinize registrations in the core2022-05-14T19:25:38+02:00Tomáš PeckaAdapt to changes in Determinize registrations in the coreCommit https://gitlab.fit.cvut.cz/algorithms-library-toolkit/automata-library/commit/1a4de925c48aace75ff364fbc85dc7d8ffac5924?merge_request_iid=227 in the core merged all the no-op Determinize overloads into one.
This brings two issues....Commit https://gitlab.fit.cvut.cz/algorithms-library-toolkit/automata-library/commit/1a4de925c48aace75ff364fbc85dc7d8ffac5924?merge_request_iid=227 in the core merged all the no-op Determinize overloads into one.
This brings two issues.
First, the edges between boxes report cast issue
```
Type
automaton::DFA<Universal type, unsigned>
is not castable to type
variant<
automaton::DFA<Universal type, Universal type>,
automaton::DFTA<Universal type, Universal type>,
automaton::DPDA<Universal type, Universal type, Universal type>,
automaton::InputDrivenDPDA<Universal type, Universal type, Universal type>,
automaton::OneTapeDTM<Universal type, Universal type>,
automaton::RealTimeHeightDeterministicDPDA<Universal type, Universal type, Universal type>,
automaton::SinglePopDPDA<Universal type, Universal type, Universal type>,
automaton::UnorderedDFTA<Universal type, Universal type>,
automaton::VisiblyPushdownDPDA<Universal type, Universal type, Universal type>
>
```
Second, the overload in the algorithm list now reports this and I have no idea how to report the types of the variants.
![Snímek_z_2022-03-26_09-38-27](/uploads/0b0e5d260f70be57d0bd7240b9e9ad6a/Snímek_z_2022-03-26_09-38-27.png)
cc @travnja3 Tomáš PeckaTomáš Peckahttps://gitlab.fit.cvut.cz/algorithms-library-toolkit/webui-client/-/issues/82Introduce parser generators for ALT formats2022-05-13T12:04:50+02:00Tomáš PeckaIntroduce parser generators for ALT formatsThese handwritten parsers are hard to maintain.
Look e.g. into [peggy.js](https://github.com/peggyjs/peggy), the successor of peg.jsThese handwritten parsers are hard to maintain.
Look e.g. into [peggy.js](https://github.com/peggyjs/peggy), the successor of peg.jsTomáš PeckaTomáš Peckahttps://gitlab.fit.cvut.cz/algorithms-library-toolkit/webui-client/-/issues/37Restyle algorithm overload list element - it is too large2022-05-13T08:27:37+02:00Tomáš PeckaRestyle algorithm overload list element - it is too largeThe algorithm overload div still takes a lot of space. Finding a specific overload for algorithms like `string::Compose` is pain.
![Screenshot_2020-10-12_ALT_WebUI](/uploads/35f9c51bc59a60a4d7913ca459a1afb6/Screenshot_2020-10-12_ALT_Web...The algorithm overload div still takes a lot of space. Finding a specific overload for algorithms like `string::Compose` is pain.
![Screenshot_2020-10-12_ALT_WebUI](/uploads/35f9c51bc59a60a4d7913ca459a1afb6/Screenshot_2020-10-12_ALT_WebUI.png)
Ideas how to improve it:
- name of argument and its type can be on a single line. If the name of the argument is longer than (lets say) 15 characters, abbreviate it with `...`.
- I was actually thinking about removing the name of the parameter and repace it with the input index. But I see that we reference the name in the docs. This is something that can't probably be done better (parsing doxygen? probably not, thank you). In the future we should solve this on the `automata-library` level. Maybe use a docstring for each parameter separatelyinstead of the full doxygen (what do you think, @travnja3 ?)
- Result and its type similarly
- Smaller margins around those <code>hr</code> tags and Result and Parameters headers.
I think making it smaller at least about one third would be desirable.BPhttps://gitlab.fit.cvut.cz/algorithms-library-toolkit/webui-client/-/issues/70worker: Remove pipe communication2022-05-11T23:44:58+02:00Tomáš Peckaworker: Remove pipe communicationSee https://gitlab.fit.cvut.cz/algorithms-library-toolkit/automata-library/issues/223See https://gitlab.fit.cvut.cz/algorithms-library-toolkit/automata-library/issues/223Tomáš PeckaTomáš Peckahttps://gitlab.fit.cvut.cz/algorithms-library-toolkit/webui-client/-/issues/50Filter ALT algorithms2022-05-10T19:53:39+02:00Tomáš PeckaFilter ALT algorithmsI don't think we want to map all the provided algorithms from ALT 1:1. For instance, I don't think we need `example::*` algos.
So let's either
* write a filter for some algorithms
* do not link some libs to the result.
This is someth...I don't think we want to map all the provided algorithms from ALT 1:1. For instance, I don't think we need `example::*` algos.
So let's either
* write a filter for some algorithms
* do not link some libs to the result.
This is something that should probably be done in cooperation with #40.BPhttps://gitlab.fit.cvut.cz/algorithms-library-toolkit/webui-client/-/issues/65We don't need to list all overloadeded functions2022-05-10T19:21:55+02:00Tomáš PeckaWe don't need to list all overloadeded functionsAs of now, we list all overloads of a function, e.g. `string::Compose`.
When user selects a `string::Compose` for e.g. `alphabet::BarSymbol` instead of `automaton::DFA`, it works, because the selection of the overload is left to the ALT,...As of now, we list all overloads of a function, e.g. `string::Compose`.
When user selects a `string::Compose` for e.g. `alphabet::BarSymbol` instead of `automaton::DFA`, it works, because the selection of the overload is left to the ALT, so it is actually not needed.
But we give user a visual warning that he chose a wrong overload (even if it works).
I'd like this to change.
* Let's list only one overload in the algorithm menu with a dropdown bar that shows all of them with appropriate docs (should the docs differ for every overload or should we unify the docs for all overloads?).
* Let's give the warning to the user only if he connects an edge from the box with a return value that cannot be used is absolutely not viable, i.e., it can't be used as an input for any of the overloads.
* However I am not sure how to deal with outputs of such overloaded box. Should we guess what the output is?BPHana LitavskáHana Litavskáhttps://gitlab.fit.cvut.cz/algorithms-library-toolkit/webui-client/-/issues/75Add a form for automaton input2022-05-02T23:07:39+02:00Hana LitavskáAdd a form for automaton inputAdd form for table input. Discussed here https://gitlab.fit.cvut.cz/algorithms-library-toolkit/webui-client/issues/51Add form for table input. Discussed here https://gitlab.fit.cvut.cz/algorithms-library-toolkit/webui-client/issues/51BPhttps://gitlab.fit.cvut.cz/algorithms-library-toolkit/webui-client/-/issues/80Let output nodes decide their features from the actual visualized type2022-04-25T17:15:15+02:00Jan TrávníčekLet output nodes decide their features from the actual visualized typehttps://gitlab.fit.cvut.cz/algorithms-library-toolkit/webui-client/merge_requests/47#note_276115https://gitlab.fit.cvut.cz/algorithms-library-toolkit/webui-client/merge_requests/47#note_276115Tomáš PeckaTomáš Peckahttps://gitlab.fit.cvut.cz/algorithms-library-toolkit/webui-client/-/issues/64Filter by return type / argument types2022-04-25T14:06:13+02:00Hana LitavskáFilter by return type / argument typesBPhttps://gitlab.fit.cvut.cz/algorithms-library-toolkit/webui-client/-/issues/51(Finite) Automaton output nodes2022-04-20T19:02:48+02:00Tomáš Pecka(Finite) Automaton output nodesI think we should create a new outputnode that will parse the automaton and display it as a [table](https://v4.mui.com/components/tables/).
Or, alternatively, we could merge this into the DotOutput node and add two [tabs](https://v4.mui...I think we should create a new outputnode that will parse the automaton and display it as a [table](https://v4.mui.com/components/tables/).
Or, alternatively, we could merge this into the DotOutput node and add two [tabs](https://v4.mui.com/components/tabs/) there (Table, Dot) so user can easily see both versions.
Personally, I like the later version but adding "Discussion needed" label.BPhttps://gitlab.fit.cvut.cz/algorithms-library-toolkit/webui-client/-/issues/71Add input and output boxes with Parse2022-04-19T17:35:22+02:00Hana LitavskáAdd input and output boxes with ParseAdd input and output boxes for string input that will be parsed to grammar, automaton... Using string::Parse templated algorithm.Add input and output boxes for string input that will be parsed to grammar, automaton... Using string::Parse templated algorithm.BPHana LitavskáHana Litavskáhttps://gitlab.fit.cvut.cz/algorithms-library-toolkit/webui-client/-/issues/77Fix grammar form validation for digits2022-04-17T10:59:25+02:00Hana LitavskáFix grammar form validation for digitsSymbol shouldn't start with digit.
When symbol `0b` is input and is submited with DONE button, the snackbar with error is shown but the form will close anyway and must be reopened for correction.Symbol shouldn't start with digit.
When symbol `0b` is input and is submited with DONE button, the snackbar with error is shown but the form will close anyway and must be reopened for correction.https://gitlab.fit.cvut.cz/algorithms-library-toolkit/webui-client/-/issues/78Grammar form does not add initial symbol into grammar's alphabet2022-04-17T10:59:25+02:00Tomáš PeckaGrammar form does not add initial symbol into grammar's alphabet![gform](/uploads/9062dcddd6ac144c9f5edd12b2c9df7d/gform.gif)
Tested on: d4d1827289b00de1564385547d640497e86c4dbb
![gform](/uploads/9062dcddd6ac144c9f5edd12b2c9df7d/gform.gif)
Tested on: d4d1827289b00de1564385547d640497e86c4dbb
Hana LitavskáHana Litavská