Oh, that's what i thought myself, because i tried searching for maximize in W3C spec. So if that's not in W3C and is some sort of leftover, then shouldn't it be removed from REST API instance XML or completely removed ?
I'll delete maximize check from plugin code, because it's not in W3C spec, so all the plugins will be maximizeable. All current frameworks have methods for maximize value, which seems kinda pointless if it can only be set via webadmin and it's not really needed at all. -- Raido On Fri, Mar 26, 2010 at 10:06 PM, Scott Wilson <[email protected]> wrote: > > On 26 Mar 2010, at 17:37, Raido Kuli wrote: > >> Hi. >> >> I've done some more work on Wordpress plugin, see >> http://code.google.com/p/wookiewordpressplugin/ for more information. >> >> Fixes: >> * user, display_name passing >> * Implement Highslide JS for maximize feature, widget can be maximized >> only if widget instance "<maximize>false</maximize>" value is true. >> * Some error checking and cleanup >> * Width/height bug fixed >> * Plugin detect bug fixed >> * Participants add bug fixed (problem was username, display_name passing) >> >> See project homepage/Wiki for more information. > > Great work Raido! > >> >> One question too, can maximize parameter be set from widget config.xml >> ? Or is it possible only via wookie-admin interface, where the >> checkbox is ? > > Its not really part of W3C but something left over from earlier in > development, so only really accessible from within wookie admin. > > We could add it as a feature extension, e.g. > > <feature name="http://incubator.apache.org/wookie/features/maximize";> > <param name="maximize" value="true"/> > </feature> > > At some point we'll want to look into the Widget View Modes spec, which uses > CSS Media Queries: > > http://www.w3.org/TR/widgets-vmmf/ > > >> >> -- >> Raido > >
