as i already am posting videos so i don´t need to put so much text into the thread this one is quite worth it. “cleverman”.
i like the deep club sound! technoid but natural 
aware
Reply
Author Archives: bigbabou
fukushima incident explained for japanese children
okay, i really got set up with all that repeating news spam about the earthquake nuclear power plant fear. but i admit i just liked watching this weirdie.
it remembered me for those old movies like “when the wind blows” but got a bit more of the manga flair 
“fear not, the real threatening poo is too heavy to fly”
Twitter Weekly Updates for 2011-02-18
- Yummy chili von carne göttingen my deal right now! #
replyto with the standard mailform ce in TYPO3
if you want the standard mailform content element in TYPO3 to send emails not from the ugly www-data@server.com sender but the writer´s email adress and name you just need to use explicitly labelled fields as follows:
- from_name
- from_email
This will do the trick. But there´s even more. If you need to provide a reply-to attribute you can do this by using these fields (which may be hidden):
- replyto_name
- replyto_from
Well, nowadays i´d recommend sophisticated mail form extensions like powermail but if you happen to edit a project that might help
tooltips with ext:contagged
for some reason the very good extension contagged does not provide the dropdown to select what type of term the current item is. so all my entries in the sysfolder “terms” have type 0.
the little tweak in the userTS changes all newly created terms to be a tooltip:
TCAdefaults.tx_contagged_terms.term_type = tooltip
a small UPDATE in mysql made the already existing terms to tooltips as well. a post before i saved how to have only contagged items in this sysfolder.
to avoid editor´s overkill when just creating a little tooltip i also remove some fields from the very flexible contagged terms item in PageTS:
TCEFORM.tx_contagged_terms {
image.disabled = 1
imagecaption.disabled = 1
imagetitle.disabled = 1
imagealt.disabled = 1
exclude.disabled = 1
term_type.disabled = 1
term_replace.disabled = 1
desc_short.disabled = 1
starttime.disabled = 1
endtime.disabled = 1
fe_group.disabled = 1
sys_language_uid.disabled = 1
}
i also do hide fe_group access dropdown and the system´s language selector thus making the backend experience more simple.
keep TYPO3 sysfolders clean
just a small hint to restrict the creation of new elements inside a page (eg. a sysfolder) so that this sysfolder will only hold tt_news entries or sys_templates or whatever. you put that code into the pageTS of the sysfolder/page:
mod.web_list.allowedNewTables := addToList(sys_template)
if you´d like to only contain tt_news entries and tt_news categories you´d put addToList(tt_news,tt_news_cat) into the TS and then these are the only elements to create new inside that folder. if you want the sysfolder to hold only entries for the nifty contagged extension, you use addToList(tx_contagged_terms). here´s more on contagged as tool tip manager.
control leds at the numark mm control
today i got my numark mixmeister control surface and i not even installed the included software since i mix music with my traktor pro. the mm control provides all the encoders i need to completely remove the keyboard and mouse from my mixing hours. input mapping worked okay due to the cool controller editor from ni, but making the controller show stuff like track cueing or fx status… that worked not so well.
as i didnt find them over the net: these are the (channel 1) notes to trigger the leds of the mm control
C#6 Preview C6 Jog Wheel B5 Fader 4 A#5 Fader 3 A5 Fader 2 G#5 Fader 1 G5 Mix top F#5 Stop top F5 Play top E5 Mix bottom D#5 Play bottom D5 Stop bottom C#5 T6 C5 T5 B4 T4 A#4 T3 A4 T2 G#4 T1 G4 S4 orange F#4 S4 green F4 S3 orange E4 S3 green D#4 S2 orange D4 S2 green C#4 S1 orange C4 S1 green
weird thing is, that you need to substract one octave from every note inside traktor´s controller editor. so, if you read D4 make it D3 and you´re fine.
know more about the requesting browser
propably you´ve heard about the modernizr javascript which tests the requesting browser for css3 and html5 capabilities and then sets classes to the root <html> element which your apes css coders use for selector queries. no more conditional hacking. that sounded so good that i stuck it and found this little post about server-side modernizr.
another handy javascript piece is yepnope. best is: both scripts join forces and reduce http requests and, thus save the world!
all in all this is great news for systems like TYPO3 that already provide conditions for environment variables like the client´s browser family, the os and so on. wouldn´t it be a nifty thing if the system chose the template to provide depending on the client´s capabilities to handle them?