But sometimes, you want to do something with your friends, but you don't know precisely where and when. For that purpose there is a type of activity called a proposition. The syntax to create a proposition is the same as the one to create a plan with one exception. You need to add a question mark at the end of your post to create a proposition. The proposition allows you to specify multiple choices.

For example, you want to lunch with friends but don't know when and where, just enter the choices separated by semicolon.

Example

Once a proposition is created you can decide if you want to leave the different choices (what, where of when) open or not. Just click on the links next to the choices to open or close them. By default the choices are open.

If you want to invite people to discuss this proposition, click the "invite people to this event" button. You can either select particular friends on the service or invite new friends by entering their email addresses separated by commas.

When your friends receive an email there is link to the detail page. On this page, your friends can  vote or make suggestions if you left the choices opened. And each time something is happening on this proposition (vote, suggestion) or posted to the proposition (comment, media) the users invited to the proposition are notified via their preferred communication channel.

And once the votes are over, the person who created it can transform the proposition into a plan. The administrator of the activity needs to make some of the choices final.

And make it final

Here is a short tutorial on how to do it. First, get your external calendar url and copy it into the input field as shown below. If you use GCalendar, we recommend you to create a new calendar, you can get the GCalendar url in the calendar settings page as shown here:

After clicking on the subscribe button we copy all calendar events to mixin. If you set a privacy on your external calendar all the events from this calendar will have the selected privacy when the are copied.

We copy and update the events from your calendars to mixin every hours. For each event copied from your calendar, we do this process:

• We try to match the mixin activities type with your event as follow:
  • If there is a location specified, a date and no what (title for the event) we create a location
  • If there are multiple locations (i.e. using the syntax with the ; "1 Baker Street; Home") or multiple whats (i.e. using the syntax "Watching a movie; Playing Wii" in the event title) or the event title ends up with a "?", we create a proposition
  • If there is a date and the title contains "free" or "available" (we accept an optional location), or if the title and location are empty we create an availability
  • Else we create a plan
• If there are any attendees in your event, we will try to find registered user by email on mixin. If we find a registered user, we will show him as invited in mixin. If the attendee is not a registered user, we will create a guest account for him in mixin, we do not send any emails. If he joins mixin later, this activity will be part of his agenda.

If your event has been updated in your calendar we will synchronize the changes in mixin unless you edit the event in mixin. In that case, we break the synchronization link. You can always invite attendees and add medias in mixin, this will not break the link but theses changes won't be synchronized back to your calendar.

Limitations & restrictions

• If you invite more attendees from your calendar they won't be updated in mixin if the event has already been copied to mixin
• If your event is deleted in your calendar, it won't be deleted in mixin
• Whoever is the event owner in your calendar, you will be the activity owner in mixin
• For the moment you cannot subscribe to your ICal or Outlook calendar BUT you can still create activities from these clients simply by adding mixin@mixin.com as a guest to the event
• There are no way to create wishes from your external calendar
• We do not copy your events which are older than 1 year

Coming soon: a better GCalendar integration.

After you sign up for Mixin you can create a profile with your photo, a custom background, and add links to your Twitter, flickr, and qik accounts.  From there, you just need to update your timeline with any events you'll be participating in or you can "wish" for something.  Making a "wish" can be something like wanting to go hiking for the day or stating that you'd like to see a particular movie.  Your friends can do the same and you can follow each other to keep up with each others activities.  You can invite certain friends to join you in an activity and on the activity page you can post comments, suggestions, photos, and video.

All of your activities are on your agenda and you can filter your view by selecting certain types of events.  You can also choose to only view your own events, you and your real friends events, etc.  One thing that I really like about mixin is that you can choose specific people to be your "real friends" by placing a star next to their name.  That way, you can quickly see what the people you hang out with in real life are doing and decide if you want to join them.  If this sounds confusing to you, just think of it like this:

You're sitting at home on a Friday afternoon and suddenly realize that you have no plans (happens to me all the time).  So, you can log into your mixin account and post that you're free on Friday night and you're up for anything, maybe a movie.  Now let's say your friend Rita is thinking the same thing, "I'm bored and it's Friday!".  She logs into her mixin account and sees that you have no plans either or that you're going to the movies by yourself.  Rita can then join the activity or suggest something for you guys to do.  She can add an exact location and invite some other people.  Before you know it, you're surrounded by all of your friends and well on your way to a beauty of a hangover in the morning.  All thanks to mixin.

Mixin is also available on your mobile phone, over IM, or email.  You can choose to receive notifications via IM or email as well, so you'll know right away when someone is planning an event.  You can also embed your mixin timeline on your blog or website.

Learn more about mixin by watching the screencast below:
[viddler id=de294c30&w=700&h=567]

Click Here To Watch Better Quality 4m6s

Want this screencast on your site?  Click here to get the embed code for this and other DemoGirl screencasts!

[via CenterNetworks]

Why mixin
mixin filters and complements the current vision that you have through various communication channels including micro-blogging on what our friends are doing right now or what they did. mixin focuses on the future in order to create opportunities of activities in the real world. Each user has its agenda, which is an aggregation of what their friends are planning, proposing to do, where they'll be or when they might be available. mixin offers a social peripheral vision trough micro-events over the week.  

Share your micro-agenda
You can add activities in 2 clicks from your timeline on the website but can also publish via IM, SMS, Email or your actual calendar application. In addition to this, mixin parses your Twitter messages and automatically populates your agenda when activities are identified. mixin helps people to identify opportunities by filtering information they already publish. 

Structure your data
mixin users can add other popular services they might use. mixin will for example automatically link Flickr pictures or Qik videos to an activity depending on the media date. mixin structures the flow of information by activities and by group as several users can join an activity. 

What's next
We want to bring mixin to people whatever the channels they are using. We built a first version of our API so that we will be able to connect to other services and let people build their own vision of how mixin should be. Don't hesitate if you have any idea!

The first method is to go around adding classes to HTML elements that need the clearing ability added; everywhere you find that the height of a containing element isn't what you'd expect because of floating dab a little class='clearfix' (or .clearfix for us haml lovers) and voila, problem solved. Semantic purists will be vomiting into their mouthes a bit right now, but this isn't such a bad strategy. Its one drawback is keeping track of everywhere you put the class looks suspiciously like work (and work is something I try to avoid if possible).

The second method is to keep updating the css declaration to include the new elements you'd like the fix applied to. So, if you started out with

.clearfix:after {
content: ".";
display: block;
height: 0;
clear: both;
visibility: hidden;
}
.clearfix {display: inline-block;}

and need to make the div #my-cool-contents also properly contain its floated elements you'd alter your css to

.clearfix:after, #my-cool-contents:after {
content: ".";
display: block;
height: 0;
clear: both;
visibility: hidden;
}
.clearfix, #my-cool-contents {display: inline-block;}

and now anything with the class .clearfix or the id of my-cool-contents will clearfix itself. Before the semantic purists rejoice I have to mention: this can be a headache to maintain. Imagine a situation where three or four developers are all adding elements that need clearing and you can quickly end up with css declarations with dozens of rules kept in a separate location from the other rules for those elements. I've found this strategy to be even more work than the first.

It's just not pragmatic to trade semantic purism for more difficulty maintaining your css files.

Enter the sass mixin

A recent edge version of haml/sass includes the oft-requested ability to keep what are being called 'mixins' available for use in many places. If you're not familiar with haml or sass do yourself a favor and read the tutorial, play with them online, and then install them on your development box.

Mixins (in sass) are freestanding css rules not attached to any particular declaration. Sass normally looks like this:

#my-div
  :border   1px solid black
  :width     300px
  :margin   10px

where css directives are specifically attached to an element with the id of my-div and complies into this:

#my-div {
  border: 1px solid black;
  width: 300px;
  margin: 10px;
}

But, edge versions of sass will let you have bits free standing bit of css that an not attached to any declaration (and don't print until they are attached). You create them with the '=' character:

=message-box
  :padding 15px
  :border=  3px solid !layout_highlight_color

This snippet of sass can be attached to any sass declaration with the '+' character.

.warning
  :width 100%
  +message-box

will compile to

.warning {
  width: 100%
  padding: 15px;
  border: 3px solid #fafafa
}

Putting it all together

You can combine the sass mixin with repeatable css strategies (like clearfix) to get some pretty clean, semantic, and maintainable html and css.

Here is clearfix rendered as a sass mixin (note: you'll need a recent version of haml checked out from git and rake installed)

=clearfix
  *display:                 inline-block
  &:after
    content:                " "
    display:                block
    height:                 0
    clear:                  both
    visibility:             hidden

You can apply it anywhere in your sass that needs some clearfixing:

.images
  :width 44%
  +clearfix

#main-article
  :width 25%
  :float left
  +clearfix

Snag it

I keep clearfix (as both a class and mixin) sass file up in my git repo. Feel free to use and abuse it
clearfix.sass

Trav ---> Rob3rto

Vic ---> Trav

Tree ---> Ryan

Rob3rto ---> Adam

Adam ---> James

Ryan ---> Brad

James ---> Farrell

Farrell ---> Tree

Nate (aka "Ricky") --> JB

Brad (JUDGE)---> Marcus

JB ---> Nate

Marcus --> Vic

Please let me know if there are any recent repeats, and please let me know if you didn't get a mix last month. I never heard from Jacob, so I had to leave him out this month, but Jacob, if you see this, hit me up. Remember to post your mixes by the last day of the month so that brad can judge them, and whoever wins gets to pick the next theme! Also, don't forge to get addresses or to hand off your mixes by the end of the month!

So, with that all said, here's the rotation for March, mixes due by MARCH 31!!!!!!

Vic ---> Rob

Farrell --> Jacob

Nate ---->  James

Brad ---> Nate

Trav ---> Marcus

Tree ---> Farrell

JB ----> Vic

Rob ---> Trav

Jacob ---> JB

James ---> Brad

Marcus ---> Tree

Ready....GO!!!

1. Kita mulai dari Mixin'...
ketika kita mulai merekam instrumen...yang terlintas di benak kita adalah hasil mixin' harus sebisa mungkin mendekati dengan suara yang kita rekam...
dan mulai mengembangkan teknik agar dapat mencai hasil rekaman dengan pure yang baik...
teknik mixin'pun mulai berkembang...karena mixin' adalah perpaduan seni dan presisi dan kitapun dituntut untuk kreatif dan mampu bereksperimen...
yupz...dan ini adalah bidang khusus bagi seseorang yang digelari Sound Engineerin'...Wikwiw...^_^
Punya dana yang minim...?g usah sedih...sekarang kan dah masuk era digital...dan kita bisa melatihnya cukup dengan memiliki pc yang memadai untuk multimedia ( Kalo g pnya pinjem yg temen :) ) dan menggunakan software2 pembuat instrumen seperti fruity loop, Dll...

1 1/2. Hal pertama yang harus kita perhatikan adalah dimensi ( Kalo kata si Om Pam2 'Ngeruang' :> )...
pada dasarnya mixin' adalah sebuah proses penyesuaian ( Kalo Kata Keren'y Adjustment ) elemen2 pada keseluruhan komposisi musik...
Hasil akhir dari penyesuaian sendiri adalah diperolehnya hasil rekaman yang betul2 semirip mungkin dengan apa yang kita rekam...
dengan artian hasil rekaman tersaji dalam suatu ruang 3 dimensi...
dan seorang professional menyebutnya dengan istilah stagin' ( Stage Image ) yang mantap dan proposional...
kunci agar kita dapat mencapai hasil berdimensi ( 3 dimensi ) dalam melakukan mixin' adalah sisi kanan dan kiri ( Panning ) dan tersaji dalam bidang datar...
Untuk mencapai imej ini...kita dapat memanipulasi panpot ( Panorama Potensio )...
Sedangkan kedalaman ruang dimensi...bisa diperoleh melalui manipulasi gain atau level parameter dan juga besaran respon bunyi terhadap struktur ruang atau biasa di kenal dengan Reverb...
Proses mixin' secara keseluruhan bisa terbagi dalam dua tahap...Yaitu tahap rekaman dan tahap editing...
Dan tentu saja selalu diakhiri dengan sentuhan akhir ( Finishin' Touch )...
Jika Kita ( Musisi ) yang ingin melakukan mixing...hal pertama yang harus Kita sadari adalah bahwa kita mungkin sekali membutuhkan orang ketiga ( Teman, Sound Engineer atau juga produser )...
Dan Kita harus mengerti sepenuhnya bahwa mixing bukanlah proses yang instan...Mixing adalah sebuah seni mengolah bunyi yang kadang bisa sangat melelahkan dan menjemukan bahkan dapat membuat FRUSTASI...
Untuk Itulah...Langkah pertama yang harus kita ambil agar lebih teliti adalah menuangkannya dalam bentuk Score melalui notasi musik...

To Be Continued

Video by: scobleizer

This is a social calendar demo that hooks to Twitte thought of sharing with the rest of class MixIn

Z

This time I got a demo and met the development team for MixIn, which is a social calendar that hooks to Twitter. On Qik I got a good demo.

Wuala - "the skype of online storage". Simple, neat. Watch these guys.

Mixin - a really exciting new way to organise your (online) social life. Gra is going to love it. Destined to be very popular with the Twitter/Dopplr/Upcoming... possibly even the Facebook set. Can't wait to try it out with the Brighton/London folk. Well mashed and stirred. "Social applications have a long way to go, currently in their infancy and strangely disappointing." Mixin is meant to take things on to the next level. Let's see how it goes. "Helping you digest the noise". Scoble is rawther juiced up about the whole thing. Rightly so.

Pixelux - interactive physical simulation technology.... brand/media experience channels, multi-sensory. Takes the stuff we have seen in conceptual art spaces forward into super slick stuff that the retail marketing folk will clamour for. It will be in our face, seducing us to buy buy buy before you can shake a mouse at it. But beautiful, beautiful stuff. Will be good to see what the cultural and heritage sector can do with it. LCD, Plasma screen, projection on to floors.

Cocomment - "Helping you track your conversations on the web." You know how we struggle to manage our conversations in the blogsophere? Well here's a great free tool that really helps. Let's all get on and give a go... Enhances conversations, helps you track what you said and who said what to whom. The speed has improved a lot recently. More work to be done on the useability we hear from early adopters (eg. Scoble). Another social networkto maintain though? I'll let you know...

clipperz - "think of it as a web rollodex"... "free and anonymous online password manager"

and more to come.

Downloading Wuala closed alpha trial right now, just registered for cocomment. Love it. Love seeing the response from the expert, whizzbang panel, asking all the tricky questions that Gra would be thinking and asking if he was here. Sniff.

So far every venture that's been chosen is fantastic. Really enjoying being in at the ground level with "The New".

Somewhat ashamed to have posted the question about "where else if not Venture night..." on the LIFT community blog.

Battery just about dead, brain full, drinks are calling... out the door right now...

Le concept c'est du microblog sans login, depuis une page centrale.

A tester sans crainte ça ne vous rendra pas addict.

So consider the following code:

module BarModule
  def hello_world
    puts "Hello World"
  end
end

class BaseClass
  def class_method
    puts "In class method"
  end
end

class Foo < BaseClass
  include BarModule
end

f = Foo.new
f.class_method
f.hello_world

In this example, we are creating a module named BarModule with a hello_world method, a class named BaseClass, and then another class Foo that extends BaseClass and includes BarModule. The class Foo will then have both the methods from BarModule and BaseClass, but it will only BE an instance of BaseClass as that is its only parent. Somewhat different than what a Java developer would do, but it makes sense. Running this file will result in the following output:

$ ruby foo.rb
In class method
Hello World
$