Less configuration hardcoded? about bootstrap_package HOT 6 CLOSED

Hey, glad you like it - and at the current state the less configuration is hardcode and will not be overritten at anytime. I working on a concept how to make it more flexible.

I´ll keep you informed about the progress.

from bootstrap_package.

When compiling the theme.less, I got some errors:

1. was because theme.less is using a variable that is into bootstrap folder
2. after the uncomment of the bootstrap include, was error with "variables" include... because it is inside Default folder... I correct the path and then everything worked.

Could you maybe add the config file too? I guess it would nice to have this with a README explaining briefly what... where...

Just to discuss, I don't think that is a good idea to place Resources in fileadmin, I guess it is like misuse of the concept... customize the ext/bootstrap_package is much better... no?

from bootstrap_package.

@jnotaro i think you have tryed to compile the less files yourself? this is currently not intended - when you have a look at the backend you will find a "Style" module. the intention was to make it easy for non developers to manipulate the variables of the bootstrap package and compile them on save.

the variables file does not exist by intention, it is not needed for the frontend to work since there is a precompiled css files that will get included. the variables file is created after you press the first time the save button in the backend module.

and yes i dont like the idea to place resources in the fileadmin and you should not edit the bootstrap package. this is exactly my problem at the moment and i am playing a around how to get this working.

the main idea is to make the backendmodule extendable with custom form configurations and stuff like the themes from http://bootswatch.com/ and provide some kind of api for that

my biggest problem is that is must be usable by persons that are not used to typo3 in an easy understandable way.

requirements

• integration in the backend module
• frontend includes of the needed css files
• multisite / multithemes
• rte in the backend
• easy to add custom themes
• upgradeable

this is kind of tricky to automate this things and did not find a good solution for that yet but i am working on that.

from bootstrap_package.

Yes, I am compiling the less, I added my own variables file, a custom file... works. So, I would not close the door for this way because, in the case of typo3, I believe it is not like a wordpress or drupal where we can do such stuff, install a theme and make some changes.

But if you believe it can do this... what you did is already great. As End-User, I thought that the Styles module should be more readable... I don't if it is the better word, "readable"... I mean, the variable names should be encapsulated. I would then maybe have, by customizing, these sub pages -> basics, buttons, states, alerts, panels, components, Navigation... each page having the sections, ex.: Tables, Inputs, and so on... then the user can make changes in the style settings and check it right way on FE. Instead of "@table-cell-padding" or "@table-condensed-cell-padding" maybe just write a real title... the same title that the end user will find into the customizing pages, so like the link you placed here bootstrapwatch, it is like I am thinking. Then, after end-user changes, he can just hide this "customizing" page.

To install more bootstrap themes... I believe the templates structure should be improved, I guess there are a lot of Default.html, I believe it should be just one... I preferred as you did by partials.
Or by template/Page with specialStart.html... and Default2Columns would be 2Columns.html thats enough. I am not that fun of automatic theme install anyway, and with typo3 and typoscript... is a hard work

from bootstrap_package.

@jnotaro i think we have an missunderstanding here what the package is made for

the target group for bootstrap_package is not the typical integrator or developer. the bootstrap_package will only solve the needs of the unexperienced users to give them a quickstart into a clean typo3. like a theme that is easy to install with the limitations indeed. for the experienced typo3 users its more a codebase to have a look at to get an impression how things can be done without hacking the system and/or installing thousands of extensions - this is also the only reason why no news extension is in use - just to show that its possible without.

i am currently thinking about a kickstarter for "themes" that help you setup structure of an extension like bootstrap package with empty configurations - so we get rid of the typoscript in the fileadmin (userspace).

and yes the styles editor is a bit tecky it just shows every single variable from the bootstrap css framework to get full control about it - maybe there sould be a second option to reduce this just to some basic color/font settings. i am still planing to enhance the module and give more options and explainations - but at first i need to solve some problems that currently exist with multisites to provide a better backend here.

i really appreciate your feedback thx a lot for that.

from bootstrap_package.

Hi @suburbanworrier, @jnotaro,

sorry that this took so long but the configuration is now excluded. I removed the backendmodule in favor of configurable typoscript constants. You can find all of them in the normal constant editor.

You can not inlcude normal .less files like you already know it from css files in your setup.txt this ensures that you can edit the variables for everypage seperatly and you can override it if you like to.

I think this will fix the problem and brings a lot more flexibility, since the less files are now rendered and cached on demand.

from bootstrap_package.