function readOnly(count){ }
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
+ Start a Discussion
sfdc startsfdc start 

vf page question

1.  i want to pass the value from vf page to custom component....how? and  what the tag..?plz give eample and explanation
2.what is salesforce1 and what the use..
Best Answer chosen by sfdc start
Amit Chaudhary 8Amit Chaudhary 8
1.  i want to pass the value from vf page to custom component....how? and  what the tag..?plz give eample and explanation

The easiest way is to pass in the controller of your visualforce page. This means you'll need either a custom controller or an extension. When you pass in the controller, you can then call getters or setters on the controller given they are publicly accessible.
<apex:component>
    <apex:attribute name="ctrl" description="My controller" type="MyControllerClassName" required="true"/>
    <apex:image value="{!URLFOR(ctrl.ImageUrlGetter)}"> </apex:image>
</apex:component>
https://developer.salesforce.com/forums/?id=906F000000096c6IAA


2.what is salesforce1 and what the use..

Salesforce1 is a new platform, complete with a host of new APIs and mobile UI tools.
To oversimplify it, it's taking the Chatter mobile app, which up until this point has just been an app running on closed source code and building it into a platform, while really blowing out its capabilities. It's built on the premise that our business lives are increasingly happening in the feed. Every action from a like to a comment, now has a public API and method call behind it. More than just Chatter however, it's allows you to embed your business applications either through Visualforce or custom publisher actions (with you app hosted wherever). Salesforce1 will offer custom branding, administrator configuration, and allow for installable apps. 3rd party sales tools, service tools, marketing apps will be able to plug right into this framework.
More than just mobile, while it is the focus, Salesforce1 represents a new API-first mentality at Salesforce.com. Every action, interface, and new feature is built on top of a public API that developers can also wield and consume. Think about a list view in Salesforce, it's not something you can build without some pretty deep customization and code of your own. This UI component is not built on a public API. This is the old paradigm of Salesforce.com and Salesforce1 is the new one.
Worth referencing here is the Salesforce1 App Developer Guide and a full listing of Salesforce1 APIs
1) https://developer.salesforce.com/docs/atlas.en-us.186.0.salesforce1.meta/salesforce1/salesforce1_guide_introduction.htm
2) https://developer.salesforce.com/docs/atlas.en-us.186.0.salesforce1api.meta/salesforce1api/salesforce1_api_preface.htm


Some usefull link
1) http://blogs.forrester.com/john_r_rymer/13-11-26-what_is_salesforce1_anyway
http://www.salesforce.com/company/news-press/press-releases/2013/11/131119.jsp

All Answers

Amit Chaudhary 8Amit Chaudhary 8
1.  i want to pass the value from vf page to custom component....how? and  what the tag..?plz give eample and explanation

The easiest way is to pass in the controller of your visualforce page. This means you'll need either a custom controller or an extension. When you pass in the controller, you can then call getters or setters on the controller given they are publicly accessible.
<apex:component>
    <apex:attribute name="ctrl" description="My controller" type="MyControllerClassName" required="true"/>
    <apex:image value="{!URLFOR(ctrl.ImageUrlGetter)}"> </apex:image>
</apex:component>
https://developer.salesforce.com/forums/?id=906F000000096c6IAA


2.what is salesforce1 and what the use..

Salesforce1 is a new platform, complete with a host of new APIs and mobile UI tools.
To oversimplify it, it's taking the Chatter mobile app, which up until this point has just been an app running on closed source code and building it into a platform, while really blowing out its capabilities. It's built on the premise that our business lives are increasingly happening in the feed. Every action from a like to a comment, now has a public API and method call behind it. More than just Chatter however, it's allows you to embed your business applications either through Visualforce or custom publisher actions (with you app hosted wherever). Salesforce1 will offer custom branding, administrator configuration, and allow for installable apps. 3rd party sales tools, service tools, marketing apps will be able to plug right into this framework.
More than just mobile, while it is the focus, Salesforce1 represents a new API-first mentality at Salesforce.com. Every action, interface, and new feature is built on top of a public API that developers can also wield and consume. Think about a list view in Salesforce, it's not something you can build without some pretty deep customization and code of your own. This UI component is not built on a public API. This is the old paradigm of Salesforce.com and Salesforce1 is the new one.
Worth referencing here is the Salesforce1 App Developer Guide and a full listing of Salesforce1 APIs
1) https://developer.salesforce.com/docs/atlas.en-us.186.0.salesforce1.meta/salesforce1/salesforce1_guide_introduction.htm
2) https://developer.salesforce.com/docs/atlas.en-us.186.0.salesforce1api.meta/salesforce1api/salesforce1_api_preface.htm


Some usefull link
1) http://blogs.forrester.com/john_r_rymer/13-11-26-what_is_salesforce1_anyway
http://www.salesforce.com/company/news-press/press-releases/2013/11/131119.jsp
This was selected as the best answer
seriale onlineseriale online
More than just Chatter however, it's allows you to embed your business applications either through Visualforce or custom publisher actions (with you app hosted wherever). Salesforce1 will offer custom branding, administrator configuration, and allow for installable apps. 3rd party sales tools, service tools, marketing apps will be able to plug right into this framework.
More than just mobile, while it is the focus, Salesforce1 represents a new API-first mentality at Salesforce.com. Every action, interface, and new feature is built on top of a public API that developers can also wield and consume. Think about a list view in Salesforce, it's not something you can build without some pretty deep customization and code of your own. This UI component is not built on a public API. 
Some link listed below if you need
https://lsresult.in/