@justinbmeyer a electron gulp task can look like this: https://github.com/pYr0x/testapp/blob/master/gulpfile.js . this app works with electron on windows. how can we make this gulp task more doneJS-like? if you want we can talk about. let me know
Does CanJS support
{{#if [helper] arg1 arg2}}
It supports {{#helper arg1 arg2}}
thanks
Where helper implements the if by calling options.fn and options.inverse
For the if/else blocks respectively
Check out mustache_helpers.is for examples
.js *
you can also do
{{#if helper(arg1, arg2)}}
depending on what your helper does, it might simplify it to use a call expression
Helper is a viewmodel method in that example, isn't it?
I haven't used the 2.3 syntax yet
it doesn’t need to be
it will look at the viewmodel and then the helpers
in stache how do I check the condition xxx > yyy?
when does it make sense to add a function to the viewModel versus as a helper?
it’s much easier to unit test functions or properties on the viewModel
I only use helpers if I have no other option
that’s basically my approach also
or for global things like language translation or different formatters
thanks, what about the other question? xxx > yyy in stache
you’ll have to use a function
would it make more sense to use mustache or ejs for complex templates? are those available as options?
I would use can.stache
it has a lot of performance benefits and other features compared to mustache
ejs is depracated
and can’t be used with components
any plans on expanding stache to include #gt, #lt, etc.?
not that I know of
definitely feel free to open an issue to request it
Thanks. In fact if you point me to the code, I could create a PR.
This message was deleted
This message was deleted
so what is the problem?
I was just in the process of deleting the message
I have figured it out
Thanks
I am building Map’s with defines
I am liking what is provided here
How do I specify an array of Types?
like a single property that can have multiple types?
no, something like
xxx: [ Person, Person]
so you want a property on a Map that is a list where each entry is a Person?
yes - your question probably explained the answer -
can.List.extend({ define: person: {Type:Person}})
something like that, yeah
thanks
the define plugin isn’t 100% supported on can.List
Type: Person.List
@gsmeets that isn’t working either
when I use
{{person[0].status}} I am getting [object Object]
that was the same result as what I typed earlier
does
{{#each person}}
{{status}}
{{/each}}
show the same thing?
that works with Type: Person.List
that’s good enough to keep me going, but how would I reference
person[0]?
you can either do something like add a
first property to your list or a firstPerson property to your map
actually… does
{{person.0}} work?
it does
thanks
sure
is there a type for Function?
other questions: I have an array of strings - how do I represent that in a Map? How do I show one or more values in stache?
For the Map I have tried String.List, that seems to be okay
Make it a can.List
Once it is a can.List - how do I show the items?
{{#each myList}}
<p>{{.}}</p>
{{/each}}
thanks
. means current context, which would be the string if it’s an array of strings
Thank-you. BTW String.List worked in my Map.define
Do not use String.List
Messing w/ native prototypes is taboo
okay, what should I use in my Map.define
{
define: {
myList: {
value: Array
}
}
}
I always use value: Array/Object, and combine that w/ Type unless it’s a can.List/can.Map, which is implicit
@RALifeCoach just so you know, you don’t need to always set the Type
how would define know whether it is an array of numbers or strings?
it doesn’t need to know
define’s really just used for fine-grain control of properties on maps
While I agree I don’t always need to set the type, good practice suggests that the more information I provide, the better
I generally try to avoid string lists tbh
I think about half the places where I used it I had to add some property besides the string at some point in the lifetime of that functionality
and then I had to convert it to a Map.List anyways
Unfortuneately, this is legacy code and I don’t have the option to make those kinds of changes
always go with what works ;)
I'm in the process in converting a whole slew of legacy code as well
one spec at a time ;)