New PHP Framework

[eluser]Sbioko[/eluser]
Yes, I'll definitely release 0.1 in a few days on GitHub.

[eluser]pbreit[/eluser]
Here's a question I have about frameworks: is it really better to do this in code or in HTML:
http://kerkness.ca/wiki/doku.php?id=how_...dden_field

[eluser]luke holder[/eluser]
[quote author="pbreit" date="1288095930"]Here's a question I have about frameworks: is it really better to do this in code or in HTML:
http://kerkness.ca/wiki/doku.php?id=how_...dden_field[/quote]

You can do either... but if your generating dynamic hidden fields, why wouldn't you use php and the helpers? Otherwise your doing a bunch of string manipulation = boring.

[eluser]pbreit[/eluser]
I guess if they were dynamic, it makes sense to use code. But I like to stay in HTML as much as possible. This one kills me: form_close();

[eluser]Sbioko[/eluser]
Guys, excuse me, but please read the title of the topic. Its not for your CI related problems!

[eluser]pbreit[/eluser]
My comment was a general one about frameworks. I find they frequently do too much stuff that would be better done in HTML or regular php.

[eluser]Sbioko[/eluser]
Aah, ok. Sorry.

[eluser]andyy[/eluser]
Why don't you just build on CI? Like custom hooks, extending the classes and so on, releasing useful plugins to the community where you will undoubtedly receive the fundamental feedback needed all the while extending CI's already great capabilities? Have you ever heard "don't reinvent the wheel - just understand how it works and improve upon its flaws"?

I'm fairly new to CI (~1 year) but not to programming. I see lots of little things that could be better extended and applied upon but don't have the luxury at this moment to start developing plugins. Maybe you should!

Some things I see myself working on in the near future:
-proper jQuery class implementing multiple methods for different uses and also extending to popular UI libraries (jgrowl, jquery UI, mootools, error message methods, specific HTML elements update methods, etc),
-better validation class with more practical rules,
-rapid form development (much like scaffolding only secure),
-better string class,
and so on..

This is just my opinion of course, good on ya if you want to create a new framework.

[eluser]Sbioko[/eluser]
I'll try to be constructive.
Q: Why don't you just build on CI?
A: Because it is not great for me in core. Because of PHP4 support, CI does not have Autoloading, Magic Methods and all those great PHP5 features. To implement support of UTF8, you need to replace all the functions to their mb_* equivalent if you are not able to just turn mbstring.func_overload on. CI's database library allows writing only SQL drivers. You can't write MongoDB or CouchDB native driver. As library - yes, as driver - no. What's the benefit of creating native driver instead of library? Easy switching. For example, my site is now on MySQL, and I want to switch to MongoDB. If I don't have MongoDB native driver to database class, I need to replace all my functions or method calls to that new library. I think you understand me.

Q: Have you ever heard "..."?
A: Yes, I heard about this 1 million times. But if everybody followed this, we didn't have all these great frameworks as Codeigniter, CakePHP, Yii, Kohana and others. Why only frameworks? We could not have current "developed world".

As I said to Phil, I'll release 0.1 version and see if people will like it. Or at least 0.1, 0.2 and 0.3. If they will not like it, I will stick to Fuel, Kohana or CI2.

[eluser]ntheorist[/eluser]
don't reinvent the wheel, reinvent new tires and treads.