<Linuturk> ah
<Linuturk> do you have spare time, and a desire to help out the open source community ?
<Linuturk> briand ^
* Linuturk removes channel operator status from Linuturk
<Linuturk> Basically, I'm working on Fluxbuntu
<Linuturk> we are creating a control panel type application in gtk+ called the Dashboard
<Linuturk> no one knows any C or C++ to create the Dashboard engine to take the plugin files
<briand> so, umm... you've come up with some plugins, and all I need to do is come up with the main application that will implement them?
<briand> seems a bit like putting the cart before the horse. :)
<Linuturk> no no
<Linuturk> that's the concept
<Linuturk> we haven't made anything but the concept yet
<briand> well, what exactly is this conceptual program supposed to do?
<Linuturk> there are two componets
<Linuturk> the engine
<Linuturk> and the plugin
<Linuturk> I'm sure you know how the menu is generated in fluxbox, right?
<Linuturk> it reads a plain text file, with a special syntax, and shows the menu
<Linuturk> well, same concept
<Linuturk> the engine
<Linuturk> and the plain text plugin
<Linuturk> we can write plugins all day
<Linuturk> but we need the engine to take those plugins and make it easy for the end user to change configurations on his/her system
<Linuturk> such as wallpaper, server controls, etc etc
<Linuturk> for example, we'd have a General tab, for the general configs
<Linuturk> we'd have a Server Control Tab, for starting and stopping services (ie Apache)
<Linuturk> almost anything, really
<Linuturk> considering they are plain text
<Linuturk> basically, we want to make fluxbox easy to configure
<briand> so, basically, write an application that provides all the functionality that the lightweight window manager doesn't already have
<Linuturk> it's something most other distros don't have
<Linuturk> lol
<briand> but, there's a catch...
<Linuturk> something that allows you to configure the lightweight wm . . .
<briand> not only do that, but do it by parsing user-modifiable text files, so the parsing would be very slow (comparatively) and would need to have all sorts of error-checking (because user's often make errors)
<briand> why not just use a window manager that already has this functionality?
<Linuturk> well, the plugins will be written by developers mostly. end users won't be writing them
<Linuturk> we can follow whatever syntax you lay out
<Linuturk> and, is there a wm as light as fluxbox that has these functions?
<briand> or, is the real question, "Is the reason this wm is so light is because it lacks these functions?"
<briand> :)
<Linuturk> i don't think that's the case. DSL has deployed their control panel, and it's just as light
<briand> what you propose, as a concept, is fairly trivial...
<briand> implementing, in practice, is not so trivial....
<Linuturk> yeah . . .
<Linuturk> well, I just wanted to make fluxbox easier to configure
<Linuturk> and more user friendly
<briand> why not steal the menuing system out of DSL, and start playing around with it?
<Linuturk> i don't really like it much, tbh
<Linuturk> hmmm
<Linuturk> a non plugin form of that? as tough?
<briand> it would, in essence, be a new window manager
<Linuturk> I'm not talking about rewriting fluxbox
<Linuturk> just a control panel to do common configurations