> I just wanted to say that I'm very impressed with Suteki so far - I've not
> really had to touch the codebase at all yet, and have a lot of functionality
> for the e-commerce build I wanted already in place.
>
> There are a few things that I wanted to mention however, and perhaps if
> you're in agreement with me on them I could join the project and help get
> things changed around or implemented?
Thanks Graham, I'm very pleased that you like Suteki Shop so far :)
> Anyway, here goes:
>
> - I think that the css stylesheet is a bit confusing when starting out.
> The site is very tightly-coupled (in a style sense!) to the JTG site, which
> makes it arduous to sort out to begin with. I think that a possible solution
> to ease this would be to have separate stylesheets for the site and the
> admin pages, which would help people to work out what they could safely
> change without cascading breaking styles. Coupling a (very) simple template
> with the separate stylesheets (I'm thinking bare bones site skeleton here)
> would make it easy for people to reskin the site as they see fit.
> - I think that a separate Admin.Master page would be useful - the admin
> menu and stylesheet could be added to just this page, keeping it properly
> compartmentalised. This would also enable people to have a totally separate
> style for the admin section, which would be useful if they'd implemented a
> radical main site design.
I agree about the CSS design. It's definately one of the poorer parts
of Suteki Shop. Any input you have would be welcome. I think the idea
of splitting the CSS into 'skin' and 'structure' parts (must be better
names) is great.
One think I don't like about a lot of eCommerce applications are the
separate user and admin sites. I wanted Suteki Shop to be more like a
wiki, where the administrator simply gets extra features and can edit
things in-place. Because there aren't really separate admin and user
sites it doesn't make sense to have separate styles or an admin master
page.
> - I couldn't find any Product Search functionality. Am I being thick, or
> is it not implemented? I'm more than happy to work on this and add it in if
> need be.
No, there is no Product Search functionality. A patch would be most
welcome :) What's your opinion about how to implement it? Would you
simply use the Google API, or would you search the DB?
> - What's the deal with LTS and nHibernate? Is the site in the process of
> being ported? I found this really confusing to be honest, although I have
> not spent much time on it really, seeing as I've not needed to change any
> code yet!
Yes it is confusing. Suteki Shop uses LINQ-to-SQL. The Suteki.Common
project has been used in one of my commercial projects that used
NHibernate. A while back I merged lots of stuff from the commercial
project back into Suteki Shop including the NHibernate repository (and
the NHibernate dependencies it has). That's why you see NHibernate
dlls in the references for Suteki.Common.
My intention is to port Suteki Shop to NHibernate. But since it uses
LINQ throughout, I wanted to wait until the NHibernate-LINQ
implementation was mature enough to support it.
> - I think the project would really benefit from a SharpArchitecture style
> "Getting Started" document. I'm happy to contribute this once I have a
> thorough understanding of how everything's built, but I think that that's
> some way off yet ;)
That would be very nice :)
> Anyway, I hope that you don't see the above as criticism, I think you've
> made an excellent framework here! I'd love to get involved if you have
> anythign for me to do on it :)
Not at all, criticism is *good*!
Patches are very welcome. I think you've made some excellent
suggestions. If you want to have a go at implementing any of them just
send the patch to the group. I'll check it out and add it in :)
Mike