[Freeswitch-users] WikiPBX Installation

[Matthew Lockwood]

Thanks for all this. What I meant to respond with before I passed out asleep
was:

The framework doesn't matter that much. We've all got looped on this issue.
Everything that is done has to add value to the end user. The framework is
far down at the bottom of the list of things that provides value, but it's
not something to be ignored.

The vision I have for this is something that's so simple it lowers the
barriers that would otherwise stop people from using FreeSwitch. Using some
relatively unheard of framework is going to most certainly complicate
things. Simple = good. And plus, on a side note if we throw out a whole
bunch of frameworks and acronyms and make a big deal about the actual
technology that powers the GUI (not that people even care most of the time),
people will start to get more confused and it'll backfire.

I'll be using .NET/Mono unless I can come up with an exceptionally good
reason to use something else. I'm choosing this framework over everything
else because it's what I know best and I'll be writing the code base. I've
got years of experience writing code in C# and developing .NET web
applications so it makes more sense than learning something new that will
slow the development time and result in me producing poorer code. This isn't
me being mercenary, but the GUI isn't likely to cross the million codeline
barrier (even with everything implemented) and this is a framework I have a
lot of experience with. I'm totally fine being the lone developer for now,
and there are a lot of people with similar programming skillsets as mine so
it's not like there will never be anybody else that'll ever contribute code.


Personally, I think it's more important to have well written code that is
rapidly developed than it is to have a shiny technology that adds no value.
:-) Of course, the final product will be perfectly standards compliant and
100% accessible. I know this is important.

I'm going to lay the framework issue to rest now. It'll be .NET/Mono unless
there is some super-compelling reason to use something else. If for some
reason there is such a reason not to use .NET/Mono, the second choice is
PHP.

The other thing is I'm pretty much going to develop upwards of 95% of the
features in one go. Nobody wants an incomplete product that lacks necessary
functionality, so from v1.0 it'll be pretty much feature complete. I'm
developing this for use in my business, so I need it feature complete, and
that's what the community will get too - a feature complete product. Hope
you're happy having a fully fledged GUI! ;-)

M


On Fri, Jun 5, 2009 at 1:26 AM, seven <dujinfang at gmail.com> wrote:

>
> On Jun 5, 2009, at 1:36 PM, Michael Collins wrote:
>
>
>
> On Thu, Jun 4, 2009 at 6:52 PM, Matthew Lockwood <
> matthew.lockwood at gmail.com> wrote:
>
>> That would involve me learning a totally new framework. It'll not the
>> hardest code I'll ever write by far, so I'm okay coding it up on my own.
>> However, I definitely need a lot of help from fabulous designers to actually
>> make the interface pretty and useable. Plus, I'm only one person and will
>> need a lot of feedback to create something that rocks - everybody has a
>> different use case and I can't foresee how everybody will use it, so that
>> kind of feedback will go into re-engineering it.
>>
>
> If you guys are serious about this then I would like to make a few
> suggestions that might be obvious but for the sake of the project we'll make
> them explicitly obvious.
>
> First, before deciding what framework to use, it would be good to hold some
> discussions about what the GUI actually needs to do:
> What are the design goals?
> Will it be just for setting up extensions and the dialplan? Or will it go
> much farther than that?
> Will you be using mod_xml_curl for everything? If so, what database(s) will
> you support?
> Are you going to have extra goodies like an IVR builder?
> A 'visual voicemail' page?
> A user portal?
> Management interface to 'spy' on users?
> A CDR/call accounting system?
> FIFO and/or ACD queue management?
> MOH and sound files management?
>
>
> and conference management
>
>
>
> It's okay to start small and build your way out, but you need to know
> before you start building what the grand scheme will be. The larger the
> goals of the project, the narrower your choices for a framework that can do
> it all. The simple fact of the matter is that if you want to use a MVC web
> framework then you have a somewhat limited number of choices. You need a MVC
> WF that fits your needs, which means it needs to be at least somewhat
> flexible. If you want a pretty GUI then you need to decide if you want a
> rich Internet application (RIA) front end like AIR, or do you want something
> along the lines of XHTML/CSS/JS and use a platform like Dojo which gives you
> cross-browser widgets and tools. All of this on top of the fact that if you
> want volunteers to assist you will need to pick something that people either
> know or can learn quickly.
>
> Oh, and be prepared for people to give you unsolicited opinions about all
> sorts of things. :)
>
> All that being said, I say go for it. Find what works for you and see what
> happens. Be sure to use #freeswitch-gui. If this really takes off I'm sure
> that we could even start a mailing list for GUI development.
>
>
> Once the goals and features decided I think more ppl can join and work this
> out together.
>
> Enjoy!
> -MC
> _______________________________________________
> Freeswitch-users mailing list
> Freeswitch-users at lists.freeswitch.org
> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
> http://www.freeswitch.org
>
>
>
> _______________________________________________
> Freeswitch-users mailing list
> Freeswitch-users at lists.freeswitch.org
> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
> http://www.freeswitch.org
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.freeswitch.org/pipermail/freeswitch-users/attachments/20090605/bec4fff3/attachment-0002.html