Main Stories
Slash Boxes

Slash Open Source Project

Slashcode Log In

Log In

[ Create a new account ]

Article Poll

Poll I found this article to be
Very Helpful
Helpful
Not Helpful
Not Very Helpful
[ Results | Polls ]
Comments:0 | Votes:0

Admin interface woes...

posted by Krow on 12:31 PM October 26th, 2000   Printer-friendly   Email story
iomud writes "Slashcode is a killer weblog perhaps the best. However, upon logging into the admin interface I feel as though I've missed out on the better part of an inside joke (read:confused). For those who coded it I'm sure it's easily understandable and quite useful, but to the layman it's not exactly the most intuitive design. Maybe it just takes time to get used to but, I think some effort ought to go into making the admin interface more rubust. Maybe something on the level of say geeklog's admin interface which is quite friendly and easy to use and takes little to no explanation to grasp. The front end looks great why not the backend too? I'm only a bit critical of it because I know the talent abounds among the slash developers to create something even better."
It would be simple enough to write a better login interface. I can't say that I am in love with it either. This would probably make for a good module. I think it would be nice if the admin interface could be used to edit several slash sites at once.
This discussion has been archived. No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login
Loading... please wait.
  • In my experience building Slash-based sites in large corporations, every project that adds something to the default code base invests significantly more effort in things that the end user can see. Often, Author productivity in BackSlash is 5th or 6th on the priority list and stays there for many iterations of the development cycle.

    After nearly two man-years of development on one large Slash-based system, the sponsors have realized that they must allow us some development time to improve Author productivity. We have added a number of features that make some system configuration and operations-related features of Slash usable/more readily available through backSlash.

    Of course the main problem we have, which has been consistantly plagued us since we began working with this platform, is that 0.9x and 1.0x significantly changed their internals from 0.3. This has made it impossible for us to offer patches and enhancements up to now.

    Happily, we have successfully installed Slashcode 1.09 on one of our development machines [ctdata.com], and we hope to apply some of our enhancements to the current Slashcode base.

    Perhaps the core developers can comment on how quickly they plan to de-emphasize the 1.0x branch of development once Bender stabilizes?
    --

    Dave Aiello
    Chatham Township Data Corporation

    --

    --

    Dave Aiello
    Chatham Township Data Corporation [ctdata.com]

  • I don't know why, but the total commitment to Bender was not clear to me. Looks like we'll have to uninstall 1.09 and install Bender immediately. This is welcomed news, from my perspective.
    --

    Dave Aiello
    Chatham Township Data Corporation

    --

    --

    Dave Aiello
    Chatham Township Data Corporation [ctdata.com]

  • Yeah, maybe this should be in the FAQ.
  • Perhaps the core developers can comment on how quickly they plan to de-emphasize the 1.0x branch of development once Bender stabilizes?

    Well, what time is it now? :) Seriously, we have put 1.0.x into permanent maintenance. We don't have the resources to continue active development of it. Bender is the primary focus, and when it is stable, will be the only focus, I think, aside from bugfixes.

    I can't imagine this will be the case, but if there is significant interest in development of the 1.0.x code, we might consider handing it off to those who are interested in maintaining it. That can be discussed at a later date if anyone is really interested in it.

    But again, Bender should be superior in almost every way; the only reason to stay with a 1.0.x site, that I can see, is if you have already modified it a lot, in which case development of the 1.0.x code won't help much anyway; at that point, if you are going to invest time in changing a lot of code (to sync with 1.0.x), you might as well go to bender.