Skip to content
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

how to revive fragile? #10

Open
almereyda opened this issue Jun 9, 2014 · 5 comments
Open

how to revive fragile? #10

almereyda opened this issue Jun 9, 2014 · 5 comments

Comments

@almereyda
Copy link

It seems fragile itself was more fragile thant it thought.
Unfortunately most things don't work (anymore?) with it.

As GitHub Stars are messy and gitrep.com is not updated at all, it seems interesting to revive this one and have a handy tool at hands to underst one's own interactions on GitHub a little better.

@bollwyvl
Copy link
Owner

@almereyda thanks for the interest! it is true: i haven't revisited it some time. However, I was able to get it some of the basic stuff working (after authenticating). Maybe anonymous auth went away?

Here's a link that worked:

https://fra.gl/?!config/ipython#
Note: the ! could be anything... not sure why that changed

If I get around to it, perhaps this weekend, I'll try to investigate further, as it seems like some small changes would restore basic functionality.... feel free to PR if you, if you really wanted to dig into it!

However, I would prefer to take this as an opportunity to reassess what it does, and what it could do.

build

I still love flask and jinja, but I would probably start over again with Node for a grunt/gulp build process: at the time, i hadn't done any work in that environment, but I think it would be much more appropriate to the single page architecture approach, as well as managing all of the asset dependencies.

data model

Additionally, instead of the "dumb" data store, I would want to use something at least somewhat better: there are a couple dimensions that would be interesting:

app logic

the data model would inform this, but using something like derby-standalone

visualization

I really like some of the developments in creating more "predicatable" d3 charts:

Insight welcome!

@almereyda
Copy link
Author

Wow, raw and vega kick asses.

You know, unfortunately I have to admit once again, I am not that much of a real developer, more a human search engine that's browsing the web for nifty tidbits to give to people.

Also, if we're already talking buzz, http://ampersandjs.com/ could be for you. Or one goes directly into direction of ES6 and does Ember.

How could I assist anyhow?

@bollwyvl
Copy link
Owner

Use cases always help: how can fragile (or something like it but better)
help you and your project? My initial interest was in "ecosystem" projects
that have many repos, mailing lists, etc.

I haven't spent any quality time with ember. & looks cool, though!

I think Vega is really appropriate for the kinds of information we'll
have... While raw has really great ui fundamentals, though navigation could
be a bit better, especially on mobile. I don't have the Angular chops to
pitch in there, though.

I wasn't trying to go crazy buzzword on you! I just meant that my initial
"free form" app uses arrays of dumb objects, and that many of the
frameworks offer nice object lifecycle events, which are useful no matter
how one builds DOM.

Wow, raw and vega kick asses.

You know, unfortunately I have to admit once again, I am not that much of a
real developer, more a human search engine that's browsing the web for
nifty tidbits to give to people.

Also, if we're already talking buzz, http://ampersandjs.com/ could be for
you. Or one goes directly into direction of ES6 and does Ember.

How could I assist anyhow?


Reply to this email directly or view it on GitHub
#10 (comment).

@almereyda
Copy link
Author

ping @elf-pavlik

@almereyda
Copy link
Author

The use case regarding @ouisharelabs would be to have some kind of collaborative dashboard, that shows us our aggregated group activity within different repos, as we try to build infrastructures that rely on small components as well as full-blown applications.

Additionally, my GitHub stars will soon pass the 1.000 mark and the are hard to maintain. A simple tagging interface would already be enough, as I said in the initial comment.

Additionally, hell yes, why not rebuild fragile on top of https://github.com/spumko/hapi with help of gulp. I'd be interested in seeing that grow and use. Also see http://fed.coevolving.com/view/digest-2014-06-18/view/digests-from-sfw-meetings/view/digest-2014-07-09 for elaborations of Node web frameworks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants