search

meteor / blaze

:fire: Meteor Blaze is a powerful library for creating live-updating user interfaces
http://blazejs.org/
Other
528 stars 115 forks source link

List of potential changes to Blaze #75

Closed mitar closed 3 years ago

mitar commented 8 years ago

Just a list of some ideas I have what we could change in Blaze to make it a bit better, keep the good parts and move on. Some of them might be breakable so we should see how to integrate this. Personally, I would like to see that we do just incremental changes. One thing to do that would be to introduce components. Then <template>s could be seen simply as a HTML fragments with placeholders you can reuse, without any logic. This is what I also started with Blaze Components.

But the new components (in contrast with Blaze Components) would have some changes. I will be making it a lit of comments for each of those so that community can upvote/downvote them.

Please write only ideas (and variations of existing ideas). If you want to discuss details of an idea implementation, process, roadmap, open a ticket for that particular idea (we can update then its comment here with a link to the ticket).

What are your ideas? What would you like to improve in Blaze?

mitar commented 8 years ago

You should definitely check out guide because this is probably what is most suitable for there, no? But I would love to have that for blazejs as well, it seems that blazejs will be then more like "meteor classic" or what. :-) But yea, open a ticket/pull request and let's discuss it there.

LaughingBubba commented 8 years ago

The guide is awsome and did not happen overnight. I'm just trying to capture that "wow" moment back in the 1.0 days. You did not need a monster guide back then cuz blaze templates and handlers were quite understandable. Anyways I think these up in rough form and throw it out there and if I've done the job right it'll be self evident. If so then we figure where it sits. Cheers.

mitar commented 8 years ago

Sounds amazing! Go for it! :-)

alexandesigner commented 8 years ago

Guys.. I don't know if it's the moment, but maybe write a blog (medium)? where would have daily or weekly postings. This could give blaze us a little more visibility and also make new developers interested learn blaze and other things related.. What do you think?

mitar commented 8 years ago

don't know if it's the moment, but maybe write a blog (medium)? where would have daily or weekly postings. This could give blaze us a little more visibility and also make new developers interested learn blaze and other things related.. What do you think?

I personally do not know much what we would write, but if anyone wants to take a lead on that, it could be great! :-) We could probably create Medium publication and then people could just submit posts they would like to be published under that banner? (Maybe the only requirement could be that guest posts have to be true, about Blaze, a good practice, and not too promotional for your own stuff.) I am not sure what we would already post, but maybe even just simple things, maybe just things from the changelog, an example of a change and how this improves something, maybe shoutouts to projects using Blaze, things like that? So yea, if anyone has ideas for this, it could be interesting. I am trying to focus my limited time on more technical things.

We can open another issue to discuss this in more detail (what would be the rules for publishing there guest posts and things like that).

nicooprat commented 8 years ago

If you make the one-file-component happen, please don't forget CSS :) The way VueJS does it looks perfect to me!

PS. Very happy to see Blaze resurrecting :D

mitar commented 8 years ago

@nicooprat: Can you explain a bit more what VueJS does, or provide a link? I do not know of anything special it is doing about CSS?

alexandesigner commented 8 years ago

We can open another issue to discuss this in more detail (what would be the rules for publishing there guest posts and things like that).

Exactly ... from the most basic level to advanced as well as projects using blaze..

I will create a page on @medium and open an issue to discuss how we could make the publications.

Can you explain a bit more what VueJS does, or provide a link? I do not know of anything special it is doing about CSS?

I think he is suggesting something as quoted in another issue ... Single File Components

mitar commented 8 years ago

I will create a page on @medium

You mean a publication?

mitar commented 8 years ago

I think he is suggesting something as quoted in another issue ... Single File Components

Oh, yes. <style> tag along with <template> tag and <script> tag. For sure! :-)

We can also think about ways to do <style> tag scoped to the component.

(Discussion: #110)

alexandesigner commented 8 years ago

You mean a publication?

Exactly

mitar commented 8 years ago

On the other hand, it would be even crazier if <style> would get the same context as <template>. So you could do:

<style>
  .button {
    width: {{width}};
  }
</style>

(Discussion: #110)

aadamsx commented 8 years ago

What do you say about using something like these to help manage this Blaze project?
https://github.com/integrations/feature/project-management

(Discussion: #127)

mitar commented 8 years ago

What do you say about using something like these to help manage this Blaze project?

I looked into GitHub projects when they came out, I do not yet see usefulness for that (mostly, upvotes are not visible). And for integrations with others I tried them in the past but then none really provided so much benefit to me that it would balance the minus you get: people have to search for things in to places, you divide the focus into two places, beginners have issues knowing where something is, you get sometimes things desynced. Just remember Meteor Trello roadmap as an example. This is why I prefer everything to be in one place. So using issues for both discussions, bug reports, and feature requests. And then using extensively labels and milestones for content-based categorization and time-based categorization, respectively.

But if you have a concrete proposal what you think would improve management, please open a new issue with a suggestion.

I think that for now community is small enough that what we have is manageable. And moreover, any extra tool requires extra resources to keep it useful, and those resources I would prefer to direct at Blaze itself for now.

But yes, if you want to propose any concrete one, let's have a discussion in a separate issues for it. Maybe somebody can also volunteer to take it over to manage it.

(Discussion: #127)

mitar commented 8 years ago

But you are right, I think it is time to open separate issues for some of the ideas upvoted above. And start discussing details.

alexandesigner commented 8 years ago

What do you say about using something like these to help manage this Blaze project?

I like the idea.. I think some of these tools could improve the visualization and understanding of what should be done and what has been done.. They are integrated with github

nicooprat commented 8 years ago

@mitar Yes, I mean style tag in the same file, and the possibility to have that CSS scoped to its component, by generating a random ID (http://vue-loader.vuejs.org/en/features/scoped-css.html). It's using webpack though.

(Discussion: #110)

mitar commented 8 years ago

I opened tickets for some of the ideas above.

aadamsx commented 8 years ago

I looked into GitHub projects when they came out, I do not yet see usefulness for that (mostly, upvotes are not visible).

I'm using GitHub projects for internal projects and it helps organize the issues. Basically can can categorize and track issues with GitHub project with a Kanban type board.

I think just having a the following columns will work for

Blaze-Classic project and a Blaze-2.0 project:

> Backlog

> Planning

> To Do

> In Progress

> In Review

> To Pull

I for one am a little confused as to what issues are on the 1. release and which are slated for 2.0. Which are being worked on and by whom. Besides -- it takes nothing away, only adds to our understanding.

(Discussion: #127)

mitar commented 8 years ago

I do not understand what is the advantage over milestones. It is clear what is slatted for future, and what is the next version (2.2). You have a nice list as well, and if users are assigned, you can see that as well.

Besides -- it takes nothing away, only adds to our understanding.

Hm, you have to maintain both the roadmap and projects, no? What if they conflict? So what is the advantage over a project over the roadmap?

BTW, this should go to another issue for discussion. I am not completely opposed to using projects, or whatever, but I have not yet been convinced. Mostly because our current mode of operation is mostly that we respond to random pull requests from people. We do not really have a steady development where we would have dedicated people working on stuff. But if you want to know what would be great to work on, you can, or check those lists:

Volunteers welcome! Pull requests as well.

Or what other problem we want to solve with projects? So planing - for me roadmap works. Knowing what to work on - labels and milestone works as well.

(Discussion: #127)

filipenevola commented 3 years ago

I'm closing this issue because it's too old.

If you think this issue is still relevant please open a new one.

Why? We need to pay attention to all the open items so we should keep opened only items where people are involved.