-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Please people make the guy writing the WSF's life easier #45
Comments
Also, view the current WSF here: https://github.com/ElementalCode/Elemental/wiki/WSF-Format |
I'd recommend something like this to avoid cluttered block categories and because your forgetting the fact you can drag blocks and scripts: [
{
scriptType: "html",
position: {
x: 100,
y: 100
},
scriptContent: [
{
type: "c-container",
data: {
values: {
tag: "header",
attr: {}
}
},
content: {
}
},
{
type: "c-container",
data: {
values: {
tag: "body",
attr: {
"lang": "en"
}
}
},
content: {
}
}
]
}
] This would be much more expandable and flexible. |
As long as you can compile the HTML and CSS blocks to this - |
:/ |
Seemed basically the same. |
I'll use something like robin's. |
Could you at least check out and mess around with the npm links I gave? It'd be a lot easier to write compilers that way. |
That's not block-based tho |
Yeah, I mean compile the blocks into that JSON format |
We can easly write out own parser. |
What I don't like it you have body and head as seperate blocks. You can't have more than one body, so there's no point! |
I vote the npm packages and GH repo, but let's wait for some other people's input. |
robin's |
I vote robin's |
@Firedrake969 You'd be having to recompile the project every time when you load it and saving would loose you so much data. @an-OK-squirrel my idea litterly has 2 blocks and the rest are data types such as attribute blocks and tag blocks. having seperate blocks of head and body would over complicate things and make saving a little more complicated |
What I'm saying is that I like head and body being combined into one block. |
lose* also, for CSS - |
btw PJ and I did talk about this earlier... |
Yes, what quat said. Like that :P |
Yeah, I know |
If we we're to combine it, there would be multiple c blocks with and without the tag selectors and it would just be alot more complicated to save. |
What? |
Just realised this is still closed. :P |
I still think that we should allow html tags inside of the c block as it would limit advanced users. There is no harm in doing so |
Do you mean, like, typing in custom html tags? If we have every html tag in the dropdown, we don't need to allow typing. But something like a dropdown that also lets you type in stuff into it yeah nice |
Yeah, I'm going to go back to working now. Seeya :P |
Basically what that means is that I'm not listening to any of the suggestions from now to when I finish it. |
Which was why I closed this. (Looking at you, @quat1024. :3) |
Just want to give everyone a quick heads-up: I updated the project goal in the
|
Yes! Closing this and working now. |
Robin, you're misunderstanding me and getting confused. You keep mentioning "your" format - what makes you think we're using it? We're just trying to persuade each other here xD Anyways. Hope you guys all see what I'm getting at - purely the back-and-forth conversion of HTML/JSON so the user can open up their project in a browser after someone writes the block parser to the JSON format. about age - I won't disclose my age, but you should be able to get a good idea if you've read my Scratch stuff before (About Me/What I'm Working On) and have seen my other accounts on the Internet. |
@Firedrake969 Of course we would be using a zip to save the exported files.but we cant use it for what you want to use it. We need to save block positions within the project. |
Not really given that there's only one overarching position per page, and that's the HTML/head/body one. |
@quat1024 No I was relating to another suggestion I made about categorized tag blocks/operators. |
Actually, know what we should do? |
@Firedrake969 Yes for now we could do it your way but honestly, may way would support every way of creating a certain layout. Your way doesnt really care about the position of the blocks thus the saved project isn't the project you wanted to save. While your method is easier for humans to read, my method is easier for compiling and viewing within the block editor. |
There is only one position - where the head/body tag grouping is. Anything else is superfluous. It's like putting HTML tags before the DOCTYPE declaration or after the closing html tag. Also, we can just add X and Y coordinates to the JSON object if we really really want the precise position. "My" and "your" methods have nothing to do with readability since humans should never need to see the JSON unless they're the developers, lol anyways I'm going to lock this because I think it's a waste of time until we can actually get blocks working, and it'd be better for everyone to spend their time elswhere for now |
guys, I closed the issue for a reason |
I'm locking it too :P |
I don't want a lock. |
Leave it. |
:/ |
Whatever, it's not a big deal. I just feel that it doesn't do anything since we're all collaborators. |
It was mainly robin arguing with me, so I was just shutting it down. |
kk, also check out #46 |
You mean to just your page, right? We can add to all the other wiki pages, if need be? |
Just to the the format page and block page. |
And post your ideas for the WSF here. Some of the ideas going on here are going to be impossible to do, which sucks for me.
The text was updated successfully, but these errors were encountered: