I'm working on a fun project.
Looks nice! Do you build it all yourself or do you use bootstrap or something similar? How is it talking to the database? Can we expect to download it in the near future?
C'mon Steef, tell us a bit more :)
regarding the paging mechanism ...
most tables, queries we work with are quite big with millions, tens of millions or more rows, for the sake of discussion i would consider them infinite
having a grid that either shows the total number of rows for the table or query, or worst loads everything would be a problem, no?
we decided to base our framework on extjs not telerik but in our framework the grid (connected to a data object/store) loads pages as needed or as you scroll off end, so to speak.
> the grid (connected to a data object/store) loads pages as needed or as you scroll off end, so to speak.
Both are possible, yes, could be in the config info per .html or more central.
Cool stuff! :)
-- Kind regards,
Library select2.js to style select elements.
Curious to see how the open source kendo components will fit
Curious to see how the open source kendo components will fit in my framework!
"Prefer dedicated libraries to monolithic frameworks. When you choose
a framework, you make a large, long term committment. You sign up to
learn about the framework's various inner workings and strange
behaviours. You also sign up to a period of ineffectiveness whilst
you're getting to grips with things. If the framework turns out to be
the wrong bet, you lose a lot. But if you pick and choose from
libraries, you can afford to replace one part of your front end stack
whilst retaining the rest."
"There will never be a perfect framework so you can just hack the
most relevant features together.
By using small libraries - components with a dedicated purpose and a
small surface area - it becomes possible to pick and mix, to swap
parts of our front end stack out if and when they are superceded. New
projects can replace only the parts that matter, whilst core
functionality whose designs are settled - routing APIs, say - can stay
exactly the same between the years."
this post as spam/abuse.
I want a framework that consists of libraries. :-)
(in fact that's what I'm building. loosely coupled components blabla etc.)
Long live the fragmented environment!
Here's a fun take on this discussion: www.stilldrinking.org/programming-sucks
That was a hilarious (and somewhat painfully sad) read! Thanks for sharing it with the community!