Plugin-Template

[RYX]

I have created a first basic approach for a Plugin-page template. You can see it here (http://www.compiz.org/Template:PluginTemplate) ... And a demo-page using the Template is here (http://www.compiz.org/Plugins/MovePlugin). Check the source of the demo-page to see how a template works. It is really simple for the editing user.

The demo-page is unfinished and any suggestions (e.g. things missing in the template) are happily welcome ... :D

:)

[amgeex]

I think the template is good. There should be a general Plugins:PluginsList page or something like that that would list all available plugins by category. What other additions do you have in mind? I can start porting plugins this week, just let me know. Nice work Rico! 8)

[RYX]

Thanks :D ... There is already a list-page - "Plugins:Plugin_Database". It could become the starting-page for the Plugins-tab. Other useful additions would be a nice way to present the plugin's options or some icons. I have to read some more through the wiki-wiki ....

:)

[amgeex]

Alright... gonna fool around with these test pages a bit, if you need anything just say it. 8)

EDIT: Hey, maybe we could use the same styling and order we used in the Documentation page. What do you think?

[RYX]

Yes, that would be good ... (didn't see your edit :))

[amgeex]

Just did some quick editing, check it out... :D

[FunkyM]

Try swaping everything you got on the right side (Title, Infobox, Imagebox) with the left side (Info, Usercontent).

[RYX]

How about categorizing the plugins more logically? I think core/optional/extra is a very bad way of grouping them. The user would find his way around much better with categories like this (only examples, could be more):

- "Core/Essential"(move, resize, place),
- "Configuration/Backends" (gconf, ini, dbus, fuse),
- "Effects" (wobbly, water, neg, ...),
- "Usability" (gestures, ...),
- "Desktop" (cube, plane, wall, menu, wallpaper, ...)

@FunkyM: We could offer two templates for that once the basic-template is ready. The developer could then just select the one he prefers. I think in most non-asian countries people write/read from left to right so I found it more appropriate to put the info on the left.

:)

[mikedee]

My bet for plugin groupings would be something like

base
extra
unsupported

Some people like

base
good
bad

What do you guys think of these? One or the other is very likely to become 'official' soon, unless we can think of something better ;)

[RYX]

I think we shouldn't confuse the package-grouping with the grouping of plugins in the wiki. I am very sure that most end-users would prefer a grouping by purpose rather than by "division". To me the base/good/bad naming seems even worse than the core/optional/extra ...

I, personally, have no problem with grouping by division, but I try to see it from the pov of an end-user who is navigating through the site for the first time ...

[franzrogar]

Hello,

I think a middle-way could be the best aoproach:

Group by "target":

- Core (or General) Management (dbus, crashhandler, jpeg, png, text...) Plugins that affect the whole compiz environment
- Window Management (wobbly, resize, place...) Plugins that affect windows only
- Desktop Management (cube, plane, wall, menu...) Plugins that affect desktop only
- Visual Effects (water, snow...) Plugins that add eye-candy only
- Accesibility (gestures, zoom...) Plugins that add accesibility

and when you're in plugin configuration, it will show you this info:

Plugin name
Plugin present in: (base || extra || unsupported)
Plugin configuration....

That'd be:
- base: compiz core plugins
- extra: composite community ones
- unsupported: 3rd party plugins

So you have both ways: human one (first) and system pkg one (latest one).

My 2 cents of Euro :)

[mikedee]

I think we shouldn't confuse the package-grouping with the grouping of plugins in the wiki. I am very sure that most end-users would prefer a grouping by purpose rather than by "division". To me the base/good/bad naming seems even worse than the core/optional/extra ...

I, personally, have no problem with grouping by division, but I try to see it from the pov of an end-user who is navigating through the site for the first time ...

I agree the package should be there so people know where to get it from, maybe you could have tags (yaeah I know its very web 2.0), so you could add a few to each plugin to help with searching etc.

[amgeex]

That would certainly help. I'm liking franzrogar's proposal, what do you think RYX? I can do the template editing if you want (or are feeling lazy lol). Let us know! 8)

[RYX]

I modified the template a little bit. It now contains a "package"-option where the author can put the name of the package the plugin can be found in. This can be anything - core/extra/good/bad/ugly/... The Download-option is now called "Source" and should contain the url of the tarball with the plugin-source.

I also added a options-option where a list of available plugin-options can be defined. I will create another template for defining options (can be used within the PluginTemplate). We should use as much templates as possible to separate content and layout ...

The template is still only a draft and needs some more details and most likely more quick-info about the plugin (in the block on the right) so any suggestions are welcome ...

:)

[Spillaz]

In fact

Core Functions
Core Options
iNotify
DBUS
FUSE
INI
GCONF
KCONF
(Or LibBS)
JPEG
SVG
PNG
TEXT
Clone
Decoration
Move
Resize
Place
Winrules
Put
Shortcuts
Profiles
Crashandler
Debug

Window Management:
Scale
Switcher
Ring
Showdesktop
Tile
Thumbnail
Vignettes
Group and Tab
Snap
Trailfocus

Desktop Management:

Desktop Cube /Rotate
Desktop Wall
Widgets
Miniviewport
DesktopClick


Visual Effects :

3D Window Layering
Animated Transtions (Animation)
Blur
Relection
Motion Blur
Fade will be depricated soon ;-)
Wobbly
Opacity Brightness and Saturation

Acessibility
Opacity
Concentration Helper (ADDHelper)
Negative
BlackandWhite
Annotate
Mousegestures

Toys
Benchmark
Splash Screen
Snow
Fireflies
Stars
Screensaver
Screenshot and Video Capture
Flash
Water Effects

[RYX]

I have updated the template again - any suggestions ?? :D ..

[amgeex]

The template is fine.