Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • Oct 05 2017 17:37

    sakamies on master

    todos (compare)

  • Mar 03 2017 18:37

    sakamies on master

    formatting (compare)

  • Mar 03 2017 18:36

    sakamies on master

    different color for attr/value … deleting empty items added usel… notes and 1 more (compare)

  • Mar 03 2017 18:11

    sakamies on master

    Update README.md (compare)

  • Mar 03 2017 18:10

    sakamies on master

    Update README.md (compare)

  • Mar 03 2017 17:42

    sakamies on master

    keep values tied to their props (compare)

  • Mar 03 2017 16:56

    sakamies on master

    less confusing tag/txt editing … (compare)

  • Mar 03 2017 16:47

    sakamies on master

    some very basic copy & paste sa… (compare)

  • Feb 28 2017 16:49

    sakamies on master

    Update README.md (compare)

  • Feb 28 2017 16:49

    sakamies on master

    Update README.md (compare)

  • Feb 28 2017 16:25
    sakamies closed #6
  • Feb 28 2017 16:23

    sakamies on master

    Update README.md (compare)

  • Feb 28 2017 16:22

    sakamies on master

    Update README.md (compare)

  • Feb 28 2017 16:22

    sakamies on master

    Update README.md (compare)

  • Feb 28 2017 16:22

    sakamies on master

    Update README.md (compare)

  • Feb 27 2017 19:04
    matthewfcarlson opened #6
  • Feb 27 2017 16:32

    sakamies on master

    clean up (compare)

  • Feb 24 2017 18:35

    sakamies on master

    rudimentary copy paste (compare)

  • Feb 23 2017 17:59

    sakamies on master

    styling fix error when trying to add pr… implement additive selection vi… and 1 more (compare)

  • Feb 22 2017 18:46

    sakamies on master

    todo (compare)

Risord
@Risord
So everything something like this is valid input (quite extreme example but still):
<br cellspan="* { color :: red }">
  <mkdir>
    <html a="b">
    <p>
  </mkdir>
</br>
More strict validation can be of course added afterwards
But this A / "format first" it's fine starting point
Risord
@Risord
But about these two possibilities: I don't think these are one or another selections but we can take both. It just question which approach should be taken as starting point.
If strict editing should be added for HTML I would say that even if we are already using A model for editors we still implement model B. We can then use mapper / "lens" / computing microeditor which will transform these models in realtime.
Risord
@Risord
Multi model is one essential feature to be handled
Same way if strict template language editing is wanted we need model "C" (B like implementation for templatete language)
Of course one can say that we don't need these since we have this "universal A" and we can build all syntax checkers on top of that. However I would say that it's pretty hacky solution and if we start supporting CSS / JS whatever non xml like we notice immediadly that model A has nothing universal.
Risord
@Risord
These strict models of course are very long term goals. I would still like to see relatively soon how multi model idea works in practice with some simple models.
Ville V. Vanninen
@sakamies
Again custom components don't belong to html specs
that's true, but they're used all the time in practice
Risord
@Risord
First if that sounded mean I am sorry.
But yea. If HTML model won't support custom template things it won't mean that these template things need to be completely unsupported or live in separated world from user viewpoint.
We have to just define same kind of model for template language as HTML.
Risord
@Risord
And then we would have strict editing which understand both HTML and template language.
But this multidomain thing is complex topic...
I would like to avoid that for beginning
Risord
@Risord
So much posibilities :D
Ville V. Vanninen
@sakamies
what no, I didn't take it as mean :D
Risord
@Risord
I have now done that simple schema for model A (which is almost a toy). I am currently studying shacl playground source code and implementing some simple validation for cycle application.
That shacl playground source is currently propably the best documentation for the validator.
Ville V. Vanninen
@sakamies
oh boy, haven't gotten anything done for a while, this channel needs some life
Risord
@Risord
I will get my side project out at this week. Also I might reduce my day work to 4x8 later this spring so hopefully I get something done soon.
Ville V. Vanninen
@sakamies
found this today, interesting stuff again https://harc.ycr.org/flex/
Risord
@Risord
Hello fellows
I have finally some time to focus for this project
I have also received some stipend from university for prototype
so a bit time - check
back preassure - check
Ville V. Vanninen
@sakamies
👍👍👍
this has been on my mind, but haven't gotten any code done
been thinking hard about making a native app instead of electron/browser based
Risord
@Risord
Some recent HN stuff:
Paper about GUI programming - https://news.ycombinator.com/item?id=14609215
Luna: funded visual/textual hybrid programming enviroment - https://news.ycombinator.com/item?id=14612680
Ecola: simple tree editor prototype, nice zooming effect - https://news.ycombinator.com/item?id=14627646
Pencil: GUI prototype tool (just for doing design) - https://news.ycombinator.com/item?id=14627985
Ville V. Vanninen
@sakamies
nice ones, thanks!
Risord
@Risord
My experiment about data-structure based "multi editor"
https://www.youtube.com/watch?v=CNryKyBPfws
Ville V. Vanninen
@sakamies
wow, looks like quite a contraption, would love to try a demo :h
:j
damn, still can't type :D
Ville V. Vanninen
@sakamies
now that i looked at it on my laptop instead of phone screen, damn, that looks really promising!
Risord
@Risord
I am writing currently doing rewrite for a demo to allow some more future development.
I hope that in next version we could integrate your html editor.
Ville V. Vanninen
@sakamies
exciting!
Risord
@Risord
Demo has been made with Vue I think just in two days but it has some dead-ends.
It has some bugs and therefore I haven't shared a demo because "you have to know few things". However these aren't hard issues anyway but I just don't want put more effort to that version.
Risord
@Risord
I think tough that demo shows it main point quite well: We don't have to pick just one way of interacting things and these mechanisms can be user composeables
Ville V. Vanninen
@sakamies
totally agree, the semo shows that well
Risord
@Risord
Note that those text inputs inside GUI editor are also just another separated editors which can be changed independently.
Risord
@Risord
1:33 is one challenging point: when json is edited and it is invalid it can be considered as detached from rest of the world but as soon as json is valid again it will be synced to structure. Since data backend only stores pure data all whitespace are just from pretty print formatting and all user inserted formatting is exist only temporary. This issue is sadly those "easy to fix bugs" but more fundamental property. I believe strongly that this issue is solavable by storing whitespaces as editor spesific metadata to structure so that from json editor perspective whitespaces exists in structure like whitespaces inside C# / Roslyn AST.
But it's still quite funny. "Text people" build linters to avoid random user inserted formatting mess and we need to put some serious effort to support theses same things :D
"Structural editor doesn't support imperfect formatting by default"
There are also some other simpler ways to live with this "issue".