setting date field to readonly doesn't work

[lmueller74]

I'm trying to make my datepicker field readonly and that attribute in the schema seems to be ignored. any ideas?

[davidlgj]

Oh, it's the template that needs an ng-disabled https://github.com/Textalk/angular-schema-form-datepicker/blob/master/src/datepicker.html#L8

[lmueller74]

i guess i still don't see how to do that within the framework of angular-schema-form - is there a straightforward way, or is this like a post-processing step?

[Dervisevic]

It's not done within the framework. The template needs to be edited. The input needs a ng-disabled like this one here https://github.com/Textalk/angular-schema-form/blob/development/src/directives/decorators/bootstrap/default.html

On Wed, May 27, 2015 at 4:44 PM, lmueller74 notifications@github.com
wrote:

i guess i still don't see how to do that within the framework of angular-schema-form - is there a straightforward way, or is this like a post-processing step?

Reply to this email directly or view it on GitHub:
#25 (comment)

[lmueller74]

I see - wasnt there on first link, but i get it now.

On Wednesday, May 27, 2015, Denis Dervisevic notifications@github.com
wrote:

It's not done within the framework. The template needs to be edited. The
input needs a ng-disabled like this one here
https://github.com/Textalk/angular-schema-form/blob/development/src/directives/decorators/bootstrap/default.html

On Wed, May 27, 2015 at 4:44 PM, lmueller74 <notifications@github.com
javascript:_e(%7B%7D,'cvml','notifications@github.com');>
wrote:

i guess i still don't see how to do that within the framework of
angular-schema-form - is there a straightforward way, or is this like a

post-processing step?

Reply to this email directly or view it on GitHub:

#25 (comment)

—
Reply to this email directly or view it on GitHub
#25 (comment)
.

[davidlgj]

Sorry @lmueller74 I could have been a lot more clearer! The problem is basically that the datepicker doesn't implement it yet, but it's probably just a ng-diasabled that needs to be added to the datepickers template.

Look at the template @Dervisevic linked to. Afterwards there is a build step, first npm install (if you haven't done it) and then invoke the default task of gulpfile.js with gulp (or node_modules/gulp/bin/gulp.js if you don't have gulp installed)

If you do this please consider making a PR (just don't include the minified files in the commits)

[lmueller74]

i'm actually working within MS VS 2013 - so i'm currently referencing
everything on CDN... I will get around to installing everything locally -
it's just a bit of a pain with VS in my experience....all the bower and npm
installs instead of NuGet

On Wed, May 27, 2015 at 2:51 PM, David Jensen notifications@github.com
wrote:

Sorry @lmueller74 https://github.com/lmueller74 I could have been a lot
more clearer! The problem is basically that the datepicker doesn't
implement it yet, but it's probably just a ng-diasabled that needs to be
added to the datepickers template.

Look at the template @Dervisevic https://github.com/Dervisevic linked
to. Afterwards there is a build step, first npm install (if you haven't
done it) and then invoke the default task of gulpfile.js with gulp (or
node_modules/gulp/bin/gulp.js if you don't have gulp installed)

If you do this please consider making a PR (just don't include the
minified files in the commits)

—
Reply to this email directly or view it on GitHub
#25 (comment)
.

[davidlgj]

@lmueller74 I felt a bit sorry for you :) I think it's fixed with the latest release (0.4.0) please try it out.

[lmueller74]

Awesome - thanks!

On Thu, May 28, 2015 at 9:45 AM, David Jensen notifications@github.com
wrote:

@lmueller74 https://github.com/lmueller74 I felt a bit sorry for you :)
I think it's fixed with the latest release (0.4.0) please try it out.

—
Reply to this email directly or view it on GitHub
#25 (comment)
.