Re: [kohana] Great widgets to use in interface!
- Rafi B.
- 2009-12-29 @ 18:13
Are you referring to Kerkness' GUI module? I haven't used it, just took a
brief look at it.
I'm having the same thoughts as you, dealing with JS/CSS boggles my mind
right now, and I'm trying to come up with a neat way of building a nice UI
module for Kohana, having all the widgets I need inside the vendor folder
and serving them through some factory.
I was thinking about an array in each controller that holds the names of UI
widgets that need to be loaded and used within a controller. So for example
the main template controller can have just "jquery" and "jquery-ui", and
categories controller can also have "tree". I don't think there's a perfect
formula for this, but making it neat and encapsulating all UI widgets within
a UI module that can overload the scripts/styles of the response seems nice.
I have a deadline at the end of January, so I don't think I'll be able to
accomplish this soon, but right now working on my current project gives me a
lot of ideas and gives me the perspective of using them in real life.
I'm thinking about a general UI module, that can have a factory which uses
specific Models for specific widgets, and anyone could extend them and add
more modules. Importing and including the actual widgets libraries will be
in the modules/ui/vendor folder. It could certainly be great to create a
main module that everything can fork from and extend it.
On Mon, Dec 21, 2009 at 2:39 AM, Ryan Mayberry <email@example.com>wrote:
> Hi Rafi,
> Are these K2 or K3.. ( I know I can look at the source but I'm away
> from a computer at the moment )
> I've been sticking some code into a github project called GUI which
> is all jquery enhanced user interface elements for KO3. I've got a
> Tabs element and some other half completed elements. I also have a
> TinyMCE Sprig field and a Markdown Sprig field which are nice. It
> would be nice to add your elements to an over all GUI module.
> One of the issues with enhanced interface elements and modules (in KO3
> at least) is that there is no unified way of using required JS, Images
> or CSS in an app or including them in a module. The "best practise"
> would say that media files should be accessible from the html root
> folder. This approach however doesn't make it easy for users to just
> install a module and use it ( without having to upload media files
> separately and modify templates or template controllers )
> Anyone have ideas of how to best work with media files in a module ?
> ps: is this list a general Kohana list or specific to version 2 or 3 ?
> On Sun, Dec 20, 2009 at 11:21 AM, Rafi B. <firstname.lastname@example.org> wrote:
> > Well, I'm not the creator of these awesome widgets. I've been following
> > jsTree since the past 1.5 years, and the guy (Ivan) has been rapidly
> > developing this excellent widget. About CKEditor, in my opinion, it's the
> > best (free) wysiwyg editor in the market, and the performance is great.
> > I am mirroring both these projects manually for my own use, but you can
> > clone as well :)
> > Another great product I'm using in my current project is the amazing
> > with Wouters' awesome Kohana module MangoDB.
> > I would love to hear any other great UI or server products you guys are
> > using in your Kohana development! ;)
> > On Sun, Dec 20, 2009 at 7:11 PM, Mathew Davies
> > <email@example.com> wrote:
> >> Nice work Rafi, how often are they updated?
> >> -Mathew
> Mayberry Fine Art