Home » Archive » LxAdmin » Lxadmin 6.0 Feature request » If I may comment on the LXAdmin webdesign...
|
| Re: If I may comment on the LXAdmin webdesign... [message #59270 is a reply to message #59259] |
Thu, 12 March 2009 00:52   |
Lxhelp
Messages: 23691
Registered: July 2006 |
The Champion |
|
|
Yes, I will provide a custom CSS.
Actually, the only reason Lxadmin exists in the market is that our competitors have not been intelligent enough to come up with a proper software development methodology.
Otherwise, it would be impossible for yet-another-control-panel to make into the market nearly 7 years late.
thanks.
On Wed, Mar 11, 2009 at 10:53:42PM -0000, Arthur Thornton wrote:
>
>
> For the sake of reason, please just add the ability to include a custom css file. It takes a few lines to do the following:
> - check database for whether or not custom css exists
> - if yes add in the code for the custom css file
> - if not do not add the code
|
|
|
| Re: If I may comment on the LXAdmin webdesign... [message #59356 is a reply to message #59259] |
Thu, 12 March 2009 13:05 |
 blinkie 
Messages: 56
Registered: January 2009 |
Valuable Member |
|
|
| arthurthornton wrote on Wed, 11 March 2009 15:53 | For the sake of reason, please just add the ability to include a custom css file.
|
But it's not going to help much because there are no targettable individual class or id attributes defined in the current output. All you could hope to do is some very basic styling.
LXHelp, with regard to your 7000 lines of code statement... To be honest, I find that hard to believe. And with regard to your statement...
| Quote: | Actually, the only reason Lxadmin exists in the market is that our competitors have not been intelligent enough to come up with a proper software development methodology.
Otherwise, it would be impossible for yet-another-control-panel to make into the market nearly 7 years late.
|
You are clearly indicating there is, in fact, room for yet another panel that does support the level of customization that your current and potential customers are demanding in this thread.
Clearly, LXAdmin is an engineering-driven product vs a customer- or market-driven product. I've never seen any long lasting products that were driven by engineers instead of customers. So to say the least, this is troubling.
You'd be a fool to underestimate the competition or to think (!) that there isn't someone out there building something 1000% better than what you currently have.
|
|
|
| Re: If I may comment on the LXAdmin webdesign... [message #59358 is a reply to message #59356] |
Thu, 12 March 2009 13:24 |
Lxhelp
Messages: 23691
Registered: July 2006 |
The Champion |
|
|
| Quote: |
On Thu, Mar 12, 2009 at 05:05:29PM -0000, Blinkie wrote:
> But it's not going to help much because there are no targettable individual class or id attributes defined in the current output. All you could hope to do is some very basic styling.
>
> LXHelp, with regard to your 7000 lines of code statement... To be honest, I find that hard to believe. And with regard to your statement...
|
You should check some our modules that we have open sourced. For instance, the mail modules and drivers. Lxadmin is a radical departure from traditional ways of coding. We are categorically claiming theoretical perfection.
| Quote: |
> You are clearly indicating there is, in fact, room for yet another panel that does support the level of customization that your current and potential customers are demanding in this thread.
>
>
|
You are completely ignoring the market realities. Cpanel has ONLY 1 single skin. Cpanel's skinning is irrelevant. So is hsphere's as you yourself have explained.
As I said: Show me a real world example of where skinning has been successful. I cannot implement features that are patently and obviously useless. It doesn't provide one bit of advantage.
Nobody uses a skin other than the one provided by the provider. In fact, using a skin by third party would be suicidal. I have no idea how anyone can comfortably use it.
| Quote: |
> Clearly, LXAdmin is an engineering-driven product vs a customer- or market-driven product. I've never seen any long lasting products that were driven by engineers instead of customers. So to say the least, this is troubling.
|
Lxadmin is a pure customer driven project. We have completely redesigned the architecture not once, but many many times. Lxadmin started as a plesk like system, but it has been completely re-written to be exactly like cpanel, at the same time maintaining all the advantages of the plesk on the admin side.
| Quote: |
> You'd be a fool to underestimate the competition or to think (!) that there isn't someone out there building something 1000% better than what you currently have.
|
There are physical and theoretical impossibilities. Control panels are a lot of work. The market is littered with the corpses of too many 'promising' control panels. Again, we should note that Control panels are an extremely mature market with near 10 year history. If nobody has been able to do anything worthwhile for the past 10 years, how can you expect someone to suddenly come up with something?
|
|
| |
| Re: If I may comment on the LXAdmin webdesign... [message #59381 is a reply to message #59380] |
Thu, 12 March 2009 15:24 |
Lxhelp
Messages: 23691
Registered: July 2006 |
The Champion |
|
|
That would be even more difficult since you will need to keep up with the changes, which I don't think it would be possible.
Cpanel is a absurdly peculiar applicationS. That is, it is hodge podge of 2 separate applications, and the even there the most you change is the main page which contains all the icons.
So the most you would want to change is the domain owner home page.
On Thu, Mar 12, 2009 at 07:20:25PM -0000, Arthur Thornton wrote:
>
>
> Quote:
> > In fact, using a skin by third party would be suicidal
>
> Who said we would be buying or selling the themes. We would be making our own, and therefore we would not be doing anything suicidal.
>
> --
> http://www.zantagonox.com
>
>
|
|
| |
| Re: If I may comment on the LXAdmin webdesign... [message #59496 is a reply to message #59358] |
Fri, 13 March 2009 12:29 |
blinkie
Messages: 56
Registered: January 2009 |
Valuable Member |
|
|
| Lxhelp wrote on Thu, 12 March 2009 10:24 |
You should check some our modules that we have open sourced. For instance, the mail modules and drivers. Lxadmin is a radical departure from traditional ways of coding. We are categorically claiming theoretical perfection.
|
It's a mistake to claim perfection. That's just arrogance.
Where are the open source modules? The following is a complete list of "open source" code installed with the control panel:
./lxadmin/bin/common/misc/reset-mysql-root-password.phps
./lxadmin/bin/common/langcompare.phps
./lxadmin/bin/changetoclientlogin.phps
./lxadmin/bin/raw_update.phps
./lxadmin/bin/migrate/cpanel.phps
./lxadmin/bin/misc/fixftpuserclient.phps
./lxadmin/bin/installapp-upload.phps
./lxadmin/bin/installapp-update.phps
./lxadmin/bin/delete-old-spam.phps
./lxadmin/file/script/phpinfo.phps
./lxadmin/file/script/cp.phps
./lxadmin/file/webmail-chooser/webmail_chooser.phps
./lxadmin/file/webmail-chooser/roundcube-config.phps
./lxadmin/file/webmail-chooser/db.inc.phps
./lxadmin/file/horde.config.phps
./lxadmin/httpdocs/lbin/header.phps
./lxadmin/httpdocs/lib/alternate.phps
./lxadmin/httpdocs/lib/domain/mmail/driver/autoresponder__qmaillib.phps
./lxadmin/httpdocs/lib/domain/mmail/driver/mailaccount__qmaillib.phps
./lxadmin/httpdocs/lib/domain/mmail/driver/mmail__postfix.phps
./lxadmin/httpdocs/lib/domain/mmail/driver/mmail__qmaillib.phps
./lxadmin/httpdocs/lib/domain/mmail/driver/mailforward__qmaillib.phps
./lxadmin/httpdocs/lib/domain/mmail/driver/mailinglist__ezmlmlib.phps
./lxadmin/httpdocs/lib/domain/mmail/driver/mailaccount__postfix.phps
./lxadmin/httpdocs/lib/domain/mmail/driver/mailforward__postfix.phps
./lxadmin/httpdocs/lib/domain/mmail/driver/autoresponder__postfix.phps
./lxadmin/httpdocs/lib/domain/mmail/driver/mailcontent__postfix.phps
./lxadmin/httpdocs/lib/domain/mmail/mailinglistlib.phps
./lxadmin/httpdocs/lib/domain/web/driver/installsoft__linuxlib.phps
./lxadmin/httpdocs/lib/domain/web/driver/allinstallsoft__linuxlib.phps
./lxadmin/httpdocs/lib/domain/web/driver/installappsnapshot__sync.phps
./lxadmin/httpdocs/lib/domain/web/installsoftlib.phps
./lxadmin/httpdocs/lib/domain/web/allinstallsoftlib.phps
./lxadmin/httpdocs/lib/domain/web/installappsnapshot.phps
./lxadmin/httpdocs/lib/print_tab.phps
./lxadmin/httpdocs/htmllib/lib/apilib.phps
./lxadmin/httpdocs/htmllib/lib/pserver/driver/servermail__postfix.phps
./lxadmin/httpdocs/htmllib/lib/pserver/driver/serverftp__pureftplib.phps
./lxadmin/httpdocs/htmllib/lib/pserver/driver/servermail__qmaillib.phps
./lxadmin/httpdocs/htmllib/lib/pserver/serverftplib.phps
./lxadmin/httpdocs/htmllib/lib/pserver/servermaillib.phps
./lxadmin/httpdocs/htmllib/lib/dns/driver/dns__bindlib.phps
./lxadmin/httpdocs/htmllib/lib/dns/driver/dns__powerdnslib.phps
| Quote: | You are completely ignoring the market realities. Cpanel has ONLY 1 single skin. Cpanel's skinning is irrelevant. So is hsphere's as you yourself have explained.
|
Did I write that about HSphere? If I did, then I take it back. I never meant to suggest that themes, skinning, or any other type of UI customization, is irrelevant. I'm just saying that a platform has to be designed from the beginning to support UI customization. It's possible that that was the intention with HSphere but then poor (sloppy) implementation made this difficult to maintain. To reiterate, HSphere 3.x was fully skinnable, in a way that wouldn't break between incremental minor upgrades, but it would have been a pain to diff all the files everytime a new release came out (because you'd want to be sure that nothing changed). Still, you never would have recognized my UI customization with that platform compared to the installed look.
I maintain that if there is a clear separation between visual presentation and the rest of your code, there should be no great difficulty in opening up the visual code so that the entire user interface could be customize. But my bet is your presentation code is tightly coupled to the rest of your code...which is simply poor design.
Also, I would strongly suggest you follow the links to the other two examples of licensed open source that I provided in my previous post. They are excellent models for you to emulate and as I mentioned before, they would likely result in greater revenue for you. Plus, you would be the only company in the CP market that would offer an open source licensed product.
Another reason for open sourcing is that we would be free to extend (on our own) the system as far as we'd like. And maybe you'd even get some source code back. For example, what about those of us who had asked about adding support for multiple MX servers? Or how about those of us that might want to be able to create and manage load balanced web servers from within the CP? Neither feature is currently supported by LXAdmin. And some of us do require these features now despite the fact that they may not be that high up on your list of priorities.
I really don't think it's productive to dismiss our requests by stating that your product is superior to anything else out there despite the fact that it doesn't address the features we are looking for AND you have no plans to change anything.
All I can say is that I'm kinda glad I don't have any customers installed on these systems yet.
|
|
|
| Re: If I may comment on the LXAdmin webdesign... [message #59501 is a reply to message #59496] |
Fri, 13 March 2009 13:04 |
Lxhelp
Messages: 23691
Registered: July 2006 |
The Champion |
|
|
| Quote: |
On Fri, Mar 13, 2009 at 04:29:43PM -0000, Blinkie wrote:
>
>
> Lxhelp wrote on Thu, 12 March 2009 10:24
> > You should check some our modules that we have open sourced. For instance, the mail modules and drivers. Lxadmin is a radical departure from traditional ways of coding. We are categorically claiming theoretical perfection.
>
>
> It's a mistake to claim perfection. That's just arrogance.
|
Arrogance is always good trait in developers. Lxadmin code has been re-written from scratch many many times over. Normally software development progresses by adding DUCT-TAPE patches to existing code. That's why Cpanel/Plesk/Hsphere, after 10 years, are nowhere. Indeed, developers of those panels should ashamed that after 10 years and millions of dollars, they not made any significant progress.
| Quote: |
> Where are the open source modules? The following is a complete list of "open source" code installed with the control panel:
|
You can check the mailinglist.phps and the associated drivers.
Generally all the phps files inside the httpdocs/lib directory.
> ./lxadmin/httpdocs/lib/domain/mmail/mailinglistlib.phps
> ./lxadmin/httpdocs/lib/domain/web/driver/installsoft__linuxl ib.phps
> ./lxadmin/httpdocs/lib/domain/web/driver/allinstallsoft__lin uxlib.phps
> ./lxadmin/httpdocs/lib/domain/web/driver/installappsnapshot_ _sync.phps
> ./lxadmin/httpdocs/htmllib/lib/dns/driver/dns__bindlib.phps
> ./lxadmin/httpdocs/htmllib/lib/dns/driver/dns__powerdnslib.p hps
| Quote: |
> Did I write that about HSphere? If I did, then I take it back. I never meant to suggest that themes, skinning, or any other type of UI customization, is irrelevant. I'm just saying that a platform has to be designed from the beginning to support UI customization. It's possible that that was the intention with HSphere but then poor (sloppy) implementation made this difficult to maintain. To reiterate, HSphere 3.x was fully skinnable, in a way that wouldn't break between incremental minor upgrades, but it would have been a pain to diff all the files everytime a new release came out (because you'd want to be sure that nothing changed). Still, you never would have recognized my UI customization with that platform compared to the installed look.
|
Hsphere was already cumbersome to begin with. And then it was made COMPLETELY irrelevant by the latest parallels redesign of the interface. Just as cpanel made everything irrelevant with X3.
Yes, I agree skinning USED TO work (albeit with enormous amount effort and a lot of hacks), till version 3.x.
I can even theoretically predict that EVERY Software will reach a particular stage where skinning automatically becomes irrelevant. Skinning is great for very small softwares with around 100 or so pages. But as the software becomes more and more complex, it becomes more and more cumbersome, and at some point, the developer will simply opt to completely discard multiple skins.
The above evolution of software has happened with both cpanel and hsphere, and I don't think it is a mere coincidence.
| Quote: |
> I maintain that if there is a clear separation between visual presentation and the rest of your code, there should be no great difficulty in opening up the visual code so that the entire user interface could be customize. But my bet is your presentation code is tightly coupled to the rest of your code...which is simply poor design.
|
Just check Lxadmin modules and you will see that Lxadmin has the CLEAREST separation between code and presentation.
Inside the module, all you need to provide are variable names, and the framework will create the entire page. This has allowed us to completely re-design the entire front-end in a week's time. You should actually check the forum on how fast our frontend design evolved after we switched to the feather theme. It took less than a week to change the entire thing.
Again, you should go through the modules and see for yourself.
The presentation is 100% separate from the rest of the code.
I have said it again again. Our ENTIRE PRESENTATION (for BOTH hyperVM AND lxadmin TOGETHER) amounts to less than 7,000 lines of html. That would be impossible unless code and presentation were 100% separate.
The code merely defines variables as $vlist['variable'] = array('s', $list);
The presentation takes this simple variable list, and creates the entire interface.
That's why I have been saying that Lxadmin/HyperVM are theoretically perfect software.
|
|
| |
| Re: If I may comment on the LXAdmin webdesign... [message #59532 is a reply to message #59501] |
Fri, 13 March 2009 16:07 |
blinkie
Messages: 56
Registered: January 2009 |
Valuable Member |
|
|
| Lxhelp wrote on Fri, 13 March 2009 10:04 |
Arrogance is always good trait in developers.
|
Only if you ever want to work in a bubble, only care about shipping a product when you are done (vs what the business or market needs are) and only ever want to create a business of a limited size (typically: small).
| Quote: |
Lxadmin code has been re-written from scratch many many times over.
|
See, that's what happens when something wasn't designed properly the first time through. I wouldn't call this kind of development "beneficial" to any extent. You end up rewriting large chunks over and over again...time you could have spent implementing or improving something else.
| Quote: |
Our ENTIRE PRESENTATION (for BOTH hyperVM AND lxadmin TOGETHER) amounts to less than 7,000 lines of html.
|
So you are saying that ONLY the presentation layer is 7000 lines. I thought you were saying the whole package was 7000 lines.
| Quote: |
The code merely defines variables as $vlist['variable'] = array('s', $list);
|
Not OOP?
| Quote: |
The presentation takes this simple variable list, and creates the entire interface.
|
Well, if that's the case, then you should be able to open up everything after the vlist is created. Ship an example (the current templates would suffice) and that will allow your customers to write all of the additional presentation code they need to create a fully custom environment. As long as you never change keys in that vlist nothing should break (you will obviously be free to add additional keys down the road).
In some ways, this would be 1000% better than trying to use Smarty. And at the same time, you would fully protect the rest of your encrypted code. Furthermore, by exposing your current templates (I personally prefer the old tabbed interface over feather) you will save yourself some time in having to write documentation.
And you know, if you really want to get fancy, you could add an XML layer that will export that vlist in XML instead.
BY the way, I must say that I'm impressed about how responsive you've been. 
|
|
|
| Re: If I may comment on the LXAdmin webdesign... [message #59569 is a reply to message #59532] |
Sat, 14 March 2009 03:12 |
Lxhelp
Messages: 23691
Registered: July 2006 |
The Champion |
|
|
| Quote: |
On Fri, Mar 13, 2009 at 08:07:48PM -0000, Blinkie wrote:
>
>
> Lxhelp wrote on Fri, 13 March 2009 10:04
> > Arrogance is always good trait in developers.
>
>
> Only if you ever want to work in a bubble, only care about shipping a product when you are done (vs what the business or market needs are) and only ever want to create a business of a limited size (typically: small).
|
In this particular case, it is not even arrogance, but merely I am stating the facts. I have gone through the code of some of the open source control panels and I can very categorically say that Lxadmin is a million years ahead.
| Quote: |
> Quote:
> > Lxadmin code has been re-written from scratch many many times over.
>
>
> See, that's what happens when something wasn't designed properly the first time through. I wouldn't call this kind of development "beneficial" to any extent. You end up rewriting large chunks over and over again...time you could have spent implementing or improving something else.
|
Refactoring is an integral part of software development. At least that's case if you are planning on developing something significant. Other than trivial softwares of less than 10,000 lines of code, all softwares should undergo refactoring. You cannot plan 100% for the future. And that's why software turns into spaghetti code. In normal cases, when a developer wants a new feature, he will _softly_ work around the existing code, by patching in the new code without disturbing the existing one. When Lxadmin needed a new feature, we redesigned the entire framework to properly incorporate the new feature.
| Quote: |
> Quote:
> > Our ENTIRE PRESENTATION (for BOTH hyperVM AND lxadmin TOGETHER) amounts to less than 7,000 lines of html.
>
>
> So you are saying that ONLY the presentation layer is 7000 lines. I thought you were saying the whole package was 7000 lines.
|
Lxadmin/hyperVM together is 100s of thousands of lines of code. But everything is handled by 7,000 lines of presentation. That's why I claim that it is theoretically perfect.
Entire software being 7,000 would make lxadmin/hyperVM trivial and useless softwares. Lxadmin and hyperVM are extremely large and behemoth softwares. But their presentation layer is extremely small.
| Quote: |
> Quote:
> > The code merely defines variables as $vlist['variable'] = array('s', $list);
>
>
> Not OOP?
|
Please go through the modules. Lxadmin is 100% object oriented. Every resource in Lxadmin/hyperVM is an object. That doesn't mean you use objects where it doesn't make any sense.
| Quote: |
> Well, if that's the case, then you should be able to open up everything after the vlist is created. Ship an example (the current templates would suffice) and that will allow your customers to write all of the additional presentation code they need to create a fully custom environment. As long as you never change keys in that vlist nothing should break (you will obviously be free to add additional keys down the road).
|
There are no templates for separate pages. EVERY page in lxadmin/hyperVM is rendered by 7,000 lines of presentation, and so this presentation code is extremely generic, and very complex. It has the least number of lines, but it is not actually simple. There is no templating concept.
I can make everything based on css, so that you can customize the css.
|
|
|
| Re: If I may comment on the LXAdmin webdesign... [message #59636 is a reply to message #11621] |
Sat, 14 March 2009 12:49 |
|
For the time being, the custom CSS would be nice. But it would also be nice for you to give us an existing template so as to let us customize it and make one for ourselves. You could then let us know the necessary HTML code for each added link, function, etc. so we could implement it before updating LxAdmin.
My Site
|
|
|
| Re: If I may comment on the LXAdmin webdesign... [message #60106 is a reply to message #11621] |
Fri, 20 March 2009 08:44 |
rmwebs 
Messages: 86
Registered: September 2007
Location: UK, England |
Valuable Member |
|
|
I dont think LXHelp gets what this is about.
We're not disputing code or the way to develop LXAdmin or HyperVM. We are ASKING for theme support. An easy little addon that would take you no longer than a day to complete. Its clearly what people want.
Go on WebHostingTalk. You will see that almost every HyperVM/LXAdmin thread comments on the (excuse the language) crap design. I'm not talking about the design of the program, I'm talking about the skin/theme design, the images, the colors, not the code.
People want the ability to modify the design. This CAN be done in cPanel. The hostgator example is clear evidence that it can, that skin they made is build on the X3 skin, not a custom front-end.
Its not rocket science. We want themes...css and such for both LXAdmin and HyperVM....not hard.
You boast that you keep the html and php separate, if this is the case then it'll be a doddle!
Take a look at cpskins.com -- you can see just how customizable all your competitors control panels are!
[Updated on: Fri, 20 March 2009 08:46] Report message to a moderator |
|
|
| Re: If I may comment on the LXAdmin webdesign... [message #60117 is a reply to message #60106] |
Fri, 20 March 2009 12:12 |
blinkie
Messages: 56
Registered: January 2009 |
Valuable Member |
|
|
According to LXHelp no one wants theming, no competitor has been able to pull off theming reliably, and we all should be happy because LXAdmin/HyperVM are so superior to everything else (although there's no way to tell since it's all closed source) despite the fact that the developers never thought to give us the ability to apply something as simple as CSS. Or how about this: wouldn't it be nice to just have some control over page title?
Their solution has been to come out with the new "Feather" theme that will allow us to customize the graphic at the top (that is, the "feather" image). This is progress?
And when you switch to the brand new and supposedly far superior (heh!) feather theme you also get stuck with the ridiculous updated interface choices they've made (those tiny icons at the top that in usability terms suck compared to the legacy tabbed layout which we're sticking with).
I would not agree that adding support is a trivial matter. If the system hasn't been designed right from the start with custom theming in mind then it can be painfully difficult to add support. My opinion is that LXAdmin/HyperVM, despite being so superior, fall into the latter camp: they can't be easily adapted at this point.
My solution, which LXHelp has ignored to comment on, would be to open source the entire package except for critical licensing code. That way we'd be able to all customize to whatever extent we needed. I pointed out that it is likely that LXLabs would make a lot more money with the open source licensed model because they'd be able to charge more. A lot more. And the two examples of how to do this successfully are Interspire's Email Marketer (formerly "SendStudio"), and Octeth's OemPro. But you could also look at SugarCRM as an example where (AFAIK) even the Pro versions are 100% open source but require licenses.
Anyhow, I feel that continuing on with this thread is like beating a dead horse. The LXLabs folks obviously have never operated in the highly competitive ISP space before so they don't have a clue about what the business conditions are like.
|
|
|
| Re: If I may comment on the LXAdmin webdesign... [message #60118 is a reply to message #60117] |
Fri, 20 March 2009 13:05 |
Lxhelp
Messages: 23691
Registered: July 2006 |
The Champion |
|
|
Hi,
I really appreciate your feedback. I am now fully working on interface customizability. Skinning is not possible, but as you said, I will need to switch to css and make it customizable.
Open sourcing is not an option at this point, since we don't have enough resources to enforce the license.
thanks.
On Fri, Mar 20, 2009 at 04:12:14PM -0000, Blinkie wrote:
>
>
> According to LXHelp no one wants theming, no competitor has been able to pull off theming reliably, and we all should be happy because LXAdmin/HyperVM are so superior to everything else (although there's no way to tell since it's all closed source) despite the fact that the developers never thought to give us the ability to apply something as simple as CSS. Or how about this: wouldn't it be nice to just have some control over page title?
>
> Their solution has been to come out with the new "Feather" theme that will allow us to customize the graphic at the top (that is, the "feather" image). This is progress?
>
> And when you switch to the brand new and supposedly far superior (heh!) feather theme you also get stuck with the ridiculous updated interface choices they've made (those tiny icons at the top that in usability terms suck compared to the legacy tabbed layout which we're sticking with).
>
> I would not agree that adding support is a trivial matter. If the system hasn't been designed right from the start with custom theming in mind then it can be painfully difficult to add support. My opinion is that LXAdmin/HyperVM, despite being so superior, fall into the latter camp: they can't be easily adapted at this point.
>
> My solution, which LXHelp has ignored to comment on, would be to open source the entire package except for critical licensing code. That way we'd be able to all customize to whatever extent we needed. I pointed out that it is likely that LXLabs would make a lot more money with the open source licensed model because they'd be able to charge more. A lot more. And the two examples of how to do this successfully are Interspire's Email Marketer (formerly "SendStudio"), and Octeth's OemPro. But you could also look at SugarCRM as an example where (AFAIK) even the Pro versions are 100% open source but require licenses.
>
> Anyhow, I feel that continuing on with this thread is like beating a dead horse. The LXLabs folks obviously have never operated in the highly competitive ISP space before so they don't have a clue about what the business conditions are like.
>
|
|
|
| Re: If I may comment on the LXAdmin webdesign... [message #60124 is a reply to message #11621] |
Fri, 20 March 2009 15:32 |
|
Please make the ability to make custom themes a TOP priority. I do want interface skinning, but as you said, you have completely redone the entire backend before and as such, if we get enough support, maybe you can redo the frontend setup to allow for skinning. Redoing 7000 lines is better than 100000 lines, now isn't it?
My Site
|
|
| |
| Re: If I may comment on the LXAdmin webdesign... [message #60678 is a reply to message #60677] |
Mon, 30 March 2009 04:45 |
Lxhelp
Messages: 23691
Registered: July 2006 |
The Champion |
|
|
File manager has an archiver right?
On Mon, Mar 30, 2009 at 08:41:36AM -0000, support@animedaisuki.co.cc wrote:
>
>
> I dont care if they make an option for reskinning enable or not it juz they need to come out with a proper + faster loading interface eg: when you open file manager its obviously slower than other competitors plus the option you have on file manager like unzipping or gzip is not there. Altho you can di this via ssh but i dont expect you will allow client to have access via ssh...
>
> The overal design for me is good you juz need to make it load fast... thats all
>
|
|
|
Goto Forum:
Current Time: Fri May 24 21:18:26 EDT 2013
Total time taken to generate the page: 0.01507 seconds
|
HyperVM & Kloxo Support
Members
Search
Help
Register
Login
Home
