One of the G2 features I love (Despite my hosting issue with embedded) is the ability to taylor the "layout" to suit the embedded application requirements
The downside to this is should you or someone else directly acess your gallery (that is NOT via the embedded php) the "stand alone" look tends to be totally crap because it has all been changed to suit the embedded application.
My suggestion would be when running embedded, the layout/theme be different (Either defined in Gallery Layout Admin Panel) or maybe hardcoded to be a layout/theme called embedded, for example.
That way we have maximum flexibility for changing the way G2 looks while embedded while still retaining the ability to access G2 as a standalone should the suitation ever require it..
Posts: 32509
ozgreg, something like this was discussed a while ago. We could indeed have a check for something like a "embedded" directory similar to the "local" directory for templates.
But is this enough, or do you want different layouts/themes active for embedded/standalone? ...
We should start collecting a wishlist for embedded G2 apps, with input from you WP guys, mambo, phpnuke, drupal, etc., etc.
Posts: 1378
Valiant, you would best know the level of effort but for my 5 cents worth (bloody inflation it use to be two cents) I would separate the Theme / Layout Templates / style sheets for embedded / standalone that way G2 would have two very different ways of being displayed. Both of them could be totally independent (in terms of layout ) from each other..
If that proved a large amount of effort before release G2 (maybe future release type functionality) then instead as a work around, your suggesion was excellent, that is, having an embedded directory like local, to seperate the two modes.
As it stands in G2 B2, it is very hard to balance a nice looking embedded G2 without it looking crap in standalone.
Posts: 7994
When presented with this decision in the past we've always aimed to satisfy the 80% case. And right now the 80% case is that people don't need to view their Gallery in both embedded and standalone modes simultaneously. And that's being generous; I imagine it's a very very small percentage of people who want both. So for the 2.0 release, I don't think we should worry too much about that scenario, at least not until we have mastered embedding on a wide variety of platforms.
Posts: 32509
bharat, that's fine for me. I also believe that only a very tiny percentage will run G2 standalone/embedded at the same time. perhaps during site development/design, but not once the site is in production.
Should we create a feature request / task scheduled for late 2005 to keep track of this need?
Posts: 1378
Very happy to run up a poll over this to track this requirement, what do you both think.. Right now it is a pain in the ass because we switch a lot between the modes which you expect in a beta environment.
Posts: 2258
see the new poll on the front page and tell us how you feel!
Posts: 17
I'm embedding g2 into pmwiki, which hasn't built in a real user management. So I decided to use g2 standalone for admin and g2 embedded just for viewing. As discussed earlier in this thread, it is very difficult to have a layout/theme that works for both scenarios.
I haven't looked at the code yet, but wouldn't it be quite easy to integrate a default layout/theme selection into the GalleryEmbed class, maybe as an optional argument to the init call.
Cheers,
Christian
Posts: 80
Well, here is a problem - most php sites force their own fonts and sizes onto Gallery, so in my instance (and i've tried several web site packages) gallery fonts look so small that no one can read them....I wish there was a way to adjust that.