History of StylistPackage

Differences from version 7 to 9

@@ -1,117 +1,63 @@

 !My Site Stylist
 my site stylist is a configurable graphical user interface to modify (perhaps even create) new themes.
-^note: this package is still in developement and certain aspects are nowhere near completion :)^
+{img src=/img/wiki_up//stylist.gif align=center}
-now it's possible to select the style you want to edit rather than just picking the one that is being displayed
-it's not required to use the GUI. you can use edit the css file using a massive textarea
+!!admin area
+the admin area allows you to define what tags, classes and ids can be modified by users using the stylist. this allows the admin total control over how much can be modified.
+e.g. if you don't want the users to change the banner you have put up, don't allow users to change the settings for #tikitop.
+in addition it's possible to define what properties can be set.
-!!features and items available
-*admin area allows users with permissions to add/remove elements and modify definable properties that can be set for these
-*relatively simple to work with and allows basically full customisation of the site if you take the time to add all classes, tags and ids to the list of editable items.
-*it's possible to customise a css file that is visible globally for all users using that particular theme
-*in addition every user can have his/her own css file that is only applied when that user calls that theme
-**ideally this file should be visible if the style is applied to the individual area
-***user selects his/her favorite theme for his/her user area
-***user customises his/her favorite theme
-***user applies modifications to his/her user area
-***customisation is visible to every user accessing his/her user area
-*it is possible to manage images in all these customisations making my site stylist quite flexible and powerful
+!!original files are never modified
+stylist doen't modify any of the original files but either creates new files that are loaded in addition to the original <style>.css file (when you use the graphical user interface(GUI)) or it creates a copy of the original file that is loaded instead of the original <style>.css file.
--=this is a brief log of things that have been done and will be done=-
--=gui related=-
-form is collapsable at every element to save space
-individual and unified settings for borders and margins available
-admin area is now
-link to view original file is available
-*for simplicity reasons, i think it's better if the original file isn't directly modified (or copied and modified) but custom settings are loaded later resulting in overwriting of original css settings
+!!global style modifications
+depending on your permissions it is possible to create global css files. the global css modifications you make (be it with or without the GUI) are visible to all users using that particular theme.
--=data related=-
-form submission results in easy to manage variables, similar to css syntax
-individual form buttons work (still submit full form - should be fixed at some point)
-final submit button for entire form is working as well
-read css file and
-*create array of classes
-*pass all variables to form and populate it
-*create css file from date generated in form
-classes, ids and tags have appropriate column settings in table since . and # conflict php varibles
-array structure
-$css_elements = array(
- 'tag' =&gt; array(
- 'body' =&gt; array( 'border','margin','font','background' ),
- 'table' =&gt; array( 'border','margin','font','background' )
- );
- 'id' =&gt; array(
- ...
- );
- 'class' =&gt; array(
- ...
- );
-on the admin page
- |border
- |margin
- |background
- |border
- |margin
- |background
+stylist allows you (depending on the settings in the admin section) to upload your own images and thus customise the feel for your site without actually having to touch the css file directly or the need of ftp.
-permissions and preferences that are available
-tiki_p_admin_stylist|obvious as well
+it is possible to work on any style that is available without having to change the theme set in your preferences. to simply this task, it is possible to preview the style you are working on and thus see all changes you make after every time you save the modifications you have made.
+!!personal style manager
+there is an integrated custom style manager which gives you an overview of all styles you have already modified and what images are available for every one of them. also, you have the option to delete custom modifications if you wish to do so.
+!!permissions and preferences that are available
+tiki_p_admin_stylist|user has the right to set tags, ids and classes that can be modified by other users
 tiki_p_edit_global|user has rights to edit the global css
-upload_style_images|leads to the fact that 'background' can't be set by users without this perm
-copy_style_images|can't copy images from original image folder to custom folder
-apply_style_globally|allows user to apply his/her modifications globally for the given theme
+tiki_p_edit_css|user can edit a copy of the original css file using a textarea. the user has no constraints on what the css file contains
+tiki_p_use_stylist|if the user is allowed to use the stylist at all
+tiki_p_no_max_file_size|user isn't bound to the preference set in max_file_size
-max_file_size|set MAX_FILE_SIZE for image upload
-ignore_max_file_size|ignore the above setting and set it to 100MB
+max_file_size|set MAX_FILE_SIZE for image upload (if not set, or tiki_p_no_max_file_size is set) it defaults to 10MB
 use_color_picker|should we use the color picker popup window?
-custom css files that are created
-*global css files are stored in the storage directory
-*private css files are stored in the individual storage folder
-*when you use the stylist the file created is in
-*when editing the css file without stylist, the file is called
--=this still has to be implemented. currently we only load base.css and &lt;style&gt;.css=-
-order of loading css files is
-**first check if user has &lt;style&gt;/&lt;style&gt;.css --&gt; continue with loading &lt;style&gt;_&lt;browser&gt;.css
-**then check if there is a global version of &lt;style&gt;/&lt;style&gt;.css --&gt; continue with loading &lt;style&gt;_&lt;browser&gt;.css
-**finally load original &lt;style&gt;/&lt;style&gt;.css --&gt; continue with loading &lt;style&gt;_&lt;browser&gt;.css
-**this is a css file that is loaded in addition to &lt;style&gt;.css if &lt;browser&gt; matches the client browser
-**first load custom.css found in the global storage directory
-**then load custom.css found in individual storage area
+!!theme selection restrictions
+the admin always has control over what themes users can pick, and when these can be displayed.
+1|user can pick a theme for his/her homepage. this setting takes precedence over all settings.
+2|it is possible to pick a theme based on a category.
+3|user can pick a theme to view the entire site using a particular theme.
+4|theme control module.
+5|global theme setting for entire site.
+!!loading of css files - full listing
 || |file|location|notes
 1|base.css|themes/|this is always loaded and helps functionality of site|
-2|&lt;style&gt;.css|storage/users/&lt;user_id&gt;%1000/&lt;user_id&gt;/themes|if found, continue with # 3
+2|<style>.css|storage/users/<user_id>%1000/<user_id>/themes|if found, continue with # 3
 | |storage/themes|if found, continue with # 3
-| |themes/&lt;style&gt;|if found, continue with # 3
-4|custom.css|storage/users/&lt;user_id&gt;%1000/&lt;user_id&gt;/themes|last file
+| |themes/<style>|if found, continue with # 3
+4|custom.css|storage/users/<user_id>%1000/<user_id>/themes|last file
 | |storage/themes|last file
-||{img src=/img/wiki_up//stylist.gif align=center}
Page History
23 Feb 2005 (04:57 UTC)
Current • Source
View • Compare • Difference • Source
View • Compare • Difference • Source
View • Compare • Difference • Source
View • Compare • Difference • Source
View • Compare • Difference • Source
View • Compare • Difference • Source
View • Compare • Difference • Source