[FLOW3-general] Rumours of Phoenix dropping ExtJS?

Thomas Allmer at at delusionworld.com
Mon Oct 10 15:36:35 CEST 2011


On 10.10.2011 10:02, "Christian Müller (Kitsunet)" wrote:
> Additionally there is the proverb of "making the experience yourself",
> sometimes that is just needed to gain certain insights...

indeed correct, but making all the experience yourself might take quite 
a while :p

> And finally please share your experiences with us and join the team. If
> you feel you had known it from the beginning, don't wait, we are
> searching for devs all the time, just help us out and bring your
> experience in.

I thought that I tried that already but then again yeah sure what do you 
want to know? maybe just contact me on irc in #flow3 my user there is 
"daKmoR" :)

> [...]I know clientcide a bit and it is really nice. Sproutcore doesn't do it
> that way, but I think that is good for certain parts. Look at our code
> and you see there are parts that use enhancement and some that rely on
> the javascript, but that is (in my opinion) needed for our editing
> experience. We need a model to keep track of content properties and
> changes to the content, it all gets very complex fast if you want to mix
> Aloha with non Aloha content add in autosaving (to local storage and
> server) and properties that cannot be edited in the page itself (like
> hidden, image position and so on). I doubt that is possible without
> having a javascript model of your content.[...]

I just hope the the javascript will be easy to use... and I can tell you 
that so far I haven't found anything more easy to use than Javascript 
Behaviors... I'm talking here about people using the framework not 
building it...

1) just a really really simple example...
- I have an input to show the startdate
<input type="text" name="start" />
- now I want it to have a datepicker
<input type="text" name="start" data-behavior="DatePicker" />
- different style?
<input type="text" name="start" data-behavior="DatePicker" 
data-datepicker-options="{pickerClass: 'datepicker_vista'}" />
OR
<input type="text" name="start" data-behavior="DatePicker" 
data-datepicker-pickerClass="datepicker_vista" />

2) or something more complex?
- heading
<h3>my power page</h3>
- make it inline editable with Aloha
<h3 data-behavior="Aloha">my power page</h3>
- don't allow images or multiline?
<h3 data-behavior="Aloha" data-aloha-options="disallowTag: 'img', 
multiline: false">my power page</h3>

so that's about it...
it should be as simple as that for users...
I mean the PHP is so freaking awesome with dependency injection and 
fluid and all... just freaking awesome!! - why the hell is the 
javascript so complicated to use... :p

3) and finally edit a tt_content heading with ajax saving on typing-stop
<h3 data-behavior="Aloha" data-aloha-maptoInput=".pageName" 
data-aloha-finishSubmit=".contentForm">my page name</h3>
<form class="contentForm" data-behavior="ajax">
   <input type="text" value="oldpagename" class="pageName" />
   [...] all the field you can probably edit
</form>

as you can see it's just defining some stuff inside html5 data-*. I 
don't have to write any javascript at all to use that stuff... yeah sure 
someone has to write it but as a user I don't care how and in what 
framework that javascript is written...

it also enable you to completely change the javascript without changing 
any non javascript code... us sure will have to write adapters to what 
behavior does what but it's like with css... all the data is in the html 
and you can completely change how it looks (with css) and behaves (with 
javascript) without actually changing any data (in html)

maybe this gives you some nice ideas :)
and I now leave you with some nice examples of behaviors
http://anutron.github.com/mootools-bootstrap/

PS: I actually don't use aloha for my inline editing stuff but it could 
sure be archived.

-- 
+---------------------------------+-----------------------------------+
| Thomas Allmer                   |   http://www.delusionworld.com    |
| E-mail: at at delusionworld.com    |   phone: +43 699 16217064         |
+---------------------------------+-----------------------------------+


More information about the FLOW3-general mailing list