What's should 2.0 look like?

[ckirkendall]

Now that 1.0 release is out the door, I would like to discuss where we take Enfocus from here.  I am very interested in hearing from those using Enfocus and other tools.  I have put a list together of some  things I have heard and thought over the last year.

• Pure ClojureScript selector engine - This is no small task but, with macro expansion, we have the potential for some significant speed improvements.
• Remove macro shadows - Most of the transforms are just functions but for a lot of reasons I choose to shadow everything in enfocus.macros. This has caused issues when people wanted to compose things. In 2.0 I would like to move away from this completely.
• Optimization of compiled templates - This will probably require us to integrate with Enlive more closely and add string selectors to Enlive.
• UI widget transforms - In much the way the JQuery UI exists to provide basic UI components for JQuery,  I would like to see an Enfocus UI project.  Components would include things like tabs, accordion  and data tables.   
  

Creighton Kirkendall

[Gary Johnson]

+1 for removing the macro shadows and a tighter integration with Enlive. Incidentally, I seem to remember you commenting in another thread awhile back that Enlive had (undocumented) support for some Enlive selectors already. Is there a reference posted online somewhere of what this subset contains?

Also, perhaps we could look for a shorter syntax for getting the values of forms, a la SeeSaw's behavior for getting all values in a form as a map.

  My 2c,
    ~Gary

[Creighton Kirkendall]

Gary,

Enfocus does support most the base selector syntax of enlive (i.e. [:td.class1 :> :span]).  I have not promoted it because the support is limited to what I can support via css3 selectors and I didn't want to confuse people.   I can probably come up with wiki page on what is supported and what is not.

I like the idea of simple syntax that grabs all the form data as a map.   I don't think this would be hard.  I will take a look at SeeSaw's syntax for this and see what I can come up with.

CK

--
 
---
You received this message because you are subscribed to the Google Groups "Enfocus" group.
To unsubscribe from this group and stop receiving emails from it, send an email to enfocus+u...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Gary Johnson]

Great! Thanks for being so responsive, Creighton. Enlive has been a great tool to work with, and your example site was invaluable in demonstrating working examples for me when I was first trying to learn it last year. Keep up the good work!

  ~Gary

[Alan Moore]

Let me introduce myself, my name is Alan Moore and I'm a software engineer working out of Grass Valley, CA. My day job involves building web interfaces for embedded systems (video/audio.) While we do not deploy java on the server side (C++ primarily) we do use javascript very heavily on the client.

In addition, I have personal interest in developing clojure/script based UIs for a pet project I am working on ;-)

inline...

I am interested in and I can help with the UI Widget effort - let me know the best way to contribute. Who else is interested in this aspect of enfocus?

Thank you for your hard work on enfocus!

Alan Moore

[ckirkendall]

Alan,

I would love any and all help you can provide.  The basic idea is similar to JQuery UI: http://jqueryui.com/themeroller/.  We need to recreate the basic widget set on this page in enfocus.  There are two possible approaches we can take;  One is reuse as much of the artifacts such as images and css from jquery to make this work and reimplement them in clojurescript, or Two we can create transforms that expose the built in components of goog.ui.  

I plan on creating a github project for enfocus-ui that will hold the widget transforms.  In this project new widgets will start out under a sandbox area where we can try out different designs for widget and then once a stable design is found we promote the widget to main stage.

CK  

[ckirkendall]

Alan,

If you are interested in looking at what goog.ui has to offer go to: http://docs.closure-library.googlecode.com/git/index.html and click on the demo tab on the right.  It a much more complete list than JQuery.

CK

[ckirkendall]

All,

I uploaded the first installment of 2.0.0-SNAPSHOT.  The only change in this file over the 1.0.1 release is the removal of macro shadowing.  All transforms are now located in enfocus.core namespace with the exception of clone-for.  It requires a macro so it stayed in enfocus.macros.

CK

On Saturday, March 2, 2013 12:54:10 PM UTC-5, ckirkendall wrote: